Short answer: Most "where is my order" tickets can be cut by fixing the basics first: add tracking to every order quickly, send a delay notice before the customer notices, and point people to a working order status page. For the emails and chats that still arrive, an AI assistant can read the message, find the order, check live tracking and reply with the real status in seconds, while anything unusual (stalled parcels, "delivered but not here", address changes) goes to a person.
The problem
If you run an online shop, you know this ticket. "Hi, I ordered last Tuesday, where is it?" Sometimes with an order number, often without. Sometimes the parcel is moving fine and the customer just wants reassurance. Sometimes it has sat in a depot for six days and nobody on your side has noticed.
Operators describe the same pattern again and again. In an r/ecommerce thread about post-purchase operations, the original poster said most teams only find out about problems when customers ask where their order is, and then support and ops scramble. The replies were practical: one accurate place for order and fulfilment status, proactive messages at each stage, and alerts for orders stuck in picking or parcels with no carrier scan.
A long-running Shopify Community thread makes the same point from the other side. A merchant had to open every order one at a time to see its delivery status, and only learned about lost parcels when frustrated customers phoned. Other merchants mentioned chargebacks. The thread began in 2020 and was still active in 2026.
What it costs
You will see confident figures online claiming WISMO is 30% to 50% of all ecommerce support contacts. Be careful with them. A September 2026 review by a support software vendor looked for a primary source and could not find one: the much-repeated 40% figure traces back to a blog post quoting Forrester, and it only referred to peak season. The honest answer is that your own tagged tickets are the only number that matters.
The costs are real even without a headline statistic:
- Agent time spent looking up orders in two or three systems and pasting a tracking link.
- Chargebacks and "item not received" disputes when a lost parcel is found too late.
- Repeat contacts, because a customer who gets no answer within a day tends to write again on another channel.
- Legal exposure if orders are late and nobody tells the customer (more on that below).
Why it keeps happening
Order data is split across systems: the shop platform, the warehouse or 3PL, and the carrier. Support staff stitch these together by hand for every ticket.
Tracking is often missing or late. Shopify's own documentation notes that if an order is fulfilled without a tracking number, its order status page stays on "Confirmed", and for unsupported carriers the page only shows a tracking number linking out to the carrier, with no live status. Customers who see "Confirmed" five days after ordering will write in.
Nobody watches for stalled shipments. Carriers report exceptions, but someone has to look. In a small team that someone is usually the person who is also answering the tickets.
There is also a legal angle that many small shops overlook. In the US, the FTC's Mail, Internet or Telephone Order Merchandise Rule says you must have a reasonable basis for any shipping time you state, should expect to ship within 30 days if you state none, and must tell customers about a delay and offer them the option to cancel for a prompt refund. In the UK, section 28 of the Consumer Rights Act 2015 requires goods to be delivered without undue delay and within 30 days unless another time is agreed, and gives the customer the right to end the contract in some late delivery cases. A WISMO ticket is often the first sign that one of those clocks is running. This is general information, not legal advice.
How AI solves it
The useful setup has two halves. Proactive automation stops many tickets from being written. An AI assistant then handles the ones that still arrive. Do the first half before spending anything on the second.
Part one: stop tickets before they start
- Make sure every fulfilled order gets a tracking number automatically from your shipping tool, and that the shipping confirmation email includes the order status link.
- Run a daily check (Shopify Flow, n8n or a small script) for orders unfulfilled longer than your promised dispatch time, and parcels with no carrier scan for a set number of days.
- Send a short delay notice automatically when either check fires. Give a new expected date and, where the law requires it, a simple way to cancel.
- Put the flagged orders in a daily list for a person to chase with the warehouse or carrier.
Shopify Flow is free on Basic, Grow, Advanced and Plus plans, though its Send HTTP Request action (needed to call outside services such as a carrier API) is only on Grow and above. None of this part needs AI. It is plain rules, and it should be.
Part two: answer the tickets that still arrive
- A customer emails, chats or sends a WhatsApp message. The language model reads it and decides what it is: a status question, a delay complaint, "delivered but not received", an address change, a cancellation request, or something else.
- The model pulls out identifiers: order number, email address, name, postcode. If there is no order number, the system looks up recent orders for the sender's email.
- Plain integration code fetches the order from the shop platform and the latest tracking events from the carrier or your tracking tool. The model does not guess at any of this.
- Rules decide the route. If the parcel is moving and within the promised window, the assistant replies. If it is stalled, marked delivered but disputed, going to the wrong address, or high value, it hands over to a person.
- For the straightforward cases, the model writes a short reply in your tone using only the facts returned in step 3: where the parcel is, the expected date, and the tracking link.
- Every reply and handover is logged against the order, so the team can see what the customer was told.
Off-the-shelf helpdesks already do a version of this. Gorgias, for example, added an AI Agent action in March 2025 that pulls shipment data from a tracking platform to answer WISMO questions. If you use one of these tools and your setup is standard, try its built-in option first.
Where the LLM helps and where rules are better
| Step | Best tool | Why |
|---|---|---|
| Understanding a messy message | LLM | Customers ask the same question many ways, in many languages |
| Finding the order number or email | LLM, then a lookup | Extraction is easy for a model; the lookup must be exact |
| Fetching order and tracking status | Plain API integration | Facts must come from the source system |
| Deciding to reply or escalate | Rules | Thresholds like "no scan for 4 days" should be fixed and auditable |
| Writing the reply | LLM, from the fetched facts only | Saves agent time and keeps the tone consistent |
| Refunds, reships, cancellations | Person | Money and goodwill decisions stay with your team |
| Delay notices | Plain automation | Same message, triggered by a rule, every time |
The design principle is simple. The model reads and writes language. It never invents a delivery date, never promises a refund, and never closes a "delivered but not received" claim on its own.
Costs and timeline
These are estimates. The assumptions are written out so you can replace them with your own numbers.
Time saved (estimate)
Assume a shop sending 4,000 orders a month, where 5% of orders lead to a status question. That is 200 tickets. At 4 minutes each to find the order, check the carrier and reply, that is about 13 hours of agent time a month. If the assistant fully handles 70% of them and the rest go to a person with the order and tracking already attached (say 2 minutes each), the monthly total drops to roughly 2 hours. In peak season, both the ticket count and the saving can be several times higher. Check your own contact rate per order before trusting any of this.
Running cost (estimate)
Model usage is the small part. Assume each ticket uses about 4,000 input tokens (the message, order data and tracking events) and 400 output tokens. At Anthropic's published Haiku 5.5 rate of $0.10 per million input tokens and $0.50 per million output tokens for prompts under 100K tokens, 200 tickets would cost about $0.12 a month. Even a larger model such as Sonnet 5.5, at $2 and $10 per million, would come to under $3. Helpdesk subscriptions, tracking tools and hosting will cost far more than the model.
Build, buy or do nothing
| Option | Rough cost (estimate) | Time to live | Good fit when |
|---|---|---|---|
| Do nothing | Agent hours, plus disputes on missed parcels | None | Under a handful of status questions a day |
| Fix the basics only | Mostly staff time to configure | Days | Tracking or delay notices are currently patchy |
| Buy: AI feature in your helpdesk or tracking app | Monthly subscription, often priced per resolution or per order | 1 to 3 weeks | One shop platform, mainstream carriers, standard policies |
| Build: custom agent connected to your systems | A few weeks of build, then hosting and model costs | 4 to 8 weeks for a first version | Several sales channels, a 3PL or ERP in the middle, B2B accounts, several languages or unusual rules |
A custom build tends to pay off when order data lives in more than one place, for example a Shopify store plus Amazon plus wholesale orders in an ERP, all shipped by a 3PL with its own portal. Off-the-shelf tools usually assume one shop platform as the source of truth.
When not to use AI
If you get a few status questions a day, fix the shipping confirmation emails, add the order status link and send delay notices. That alone may be enough, and it costs nothing extra.
If the real problem is that orders leave the warehouse late, an AI reply only makes the bad news arrive faster. Fix dispatch first.
Don't let the assistant handle "delivered but not received" claims, fraud checks, refunds or reships on its own. Those need judgement and access to money, and they are where chargebacks start.
Be careful with B2B customers who have account managers. A polite automated reply to a key account chasing a late pallet can do more harm than good. Route those to the named person.
How to start
- Export the last three months of tickets and tag each one: status question, delay, delivered but not received, address change, other.
- Work out your contact rate: status tickets divided by orders shipped. Check it separately for peak season.
- Check that every fulfilled order has a tracking number and that shipping emails include the order status link.
- Set up a daily rule for unshipped and stalled orders, with an automatic delay notice that fits the FTC rule or UK consumer law where you sell.
- Try the WISMO feature in your current helpdesk before considering a custom build.
- If your data is spread across several channels, a 3PL or an ERP, map where each fact (order, pick status, tracking) lives before choosing a tool.
Our AI workflow automation service builds this kind of order status assistant, with the integrations, escalation rules and logging connected to the systems you already use. For background, see our guides on what an AI chatbot costs to build and the difference between AI agents and chatbots.
FAQ
What does WISMO mean in ecommerce?
WISMO stands for "where is my order". It covers any customer contact asking about the status of an order or delivery, whether by email, chat, phone or social media. Many shops tag these tickets separately so they can measure how many they get per order shipped.
How do I reduce "where is my order" emails?
Start with proactive communication: send tracking with every shipping confirmation, link to a live order status page, and send a delay notice as soon as an order or parcel stalls. Then automate replies to the tickets that still arrive, using a system that looks up the real order and tracking data before answering.
Can AI answer order status questions automatically?
Yes, if it is connected to your shop platform and carrier tracking. The AI reads the message, finds the order, fetches live tracking and writes a reply based only on that data. Exceptions such as stalled parcels, disputed deliveries and refund requests should go to a person.
What percentage of ecommerce support tickets are WISMO?
There is no reliable industry-wide figure. Vendor articles commonly quote 30% to 50%, but at least one vendor review in 2026 could not trace those numbers to a primary study, and the often-quoted 40% referred to peak season only. Measure your own share from tagged tickets.
Do I have to tell customers if their order is delayed?
In the US, the FTC's Mail, Internet or Telephone Order Merchandise Rule requires sellers who can't ship on time to notify customers and give them the option to cancel for a refund. In the UK, the Consumer Rights Act 2015 sets a 30-day default delivery period and gives customers remedies for late delivery. Check the rules for each country you sell into, and take legal advice if unsure.
Does Shopify have built-in order tracking for customers?
Yes. Shopify's order status page shows shipment progress and, for supported carriers, live tracking updates. Customers reach it through the link in their confirmation and shipping emails. For unsupported carriers it only shows a tracking number that links to the carrier's site.
Sources
- r/ecommerce, "How do you actually move from reactive to proactive post-purchase e-comm ops?": https://reddit.com/r/ecommerce/comments/1psiprj/how_do_you_actually_move_from_reactive_to/
- Shopify Community, "Looking for a way to see delivery status without having to click on each order": https://community.shopify.com/t/looking-for-a-way-to-see-delivery-status-without-having-to-click-on-each-order/18276
- Macha, "Ecommerce customer service statistics" (September 2026): https://www.getmacha.com/blog/ecommerce-customer-service-statistics
- Shopify Help Center, "About order status pages": https://help.shopify.com/en/manual/orders/status-tracking/order-status-overview
- Shopify Help Center, "Shopify Flow": https://help.shopify.com/en/manual/shopify-flow
- US Federal Trade Commission, "Business guide to the FTC's Mail, Internet, or Telephone Order Merchandise Rule": https://www.ftc.gov/business-guidance/resources/business-guide-ftcs-mail-internet-or-telephone-order-merchandise-rule
- legislation.gov.uk, Consumer Rights Act 2015, section 28: https://www.legislation.gov.uk/ukpga/2015/15/section/28
- Gorgias product update, "New AI Agent action for Wonderment" (March 2025): https://updates.gorgias.com/publications/new-ai-agent-action-for-wonderment-smarter-wismo-responses
- Claude API pricing: https://claude.com/pricing
If you'd like to talk through where your order status questions come from and whether automating them would pay off, get in touch at https://sintraflow.com/contact.
