Quick answer: WISMO (“Where Is My Order?”) tickets typically make up 30–50% of all ecommerce support volume — climbing past 50% during peak season — and each one costs a brand roughly $5–12 in direct agent time. For a store handling 3,000 support tickets a month, that’s $4,500–18,000 spent every single month answering a question your customer wouldn’t have needed to ask if they’d heard from you first. That’s the WISMO tax: not a line item on your P&L, but a real, recurring cost hiding inside your support budget, your churn numbers, and your reviews.
Here’s how to see the full size of it — and what actually makes it go away.
What WISMO actually is (and why it’s bigger than “a tracking question”)
WISMO stands for “Where Is My Order?” — the catch-all term for any support ticket where a customer is asking about the status, location, or expected arrival of something they already paid for. It shows up as an email, a WhatsApp message, an Instagram DM, a phone call, or a live chat message, and on the surface it looks like the simplest, lowest-stakes ticket type a support team handles.
It isn’t. WISMO is consistently the single largest category of ecommerce support volume — industry benchmarks across multiple 2025–2026 CX reports put it at 30–50% of total tickets in a normal month, and past 50% during BFCM and other peak periods. In dropshipping and consumer electronics, where shipping variance is higher, it can run even hotter. In subscription businesses, where delivery is predictable and repeat, it’s lower.
The reason it’s worth isolating from the rest of your ticket queue is simple: almost none of it requires a human decision. A WISMO ticket isn’t a judgment call about a return, a discount, or an exception. It’s a data-retrieval problem — the answer already exists in your fulfillment system. Your team is just the interface standing between that data and the customer, which is an expensive way to move information that a system could surface directly.
The real WISMO tax: what it costs across four categories
Most founders undercount their WISMO tax because they only look at one line of it — the direct labor cost. There are three more sitting underneath it.
| Cost category | What it looks like | Typical range |
|---|---|---|
| Direct agent time | 3–5 minutes per ticket: lookup, interpretation, reply | $5–12 per email/chat ticket; $7–16 per phone call |
| Opportunity cost | Time your team spends on WISMO instead of returns, exceptions, or proactive outreach that actually drives revenue | Scales with ticket volume |
| Retention leakage | Customers who don’t churn over a delay — they churn over never being told about it | ~70% say they won’t reorder after a poor delivery experience, independent of whether the delivery was actually late |
| Review damage | Slow or absent order-status communication shows up disproportionately in 1- and 2-star reviews, even when the product itself was fine | Reviews citing delivery/communication outnumber reviews citing product defects on most delayed orders |
Run the math on a mid-sized D2C brand: 500 orders a month, a conservative 30% WISMO rate on total support contacts, and a $7 blended ticket cost lands you at roughly $8,000+ a year — before you count the reorders that quietly didn’t happen because nobody told a customer their package was running late.
That number is the actual WISMO tax. It’s not hypothetical, and it’s not fixed by hiring faster typers.
Why “just improve the tracking page” doesn’t fix it
The instinctive fix is a better tracking page — more detail, a nicer UI, real-time carrier data. It helps at the margins. It doesn’t solve the underlying problem, because the underlying problem was never about information access. It was about who initiates the conversation.
A tracking page is pull: the customer has to remember it exists, go find it, and interpret carrier language like “in transit” or “arriving soon” — phrases that describe a shipment, not a promise. When that interpretation creates doubt, the customer doesn’t re-check the tracking page. They email you. The tracking page and the support ticket aren’t actually competing channels; a confusing tracking page generates tickets rather than preventing them.
The fix that actually moves the number is push: your brand telling the customer what’s happening before they have to ask. Orders that are communicated proactively — even when they’re delayed — generate dramatically fewer tickets than orders where the customer is left to check for themselves. Delays get forgiven. Silence doesn’t.
The 5 moments where WISMO either dies or multiplies
Every order has five points where a proactive message either closes the loop or leaves it open for a ticket to fill the gap:
- Order confirmed — sets the first expectation (delivery window, not just “thank you”)
- Order shipped — the tracking link, sent the moment it’s real, not a batch job hours later
- In transit / milestone update — a check-in before the customer has to check in themselves
- Delay detected — the message that matters most: proactive, specific, and honest about the new timeline
- Delivered — confirmation that closes the loop, especially important for the “it says delivered but I got nothing” ticket, which is one of the most time-consuming exceptions a support team handles
Most brands run message 1 and 2 well, skip 3, and only send 5 as a passive notification with no follow-up. Message 4 — the delay notification — is the one that does the most work, because it’s the one that converts an anxious customer into an informed one before they ever open a support channel.
How to calculate your own WISMO tax
You don’t need perfect data to get a directionally useful number. Three inputs:
WISMO tax = (Total monthly tickets × WISMO %) × Average cost per ticket
- Total monthly tickets: pull from your helpdesk (Gorgias, Zendesk, Gmail — wherever tickets land)
- WISMO %: if you haven’t tagged tickets by type, sample 100 recent tickets and count how many are status/tracking questions — 30–40% is a safe starting assumption if you have no proactive notifications in place
- Average cost per ticket: loaded agent cost per hour ÷ tickets handled per hour (most teams land between $5–12 for email/chat, higher for phone)
Multiply those out and you’ll usually land somewhere between four and five figures a month — money spent entirely on a question your fulfillment system already knew the answer to.
What actually brings the number down
The pattern across brands that meaningfully cut WISMO isn’t a better helpdesk plan or a faster reply-time SLA. It’s closing the proactive-communication gap across every channel a customer might use — email, WhatsApp, Instagram, chat, and voice — so the update reaches them wherever they’re actually looking, without a human having to trigger it manually. That’s the layer Ephanti’s MEVA system is built to run: monitoring shipment events in real time and pushing the right message, on the right channel, before the ticket gets created — not just answering faster once it does.
FAQ: WISMO tickets, explained
What does WISMO stand for?
WISMO stands for “Where Is My Order?” — the standard industry term for any customer support inquiry about the status, location, or delivery timeline of an order that’s already been placed.
What percentage of ecommerce support tickets are WISMO?
Most industry benchmarks place WISMO at 30–50% of total ecommerce support volume in a typical month, rising above 50% during peak sale periods like BFCM. The exact share varies by vertical — higher in categories with variable shipping (electronics, dropshipping), lower in subscription and repeat-delivery models.
How much does a WISMO ticket cost?
Direct labor cost typically runs $5–12 per email or chat ticket and $7–16 per phone call, based on 3–5 minutes of agent time per ticket. The fully loaded cost — including retention and review impact — is higher and harder to isolate, but consistently larger than the direct labor number alone.
Does a better tracking page reduce WISMO tickets?
It helps modestly, but tracking pages are a “pull” channel — the customer has to seek them out and interpret carrier language. Proactive, brand-sent notifications (“push”) that reach the customer before they have to check are consistently more effective at preventing the ticket from being created in the first place.
What’s the fastest way to reduce WISMO without adding headcount?
Automate the five key post-purchase touchpoints — order confirmed, shipped, in transit, delay detected, and delivered — with proactive messaging across the channels your customers actually use, rather than relying on a single tracking-page link.
See what your own WISMO tax actually adds up to — plug in your monthly order volume and ticket mix and get a number in under two minutes → Calculate your WISMO cost.