WISMO stands for "Where Is My Order?" and refers to the category of post-purchase customer service inquiries where a shopper contacts a brand to ask about the status of a shipment they have already paid for. WISMO contacts are the most common type of post-purchase support ticket in ecommerce, often accounting for the largest share of customer service volume during peak shipping seasons. The term has become shorthand for the entire problem of post-purchase delivery anxiety and how brands respond to it.

Why WISMO Matters for Ecommerce Brands

WISMO is not just an inconvenient ticket category. It is the operational signature of a gap between what customers expect to know about their order and what your post-purchase communication is actually telling them.

According to Salesforce's commerce research on WISMO, these inquiries dominate post-purchase support volume because the shipping window is the longest stretch of customer waiting in the entire purchase experience. A customer who paid yesterday and is expecting a package on Friday has four days of uncertainty to resolve. If your tracking page is generic, your notifications are sparse, or your delivery estimates are unclear, the customer fills that uncertainty by contacting support.

Each WISMO ticket has both a direct cost and an opportunity cost. The direct cost is the labor your CS team spends checking tracking, replying with status updates, and managing escalations. The opportunity cost is the time those reps could have spent on tickets that actually require human judgment: complex returns, product questions, VIP escalations. Brands that reduce WISMO volume reclaim CS capacity for higher-leverage work without growing headcount.

How WISMO Shows Up in Operations

The visible WISMO problem is the ticket queue. The deeper problem is what generates the tickets.

Customers default to contacting support when their post-purchase experience does not give them enough information to feel confident about a delivery. The triggers are predictable. A shipping confirmation email arrives but no follow-up notification appears for three days. The carrier tracking page shows a vague "in transit" status with no delivery window. The delivery date the storefront promised at checkout has slipped without any explanation. The package was marked delivered but the customer cannot find it. Each of these gaps surfaces as a WISMO ticket, and each one is preventable with the right post-purchase infrastructure.

For brands without a dedicated tracking layer, the typical CS workflow is reactive: a ticket arrives, the rep pulls up the carrier tracking page, copies the status into a reply, and waits for the next ticket. That model scales linearly with shipping volume, which is exactly the wrong scaling pattern when a brand grows. The brands that solve WISMO well shift to a proactive model, where tracking updates flow to the customer automatically and the rep only gets involved when something is genuinely wrong.

What Good WISMO Reduction Looks Like

The most effective WISMO reduction strategies operate on four layers at the same time.

Branded tracking pages. Instead of sending customers to the carrier's generic tracking page, surface a branded tracking experience hosted on or linked from your domain. The page shows the customer their order, the current status, the delivery estimate, and any relevant updates in your brand voice. This single change moves the post-purchase experience from "carrier problem" to "your brand's problem to solve well."

Proactive notifications. Customers who get an email or SMS at every meaningful tracking event (label created, in transit, out for delivery, delivered) generate dramatically fewer WISMO tickets than customers who only see the initial shipping confirmation. The notification cadence has to be calibrated, but underdoing it is the usual mistake.

Accurate delivery estimates. Many WISMO tickets are triggered when a delivery slips past the estimate the customer saw at checkout. Improving the estimate accuracy at the storefront level, especially for international shipments, removes a significant fraction of inbound WISMO volume.

Self-service status checking. Customers who can re-check their own status on a clean, mobile-friendly tracking page do so. The same customer who would have opened a support ticket will instead refresh the tracking page twice and move on, if the page is good enough.

This is what Redo's order tracking product was built around: a branded tracking page on your domain, proactive multi-channel notifications, and a unified post-purchase experience that addresses each of the four WISMO drivers at once. The deeper playbook for measuring and reducing WISMO over time is covered in our piece on order tracking software and WISMO reduction.

How Redo Handles WISMO at the Platform Level

For brands that want WISMO reduction baked into the broader post-purchase stack rather than added as a point tool, the integration matters. Order tracking that connects cleanly to loyalty and post-purchase marketing means the same data driving WISMO reduction also feeds repeat-purchase campaigns and review collection. Each touchpoint on the tracking page becomes an opportunity for retention, not just a status update.

For brands operating internationally, the WISMO problem compounds. International shipments have longer transit windows, more customs uncertainty, and more carrier handoffs. The brands that handle international WISMO well combine accurate tracking from the originating carrier through the destination carrier, transparent delivery estimates that account for customs delays, and notifications in the customer's language and time zone.

Want to see how proactive WISMO reduction works in practice? Book a demo and we will walk through how Redo's branded tracking, notification cadence, and post-purchase analytics combine to take WISMO volume off your support team.

Key Insight

WISMO is the cost a brand pays for not investing in the post-purchase communication layer. Every ticket is a customer who would have stayed quiet if the tracking experience had answered their question first. Reducing WISMO is not about getting better at responding to those tickets; it is about building the infrastructure that makes the tickets unnecessary in the first place.