A "where is my order" (WISMO) call happens when a shopper senses something has gone wrong before anyone has told them, or when nobody told them what to expect in the first place. Many WISMO contacts aren't really questions about tracking. They're the visible end of an operational exception: a parcel running late, a failed attempt, a parcel left somewhere odd, a tracking page that hasn't moved. If you want fewer "where is my order" calls for good, resolve the exception and tell the shopper first, rather than only answering the question faster.
Better tracking does cut the contacts caused by uncertainty. It does little for the ones caused by a parcel that has actually gone wrong, and those are the expensive ones.
How big is the WISMO problem, really?
You'll see many figures for WISMO's share of support contacts, often 40% or more. Be careful with them. A review of the most-cited numbers found no verifiable primary source for the share of ecommerce contacts that are WISMO, and traced the popular 40% figure to a vendor blog quoting a peak-season estimate 1.
The number that matters is yours, and it's cheap to get. Take one month of contacts, tag each WISMO contact by cause (late, failed attempt, marked delivered but not received, tracking not updating, unclear promise) and note whether the shopper contacted again about the same order. That tells you which fixes will pay off.
What is well measured is how often parcels go wrong. In Ofcom's 2025 research on UK parcel delivery, 68% of consumers had experienced a delivery issue in the previous six months. The two most common were a delayed delivery (28%) and a parcel left in an inappropriate location (26%). Incorrect or insufficient tracking was reported by 14% 2. Fewer than half (45%) of those who contacted a parcel operator were satisfied with the process 2.
Why do WISMO calls happen?
The parcel is actually late. A route is running behind, a vehicle broke down, a linehaul departure was missed. The promised window passes and nothing explains why.
The tracking is wrong or silent. The status still says "out for delivery" after the driver's shift has ended, or it hasn't changed in two days. The shopper doesn't trust it and calls to find out what's really happening.
The attempt failed, or the parcel landed somewhere unexpected. The driver couldn't get access, left it with a neighbor, or marked it delivered when it wasn't. The notification doesn't match reality.
The promise was never clear. A vague "3 to 5 business days" invites the question on day three.
The first three are operational exceptions. Only the fourth is purely a communication problem.
Why don't tracking links and chatbots fix it?
A clearer delivery promise and accurate tracking reduce the fourth cause and much of the second. A chatbot that reads the tracking status answers faster than a person. Both are worth having.
But neither one changes the parcel. When the status is wrong, a status-reply bot repeats the wrong status. When the parcel is late, it says so. The shopper then either waits and contacts again, or reaches an agent who has to do the real work: find out what happened, contact the depot or the carrier, arrange a recovery, and come back with an answer. That second contact, and the agent's time spent chasing the operation, is where the cost sits.
How do you close a WISMO case automatically, step by step?
Closing a WISMO case means doing the operational work behind it. An AI worker set up for customer resolution follows the same steps a good agent would, without the queue. The steps differ depending on whether you run your own fleet or ship through carriers.
- Read the contact and pull the full record. The order, the shipment, previous messages and any earlier cases for the same order. With your own fleet, add the route and the driver's last position. With carriers, add the carrier's tracking events.
- Find out what actually happened. With your own fleet, compare the plan with reality and, if the systems disagree, call or message the driver or depot. With carriers, check the tracking events against the promise and contact the carrier when they don't explain the delay.
- Decide what should happen, within policy. Redeliver, redirect to a pickup point, raise a recovery, contact the carrier when a parcel is marked delivered but not received, or offer a goodwill gesture if the account terms allow it.
- Act on the operation. With your own fleet, rebook the slot, update the TMS and notify the depot. With carriers, contact the carrier, chase it to an answer, and arrange an approved recovery. Status-reply automation stops before this step.
- Answer with the outcome, not the status. "Your parcel missed today's route because of a vehicle fault. It's booked on tomorrow's first route, arriving between 8 and 10 am" closes the question. "Your parcel is delayed" invites the next one.
- Follow through. Watch the new promise. When the proof of delivery comes in, confirm it. If it slips again, act before the shopper has to ask.
Anything outside the worker's authority, such as a refund above the agreed limit, a vulnerable shopper or a commercial dispute, goes to a person with the investigation already done.
Can you stop the call before it happens?
Yes, for many of them. A proactive update worker can watch for the signals that produce WISMO contacts: a route falling behind its plan, a failed attempt, a tracking event that hasn't arrived when it should. When it sees one, the exception gets resolved and the shopper hears about it first. For a retailer, that turns "Where is my order?" into "We've already moved your delivery, and here's the new time."
What should you measure?
- Contacts per order, not just contact volume, so growth doesn't hide improvement.
- Repeat contact rate for the same order. It shows whether you answered the question or resolved the problem.
- Share of WISMO cases closed with an operational action (rebook, redirect, carrier claim, recovery) versus a status reply.
- Proactive notifications sent before the shopper made contact, and how many of those shoppers contacted anyway.
- Time from exception to shopper notified, measured from the operational signal, not from the call.
Run the cause tagging again each quarter. The mix will shift as fixes land.
Where does Finmile fit?
The goal is a contact that gets closed once, with the delivery already fixed. Finmile Autonomy does this with AI workers across the service desk, order and transport systems a team already uses, sitting where agentic AI, operational AI and logistics software overlap. A Customer Resolution worker reads the contact, investigates the cause across systems and conversations, acts on the operation by rebooking, rerouting, reassigning or recovering, answers with the outcome, and follows up when the new promise has been met. A separate Proactive Update worker tells shoppers before they have a reason to make contact.
Authority is set by the business. The Customer Resolution worker runs supervised: routine actions such as rebooking inside policy can run on their own, a goodwill credit above the agreed band needs approval, and changes to contractual terms always escalate. Teams that want to run planning, execution, proof and customer communication on one system can use Finmile OS, with Finmile Autonomy built in.
Sources
- Macha, Ecommerce Customer Service Statistics 2026: review of WISMO share claims and their sources. ↩
- Ofcom, Measuring user experience of parcel delivery to residential addresses, October 22, 2025; figures as reported by ChannelX, October 22, 2025. ↩
- Finmile, Customer Service.