WISMO stands for "where is my order," and it is the single largest category of inbound customer service volume in most ecommerce stores. Published estimates of its share range from roughly 25 percent to about 60 percent of total tickets depending on the source, the vertical, and the season, with every source agreeing the number rises during peak. It is also the most reducible category, because the answer already exists in your own order data. The stores that cut it durably do so by pushing information out before the customer asks, not by making it harder to reach support.
Last updated August 2026.
What is WISMO?
WISMO is shorthand for the "where is my order" question: a customer who has already paid contacting you to find out when their package will arrive. It covers the obvious version and several disguised ones. "Has this shipped yet," "the tracking hasn't updated in four days," "I think this is lost," and "I need it by Friday, will it make it" are all WISMO tickets wearing different hats, and they all resolve against the same three data points: order status, fulfillment state, and carrier tracking.
The reason it dominates support queues is structural. Every single order creates a window of uncertainty between checkout and delivery, and the customer has no visibility into that window except what you give them. Multiply a few days of anxiety by every order you ship and you get a support queue that is mostly people asking a question your system can already answer.
What percentage of support tickets are WISMO?
Be careful with the numbers in this category, because they get repeated without sourcing and the range is genuinely wide. Figures published across industry guides and vendor research put WISMO somewhere between a quarter and 60 percent of inbound ecommerce support volume, with the higher end reported during holiday peaks. Nobody should quote a single precise figure as though it were universal, because the real answer depends on your average delivery time, your carrier mix, your product category, and how much you communicate after checkout.
What matters more than the industry benchmark is your own WISMO rate, which is worth measuring properly:
| Metric | How to calculate it | Why it matters |
|---|---|---|
| WISMO rate (share of tickets) | Order status tickets divided by total inbound tickets | Tells you how much of your team's capacity is going to a question software can answer |
| WISMO rate (share of orders) | Order status tickets divided by orders shipped | The honest measure of post-purchase communication quality. It should fall as you improve notifications |
| Time to first WISMO | Median days between order placed and the first status question | Reveals exactly where your notification gap sits |
| Repeat WISMO per order | Status tickets divided by unique orders that generated one | A number above 1.3 usually means your first answer was not good enough |
Pulling these apart means querying order data against ticket data, which is the kind of question that stalls because it sits between two systems and nobody wants to write the SQL. If that is what is blocking you, tools that let you ask your database questions in plain English will get you to a defensible baseline faster than waiting on a reporting ticket. Measure before you change anything, or you will not be able to tell whether the change worked.
Why do customers ask where their order is?
Almost always because the information they were given ran out. The pattern is consistent: the order confirmation arrives, then a shipping notification with a tracking link, and then nothing. The customer clicks the carrier link, sees a status that has not moved in three days, cannot tell whether that is normal, and contacts you.
Three specific gaps generate most of the volume. The first is the pre-shipment window, when the order is paid but not yet handed to the carrier, and the customer has no signal at all that anything is happening. The second is carrier scan silence, which is entirely normal in transit but reads as "lost" to somebody watching a tracking page. The third is a missed delivery estimate, where the date you promised at checkout passes without an update.
Notice what none of these are: none of them are the customer being unreasonable, and none of them are a support problem. They are all communication problems that surface as support tickets.
How do you reduce WISMO tickets?
In rough order of return on effort:
Set an honest delivery estimate at checkout. An optimistic date does not win the sale often enough to pay for the tickets, refunds, and trust it costs when it slips. Pad it to something you hit consistently and you will beat expectations instead of managing complaints.
Send proactive updates through the quiet stretches. Confirmation, in-fulfillment, shipped, out for delivery, delivered. The two that matter most are the ones most stores skip: a note while the order is still being picked, and a proactive heads-up when tracking has stalled longer than usual. Vendors reporting on proactive notification programs describe substantial reductions in status contacts, though the specific percentages come from vendor case studies rather than independent research, so treat them as directional.
Put tracking where the customer already is. A branded order-status page on your own domain beats a carrier link, and a status update over SMS or WhatsApp beats an email that lands in Promotions. The channel matters as much as the message.
Automate the answer for the tickets that still arrive. Some percentage of customers will always ask, and that is fine. This is a lookup with a definite answer, available at any hour, which makes it close to ideal work for an AI agent connected to your store data. An agent that reads the order and the fulfillment state can answer accurately at 2am without a human, and escalate the genuinely broken cases to a person. That is what ecommerce customer service software is for, and it is the difference between a help desk that files the question and one that resolves it.
Fix the upstream cause the tickets point at. If one carrier or one warehouse produces most of your WISMO, no amount of messaging fixes it. Treat the ticket volume as a diagnostic.
Is deflection the same as reducing WISMO?
No, and conflating them is the most common mistake in this category. Deflection means the customer did not reach a human. Reduction means the customer did not need to ask. A help widget that buries your contact form behind an FAQ carousel will improve your deflection rate and do nothing for the underlying problem, while quietly making people angrier.
The test is simple. If your deflection rate improves while your WISMO rate per order stays flat, you have not solved anything. You have moved a frustrated customer from your inbox to a review site.
Can AI handle where is my order questions?
Yes, and it is the clearest legitimate use of AI in ecommerce support. Order status has one correct answer, it lives in structured data, and it does not require judgment. An AI agent with read access to orders and fulfillment can answer the question, explain what a stalled scan usually means, and set expectations, in the customer's own thread and in your brand's voice.
What it should not do is handle the exceptions. A package confirmed delivered that the customer never received, a damaged item, a time-critical gift that will not arrive, and anything involving a chargeback all need a person. The right configuration answers the routine lookup instantly and routes the rest to a human with the full order history attached.
What does it cost to automate order status questions?
More than the sticker price suggests, and this is worth checking before you commit. Most established help desks now meter AI separately from seats, and they meter different units. Richpanel charges $0.20 per AI-handled conversation on top of $99 per seat. Re:amaze charges $0.85 per additional resolution above plan. Help Scout prices AI Answers at $0.75 per resolution. Intercom's Fin starts from $0.99 per resolved outcome. Gorgias bills per resolution, at roughly $1.00 as of a July 2026 check, though its published dollar table renders in JavaScript and cannot be read from the page source.
Run that against your own volume before signing. WISMO is high-frequency by definition, so per-resolution pricing bills you most for exactly the work you bought the software to absorb, and it peaks in the same month your ticket volume does. A store automating 3,000 status questions a month pays somewhere between about $600 and $3,000 for identical work depending purely on which meter it signed up for. Flat subscription pricing, which is how MessageAgent is structured, removes that variable entirely. Our fuller breakdown of the tradeoff sits in the ecommerce customer service software comparison, and if you are weighing the incumbent specifically, the Gorgias alternative page goes through it vendor by vendor.
Does reducing WISMO actually save money?
It does, but the saving is rarely a headcount reduction, and you should be skeptical of anyone who promises one. What actually happens is that the same team stops spending its day retyping tracking numbers and starts handling the conversations that change outcomes: pre-purchase sizing questions, recovering a botched order, upselling a customer who is already engaged.
There is a second effect that is harder to measure and probably larger. Every status question is a customer in a state of mild anxiety about money they have already spent. Answering fast and clearly, at whatever hour they asked, is the cheapest repeat-purchase intervention available to a store. The stores that treat post-purchase communication as a retention channel rather than a cost center are the ones whose WISMO rate falls and stays fallen.
Where to start this week
Measure your WISMO rate per order so you have a baseline. Read the last fifty status tickets and note the day-of-order each one landed, which will point straight at your notification gap. Add the one proactive message that gap calls for. Then automate the answer for the tickets that still come in, on a pricing model that does not charge you more the better it works.
If you want to see the automated version answering against real order data, the agent on this page is connected and ready. You can also compare the full vendor set, with US pricing and the AI meter spelled out for each, on the ecommerce customer service software page, or look at how the same agent handles pre-purchase questions in the Shopify AI chatbot breakdown.
MessageAgent · Get started
Put one AI on every channel
One agent that answers, qualifies, books, and upsells across SMS, WhatsApp, Instagram, web chat, and email, in one inbox. AI is always disclosed, with human handoff built in.