WISMO — “Where is my order?” — is the single biggest ticket category in ecommerce support. For most D2C brands it’s 30–50% of all inbound tickets, and it has a special property: almost every WISMO ticket is answerable from data you already have. Nobody is asking for a judgment call. They’re asking for a tracking status that sits one lookup away.
That makes WISMO the highest-leverage category to fix — and the most embarrassing one to keep handling by hand.
Why WISMO happens at all
Understanding the causes matters, because half the fix happens before a ticket exists:
- The expectation gap. The checkout said 2–3 days; the carrier took five. Nobody told the customer, so the customer asks you.
- Tracking black holes. The label is created, the parcel hasn’t been scanned yet — the tracking page shows nothing for a day or two. That gap produces a disproportionate share of tickets, because “no movement” reads as “lost.”
- Carrier handoffs. DHL to a local depot, DPD to a pickup shop — every handoff is a place where status updates stall.
- Off-hours ordering. D2C brands take a large share of orders on evenings and weekends — exactly when support is offline. A customer who writes Sunday night and hears nothing until Monday afternoon writes again. Now it’s two tickets.
What WISMO actually costs
Quick math for a brand doing 2,000 orders a month:
- ~25% of orders generate a ticket, of which ~40% are WISMO → ~200 WISMO tickets a month
- Each one: open the helpdesk, find the order, copy the tracking number, check the carrier portal, write the reply — realistically 4–6 minutes
- That’s ~17 hours a month of pure lookup work. At a fully loaded €30/hour, around €500/month — for answering one identical question. (Full cost breakdown in what a support ticket really costs.)
And the money is the small half. Slow WISMO answers are where “where is my order?” turns into “cancel my order” and, eventually, a chargeback or a 1-star review.
The playbook, in order of leverage
1. Fix expectations upstream
Cheapest fix first: show realistic delivery windows on the product page and in checkout, and don’t send a “shipped!” email when only the label was printed. If the label-to-first-scan gap is routinely a day, say “your parcel is being handed to DHL — tracking becomes active within 24h.” A sentence in an email prevents hundreds of tickets a year.
2. Give status a home — and push updates proactively
A branded order-status page deflects the “just checking” segment. Proactive notifications at the moments that matter — shipped, out for delivery, and especially delay — deflect the anxious segment. The delay notice is the one merchants skip and the one that works hardest: a customer who’s told about a delay rarely opens a ticket about it.
3. Handle exceptions before the customer notices
This is the biggest lever, and almost nobody does it: watch the tracking stream for stuck parcels and reach out first. A parcel with no scan for three days generates a ticket with near-certainty. If the brand writes first — “we’ve seen your parcel is delayed, here’s the status, we’ve filed a carrier query” — the ticket never exists, and the customer experience flips from frustrating to impressive.
One of our beta customers, a fashion brand, ran the classic version of this problem: two people effectively employed to copy tracking numbers between DHL, DPD and the helpdesk. With proactive exception handling plus automated responses, their WISMO volume went from ~250 tickets a week to under 20.
4. Automate the residual inbound — with live data, not macros
Some WISMO always remains. The failure mode here is the macro: “Your order is on its way!” answers the words and ignores the question. An automated WISMO reply is only worth sending if the system pulls the live tracking status for that specific order and answers with it: where the parcel is, what the last scan was, when it’s expected. That’s also the honest test for any “AI support” tool you evaluate: does it look up, or does it just phrase?
Done right, this also fixes the off-hours problem — standard cases get real answers at 11pm on a Sunday. Another beta brand cut their weekend first-reply time from over 12 hours to under 5 minutes this way, with nobody on call.
5. Escalate the genuinely broken cases — with context
Lost parcels, damaged goods, carrier investigations: those should reach a human, but as a prepared case — order, full tracking history, suggested next step — not as a bare email. The human handles the decision, never the lookup.
The three numbers to watch
- WISMO share of total tickets — the strategy metric. If it’s above ~15%, levers 1–3 aren’t done.
- First reply time, including nights and weekends — the customer-facing metric. Averages that exclude the weekend are self-deception.
- Reopen rate on WISMO replies — the honesty metric. Macro answers get reopened; real tracking answers don’t.
WISMO is the category where support automation should prove itself first: high volume, low risk, verifiable answers. It’s also where we started with our own brands — that story, including what we automated in which order, is in our ONNOA & LOVETALES case study. And if you want to see levers 3 and 4 running against your own store, the live demo resolves a real case in about a minute.