WISMO, the where is my order question, is the clearest signal of post-purchase health. When tracking is clear and updates are proactive, those tickets fall. When they are not, support drowns. This benchmark report looks at WISMO and tracking performance using public data and the operational trends we see across Pango brands. We frame our own numbers qualitatively until they are cleared for release. The goal is an honest read on what good post-purchase looks like in 2027 and where most brands still leak time and trust.
Why WISMO is the honest scoreboard for post-purchase
WISMO is the question a customer asks when the order experience has failed to answer it first. Every where is my order ticket is a small proof that tracking, notifications, or expectations fell short. That makes WISMO volume the most honest single scoreboard for post-purchase.
It is honest because it is hard to game. You can dress up a tracking page, but if customers still email to ask where their order is, the page is not doing its job. WISMO cuts through the marketing and measures whether the customer actually feels informed.
So we anchor this report on WISMO. It ties directly to two things you care about: support cost and customer trust. Fewer tickets means lower cost and calmer customers.
What drives WISMO tickets up, and what brings them down
WISMO tickets rise from a short, predictable list of causes. The customer does not know where the parcel is, does not know when it will arrive, or got an update that did not match reality. Silence during the wait is the biggest driver of all.
What brings tickets down is the mirror image. Set a clear delivery expectation at checkout. Send proactive updates at the moments that matter, especially delays and exceptions. Give a tracking page that answers the question before the customer has to ask it.
| WISMO driver | What it looks like | What brings it down |
|---|---|---|
| Silence during transit | No updates after the order confirmation | Proactive milestone notifications |
| Confusing tracking | Carrier jargon the customer cannot parse | Normalized, plain-language statuses |
| Missed expectations | Parcel later than the promised date | Honest estimated delivery dates and early delay alerts |
| No self-serve answer | Customer has to email to learn anything | A branded tracking page that shows the full status |
The pattern is simple. Answer the question before it is asked, and the ticket never gets created.
Tracking status confusion: the normalization problem
Carriers report status in dozens of different labels, and many of them mean nothing to a shopper. One carrier says in transit, another says departed facility, a third uses an internal scan code. Same reality, three confusing messages.
Normalization is the fix. It maps every carrier's raw status into a small set of plain stages the customer understands, like ordered, shipped, out for delivery, and delivered. Done well, it turns a jumble of carrier jargon into one clear story regardless of who is carrying the parcel.
This matters more as brands ship multi-carrier and cross-border. The more carriers you touch, the more raw status labels you have to tame, and the more a customer benefits from a single normalized view.
Proactive notifications: channel and timing trends
Proactive beats reactive. A notification that reaches the customer before they think to check is the single most effective way to cut WISMO. The trend is toward more moments covered, not just a shipped and a delivered ping.
Timing is where most brands leave value on the table. The high-value moments are the delay and the exception, exactly when a customer is most anxious and most likely to email. A brand that stays quiet during a delay and only pings on delivery has covered the easy moment and skipped the hard one.
On channel, email and SMS each have a role, and the honest answer is that it depends on the message and the market. We break that down in the FAQ below rather than pretend one channel always wins.
Delivery and exception signals worth watching
Beyond the ticket count, a few delivery signals predict where WISMO is about to spike. Watch your exception rate, the share of parcels that hit a problem scan like a failed delivery or a customs hold. Exceptions are WISMO tickets waiting to happen.
Watch on-time delivery against the date you promised, not the date the carrier hoped for. A gap between promise and reality is a direct WISMO driver. And watch the late tail, the small share of parcels that run very late, because those generate outsized ticket volume and the angriest customers.
These signals let you get ahead of WISMO instead of counting tickets after the fact. Fix the exception early and you prevent the email.
What Pango's operational data shows, framed directionally
Pango runs post-purchase operations across a range of ecommerce brands, so it sees tracking, notifications, and WISMO behavior directly. We are keeping this qualitative until the figures are cleared for publication.
Directionally, the data is consistent with the public picture. Proactive notifications at delay and exception moments move WISMO the most. Status normalization reduces the confused-customer tickets that carrier jargon creates. And the late tail drives a disproportionate share of tickets, so catching exceptions early pays off out of proportion to how rare they are. When the cleared first-party figures are ready, this report will package them here in place of these directional notes.
Methodology and when first-party figures will be published
This report blends public data with Pango's operational trends. Public figures are cited where they exist and treated as directional. Pango's operational data is described qualitatively, as trends and directions, never as specific percentages that have not been cleared.
We hold first-party figures until they are cleared for release, and we cut an uncleared number rather than soften it. The cleared figures will be added to this same page when ready, since the report lives at one URL and is updated in place rather than republished.
For the platform behind this operational view, see the Pango post-purchase operations platform.
How Pango fits, and where it is not the answer
Pango fits when you want tracking, proactive notifications, and WISMO reduction connected into one built-to-fit layer rather than stitched from separate apps. It reads your carriers and data, normalizes statuses, and builds the notification logic your operation needs. It is strongest for multi-carrier and cross-border brands where a fixed template struggles.
Where is it not the answer? If you ship with a single carrier and only need a simple branded tracking page, a lightweight tracking app is enough and cheaper to start. Pango earns its place when the tracking and notification problem is complex, or when it needs to connect to returns and claims in the same layer.
For more, read what WISMO is, how to reduce WISMO tickets, and proactive shipping notifications.
