One-line definition: WISMO (Where Is My Order) inquiries are customer support tickets asking about order status, tracking, and delivery - typically the single largest category of contact volume for any e-commerce store.
Every Shopify store deals with WISMO. The question is whether you're spending half your support team's time answering it, or whether your post-purchase experience answers it for you before the customer ever has to ask. A 40% reduction in WISMO volume isn't a stretch goal - it's what merchants commonly see once they fix a few things upstream. Here's where to start.
The real cost of WISMO on your support team
WISMO tickets routinely make up between 20% and 40% of total support volume during normal trading, and they climb past 50% during peak periods like Black Friday or the December rush. Each one costs roughly €5 to €12 to handle once you factor in agent time, tooling, and the cost of that agent not being available for higher-value work.
For a store doing 5,000 orders a month with a 10% contact rate, 30% of which are WISMO, that's 150 tickets a month. At the upper-end cost figure, you're spending around €1,800 a month - close to €21,600 a year - to tell customers what their phone could have told them.
The bigger cost is harder to see on a spreadsheet. Roughly 70% of customers say they're less likely to buy from a brand again if a delivery is delayed and the brand fails to notify them. That's not the cost of the support ticket - that's the lost lifetime value of the customer who never came back.
WISMO is the symptom. The disease is silence: the gap between what the customer expects to know and what you've actually told them. Close the silence, and the tickets disappear on their own.
Proactive vs. reactive communication: keeping the customer informed
Reactive communication waits for the customer to ask. Proactive communication answers the question before it forms.
The reason this matters is that customer anxiety doesn't fire at random. It fires in predictable windows:
- 24-48 hours after order placement, if no shipping confirmation has gone out
- Right after a label is created, when tracking shows "Label created" but no carrier scan
- During any 48-72 hour gap in carrier scans mid-transit
- When the promised delivery date passes without an update
- When a delivery attempt fails (more on that below - see our guide on how delivery attempts work)
Every one of those windows is something you can anticipate. If your warehouse takes 24 hours to dispatch, the customer should hear from you at hour 24 - not when they email you at hour 48 wondering if you've taken their money.
Proactive doesn't mean noisy. It means the customer gets a message at each genuine status change: order received, order packed, shipped (with tracking link), out for delivery, delivered. Most carriers expose these scans through their tracking APIs, and apps like Packrooster pull the carrier's tracking link automatically into the Shopify order page and confirmation emails, so the link is there the moment the label prints rather than buried a few clicks deep.
A rule of thumb: if you've ever had to send the same manual status update more than twice, automate it.
The power of the branded tracking page (and why Shopify's default isn't enough)
Shopify's out-of-the-box approach is to send the customer to the carrier's tracking page - UPS, DHL, PostNord, Posti, whatever shipped the order. That does the basic job of "show me where my package is," but it costs you in three ways.
First, you lose the customer to a different domain. They land on the carrier site, see other companies' ads, and leave your brand entirely until the box arrives. McKinsey's 2025 research on e-commerce delivery found that customers check tracking pages four to five times per order. That's four to five opportunities to reinforce your brand, recommend related products, or reassure the customer - none of which a carrier page does for you.
Second, carrier pages speak carrier language. "Label created. Awaiting collection." "Acceptance scan." "In transit at sort facility." Most customers don't know what those mean. You do. A branded tracking page can translate carrier status into something useful: "Your order has been packed and is waiting for our carrier to collect it later today."
Third, carrier pages can't take action. A branded tracking page can. The customer who realizes they entered the wrong address can self-correct. The customer whose first delivery attempt failed can pick up at a pickup point instead. Every one of those self-service actions is a WISMO ticket that never gets opened.
You don't necessarily need a separate branded tracking app to start. Getting the carrier tracking link into your confirmation emails and into the customer's Shopify account order page already closes a big chunk of the tracking gap - and Packrooster handles that part automatically. If you outgrow it and want a fully branded post-purchase page, the upgrade is incremental rather than a rebuild.
How to handle delivery exceptions before the customer complains
Delivery exceptions - failed attempts, customs holds, weather delays, address issues, parcels stuck at a depot - are inevitable. Your shipping volume goes up, your exceptions go up. The question isn't how to prevent them. It's how fast you spot them and how you handle them.
The honest version: if you find out about a delivery exception because the customer emailed you, you're already losing.
A few practical moves:
Watch for patterns, not single events. A single carrier scan can be ambiguous. But "Label created" with no movement for 48 hours, or "In transit" with no new scan for 72 hours, are reliable signals that something needs attention. Most shipping apps can surface these signals for you. In Packrooster, exception alerts are available where the connected carrier exposes them through its API.
Tell the customer first. When you spot an exception, send a short message that does three things: confirms you know about it, gives the most likely cause if you have one, and tells the customer the new estimate or the action they can take. Don't send "your order is delayed" and stop there. Send "your order is sitting at our regional depot due to higher parcel volume after Black Friday. We expect movement tomorrow and we'll message you again when it scans."
Give them a way to self-serve. Many exceptions resolve faster if the customer can change something themselves - update an address, pick a pickup point, reschedule delivery. The more you push to self-service, the fewer tickets your team handles.
Done well, exception management removes more WISMO volume than any other single lever. Industry figures put the reduction in exception-related tickets at 60-80% once proper self-service is in place.
Using SMS vs. email for order status updates
Email is the default for shipping notifications because it's effectively free, native to Shopify, and where order confirmations already live. The catch is the open rate: average email open rates in 2025 sit at 20-30%, according to recent HubSpot and Klaviyo benchmarks. If you send a delay notification by email, fewer than a third of customers see it in time to act on it.
SMS open rates are 90% or higher and most messages are read within minutes. WhatsApp, in markets where it's dominant, behaves similarly.
The practical split most stores land on:
Email for the full record. Order confirmation, shipping confirmation with carrier tracking link, invoice, delivery confirmation. Email is searchable, lives in the customer's inbox forever, and is the right format for anything they might need to refer back to.
SMS for time-sensitive exceptions. Failed delivery attempts. Out for delivery. Delay with action required (pickup point selection, address confirmation). Anything where the customer needs to act in the next few hours.
Two things to keep in mind. SMS isn't free - there's a per-message cost that adds up at scale, so it pays off for the moments that genuinely matter. And it's intrusive, which is exactly why it works: customers read it, but they'll also tune you out fast if you overuse it. Carrier-driven shipping notifications routed through Packrooster are configurable per event, so you can decide which channel handles which moment rather than firing both for everything.
For cross-border orders, especially within the EU, SMS deliverability and pricing vary by destination country. Worth checking with your carrier or notification provider before turning it on globally.
Setting realistic "arrives by" dates at checkout
The single biggest source of WISMO isn't a slow carrier or a missing tracking update. It's a delivery promise that doesn't match reality.
If your checkout says "arrives in 2-3 business days" and the actual median delivery is five days, every order outside that window becomes a support ticket. You can have flawless tracking, a beautiful branded page, and instant SMS notifications, and you'll still drown in WISMO because the expectation is wrong from the start.
A realistic delivery estimate accounts for:
- Your dispatch time, not just carrier transit time. If your warehouse picks and packs in 24 hours, day one is gone before the carrier touches the parcel. Build that into the promise.
- Carrier transit times for the customer's actual destination. Shipping from Helsinki to another Finnish city is not the same as shipping to rural France. Your shipping setup should calculate this per order rather than quoting a single national average.
- Cutoff times. Orders placed Friday afternoon don't ship until Monday. Show the customer that math at checkout so they're not expecting Saturday delivery.
- Variability. Add a small buffer for carriers having a bad week, peak season volume, and customs review for cross-border shipments.
Underpromising and overdelivering beats the opposite every single time. A customer told four days and delivered in three is happy. A customer told two days and delivered in four is writing a support ticket and considering a chargeback.
If you sell across borders, this gets harder - you're dealing with multiple carriers, customs, and varied last-mile networks. Surfacing carrier-specific delivery estimates directly at Shopify checkout, rather than relying on a single static shipping label, is worth the setup time.
Bringing it together
Reducing WISMO isn't about deflecting customers from your support team. It's about making sure the customer never had to ask in the first place. Every ticket your store doesn't receive is a customer who got the information they needed, on the channel they trust, at the moment they wanted it.
The 40% reduction isn't a single magic switch. It's the cumulative effect of accurate delivery promises at checkout, proactive notifications during transit, a tracking experience that translates carrier-speak into plain language, and self-service for the exceptions that will always happen. Most stores can get most of the way there in a quarter if they tackle these one at a time.
Start with the one that's costing you the most right now - usually it's either checkout promises that don't match reality or silence in the first 48 hours after order placement. Fix that, measure the ticket drop, then move to the next.
