How to reduce "where is my order?" contacts
WISMO is the single biggest contact driver in e-commerce support. Proactive tracking updates, SMS self-service, and OMS integration can resolve most of it before a customer ever reaches the queue.
On this page
The most predictable contact in retail
"Where is my order?" — WISMO, in industry shorthand — is usually the largest single category of inbound contact an e-commerce support team handles, and during peak season it can dominate the queue. It's also the most solvable: the customer isn't angry, doesn't have a judgment call to make, and wants exactly one fact you already have.
A WISMO contact that reaches a live agent is almost always a process gap, not a service need. This guide covers the three layers that close the gap.
Layer 1 — proactive updates, before the customer asks
Most WISMO contacts happen because the customer's information ran out: the confirmation email said "arriving Tuesday," Tuesday came, and nothing updated. Proactive notification fills that silence:
- Order received, shipped, out for delivery, delivered — the standard milestones, by SMS or email per the customer's preference
- The delay message — the one that actually prevents calls. When the carrier scan goes stale or the promise date slips, tell the customer first, with a new estimate and a self-service link
- Exception paths — address problems, failed deliveries, and weather events get their own message and their own next step
Teams consistently find the delay message is the highest-value notification they send: a customer who hears "your order is delayed, here's the new date, tap here if that doesn't work" rarely calls. A customer staring at a stale tracking page almost always does.
Layer 2 — self-service that actually resolves
When a customer does reach out, the first responder shouldn't be a human for a status question. Conversational self-service — on chat, SMS, or voice — can authenticate the customer, pull the order from Shopify, NetSuite, or your OMS, and answer in seconds:
- Current status and carrier tracking, read back in plain language
- Updated delivery estimate when the original has slipped
- Next-step options in the same conversation: update the address, start a return, request a reship
The design rule that keeps self-service from becoming the new IVR maze: every flow has a clean exit to a human, and the handoff carries the conversation. The agent who picks up sees the order, the question, and what self-service already tried — the customer never repeats the story.
Layer 3 — agents with the order on screen
Some WISMO contacts should reach an agent: the $400 order with no carrier scan in five days, the gift that must arrive by a date, the customer on their third contact. For those, the economics depend on handle time, and handle time depends on context:
- Order status, tracking history, and return eligibility on the agent desktop at hello — no tab-hopping into the OMS
- AI-suggested next best action based on the order profile: reship, refund, replace, or escalate
- One-click SMS follow-up with tracking or label links, logged to the same interaction
Measure it like a funnel
WISMO reduction is measurable, which makes it a rare support project that finance likes:
- Order-status contact rate — WISMO contacts per 100 orders, the headline number
- Deflection vs. resolution — of WISMO contacts that hit self-service, how many were resolved rather than just deflected
- Proactive open/click rates — are the delay messages landing
- Repeat-contact rate — a customer asking twice means the first answer didn't hold
Track the rate per 100 orders rather than raw volume, so growth and peak season don't hide your progress.
The short version
WISMO is a data problem wearing a staffing costume. Send the delay message before the customer notices, let self-service answer the status question with live OMS data, and give agents the order on screen for the contacts that genuinely need judgment. Teams that do all three turn their largest contact category into their shortest.
Back to
Industries
Return to the main industries page to see the full product family.
Related guides
Guide
The year-end giving campaign playbook — planning the December surge without burning out your team
Compliant appeal outreach, SMS-first touchpoints, volunteer staffing with one-day onboarding, secure donation processing at volume, and the post-campaign follow-up that turns December givers into January donors.
Guide
The TAS migration checklist — moving off a legacy answering service platform without losing a client
Importing client scripts, rebuilding dispatch rules, preserving on-call contact trees, migrating reporting formats, parallel testing high-risk clients, and sequencing go-live so nothing breaks at 2 a.m.
Guide
The subscriber retention playbook — saves, win-backs, and the calls that keep circulation alive
Renewal reminders, price-increase notices, cancellation save offers, payment-failure outreach, and win-back campaigns — plus the two numbers that tell you whether any of it is working.