What is WISMO?
WISMO is the category of inbound customer contacts that ask about an order's status: where a package is, when it will arrive, why tracking has not updated, and what happens when a delivery date slips. It is demand generated by fulfillment that lands on support.
The pattern is predictable. One order can generate several WISMO contacts: one after checkout, one when a carrier scan goes quiet for two days, one on the promised delivery date, and one after that date passes. Each is cheap to answer and expensive in aggregate.
What does WISMO stand for?
WISMO stands for "where is my order", the sentence customers type almost verbatim into a chat window. The full form is used as a noun by support and ecommerce teams: WISMO tickets, WISMO calls, WISMO volume, WISMO rate. Retail operations teams often pair it with WISMR, "where is my return", which behaves the same way on the reverse leg of the journey and shares most of the same data.
How WISMO works
A WISMO contact is the last step in a chain that starts long before support sees it. Four layers sit between a purchase and an answer: the order management system holding the order record, the fulfillment and carrier layer that moves the parcel and emits scan events, the notification layer that tells the customer what just happened, and the support layer that fields whatever the first three failed to communicate.
Failure in an upper layer pushes work downward. Smart order routing that splits one order across two warehouses produces two shipments and two tracking numbers, and a customer holding one box will ask about the other. A carrier scan that stalls for 48 hours creates a silence the customer fills with a ticket, which is why WISMO tracks fulfillment exceptions far more closely than it tracks marketing volume.
Every gap becomes measurable downstream. It lifts ticket volume in the week after a delayed dispatch, and when the self-service tracking view cannot answer a question, it drags deflection rate down with it.
Types of WISMO contacts
WISMO is one label covering five distinct situations, and they need different fixes.
Pre-shipment WISMO: The order is paid but not dispatched, and the customer checks in during the gap before a tracking number exists.
In-transit WISMO: Tracking is moving normally, and the customer wants a firmer date than the carrier's multi-day window offers.
Stalled-scan WISMO: Tracking has not changed for several days, and the customer wants confirmation the parcel still exists.
Missed-delivery WISMO: The promised date passed, or the parcel is marked delivered with nothing at the door, which is the angriest variant.
Split-shipment WISMO: One order arrived in pieces, and the customer believes items are missing rather than in transit.
WISMO vs order tracking vs proactive notifications
These three get discussed as if they were one program, and the confusion decides where budget goes. Order tracking is a self-service surface showing a customer the current state of a shipment when they go looking for it. Proactive notifications are outbound messages pushing a state change to the customer before they go looking. WISMO is the residual demand arriving when neither surface answered the question the customer actually had. Two of the three are things you build; the third is the number telling you whether the build worked.
What it holds | Ownership | Who reads it | AI-retrievable | Choose it when | |
|---|---|---|---|---|---|
WISMO | Inbound contacts asking for order status | Support, though the causes sit in operations | Agents and AI agents | Yes, once order data is connected | You need to size and diagnose the problem |
Order tracking | Live shipment state on a page or widget | Ecommerce or CX engineering | Customers who come looking | Yes, through order and carrier APIs | Customers are willing to self-serve |
Proactive notifications | Pushed status events by email or text | Lifecycle marketing or CX operations | Customers who never asked | Partly, since delivery is outbound | Silence is what triggers the contacts |
If contacts are climbing, instrument WISMO first so you know which stage produces them, then fix that stage: pre-dispatch silence is a notification problem, stalled scans are an expectation problem, and split shipments are an order-communication problem.
Why WISMO matters for customer experience
When WISMO goes unmanaged, the cost lands in two places at once. The customer experiences silence: money has left their account, the box has not arrived, and the only route to information is a ticket that eventually quotes the same carrier page they already read. The support team experiences displacement: queue time spent on lookups is queue time unavailable for refunds, damage claims, and pre-sales questions that carry revenue.
Status questions are also the most automatable contacts in the queue, so teams that never touch them pay a premium for their simplest work while harder cases wait. Those harder cases are the ones that lift escalation rate, and they reach a human after a longer wait than they should have.
The tradeoff is real: aggressive automation of status answers can strand the small share of customers whose parcel is genuinely lost, and those are exactly the contacts where a wrong answer costs the relationship.
How is WISMO measured?
WISMO is measured two ways, and teams tracking only one misread their own progress. WISMO rate divides WISMO contacts by total support contacts in the period, showing how much of the queue is status work. WISMO contacts per hundred shipped orders divides WISMO contacts by orders shipped, showing whether fulfillment communication improves as the business grows.
The two numbers can move apart. If other contact reasons grow faster, the WISMO share falls while the absolute number of status contacts rises, so a falling percentage does not prove fewer customers are asking.
Cost per contact is the third number. The U.S. Bureau of Labor Statistics puts median pay for customer service representatives at USD 20.59 an hour and USD 42,830 a year in 2024, so a status lookup consuming four to six minutes of agent time costs roughly USD 1.37 to USD 2.06 in wages alone, before tooling, supervision, or the price of the customer's wait.
How AI agents change WISMO
An AI agent changes WISMO by turning a lookup into a resolved conversation. The mechanism is retrieval plus action: the agent verifies the customer, reads the order record from the commerce platform, pulls the most recent carrier scan, compares it against the promised delivery window, and applies the brand's own rule for what happens when a parcel has been stalled past a set threshold. Reshipping, refunding, or opening a carrier claim happens inside the same turn.
Two consequences follow. Status work stops competing for agent attention, because it resolves without ever entering a queue. And exceptions surface earlier, since an agent checking the promised window on every single contact catches late orders that a busy human would have accepted at face value. Retailers running this through peak season describe the operational detail in this guide to AI for WISMO tickets.
How to reduce WISMO volume
Reduction runs on four levers. Set the expectation before dispatch, since a delivery window on the product page and in the confirmation email removes the first wave of contacts. Push status outward, because proactive customer support at dispatch, at the stalled scan, and at the exception converts a would-be ticket into a message. Put a tracking view behind the customer's login so the answer arrives without an agent. Fix the fulfillment cause, since split shipments and optimistic promise dates generate contacts no messaging can absorb.
Four axes decide the tooling. Integration surface: does it read the order management system and the carrier feed, or only a help center. Exception coverage: can it reship, refund, and file a claim. Governance: who owns promise dates and message copy. Data handling: buyers routinely ask for SOC 2 Type II evidence and name GDPR in the contract when order and address records leave their systems. The constraint that bites hardest is carrier scan latency, because no automation can report an event the carrier has not yet emitted.
WISMO and post-purchase support
WISMO is one contact reason inside a wider post-purchase queue, and it shares plumbing with the rest of it. The order record that answers "where is my parcel" also answers "can I still return this", which is why teams automating returns and refunds workflows usually start with status. Channel choice matters too: short message service (SMS) reaches someone standing at a door with no app installed, and a delivery-day text often removes the contact outright. Together, status and returns explain most of the contact rate a brand carries after checkout.
What does WISMO mean in plain terms?
Think of WISMO as the sound a supply chain makes when it stops talking. The acronym is literally the customer's own sentence, where is my order, and nobody sends it for entertainment. They send it because a promise was made at checkout and nothing has confirmed that promise since.
If the brand had sent one message at dispatch, one when the parcel stalled, and one on the delivery day, most of those customers would never have opened a chat window at all. The contact is the invoice for the silence.
The tradeoff is that messaging has a ceiling. Send an update for every scan event and customers stop opening any of them, so the one message that mattered, the exception, gets ignored along with the noise, and the contact still arrives, later and angrier than it needed to be.
Common WISMO mistakes
Four patterns account for most of the wasted effort.
The first is treating WISMO as a support problem. Support is where the contacts land, but the causes are merchandising promise dates, routing rules that split orders, and warehouse cut-off times. A better macro never touches any of those.
The second is answering the literal question while missing the real one. The customer wants a date they can plan around; a repeated tracking link supplies motion without a commitment, so the same customer returns two days later.
The third is automating the healthy state and abandoning the exception. Containment looks excellent while the lost-parcel customers loop through the same flow three times, and those are the accounts most likely to churn.
The fourth is counting a deflection at the widget. A session that ends without an answer gets logged as a save, and the customer re-contacts by email the next morning under a fresh ticket ID, which quietly inflates both numbers.
What causes WISMO tickets?
WISMO tickets are caused by a gap between what a customer was promised at checkout and what they can see afterwards. The usual triggers are a delay between payment and dispatch, a carrier scan that stops updating, a split shipment arriving in pieces, and a promised delivery date that passes with no explanation.
What is the difference between WISMO and order tracking?
WISMO is inbound demand: customers contacting support to ask where an order is. Order tracking is the self-service surface showing shipment state to a customer who goes looking for it. Order tracking is one of the tools that lowers WISMO, and the WISMO count is how a team finds out whether it actually worked.
WISMO rate vs contact rate: what is the difference?
WISMO rate measures the share of support contacts asking about order status, so its denominator is total contacts. Contact rate measures how many customers or orders generate any support contact at all, so its denominator is customers or orders. Track both, because a WISMO share can fall while total status contacts grow.
How do you calculate a WISMO rate?
WISMO rate divides WISMO contacts by total support contacts in the same period, then multiplies by 100. If 1,200 of 4,000 monthly contacts are status questions, the WISMO rate is 30 percent. Pair it with WISMO contacts per hundred shipped orders, which stays honest when order volume swings seasonally.
Can AI agents resolve WISMO tickets on their own?
AI agents resolve most WISMO contacts end to end once they are connected to the order system and the carrier feed, because the answer is a lookup plus a policy decision. The cases worth routing to a person are lost parcels, disputed deliveries, and high-value orders where a reship or refund decision carries real cost.
Does proactive notification reduce WISMO?
Proactive notification reduces WISMO when the messages carry information the customer cannot already see: a delay, an exception, a revised delivery date. Repeating a scan event the tracking page already displays adds noise and trains customers to ignore the channel, so the one message that would have prevented a contact goes unread.