WISMO stands for "where is my order." It is the flood of questions customers send after they buy, asking where their package is and when it will arrive. Most WISMO tickets are not support problems, they are information gaps: the customer bought something, the order went quiet on the carrier side, so they came to you. The fix is not more agents. It is telling people what is happening before they have to ask, which is exactly what Pango is built to do.
What WISMO means and where the term comes from
WISMO is a support acronym that groups every "where is my order" contact into one bucket, whether it arrives by email, chat, or phone. It earns the label: Gorgias reports that "where is my order" is the most common question in ecommerce, about 18% of incoming support requests on average.
The name is useful because it names the pattern, not the channel. A WISMO ticket looks the same whether the customer asks about a delay, a missing scan, or a delivery that never showed. What they all share is one thing: the customer lost visibility and wants it back.
Why WISMO tickets pile up after checkout
Checkout is the last clear moment a customer has. They pay, they get a confirmation, and then the order disappears into the carrier network. From there they are guessing, and if nothing reaches them for three days, they come to you to close the gap.
Carrier tracking pages do not help much. They are cold, generic, and often show a raw status the customer cannot read. A scan that says "in transit, facility departure" tells a shopper nothing about when the box lands, so they open a ticket. For how those labels work, see our guide to carrier tracking statuses. With Pango, you close that gap on your own domain: branded tracking that translates the raw scan into a milestone the customer actually understands.
The real cost of a WISMO ticket
Every WISMO ticket costs money and attention. It ties up an agent, delays the customers who have real problems, and leaves the shopper feeling ignored while they wait for a reply. Worse, it scales with order volume, so the busier you get, the more of the day your team spends reading tracking pages back to customers instead of solving anything.
The stakes go past the minutes spent. In a 2024 Statista survey cited by Salesforce, 44% of US consumers said they stopped shopping with a company after a single poor customer service experience.
| Cost of WISMO | What it hits |
|---|---|
| Agent time per ticket | Support payroll and queue length |
| Slower replies to real issues | Customers with genuine problems wait |
| Repeat contacts on one order | One order becomes three tickets |
| Lost trust during the silence | Fewer repeat purchases |
Every line in that table is avoidable. That is the whole reason Pango automates the update instead of waiting for the question, so the ticket, and its cost, never lands.
Proactive updates: answer before they ask
Reactive support waits for the question, then answers it. The customer notices the silence, gets anxious, writes in, and only then learns where the order is. By then the mood is sour.
Proactive updates flip that. You tell the customer what happened the moment it happens, so the ticket never gets created. The updates that matter are tied to real events:
- Shipped: the order is on its way, with an expected date.
- Out for delivery: it should arrive today.
- Delayed: it is running late, here is the new date and what happens next.
- Delivered: confirm it landed, and catch a wrong scan fast.
Delays are the painful ones, because the customer is already frustrated by the time they reach you. This is where Pango carries the load:
- It catches the delay first. Pango treats a carrier delay or exception scan as an operational trigger, not a status someone has to notice.
- It sends the message automatically. That scan becomes a short, honest update with an accurate delivery date and the next step, through Klaviyo or Pango's own email and SMS.
- It reads every carrier the same way. Pango normalizes the 10 to 115 statuses carriers return into clear milestones, so the customer never sees a raw code.
- It runs on live shipment data. The updates fire off the same delivery management layer that knows where the parcel is, feeding the branded tracking page the customer checks.
A shopper who hears "delayed by a day, here is the new date" rarely writes in. One who finds a stalled tracking page almost always does. That gap is the entire WISMO problem, and Pango closes it automatically. To see it on your own orders, book a demo.
