Contact center operations
WISMO: What It Means and How to Reduce Where-Is-My-Order Calls
What WISMO means, what drives where-is-my-order calls, and how retailers prevent most of them.

WISMO stands for "where is my order": any call, chat, email or message from a customer asking about the status or delivery timing of an order. For retailers and ecommerce brands, WISMO is often one of the largest contact reasons, and most of it is preventable with accurate delivery promises, proactive updates and an order status page customers can find.
It rises with every promotion, peak and delayed truck. It is also the most fixable contact in your queue, because the answer already sits in your systems.
WISMO meaning: what counts as a WISMO contact?
The WISMO meaning is simple: "where is my order". In practice, it covers every contact about order status or timing: "has it shipped?", "when will it arrive?", "the tracking hasn't moved" and "it says delivered but it isn't here".
WISMO has a sibling, WISMR, "where is my refund", which follows a return. The causes and fixes are similar, so treat them together.
The cost is not only in the contact center. A customer who cannot find their order starts to doubt it will arrive. Some cancel, some dispute the payment, and they remember the anxiety next time.
What drives WISMO calls?
WISMO calls happen when something leaves the customer uncertain: a vague promise, silence after checkout, a tracking page they cannot find, a failed delivery or status data that is not live. In many retailers, a large share come from orders that are not actually late.
Vague or wrong delivery promises
"3 to 7 working days" invites a call on day four. A promise based on a default, rather than where the stock sits, today's cut-off time and carrier capacity, will often be wrong, and the customer finds out first.
73%of US online shoppers say estimated delivery dates influence their purchase decisions, according to Narvar's State of Post-Purchase report, based on a survey of 3,461 shoppers. A clear date wins the order; a missed one creates the contact.
The date shown before checkout also matters for conversion. Surprise delivery times are one reason shoppers leave, as our guide to shopping cart abandonment explains.
Silence after checkout
After the confirmation email, many retailers go quiet until the parcel arrives. Days of silence feel like something has gone wrong, especially for gifts. Narvar's research found that when issues arise, shoppers want acknowledgement (46%), clear explanations (46%) and real-time updates (45%) before they have to ask.
Tracking customers cannot find or understand
The link sits in an email the customer cannot find, the page needs a login, or the status says "label created" for three days while the parcel waits in a warehouse. Statuses written for logistics teams ("manifested", "in transit to hub") mean little to a customer.
Failed and split deliveries
A missed delivery attempt or a split shipment where only one parcel arrives produces the angriest calls.
Status data that is not live
If order status updates from the warehouse or carrier in batches, your website and your agents see stale data. The customer calls, the agent sees the same outdated status, and the call ends without an answer, which guarantees a second one.
How much do WISMO calls cost?
Each WISMO call costs the handling time plus the systems around it, and a share also cost you the order. Calculate both, because the second number is the one that gets attention from finance.
An illustrative example, with assumptions to replace with your own:
- 20,000 orders a month.
- 12 WISMO contacts per 100 orders: 2,400 contacts a month.
- Each voice contact takes 6 minutes including wrap-up, with an agent costing $30 an hour fully loaded: $3.00 of agent time.
- Telephony, software and supervision add $2.00, so $5.00 per contact.
That is $12,000 a month, or $144,000 a year, spent telling customers something your systems already knew. Now add the hidden cost: if 1 in 20 of those customers cancels or disputes the payment, that is 120 orders a month. At an illustrative average order value of $80, that is $9,600 of revenue at risk every month, before counting customers who never come back.
The formula for your own data: monthly orders × WISMO contacts per order × fully loaded cost per contact, plus WISMO contacts × cancellation or dispute rate × average order value.
The diagnostic: tag every WISMO contact by order stage
Do not just count WISMO. Record the order stage at contact and whether the order was on time. That tells you which fix comes first.
| Order stage at contact | On time? | What it usually means | First fix |
|---|---|---|---|
| Confirmed, not yet dispatched | Yes | Customer has heard nothing since checkout | A "being prepared" update with the promise date |
| Dispatched or in transit | Yes | Tracking link missing, hard to find or unclear | Tracking link in every message, plain-language statuses |
| Any stage | No, late | Promise was wrong or a real delay happened | Fix promise logic; send delay alerts before the date passes |
| Out for delivery or failed attempt | Either | Customer cannot plan around the delivery or rebook | Delivery window and one-tap rebooking |
| Marked delivered | Yes | Parcel not found, left with a neighbor, or wrong address | Proof of delivery in the message; route to a person |
If most of your WISMO calls land in the first two rows, you have a communication problem, and it is the cheapest one to solve.
Find out how many of your WISMO calls are preventable. WiseRep AI recognizes the customer, reads the order live and can reschedule a delivery on voice or chat, and the same agent sends proactive updates that stop the question being asked. Start with a WISMO call audit: we tag a month of your contacts by order stage and show where they come from. Request your WISMO call audit.
How do you reduce WISMO? The WISMO Prevention Ladder
The WISMO Prevention Ladder is the order to fix things in: make the promise accurate, tell the customer at every stage, give them an order status page they can reach in one tap, catch exceptions before they do, and only then automate the calls that remain. Each rung removes contacts the next rung would otherwise have to handle.
| Rung | What you do | What it removes |
|---|---|---|
| 1. Accurate promise | A specific date at product page, cart and checkout, based on real stock location, cut-offs and carrier capacity | Calls caused by vague or wrong expectations |
| 2. Proactive updates | A short message at every order stage, on the channel the customer reads | Silence-driven calls in the first days |
| 3. Order status page | One-tap tracking, no login, plain-language statuses | "Has it left yet?" and "what time will it come?" |
| 4. Exception alerts | Flag at-risk orders and contact the customer first with a new date and options | Angry calls after the promise passes |
| 5. AI resolution | Voice and chat agent that reads the order live and can change it | Most of the routine WISMO that still comes in |
Accurate promises depend on accurate stock. If inventory is out of sync between channels, promises break before the parcel is picked, which is why LyraCX Commerce keeps one inventory pool and real-time delivery status across web, app and store.
What post-purchase experience prevents WISMO calls?
A post-purchase experience that prevents WISMO answers the customer's next question before they ask it, at every stage from confirmation to delivery. Send a short message at each stage on the channel customers read; Narvar found nearly half of shoppers prefer SMS, push or WhatsApp for urgent updates.
| Order stage | Message | What it prevents |
|---|---|---|
| Order confirmed | Thank you, the promise date, what happens next | "Did my order go through?" |
| Being prepared | Your order is being packed and still on track for the date | Calls in the quiet first days |
| Dispatched | On its way, tracking link with no login, split-shipment note if relevant | "Has it left yet?" |
| Out for delivery | Delivery window today, how to reschedule or redirect | "What time will it come?" |
| Delayed | New date, reason in one line, option to cancel or switch to pickup | Angry calls after the promise passes |
| Delivery failed | What happened, one-tap rebooking | "The courier never came" |
| Delivered | Confirmation, where it was left, how to report a problem | "It says delivered but it isn't here" |
TipStart with the stage that produces the most on-time WISMO contacts. Fixing one missing message there often removes more calls than a full tracking redesign.
What must an order status page show?
An order status page must show the estimated delivery date, the carrier and the stages of the delivery, in plain words, reachable in one tap without a login. If customers have to leave your site or hunt for a link, they call instead.
The research firm Baymard Institute found that order tracking ranked as the most important self-service feature in its quantitative study, and that for most users the key details are the estimated delivery date, the carrier name and the stages of the delivery process. Its testing also found that sites redirecting to third-party tracking pages often fail users' information and navigation needs, because carrier pages seldom link back to the specific order.
A practical checklist for your order status page:
- Lookup by order number plus email or phone number, no account needed.
- The promise date at the top, updated if it changes, with the reason.
- Each stage in plain language, in every language you serve.
- Split shipments shown item by item.
- Actions on the page: reschedule, change address before dispatch, switch to pickup, report a problem.
- A link from every message, the app and the help page.
Test it with real customers on a phone. Self-service often fails quietly: Gartner found that only 9% of customers report solving their issues completely via self-service.
Can an AI chatbot for customer service handle WISMO calls?
Yes, if it is connected to live order and carrier data. An AI chatbot for customer service, or a voice agent on the phone line, should resolve routine WISMO end to end: identify the customer, find the order, explain the status in plain words and offer a fix. Reading out a tracking status is not enough; the customer could have read that themselves.
- Identify the customer. Match the phone number, login or loyalty ID, so they are not asked for an order number they do not have to hand. If they have several open orders, ask which one by product, not by number.
- Read the order live. Use the order system and carrier data in real time, not a nightly copy, including split shipments.
- Explain in plain words. "Your sofa is at the local depot and due Thursday between 2 and 6 p.m." beats "In transit, hub scan complete".
- Offer changes. Reschedule the slot, update the address before dispatch, redirect to store pickup or cancel if allowed.
- Hand over the exceptions. Lost, damaged or "delivered but not received" parcels go to a person, with the order, carrier history and the customer's account already captured.
- Close the loop. Send a written summary so the customer has the date and the tracking link in hand.
The same agent can work outbound, contacting customers whose orders are at risk, which turns a reactive WISMO call into a proactive service moment. For where to draw the line between AI and people across all call types, see our guide to the AI call center for retail.
Which metrics show WISMO is under control?
The headline metric is WISMO contacts per 100 orders, tracked weekly and split by order stage and on-time status. Supporting metrics show whether each rung of the WISMO Prevention Ladder is working.
| Metric | How to calculate it | What good looks like |
|---|---|---|
| WISMO contacts per 100 orders | WISMO contacts ÷ orders × 100, all channels | Falling steadily, and stable through peaks |
| Preventable WISMO share | WISMO contacts about on-time orders ÷ all WISMO contacts | Falling as updates improve |
| Delivery promise accuracy | Orders delivered by the promised date ÷ orders delivered | High and consistent by region and carrier |
| First-attempt delivery success | Delivered at first attempt ÷ out for delivery | Rising |
| Order status page use | Visits per order, and the share followed by a contact | Many visits, few follow-up contacts |
| AI resolution of WISMO | WISMO contacts resolved by AI with no repeat contact within 7 days | Most routine WISMO resolved without a person |
| WISMO cost per order | Total WISMO handling cost ÷ orders | Falling; report it to finance monthly |
Watch these closely during peaks, when WISMO jumps with volume and delays. Our playbook on call center staffing for peak season shows how to plan people and automation for that period.
What to do on Monday
- Pull last month's WISMO contacts from every channel and calculate contacts per 100 orders.
- Sample 100 and tag each with the order stage and whether it was on time.
- Find the stage with the most on-time contacts and add or fix the message for it.
- Check your order status page on a phone: one tap from every message, no login, plain words.
- Agree with logistics how at-risk orders are flagged, and who contacts the customer.
- Decide which remaining WISMO calls an AI agent will resolve, and what it must be able to change.
Reducing WISMO for good
WISMO is a symptom of customers not knowing what your systems already know. Climb the WISMO Prevention Ladder and most of the calls disappear; resolve the rest with an agent that can see the live order and do something about it.
Both sides depend on connected data. WiseRep AI answers and acts on live order data in conversation, on voice and chat, as part of Knoativ's approach to AI customer service for retail. If you run an online-first brand, our page for ecommerce and D2C brands shows how the pieces fit.
If you want to know how many of your own WISMO calls are preventable, book a WISMO call audit. Bring a month of contact reasons and we will tag them by order stage with you and show which rung of the ladder to fix first.
Frequently asked questions
What does WISMO mean?
WISMO stands for "where is my order". It describes any customer contact, by phone, chat, email or social media, asking about the status or delivery timing of an order. It is often one of the largest contact reasons for online retailers. A related term, WISMR, covers "where is my refund" contacts that follow a return.
How do you reduce WISMO calls?
Prevent the uncertainty behind them. Show an accurate delivery date at checkout, send proactive updates at each order stage, put a no-login order status page link in every message and alert customers to delays before the promised date passes. Then let an AI agent resolve the remaining calls by reading the order live and offering changes such as a new slot.
What should an order status page include?
An order status page should show the estimated delivery date, the carrier and each stage of delivery in plain language, without requiring a login. It should handle split shipments item by item and let customers act: reschedule, change the address before dispatch, switch to store pickup or report a problem. Link to it from every order message and the app.
What is a good WISMO rate?
There is no universal benchmark, because products, delivery times and channels vary widely. Measure WISMO contacts per 100 orders for your own business, split by order stage and on-time status, and aim for a steady decline. The most useful target is the share of WISMO contacts about orders that were on time, which should approach zero.
How does the post-purchase experience affect WISMO?
The post-purchase experience decides whether customers need to ask at all. A specific promise date, a message at each stage, plain-language tracking and early delay alerts answer the question before it becomes a call. Silence after checkout, vague date ranges and carrier jargon do the opposite, and they also make customers less likely to order again.


