“Where is my order?” — WISMO — is the single most common contact in retail support, and in most stores it accounts for a large minority of all tickets. The questions are repetitive, the answers are sitting in systems the customer can’t see, and every one ties up an agent who could be handling something that needs judgement. WISMO is the clearest, lowest-risk place to start with helpdesk automation, because the right answer almost always exists in data you already hold.
Why WISMO dominates your queue
WISMO volume is a symptom, not just a workload. Customers ask because the experience after checkout left them uncertain. The usual drivers:
- Tracking that stops updating between handover and delivery, especially on cross-border shipments.
- No proactive notification, so the only way to learn anything is to contact you.
- Vague delivery promises (“3–5 working days”) that customers can’t reconcile with reality.
- Split or partial shipments where one tracking number tells half the story.
Automating the answer without addressing these causes just makes a bad experience faster. The most effective WISMO programmes do both: deflect the contact and shrink the reason for it.
The data you need first
An order-status bot is only as good as the data feeding it. Before building anything, confirm you can reliably retrieve, in near real time:
- Order state from your commerce platform (placed, paid, picked, packed, dispatched, delivered).
- Carrier tracking events, normalised across carriers — each uses different status vocabularies.
- Customer identity matched to the order, so you answer the right person securely.
- Expected delivery date, ideally a live estimate rather than the static promise made at checkout.
If these live in disconnected systems, fix the plumbing first. Reliable retrieval depends on the kind of clean, joined-up data we cover in data insights; a bot that occasionally returns the wrong order’s status will destroy trust faster than no bot at all.
Designing the automated flow
A good WISMO flow is mostly retrieval, with generation used only to phrase the answer clearly. Keep generation grounded in retrieved facts.
Identify the order without friction
For logged-in customers, infer the order from their account. For guests, ask for order number plus email or postcode — never expose order details on a single weak identifier. Where a customer has one recent open order, surface it proactively: “Looks like you’re asking about order #10482, dispatched Tuesday — here’s where it is.”
Translate carrier events into plain language
A raw event like IN_TRANSIT — DEPOT_SCAN_HUB3 means nothing to a customer. Map carrier statuses to a small set of human states: preparing, on its way, out for delivery, delivered, delayed, problem — needs attention. The last two are the ones that must escalate cleanly.
Set expectations, don’t just report
The best answers say what happens next: “It’s with the carrier and due Thursday. If it hasn’t arrived by Friday, reply here and we’ll open a claim.” This pre-empts the second contact, which is where the real cost hides.
Handle the hard cases deliberately
Most WISMO is simple, but the exceptions are exactly when customers are anxious. Route these to a human with full context attached:
- Past the promised date with no recent tracking movement.
- Carrier reports delivered, customer says not received. Sensitive, sometimes fraud-adjacent — never auto-resolve.
- Lost, damaged, or returned-to-sender.
- Split shipments where only part has arrived.
Your guardrails should make the AI hand off rather than guess; our notes on support guardrails explain how to draw that line. A confidently wrong “it’s on its way” to someone whose parcel is genuinely lost is the fastest route to a one-star review.
Be proactive: the contact you prevent
The cheapest WISMO ticket is the one that never arrives. Proactive status updates — dispatch confirmation, an out-for-delivery nudge, a delay alert before the customer notices — typically remove a meaningful slice of inbound volume on their own. Pair automation with proactive messaging and you attack the queue from both ends. This is the same prevention-first thinking behind reducing cart abandonment: solve the worry before it becomes a contact.
Connecting WISMO to the wider channel
An order-status bot rarely stays purely transactional, and that is a good thing. The customer who has just learned their parcel is “out for delivery” is in a positive frame of mind — a natural moment for a relevant prompt (“set up delivery notifications?”, “rate your experience once it arrives?”). The customer whose parcel is delayed is the opposite, and the right move there is empathy and a concrete remedy, never a sales nudge.
Mapping these emotional states is part of what makes WISMO automation worth more than the tickets it deflects:
- Positive resolution (“delivered”, “out for delivery”) — light, optional engagement; an opportunity for reviews or reorder reminders.
- Neutral resolution (“on its way, due Thursday”) — set expectations, offer notifications, then get out of the way.
- Negative resolution (“delayed”, “problem”) — apologise, give a clear next step, and make escalation effortless.
Treating WISMO as a relationship touchpoint rather than a lookup is the same instinct behind turning support into a revenue channel — the difference between a store that merely answers and one that builds loyalty with every interaction.
A rollout checklist
- Instrument the baseline — what share of tickets are WISMO today, and what do they cost? (Our framework for support automation ROI helps here.)
- Verify retrieval reliability across your top carriers before launch.
- Launch on a single channel (chat or email) and one market.
- Define escalation triggers for the hard cases above.
- Add proactive notifications in parallel.
- Measure resolution and reopen rates, not just deflection.
- Tune the carrier status mapping monthly as exceptions surface.
What good looks like
A mature WISMO automation resolves the routine majority instantly and around the clock, recognises the anxious exceptions and routes them to a person with full context, and — through proactive messaging — steadily reduces the volume of questions in the first place. Agents stop reciting tracking numbers and start handling the cases that actually need a human.
WISMO is where most teams should begin, precisely because the answers are knowable and the risk is contained. Done well, it frees capacity, lifts satisfaction, and builds the data discipline every later automation depends on.
If you would like help scoping an order-status automation against your own ticket mix and carrier setup, get in touch.