Ecommerce support
WISMO. The question your support team answers all day.
Where is my order. It can run 30 to 50% of an ecommerce ticket queue, it costs $6 to $10 per conversation to answer by hand, and the answer was sitting in your order system the whole time. Here is the math, and the fix.
Last updated 9 August 2026
What WISMO means
WISMO stands for where is my order. It is the industry name for every ticket, chat, email and phone call where a customer asks about the status of something they already paid for. Did it ship. When will it arrive. Why has tracking not moved since Tuesday. The refund twin is WISMR, where is my refund, and everything on this page applies to it too.
One thing makes this ticket category different from every other one. The customer is not reporting a problem you need to investigate. They are asking for a fact your order system already holds. That is why WISMO is both the biggest category and the most automatable one, and why getting it wrong is so expensive: you are paying a person $8 a time to read a tracking number out loud.
Why it dominates ecommerce ticket volume
The numbers first, each from the vendor that published it. Gorgias, whose helpdesk processes ecommerce tickets all day, says order-status questions sit at the top for most brands, sometimes 30 to 50% of all tickets on their own (gorgias.com/blog/customer-service-automation-guide, checked 9 August 2026). LateShipment puts the everyday range at 20 to 40% and notes it can pass half the queue in peak season (lateshipment.com/blog/wismo, checked 9 August 2026). Nobody credible puts it anywhere other than first place.
The reason is structural. Between checkout and doorstep, the customer has money out and nothing in hand, and every quiet hour feeds the worry. LateShipment's numbers on the behavior: 96% of shoppers track their orders when they can, and 43% check every single day until arrival (checked 9 August 2026). Tracking pages do not absorb that anxiety, because the page answers where the package is, and the customer is really asking whether they should worry. A scan history that goes quiet for two days answers that question badly, so they write in.
And the stakes are not just cost. chatbot.com's WISMO page cites Metapack finding that 69% of shoppers call real-time order tracking a top factor when buying online, and Statista's 2024 finding that 44% of US consumers stopped buying from a company after one bad service experience (chatbot.com/solutions/wismo, checked 9 August 2026). The order-status conversation is often the only conversation a customer ever has with your brand. It decides whether there is a second order.
The part the chatbot vendors skip
Here's the thing. The cheapest WISMO conversation is the one that never happens, and the tool that prevents it is not a chatbot. It is a boring, proactive shipping notification sent at every carrier scan. Shipped, out for delivery, delayed, delivered. Most vendors in this category will not lead with that, because step one does not require their product. We sell an AI agent and we are telling you anyway: fix your notifications first.
Notifications will not get you to zero, though. Carrier exceptions, split shipments, customs holds, the customer who checks daily and writes in anyway. Some meaningful share of order-status volume survives good notifications, and that remainder arrives at 2 am, on weekends, and in December. That remainder is what you automate.
What order-status automation actually is
Not a macro. A canned response has to be true for every customer, so it says something like check your confirmation email for the tracking link. That deflects nothing, because the customer already did that. Real order-status automation is an AI agent connected to your order system, reading the live order state and the latest carrier scan, and answering with the specific fact: your order left the Memphis hub this morning and is due Thursday.
That is the whole test when you evaluate tools, ours included. Give the agent a real order number. If the reply contains that order's actual status, it works. If it contains a polite paragraph about how shipping works, it is a help-article bot wearing an ecommerce costume. Outlearn does the lookup through actions that call your own systems, answers in chat, email and Slack, and hands anything it cannot finish to your team with the transcript attached. It reads your policy docs too, because half of these conversations carry a second question about cutoffs or returns.
The cost math, with the arithmetic shown
A human WISMO resolution costs $6 to $10. That range comes from the delivery platform Sorted, cited by chatbot.com, which uses $8 as the midpoint in its own calculator (chatbot.com/solutions/wismo, checked 9 August 2026). We will use their $8, not a number of our own invention.
The automated side is computed from our published pricing, with the assumption in the open: one resolved conversation averages 4 AI replies at 1 credit each, the same assumption our comparison pages use. Growth is $199 a month with 4,500 credits, so 4,500 divided by 4 is 1,125 conversations of capacity, and $199 divided by 1,000 actual conversations is $0.20 each. Change the assumption and the number moves, which is why it is printed here instead of hidden.
| Monthly WISMO volume | Human cost at $8 each | Outlearn plan that covers it | Credits used | Cost per resolved conversation |
|---|---|---|---|---|
| 300 conversations | $2,400 | Starter, $99/mo | 1,200 of 2,000 credits | $0.33 |
| 1,000 conversations | $8,000 | Growth, $199/mo | 4,000 of 4,500 credits | $0.20 |
| 3,000 conversations | $24,000 | Scale, $599/mo | 12,000 of 15,000 credits | $0.20 |
Now the honest version, because no AI agent takes 100% of a queue. Assume it resolves 70% and hands the rest to your team. At 1,000 monthly conversations that is 700 automated plus 300 human. The bill: $199 for the plan, plus 300 times $8 is $2,400 of human time, so $2,599 total against $8,000 for answering everything by hand. The automation pays for itself at well under 100 conversations a month, and the assumption doing the heaviest lifting is the 70%, so measure yours in the first month and redo this arithmetic with your own number.
The four WISMO fixes stack, and the order matters
These are not competitors. They stack, and the order matters: notifications prevent, the tracking page catches the lookers, the AI agent answers the remainder, and your team keeps the cases that need a human being.
| Approach | What it fixes | What it misses | Cost per conversation |
|---|---|---|---|
| Human agent with a macro | Everything, eventually. Judgment calls, claims, angry customers. | Speed and cost. The queue grows faster than the team in Q4. | $6 to $10 per conversation (Sorted's range, via chatbot.com, checked 9 Aug 2026) |
| Branded tracking page | The customers who go looking before they write in. | It answers where, not whether to worry. Silent scans still create tickets. | No per-conversation cost. Deflects only the ones who look. |
| Proactive shipping notifications | Prevents the question. The single most effective WISMO fix. | Carrier exceptions, split shipments, and the anxious 43% who check daily anyway. | Near zero marginal cost per email or SMS sent. |
| AI agent with live order lookup | The questions that still arrive: answered in seconds, at 2 am, in any channel. | Lost packages, damage claims, refund judgment. Those hand off to a person. | About $0.20 per resolved conversation on Outlearn Growth (computed below) |
What automation should not touch
Some order-status conversations must reach a person, and routing them to a bot is how brands end up as screenshots. A package marked delivered that never arrived. A box that arrived crushed. A customs charge the customer did not expect. A customer who is already angry. These need judgment, empathy, and sometimes a refund decision, and the right automation move is a fast, clean handoff with the full conversation attached, so the customer never repeats their order number to a second party. Deflection is not the goal. Resolution is. A deflected customer who did not get an answer just becomes a WISMO ticket in a worse mood tomorrow.
The first working version takes an hour
1. Connect the system that knows the answer
WISMO answers live in your order platform, not in your help docs. Connect the store or order system so the agent can read live order state and the latest carrier scan.
2. Connect your policy docs too
Half of order-status conversations carry a second question: can I still change the address, what is the cutoff for holiday delivery, who pays return shipping. The agent should answer those from the documentation your team already maintains.
3. Decide what a person must see
Delivered-but-missing, damage, anything past a threshold you set. Route those to your helpdesk with the transcript attached, so the customer never repeats themselves.
4. Test with a real order number
Not a demo script. Paste an actual order number from yesterday and read the answer. If it contains that order's carrier status, ship it. If it contains a paragraph about how tracking works, keep configuring.
WISMO questions, answered first
What does WISMO stand for?
Where is my order. It is the support industry's shorthand for every ticket, chat, email and call where a customer asks about the status of something they already paid for. The refund version is WISMR, where is my refund, and it behaves the same way.
What percentage of support tickets are WISMO?
For ecommerce, 30 to 50% of all tickets, per Gorgias's own automation guide (gorgias.com, checked 9 August 2026). LateShipment puts the normal range at 20 to 40% and says it can pass 50% in peak season (lateshipment.com, checked 9 August 2026). Whichever number is yours, it is almost certainly your largest single category.
How much does one WISMO ticket cost to resolve?
$6 to $10 with a human agent, a range chatbot.com attributes to the delivery platform Sorted and uses in its own calculator at an $8 midpoint (chatbot.com/solutions/wismo, checked 9 August 2026). Automated with an AI agent that reads your order system, roughly $0.20 per resolved conversation on Outlearn's Growth plan. The arithmetic is on this page, not in a footnote.
How do I reduce WISMO tickets?
In this order: send proactive shipping notifications at every carrier scan, put a tracking link in every order email, and only then automate the questions that still come in with an AI agent that can look up live order status. Most vendors sell you step three first because step one does not need their product.
Can a chatbot actually answer a WISMO question?
Only if it can read your order system live. A bot that answers from your help articles will tell the customer how tracking works, which is not what they asked. The test when evaluating one: give it a real order number and see whether the answer contains that order's actual carrier status or a paragraph about shipping policy.
Why do customers ask where their order is when tracking exists?
Because the tracking page answers a different question. It says label created or in transit. The customer is asking whether they should worry. 96% of shoppers track orders when they can and 43% check daily until arrival, per LateShipment (checked 9 August 2026), and they still write in the moment the scan history goes quiet for two days.
What is a WISMO rate and what should mine be?
WISMO conversations divided by orders shipped in the same period. If you ship 5,000 orders and get 600 order-status conversations, your WISMO rate is 12%. There is no honest universal benchmark because it swings with carrier speed, category and season. Track your own number weekly and judge fixes against it.
Does WISMO volume really spike in peak season?
Yes, and it compounds. Q4 raises order volume and slows carriers at the same time, so a queue that is 30% WISMO in June can pass half your tickets in December, per LateShipment (checked 9 August 2026). That is also when hiring temporary agents is most expensive, which is why the automation case is usually written in October.
What does WISMO do to customer satisfaction?
The question itself is a symptom of anxiety, and how you answer it decides whether the anxiety converts to churn. chatbot.com cites Statista's 2024 finding that 44% of US consumers stopped buying from a company after one bad service experience (checked 9 August 2026). A fast, specific order-status answer is one of the cheapest satisfaction wins available.
Should WISMO answers come from a canned response?
No, and this is the one scenario where a template genuinely fails. A canned response has to say something true for every customer, so it says check your confirmation email for tracking. An order lookup says where that specific package was scanned last. Templates are the right tool for refunds and policy questions, and we keep a free library of them.
What happens to the WISMO conversations automation cannot finish?
They go to a person, and they should. A package marked delivered that never arrived, a damaged item, a customs hold, anything involving a claim or a judgment call. Automation's job is to clear the 70% that have a clean answer so your team has time for the 30% that do not.
How long does WISMO automation take to set up?
With Outlearn, the honest answer is under an hour for the first working version: connect your order source, connect the docs that hold your shipping policy, set a human handoff, and test with a real order number. Tuning what hands off to a person takes longer, and that tuning never fully ends.
Try it on a real order
Connect your order system, paste yesterday's order number, read the answer.
Free tier, no card. If the answer is generic, do not buy it. That rule applies to us too.
Sources
- Gorgias, customer service automation guide: gorgias.com/blog/customer-service-automation-guide, checked 9 August 2026.
- LateShipment, WISMO tickets: lateshipment.com/blog/wismo, checked 9 August 2026.
- chatbot.com, WISMO solutions page, carrying the Sorted, Metapack and Statista figures: chatbot.com/solutions/wismo, checked 9 August 2026.
- Outlearn pricing, the source of every computed cost on this page: outlearn.com/pricing.