How to Reduce WISMO Calls: A Practical Guide for Retail Logistics Teams

What WISMO Calls Are and Why They Spike

WISMO stands for “where is my order.” These are inbound contacts, by call, chat, or email, from customers who could not find their delivery status on their own.

Volume spikes for four reasons, and none of them is impatience:

• Tracking data is absent, delayed, or inaccurate
• Delivery windows are too wide or missed too often
• A failed attempt leaves the customer without a clear next step
• Carrier handoffs create gaps between your systems and the customer’s view

The pattern underneath all four is the same. The delivery chain is producing uncertainty, and customers are closing that gap by contacting your support team. Support volume is the symptom; the uncertainty is the condition.

The Real Cost, and How to Actually Quantify It

WISMO carries four distinct costs: agent handling time, displaced higher-value support work, the retention effect of a delivery experience that felt out of control, and escalation risk when a first contact resolves nothing.

Here is the honest position on quantifying it. No research firm publishes a credible cost per WISMO contact or a cross-industry contact-rate benchmark. The figures that circulate, typically a dollar range per contact and a percentage of total support volume, trace to vendors rather than research, and they vary widely enough to be useless in a business case. A CFO who checks will find that out, which makes borrowing them a poor trade.

Measure two numbers instead, both of which you already have:

Your fully loaded cost per contact. Agent time, tooling, management overhead, and escalation handling, divided by contacts. Your support organization can produce this in an afternoon and will defend it in a review, which no published figure will.

Your WISMO contacts per thousand deliveries. Normalize per thousand rather than as a percentage of support volume, because support volume moves for reasons unrelated to delivery and will muddy the trend.

Multiply the two for your monthly exposure, then hold the methodology fixed and track it against each change you make. That single discipline turns WISMO from an anecdote into a managed line, and it makes the eventual improvement attributable.

The reason the number is usually larger than expected: last-mile carries 41 to 53% of total logistics cost, per Capgemini last-mile research, so communication failures concentrated in the final leg sit on top of the most expensive segment in the network.

Root Causes: The Four Points Where Visibility Breaks

Most teams treat WISMO as a messaging problem. It is a data problem, and it breaks in four specific places.

1. The confirmation-to-dispatch gap. Customers receive nothing between purchase and the moment the order leaves the facility. For a next-day order that is a few hours of silence; for a scheduled delivery it can be days, and it is where the first contact originates.

2. The last-mile handoff. When an order transfers from your hub to a driver or a third-party carrier, tracking frequently goes dark for the period that matters most to the customer.

3. The failed attempt. Without immediate notification, customers discover a missed delivery hours later, and the contact that follows is both certain and avoidable.

4. The multi-carrier environment. With several transporters involved, tracking data sits in separate systems and never reaches the customer as one coherent view. This is the hardest of the four and the most common in enterprise retail.

Closing these four is what reduces WISMO. Updating the FAQ page is not.

Five Tactics That Close the Gaps

1. A Live Customer-Facing Tracking View

The single highest-impact change, because it converts a support interaction into self-service. To work, it has to update as the driver moves rather than at milestone scans, show a live ETA rather than a date window, offer a contact route where appropriate, and handle exceptions including delays and rescheduling without requiring a call.

The condition is accuracy. A tracking page that proves wrong twice teaches the customer to contact support instead, and at that point the page is generating volume rather than deflecting it.

2. Proactive Notification

Customers contact you when they are surprised. A notification sequence removes the surprise: dispatched, out for delivery with a tightened window, a short-notice alert before arrival, and immediate notification with next steps if an attempt fails.

The operative word is proactive. A notification that arrives after the customer has started wondering has already lost the contact it was meant to prevent. Worth adding a materiality threshold so customers hear about changes that matter rather than every recalculation.

3. ETA Accuracy

Wide or unreliable ETAs are a leading driver. “Delivery between Monday and Thursday” is not an estimate, it is an invitation to make contact.

Accuracy depends on three upstream things: route optimization that models live traffic and realistic service time rather than averages, capacity management that prevents overloading a driver and pushing every downstream ETA later, and dynamic routing that revises when conditions change mid-route. A two-hour window generates far fewer contacts than a four-day one, and the width of the window you can honestly offer is set by planning quality rather than by marketing.

4. Fewer Failed First Attempts

A failed attempt reliably generates contact, often twice: once to find out what happened and again to arrange redelivery.

