WISMO rate is the share of your orders that generate a "where is my order" contact. Take your WISMO tickets over a period, divide by orders shipped in the same period, and you have the single cleanest number for how much anxiety your delivery experience produces.
Most brands know what WISMO is and complain about it. Far fewer measure it as a rate, which is the step that turns a support annoyance into an operational metric you can actually move. Here is how to calculate it, what to compare it against, and what reliably brings it down.
How to calculate your WISMO rate
WISMO rate = WISMO tickets ÷ orders shipped, same period, × 100.
Three practical rules make the number honest:
- Count contacts, not conversations. One customer chasing one order across email, chat, and Instagram is three contacts of anxiety. Count them all, then dedupe per order if you want a second, stricter number.
- Tag the whole family. "Where is my order" is the headline, but "has it shipped", "why is it delayed", and "it says delivered but it is not here" are the same failure. Tag them under one WISMO umbrella in your helpdesk. Include "where is my refund", the return-leg twin, or track it as its own rate.
- Use shipped orders as the denominator. Orders that have not shipped yet cannot generate delivery anxiety. Weekly or monthly windows both work, just stay consistent.
Segment the rate three ways and the causes usually reveal themselves: by carrier, by destination country, and by delivery speed. A WISMO rate that doubles on one carrier's lane is not a communication problem, it is a carrier performance problem wearing a support costume.
What a good WISMO rate looks like
Support platforms consistently report that order-status questions are among the largest single categories of ecommerce support tickets, commonly cited at around a third or more of total volume. As an order-level rate, useful working bands for DTC brands:
- Under 3% of orders: healthy. Tracking is doing its job and delays are being communicated before customers ask.
- 3 to 8%: normal but expensive. Most brands sit here, and most of it is removable.
- Above 8%: something structural is wrong: slow or vague tracking, missed delivery promises, or a carrier lane that keeps stalling.
Treat these as orientation, not law. The benchmark that matters most is your own trend line, measured the same way every month. Peak season will spike it; the question is whether it returns to baseline.
What actually reduces WISMO rate
Set the expectation before the anxiety starts. A real delivery date at checkout removes the guesswork that creates the ticket. Vague "3 to 5 business days" promises invite day-4 emails.
Make tracking answer the question customers actually have. A branded tracking page with clean milestones beats a carrier page full of jargon. Raw feeds like "parcel data submitted to carrier" generate tickets on their own.
Message delays proactively. The single highest-leverage fix. When a delay scan triggers a message with the new expectation before the customer notices, the ticket never gets written. This is exactly the routine work AI agents should own, around the clock.
Fix the lanes, not just the words. If one carrier or one country drives the spike, reroute it. Communication patches a bad lane; routing fixes it.
The tactical playbook, template by template, is in our guide to reducing WISMO tickets, and the messages themselves are in the post-purchase email templates.
Why the rate is worth money
Every WISMO contact costs a support touch, and support time is the obvious line. The quieter cost is trust: a customer who had to chase their order starts the next purchase decision from doubt. Brands running Pango cut the inputs at the source, since the delivery promise, the tracking, and the proactive messages run on one record, and delays act on themselves. Fewer anxious customers, and a support team working on judgment calls instead of copy-pasting tracking links.
The bottom line
WISMO rate is the delivery experience compressed into one honest number. Measure it consistently, segment it by carrier and country, and attack it with promises, clean tracking, and proactive delay messages, in that order. Pango runs all three on one record. See the post-purchase operations platform and book a demo.
