Copy Link
WISMO stands for "Where Is My Order?", the single most common inquiry in e-commerce support and, at most brands, 40-60% of the inbox. Here's my take after thirty years running orders: WISMO is not a support problem to answer faster. It's an operations problem wearing a support costume - every ticket is evidence that a promise broke silently somewhere between the buy button and the doorbell. I learned that the expensive way: at the start of COVID we ran an online warehouse sale at P.E. Nation, where I was CEO. It exploded, the storefront didn't sync with the warehouse, and we took a thousand orders for stock that was gone. Tracy, my co-founder, had to hire six people just to call customers, run refunds, and cancel orders - and every call was the same question. Where is my order?
What WISMO actually is
Formally: the class of tickets where a customer chases the status of an order, exchange, or return (the reverse-leg sibling is WISMR, "Where Is My Return?"). My read: it's the most mislabeled line item in e-commerce, because it gets filed under "support workload" when it's really an operations defect count. I've run this at every altitude - I built Nike's Hurley brand in South Africa with my own capital, ran SurfStitch at $80 million with CX reporting directly to me as CEO, then P.E. Nation, then Papinelle. At Papinelle I walked into 110% complaint tickets to order volume - more complaints than orders - and essentially every complaint was about an order: where it was, why it hadn't shipped, why nobody had said anything. Support wasn't the problem. Support was the smoke detector, and the kitchen was on fire.
The automation tools that cut WISMO
The market gives you three tiers of tooling, and they do different jobs: tracking pages and notifications answer the question faster; detection removes the reason to ask. Most brands buy the first two and wonder why the tickets keep coming.
Branded tracking pages
A tracking page on your own domain, replacing the generic carrier link. It deflects the easy half of WISMO - customers who just wanted visibility - and keeps the anxious moment inside your brand. Worth having, and Shopify's built-ins get you started. Just know what it is: a better window onto the parcel, not a hand on the parcel. A beautiful tracking page showing "in transit" for six days still generates the ticket.
Proactive notifications
Automated SMS and email that reach the customer before they ask: shipped, out for delivery, delayed with a new date. The superior version notifies about the fix, not just the status. The way we built it at Keeyu: when a warehouse falls behind, a CX team sends 100 customized emails in one click; when a style oversells, bulk-cancel, refund, and notify in one move. If we'd had that during the P.E. Nation sale, six people wouldn't have spent weeks on the phone.
Detection and resolution
The layer above both: watch every order against the promise made at checkout, catch the stuck and breaking ones, and automate the resolution - replacement shipment, proactive email, carrier claim. This is what Keeyu's platform does, and it's the only tier that shrinks the event count instead of the response time.
What WISMO costs, and how to cut it
The cost formula is three numbers you already have: monthly tickets x WISMO share (40-60% for most brands) x cost per ticket ($5-10 at typical support wages). A brand doing 5,000 tickets a month at a 50% share and $8 a ticket is paying $20,000 a month to answer a question its own operations created. My view: that money isn't a support budget, it's an operations defect tax - and you cut a tax at its source, not at the counter. I watched the manual version of this up close: when I met Tracy she was working 16-hour days searching multiple systems by hand to spot and fix breaking orders. Unsustainable - so Tahir, our third co-founder, built an internal system to do the watching, and it delivered a $155k benefit. That tool is Keeyu's ancestor. Automated resolution now runs at about $1 per issue against $8-10 per handled ticket; across our customers that compounds to up to 90% fewer WISMO tickets and 50% lower support costs. One mechanism makes it concrete: our FIFO view showed one brand 113 orders placed yesterday still unshipped - statistically about 150 inbound queries tomorrow. Today's unshipped count IS tomorrow's inbox. Volume math on the pricing page.
Turn the wait into retention
The post-purchase wait is where loyalty gets decided: 79% of customers won't return after one bad experience, and 60% of the reasons customers don't come back happen after checkout. The take I've carried for years: customer service should be a profit center, not an apology queue. That idea comes from Tracy at P.E. Nation - her goal was to make her department generate more revenue than it cost, and it sounds impossible while the team is drowning in WISMO. It becomes obvious the moment they're not: a proactive "we caught it, here's what we did" turns your worst moment into your most convincing one, and the freed team works the conversations that create revenue - exchanges instead of refunds, reorders, reviews. The brands doing this are in customer stories.
Choosing the solution stack
Practical guidance: run all three tiers, but in the right order of expectation - platform built-ins for baseline visibility, a post-purchase app if you want branded tracking and notifications, and the proactive operations layer to remove the events themselves. Only the last one changes the defect count; that layer is what Keeyu is - proactive e-commerce operations, working every order backwards from the checkout promise. The proof point I always come back to: after one Black Friday I asked EHP Labs how it went, and the answer was "everything that went wrong" - peak sync failures had them flying blind with hundreds of unshipped orders, my P.E. Nation story with a different logo. They signed on the spot, and they've since cut WISMO 90% and halved manual work. Every order is a promise, and a kept promise never files a ticket. See your own broken promises live: book a demo, or start with the white paper.
FAQs
What is a normal WISMO rate?
Under 20% of your inbox means unusually clean operations; most brands sit at 40-60%. The worst I've personally walked into was Papinelle at 110% complaints to orders. Run the helpdesk query this week; it sets your baseline.
Do branded tracking pages reduce WISMO?
Yes, for the visibility half. They do nothing for stuck orders, where the angriest tickets and the churn live. For those you need detection upstream, in fulfillment and carrier operations.
What's the fastest way to start cutting WISMO?
Count today's unshipped-past-promise orders - each is a ticket in the making. That watch is the core of proactive customer service and the wider discipline of post-purchase operations. Or shortcut it: a demo shows your order book with the breaks lit up.
What is WISMR?
"Where Is My Return?" - same anatomy on the reverse leg, same fix: the return processed before the customer chases never generates the ticket.
References
Ready to Stop Reacting?
The fastest way to see how Keeyu prevents complaints is to see it in action.
In one call, we’ll map your current operations, show how our AI Agent fits in, and walk through real examples of issues fixed before customers notice.
Most teams go live within 48 hours. We never share your data.
