What is WISMO? The "where is my order" ticket, explained

Almost every article about WISMO tells you how to stop receiving them. That advice is good and this page covers it. But it skips the half that support teams live with: the tickets still arrive, and someone has to answer them accurately, today, one at a time.

What counts as a WISMO ticket

WISMO is a category, not a single question. In practice it covers:

• "Where is my order?" with no order number attached
• "Has this shipped yet?" on an order still being packed
• "Tracking hasn't moved in three days"
• "It says delivered but I don't have it"
• "Can you tell me when it will arrive?"
• "Is my parcel stuck in customs?"

They look similar and need genuinely different answers. Telling a customer their parcel is in transit when it has not left your warehouse creates a second, angrier ticket. That is why grouping them all under one macro tends to fail.

Why WISMO dominates ecommerce inboxes

Published estimates put WISMO at roughly a quarter to a half of ecommerce support volume, climbing during peak periods. The figures vary a lot by source and by store, so treat any single number with suspicion and measure your own.

The underlying cause is consistent though: a gap between what the carrier knows and what the customer knows. The carrier scans the parcel. The customer refreshes a tracking page that has not updated. The gap between those two moments is where the email gets written.

How to measure your WISMO rate

The standard formula is simple:

WISMO rate = (order-status tickets ÷ total tickets) × 100

So 300 order-status tickets out of 1,000 total is a 30% WISMO rate. Two things make this useful rather than decorative:

• Count by month, not by week. Shipping incidents are lumpy, and a weekly number mostly measures weather and carrier backlogs.
• Split "pre-delivery" from "post-delivery". "Has it shipped" is a communication problem you can fix with better notifications. "It says delivered but I don't have it" is a carrier problem that needs an investigation workflow. Lumping them together hides which one you actually have.

Reducing WISMO before it reaches you

This is the part every vendor writes about, and it works:

• Set a realistic delivery window at checkout, not an optimistic one. Most WISMO is expectation failure rather than shipping failure.
• Send the shipping confirmation the moment fulfilment happens, with a tracking link that actually resolves.
• Notify on exceptions proactively. A customer told about a delay writes far fewer emails than one who discovers it themselves.
• Put order status behind a self-service link in the confirmation email so checking does not require contacting you.

Realistically none of this takes WISMO to zero. Carriers lose parcels, addresses get typed wrong, and some people prefer emailing a human.

Answering the ones that still arrive

This is the half most guides skip. A good WISMO reply does four things:

1. Confirms which order you are talking about. Order number, date, item count. It proves you looked.
2. States the real current status, in plain words. "Packed and waiting for collection" is more useful than "processing".
3. Gives the next concrete thing that will happen, and when, if you honestly know. If you do not know, say so rather than inventing a date.
4. Names the next step if it goes wrong, so the customer does not have to ask a follow-up question to find out.

The slow part is not writing that. It is checking, for every single email, which order they mean and what is actually true about it right now. That is the lookup: switch to Shopify, search the customer, open the order, read the fulfilment block, open the tracking link, copy the number, come back. Forty-five seconds that you pay dozens of times a day.

The WISMO scenarios worth separating

If you build a template set, build it around these rather than around one generic reply:

• Not yet fulfilled — no tracking exists, so do not promise one
• Fulfilled, no carrier scan yet — label created, parcel not collected
• In transit — moving normally, include the tracking link
• Delayed — movement stalled; acknowledge it instead of resending the link
• Out for delivery — on the vehicle today
• Delivered — confirm, and offer a next step if it is missing
• Delivered but not received (DNR) — open an investigation, do not argue with the scan
• Exception — address problem, failed attempt, customs hold

Eight scenarios, eight different replies. We have written all eight out, free to copy.