Reducing failures requires address capture and validation at checkout rather than at dispatch, pre-delivery communication that confirms availability, and delivery-linked checkout that lets the customer choose a window the operation can actually hold. That last one is the least implemented and the most effective, because it removes the mismatch between when delivery is attempted and when anyone is home.

5. A Control Tower Your Team Can Act From

Support agents cannot resolve a WISMO contact if they know no more than the customer does. A control tower gives operations live visibility across every active delivery, so the team can identify delays before customers notice, reach affected customers with revised ETAs, and resolve exceptions without waiting for a driver to report back.

The qualifier matters more than the capability. Gartner research finds 95% of supply chains must react quickly to change while only 7% can execute decisions in real time, per Gartner supply chain research, and among large shippers only 22% of those above $1 billion in revenue believe their control tower is highly effective at driving action, per Gartner control tower research.

Most retail operations have already bought visibility. What reduces WISMO is visibility wired to action, with exceptions ranked by remaining recovery window and resolvable from the same surface where they appear.

Why Fixing One Tactic Underdelivers

WISMO is the combined output of four gaps, so closing one moves the number partially and closing all four moves it structurally.

The dependencies run in a specific direction. A tracking page is only as good as the ETA behind it. The ETA is only as good as the plan behind that. The plan holds only if the operation can re-decide when the day moves. And the failed attempt that generates two contacts is prevented at checkout rather than at the doorstep.

That is why a notification project bolted onto unreliable ETAs disappoints: it tells customers more often about something the operation still cannot predict.

Where Locus Fits

Locus addresses the four root causes on one decisioning layer rather than as separate tools, which matters because the dependencies above run across all of them.

Customer-facing tracking and notifications are generated from the same operational record that plans and dispatches the delivery, so the ETA a customer sees is the one the operation is working to. Route optimization decisions against 250+ real-world constraints, which is what makes a two-hour window offerable rather than aspirational. Delivery-linked checkout exposes window feasibility at the point of purchase, so the promise is validated against capability rather than asserted. And the control tower surfaces at-risk deliveries with the ability to act from the same surface.

Locus is the world’s first Decision-Intelligent, Agentic Transportation Management System, with 1.5B+ deliveries orchestrated for 360+ enterprise customers across 30+ countries at 99.99% uptime, and carrier reach through ShipFlex connecting a 1,000+ carrier network with 160+ pre-integrated carriers. A retail enterprise consolidating six legacy systems onto it sustained 99%+ on-time delivery while reducing manual dispatch effort by more than 80%. Locus is ranked #1 in Route Planning on G2.

Learn more, visit locus.sh

FAQs

What does WISMO stand for?
“Where is my order.” It refers to inbound customer contacts by call, chat, or email asking for a delivery status update. High volume indicates a visibility gap in delivery operations rather than a customer service failing.

What is a realistic target for reducing WISMO calls?
That depends entirely on your baseline and which of the four root causes dominates in your operation, which is why published reduction percentages mislead. Establish your contacts per thousand deliveries first, then set a target against your own number rather than an industry figure.

How much does a WISMO contact cost? No research firm publishes a credible figure, and the ranges that circulate trace to vendors rather than research. Calculate your own fully loaded cost per contact from agent time, tooling, overhead, and escalation handling. Your support team can produce it quickly and it will hold up in a review.

How does a customer-facing tracking page reduce WISMO calls?
It converts a support interaction into self-service, provided the data is live rather than a static estimate. The condition is accuracy: a page that proves wrong twice trains customers to contact support instead, at which point it generates volume rather than deflecting it.

Why do failed deliveries generate so many WISMO contacts?
Because a failed attempt creates two triggers rather than one: the customer contacts you to find out what happened, then again to arrange redelivery. Preventing the failure removes both, which is why first-attempt success is the highest-leverage WISMO lever available.

What is the difference between proactive notifications and order tracking emails? Tracking emails fire at fixed events such as order confirmed and order shipped. Proactive notifications update from live delivery progress, tighten the window on the day, and alert immediately when an exception occurs. The difference is whether the message reaches the customer before or after they start wondering.

Does route optimization affect WISMO volume?
Directly. Optimization produces tighter, more reliable ETAs by modeling live traffic, realistic service time, and vehicle capacity. Unreliable ETAs are a leading driver of contact, so the width of the window you can honestly offer is set by planning quality.