How to automate "where is my order?" questions with a chatbot

In short: Automating "where is my order?" questions means connecting a chatbot to your order system, asking the customer for an order number and a second detail to verify them, and explaining the current status in plain language. Puhera does this with native order lookup and customer verification for T-Soft and e-commerce integrations for Shopify and WooCommerce, and passes unresolved cases to a live agent or a ticket.

Why are "where is my order?" questions so well suited to automation?

In e-commerce, order status questions, often shortened to WISMO ("where is my order?"), are among the most repetitive requests a support team receives. The question nearly always follows the same pattern, and the answer already sits in your order system: processing, shipped, delivered.

Answering each one by hand takes agent time and keeps customers waiting, especially after hours or during big promotions. A well-configured chatbot can give the same information instantly, at any hour. Your agents can then focus on what genuinely needs a person: returns, damaged items and special requests.

What information should the chatbot collect?

The goal of an order lookup is to find the right order in as few steps as possible. These details are usually enough:

• Order number: the most direct way to locate an order. It helps when the bot reminds the customer where to find it, such as the confirmation email or account page.
• Email address or phone number: a second detail used to confirm the order belongs to the person asking.
• Extra context if needed: which product or date they mean when there are several orders.

Asking for more than necessary frustrates customers and creates needless privacy risk. Request only what you need to find the order and verify its owner.

Why is customer verification essential?

Order data is personal data: it includes names, addresses, products and delivery details. If a system returns results from an order number alone, anyone who guesses a number can see someone else's information. Verification is what makes the automation safe.

A good verification flow follows a few principles:

1. No result is shown until the order number matches a second detail such as the email or phone on file.
2. When there is no match, the bot does not reveal which detail was wrong; it simply asks the customer to check their information.
3. The reply contains only what is needed: if status and shipping details are enough, the full address is not shown.
4. After repeated failed attempts, the conversation goes to an agent.

How do you connect an order system to a chatbot?

For a chatbot to "know" an order's status, it needs access to the system where orders live. That information is not written on a web page or in a PDF; it must be looked up live for each order. There are two general approaches:

• A native integration: the chatbot platform connects directly to the e-commerce platform and offers order lookup and customer verification as a built-in capability. Setup amounts to connecting the store and authorizing access.
• An integration through a protocol or connector: the chatbot reaches the store platform through a standard connection layer. MCP (Model Context Protocol), for example, is an open protocol that lets AI assistants connect to external tools and data sources.

Whichever route you take, limit what the bot is allowed to do. If a bot only needs to look up orders, it should not have permission to cancel them or change addresses.

What does a good order status reply look like?

Status codes in an order system are often meant for internal use. Labels like "invoiced" or "transferred to warehouse" mean little to a customer. The bot should translate them into plain language and say what happens next.

• Keep the status simple: one clear sentence, such as "Your order is being prepared and you'll be notified when it ships," is enough.
• Set expectations: sharing the general delivery time from your knowledge base stops the customer from asking again.
• Show the next step: share a tracking link if there is one; if not, say when it makes sense to check again.
• Anticipate the follow-up: for a delivered order, quick-reply buttons pointing to return terms make the next question easy.

Imagine a cosmetics store whose bot replies, "Your order shipped yesterday and usually arrives within a few business days. Would you like to see our return terms?" That short reply closes the question and opens the door to the likely next one.

What should happen when the bot can't answer?

Even the best automation cannot resolve every case. Shipping delays, lost parcels, damaged items or an order the system cannot find all need a human. What matters is that the customer never hits a dead end.

• Handoff to a live agent: the bot passes the conversation to an available agent. If the agent can see the bot conversation, the customer does not have to type the order number again.
• Ticket creation: if no agent is free or the issue needs investigation, the request becomes a ticket with a tracked status and priority.
• Collecting contact details: after hours, the bot can take an email address and promise a follow-up.

Define handoff rules in advance. Good starting points are an explicit request for a human, repeated failed verification, or words like "damaged" or "lost."

Order status automation checklist

1. Write a plain-language explanation of each order status you use: processing, shipped, delivered, return in progress.
2. Add general information such as delivery times and the return policy to the knowledge base; the bot uses it alongside order data.
3. Decide which second detail you will ask for during verification.
4. Make sure the bot works with read-only access where possible.
5. Set your handoff and ticket rules.
6. Test end to end with a real test order, then publish.

How does Puhera automate order status questions?

Puhera's order tracking chatbot offers native order lookup and customer verification for stores on T-Soft, and the T-Soft integration also covers catalog sync. Shopify and WooCommerce stores can use e-commerce integrations, which run over MCP connections, for product recommendations, order lookup and similar actions. For a worked example, read our T-Soft order lookup chatbot post.

On the visual automation canvas you can define actions that run when an intent or keyword is detected, such as showing quick-reply buttons, sending an email or connecting the conversation to a live agent. With live chat handoff, the agent sees the bot transcript before taking over, and visitors wait in a priority-ordered queue. On the Enterprise plan, you can create tickets from a conversation and track them by status, priority and assignee. We cover the details in chatbot to human handoff.

E-commerce integrations and live support handoff are included in the Pro and Enterprise plans. You can start a 7-day free trial to try it.

Frequently asked questions

Where does the chatbot get order status from?

Order status is looked up live from your store's order system. That is why the chatbot must be connected through an integration, such as T-Soft, Shopify or WooCommerce.

Is it safe to look up orders by order number alone?

Not on its own, because order numbers can be guessed. Verifying the order number against a second detail, such as an email address or phone number, is recommended.

What happens if the bot cannot find the order?

In a well-designed flow, the bot asks the customer to double-check their details; if the problem persists, it hands the conversation to a live agent or makes sure a ticket is created.