WISMO stands for "Where Is My Order?". A WISMO complaint is any inbound customer contact, by email, chat, phone, or social, where a customer asks about the status or expected delivery date of their order. It signals a breakdown in proactive post-purchase communication, not necessarily a delivery that went wrong.
The difference is worth drawing. A real delivery problem, a lost or damaged package, calls for investigation and action. A WISMO complaint is usually a request for information you already hold. The order shipped, the carrier has it, the tracking is live. The customer just can't find it, or can't decode the carrier's status language.
Behind most of these queries sits possession lag: the wait between paying for something and actually holding it. That wait breeds a real sense of urgency, and the numbers show it. One widely cited consumer study found that 91 percent of shoppers track their orders and 39 percent check every day. A WISMO complaint is what happens when that anxious daily check turns up nothing new.
The most common trigger for WISMO is a communication gap between order placement and the first carrier scan, a stretch when the customer gets no proactive update. It rarely has anything to do with a late shipment. WISMO usually comes down to three causes, each tied to a different point in the customer journey.
The standard sequence at most brands is thin: an order confirmation email, then silence, then a shipping confirmation, then more silence in transit. A healthy timeline runs Confirmation, Label Scan, In-Transit Update, Out for Delivery, Delivered. Most brands skip the middle three. And since about half of shoppers track an order to confirm it is progressing on time, every skipped milestone is an invitation to open a ticket.
When a label is generated but the carrier has not yet scanned the package, tracking pages can show “Label Created” for 24 to 72 hours. To the customer, this reads as nothing happening. Decagon describes these pre-shipment statuses as a driver of contacts before the carrier has even touched the parcel. It is the single most avoidable WISMO trigger because fixing it requires zero carrier action, only a proactive email explaining the processing window.
Some WISMO starts before anything ships. A product page says "Arrives in 2 to 3 days," but that clock only makes sense once the package is actually moving, and your warehouse might need a day or two just to pack it and hand it to the carrier. So the customer counts from checkout, you count from dispatch, and the gap between those two becomes a support ticket.
As Nash puts it, customers reach out when they're left guessing, including about a delivery date they never believed. Fixing it means setting honest delivery dates on the product page and at checkout, ones that account for the time your warehouse needs before the carrier ever gets involved. .
To calculate your WISMO rate, divide your total WISMO-tagged support tickets in a given period by total orders shipped in that same period, then multiply by 100. A rate above 15 percent signals an operational problem requiring intervention.
WISMO Rate = (Total WISMO Tickets ÷ Total Orders Shipped) × 100
| WISMO Rate | Status | Monthly Cost (5,000 orders) | Recommended Action |
| Under 5% | Healthy | $1,000–$6,250 | Maintain and optimize |
| 5%–15% | Watch Zone | $6,250–$18,750 | Audit communication gaps |
| 15%–25% | Operational Risk | $18,750–$31,250 | Immediate intervention |
| Over 25% | Crisis | $31,250+ | Systems-level overhaul |
Cost estimates assume 5,000 monthly orders and a 50% phone / 25% chat / 25% email mix at $5 to $25 per ticket by channel.
Per-ticket cost depends heavily on how the customer reaches you. Gartner benchmarks put the median cost per contact at $1.84 for self-service versus $13.50 for assisted channels like phone, chat, and email. The gap widens once you count re-contacts and measure cost per resolution.
A 2026 cross-source benchmarks put self-service at $1 to $4, chat at $8 to $14, email at $9 to $16, and phone at $17 to $25. A brand routing WISMO to phone agents spends three to five times more per resolution than one deflecting Level 1 contacts to a self-serve tracking page.
WISMO tickets cluster most heavily at two stages of the fulfillment lifecycle: the processing gap immediately after order placement, and the 24-hour window following a missed or passed expected delivery date. Mapping each stage to its trigger and intervention turns a vague problem into a diagnostic tool.
| Lifecycle Stage | WISMO Trigger | Typical Window | Intervention |
| Order Processing | Label Created limbo, no carrier scan | 0–48 hrs | Proactive “preparing your order” notice with SLA |
| Carrier Handoff | Warehouse delay, batch pickup gaps | 24–72 hrs | Alert if order hasn’t moved to “Picked Up” in SLA |
| In-Transit | No mid-journey updates, tracking silence | Days 2–5 | Milestone notifications at key scan events |
| Last-Mile | Missed delivery, no reschedule option | Delivery day | Proactive re-delivery link before customer notices |
| Post-EDD | EDD passed, no delivery confirmation | EDD + 1 | Automated exception alert and outreach |
Split shipments deserve a special mention. When a multi-item order ships in multiple packages, a customer who receives the first parcel will often immediately WISMO the second, a scenario that generates volume even when nothing has gone wrong.
Beyond direct ticket-handling costs, high WISMO volume suppresses repeat purchase rates, elevates chargeback risk, and concentrates agent workload on low-complexity queries. Three costs sit outside the per-ticket math.
First, repeat purchase suppression. Zendesk's 2025 CX Trends Report found that 63 percent of consumers will switch to a competitor after a single bad experience, and a stalled order with no updates is exactly that. The math is concrete: 1,000 WISMO contacts a month, a $75 average order value, and a conservative 10 percent who don't come back means $7,500 in lost monthly repeat revenue, against a support cost in the low thousands.
Second, "item not received" chargebacks. A customer who can't track their order often goes straight to the bank. The trigger is usually a stalled tracking page, even when the parcel is in transit. Each dispute carries a processor fee of $15 to $100. Prevention is cheaper than the dispute.
Third, agent burnout. Repetitive Level 1 contacts are a documented driver of support disengagement. High-WISMO environments push agents to spend 40 to 60 percent of a shift on identical order-status queries. This compresses the time available for complex work that actually needs human judgment, and feeds the CX industry’s persistently high annual agent turnover.
Most WISMO tickets trace back to a handful of moments in the trigger map. ClickPost works by closing those moments one at a time.
Take the two that cost you most. The processing gap after checkout and the quiet stretch mid-transit are where customers start to worry, and worried customers open tickets. Order tracking and proactive notifications keep them updated through both, so the "Label Created" wait resolves itself instead of landing in your queue. A branded tracking page gives them a place to check without ever contacting an agent.
From there it gets more targeted. AI-powered customer segmentation sorts customers by how likely they are to worry, high-value orders, first-time buyers, gifts, and puts your proactive outreach where the risk actually sits.
Then there is the sequel. When the order becomes a return, the same blind spot creates WISMR. Returns management gives the refund its own status trail, so that question gets answered before it turns into a contact.
That is the whole idea behind ClickPost's post-purchase platform: answer the question before the customer has to ask it, for mid-market and enterprise ecommerce teams.
WISMR, “Where Is My Return?”, mirrors WISMO on the returns side of the transaction, typically accounting for 10 to 20 percent of support tickets and peaking in January after the holiday return wave.
| Dimension | WISMO | WISMR |
| Full Form | Where Is My Order? | Where Is My Return? |
| Trigger Stage | Post-purchase, pre-delivery | Post-return, pre-refund |
| Volume Share | 30–50% of tickets | 10–20% of tickets |
| Peak Timing | Q4 holiday surge | Q1 return wave |
| Resolution Tool | Tracking page, notifications | Returns portal, refund updates |
| Automation Fit | High (carrier API) | High (returns platform) |
Calculate your current WISMO rate using the formula above. If you don’t have the number, pull it from your helpdesk this week.
Tag WISMO tickets by lifecycle stage (processing, in-transit, last-mile, post-EDD) to see where volume concentrates.
Audit the gap between order placement and first carrier scan. If it regularly exceeds 24 hours, add a proactive “order being prepared” notice.
Review your checkout delivery promise. If arrival dates ignore fulfillment processing time, update them or add a processing disclaimer.
Activate milestone notifications at a minimum of four points: label created, picked up, out for delivery, delivered.
Build or activate a branded self-service tracking page linked from your order confirmation email. This alone can deflect 20 to 30 percent of contacts.
Review your WISMR exposure separately. Return-status inquiries need a parallel workflow on the returns side.
WISMO stands for “Where Is My Order?” It describes any customer support inquiry in which a customer requests an update on their order’s shipping status or expected delivery date.
A WISMO complaint is a support contact, by email, chat, phone, or social, triggered by a customer’s inability to find a meaningful, real-time update on their order. It signals a failure of proactive post-purchase communication, not always a delivery failure.
Under normal conditions, WISMO accounts for 30 to 50 percent of total inbound ecommerce support tickets. During peak periods such as Black Friday and the holidays, that figure rises to 50 to 80 percent.
Divide total WISMO-tagged tickets in a period by total orders shipped in that same period, then multiply by 100. A rate under 5 percent is healthy; above 15 percent signals a problem needing systemic intervention.
The main causes are post-purchase communication gaps, carrier data latency that leaves tracking on “Label Created,” overpromised delivery windows set at checkout, and last-mile exceptions with no automated customer notification.
WISMR stands for “Where Is My Return?” It is the returns-side equivalent of WISMO, triggered when a customer cannot find a status update on a refund or exchange. WISMO peaks in Q4; WISMR peaks in Q1.
Per-ticket cost varies by channel: roughly $15 to $25 for phone, $8 to $15 for live chat, and $4 to $8 for email. Routing WISMO to phone agents costs three to five times more per resolution than self-serve tracking.
Combine proactive milestone notifications at four or more lifecycle stages, a branded self-service tracking page linked from order confirmation, realistic checkout delivery promises, and automated alerts for orders that breach fulfillment SLAs before a customer contacts you.
WISMO looks like a customer habit. It is really a gap in your own communication, and gaps can be closed. The first move is to measure it. Keep three numbers in front of you: your WISMO rate, your cost per ticket by channel, and how many customers stop reordering after a WISMO contact goes unresolved. Together they show you where the volume comes from and what it drains.
Then there is the fix. A well-run post-purchase experience answers the question before the customer has to ask it, which is exactly what ClickPost's tracking and post-purchase platform is built to do.