WISMO: How to Stop Drowning in 'Where Is My Order?' Tickets
Where-is-my-order tickets are the biggest, most automatable volume in ecommerce support.
If you run ecommerce support, one question outnumbers every other in your inbox, in more spellings than you can count: where is my order? WISMO — "where is my order" — is the largest single category of tickets for most stores, and it scales with revenue. Sell more, and you don't just get more orders; you get a flood of people asking where theirs is.
The cruel part is that WISMO is mostly self-inflicted. The customer is asking because they don't have the information, and they don't have it because you haven't given it to them yet. The way out of the flood isn't answering faster. It's making sure most of these questions never need to be asked.
WISMO is the biggest, most automatable volume you have
Start by sizing the problem honestly. For many ecommerce teams, order-status questions run 30–40% of all tickets, and they spike hardest exactly when you're busiest — promotions, holidays, peak. They're high volume, low joy, and they crowd out the conversations that actually need a person.
But WISMO has a property no other category does: the answer almost always already exists, in systems you already run. The order record knows what shipped. The carrier scan knows where it is. The fulfillment status knows what's late. There's no judgment call — just a lookup the customer can't do themselves. That combination of huge volume and a clear source of truth is what makes WISMO the single most automatable category in support.
A tracking link pasted into a reply is not an answer. The customer wanted reassurance, an ETA, and a next step — give them only the link and the "simple" ticket becomes a refund request.
Resolve it before the ticket opens
The biggest lever isn't a faster reply. It's a proactive update that beats the question. If a customer hears "shipped, arriving Thursday" the moment it happens, and "running a day late, new ETA Friday" the moment that changes, most of them never open a ticket at all.
Proactive status is the cheapest deflection you'll ever build, because it removes the reason to contact you rather than just handling the contact. The order to attack it in:
- Confirm and ship notifications with a real ETA, not just "your order is on its way."
- Proactive delay alerts the instant the carrier slips, with a new honest date — silence on a delay is what turns a patient customer into an angry one.
- Out-for-delivery and delivered pings, so the last mile closes the loop without a question.
- A self-serve status page the notifications link to, so the curious customer can check anytime.
Every one of these is a WISMO ticket that never existed. You're not deflecting the question; you're answering it before it forms.
For the questions that still come, ground the AI agent in real data
Proactive updates won't catch everything. Some customers will still ask, often the anxious ones with the highest stakes — a gift that has to arrive by a date, an order to a new address. These are perfect for an AI agent, if it's wired to the same real systems.
A grounded AI agent can pull the live order and carrier data and give a complete answer in seconds, at 2am, in any spelling of the question. A complete WISMO answer does four things:
- Confirms the order by number and item, so the customer knows you're looking at the right thing.
- States the real status in plain language — shipped, out for delivery, delayed at the carrier — not a status code.
- Gives an ETA with a date, not "soon."
- Offers the next step — track, change address, or talk to a person — before they have to ask.
The non-negotiable is grounding. An AI agent that guesses at a delivery date is worse than no automation, because a confident wrong ETA generates the next ticket and a lost customer. It should answer only from the live order and carrier data, and the moment WISMO turns into something else — a damaged package, a dispute, a missed event — hand the thread to a person with the full context carried over.
Measure deflection honestly
| Metric | What it tells you |
|---|---|
| Proactive coverage | Share of orders that got an update before a question |
| Auto-resolution rate | WISMO closed with no human touch |
| Reopen rate | Whether "resolved" actually stuck |
| CSAT on automated threads | Whether customers liked the automated answer |
If auto-resolution and proactive coverage rise while reopens and CSAT hold, you're winning. If reopens climb, you're closing tickets, not solving problems.
In BearScope, WISMO is handled on the same board your team works — proactive updates that beat the question, an AI agent grounded in your real order and carrier data for the ones that still come, and a clean handoff to a person the moment the conversation turns. Every action leaves a receipt you can audit. See how it works, read the deeper take on the WISMO handoff line, or book a walkthrough.
Stop answering "where is my order?" faster. Start making sure most customers never have to ask.
See it on your own conversations.
Bring your busiest day. We'll score every conversation in it.
Book a walkthrough →