Where is my order? Proactive updates that cut WISMO tickets
TL;DR
Most order-status tickets follow silence, vague tracking or a missed date. Send updates at set triggers, contact the customer first when a parcel stalls, name who owns each exception and measure contacts per order by shipping lane.
A customer in Texas ordered a smart thermostat eleven days ago. The tracking page has said “In transit” for six of them. She writes on Monday, again on Wednesday, then opens a dispute with her card issuer on Friday. Nobody on your team did anything wrong. Nobody did anything at all.
“Where is my order?” (WISMO) questions are usually the largest single type of post-purchase ticket, and cross-border shipping makes them worse. Long transit, customs holds and handoffs between carriers create long stretches with no visible progress. The fix is less about answering faster and more about telling the customer what is happening before they need to ask.
How big is the WISMO share?
For a reference point, DigitalGenius, analyzing tickets from its own retail customers, reported an average WISMO rate of 21% in March 2023 and 36% across December 2022 and January 2023. That is one vendor’s customer base, mostly UK retail, not an industry benchmark. It does show the pattern: order-status demand rises when carriers are under pressure.
In Narvar’s 2025 survey of 3,461 US online shoppers, 74% said they had experienced a late delivery in the past year. Narvar also reports that half of consumers say they are less likely to shop again with a retailer after a late delivery. Those are stated intentions, not measured repeat purchases, but they explain why an order-status ticket is also a retention risk.
Why customers ask
Most WISMO tickets start with one of three gaps:
- Silence. The order was confirmed, then nothing for days while it waited to ship.
- Vague tracking. “In transit” or “Processing at facility” with no date and no explanation of what normal looks like on this route.
- A missed promise. The date shown at checkout has passed and nobody has said what happens next.
Cross-border orders add their own stalls: a parcel sits between carriers with no new scan, waits for customs, or shows “Delivered” to a building where the customer cannot find it. Each is predictable, and each can be explained before it becomes a ticket.
The proactive update schedule
Send a message when something the customer cares about changes, and when something should have changed but did not. Shopify’s order status page and notifications already cover several of these moments: customers can track shipments through the order status page and shipping notification emails, and shipping confirmation and shipping update emails can link back to that page. The gaps are usually the exception messages, which you have to design yourself.
| Trigger | Message | Owner |
|---|---|---|
| Order placed | Confirmation with a realistic delivery window for that destination, not the fastest lane | Automated; ops sets windows by lane |
| Shipped | Tracking link, carrier name, and what the first few days usually look like | Automated |
| No new scan beyond the lane’s normal gap | “We noticed your parcel has not moved. We are checking with the carrier and will update you by [date].” | Support agent, first contact |
| Customs hold or duties request | What the hold means, whether the customer must act, and who pays | Support agent, using an approved template |
| Out for delivery | Delivery day plus safe-place and address tips | Automated |
| Delivered | Confirmation, setup or first-use help, and how to report a missing parcel | Automated; support owns replies |
| Delivery window missed | Apology, new expected date or the options below | Support agent |
“Normal gap” should come from your own tracking history by lane. Cross-border parcels often go quiet longer at handoff than domestic ones, so set the threshold per lane rather than one number for every shipment.
If shipping has not happened yet, check your US obligations too. The FTC’s Mail, Internet, or Telephone Order Merchandise Rule requires a reasonable basis for any stated shipping time and, where no time is stated, shipment within 30 days. If you cannot ship on time, you must give the buyer the option to consent to the delay or cancel for a prompt refund. The rule is about shipment, meaning handing the goods to the carrier, not final delivery. Treat carrier delays after dispatch as a customer experience question, not as the same legal notice.
Exception rules: when a human reaches out first
A person should reach out first when:
- a parcel has passed the lane’s stall threshold;
- the promised window has been missed;
- the carrier shows a return to sender, address problem or customs request;
- the customer has already contacted you once about the same order.
For the three hardest cases, agree a decision path in advance:
- Late: give a new expected date if the carrier can support one. If it cannot, say so and offer the options your policy allows, such as waiting, a replacement once a set date passes, or a refund.
- Lost: decide the point at which you stop waiting and reship or refund, without making the customer wait for the carrier claim to finish.
- Delivered but not received: ask the customer to check with neighbors, building staff and safe places, confirm the address, and set a follow-up date. Name who decides between reshipping, refunding and waiting.
The carrier claim is a separate job. Name who files it, what evidence they need and where the outcome is recorded. For language and tone when a customer is already upset, see our guide to handling angry customers without promising too much.
Make the tracking page and first reply do more work
A repeat contact usually means the first answer missed the next question. Put three things on the tracking page and in every first reply: the expected delivery window, what the current status means on this route, and when the customer will hear from you next. Add a way to report a problem from the page itself, so a worried customer does not have to start a new email thread.
Automation can answer “where is it?” from live tracking data. Hand over to a person when the answer is “we do not know yet”, when an exception needs a decision, or when the customer has asked more than once. Our guide to when AI should hand over to a human covers those conditions. Measure whether the case was actually resolved, not just replied to; the gap between fast replies and real answers is covered in responsive customer support.
Repeat purchase and disputes
The delivered message is the first chance to help the customer use the product. A good delivery does not guarantee a second order, but a silent, late one makes it harder to earn.
Disputes are the other side. Shopify lists a tracked delivery the customer says they never received, and a delayed or lost shipment, as common product-not-received dispute scenarios, with carrier tracking, proof of delivery and address verification as the evidence to gather. Keep your exception messages and the customer’s replies on the order. They record what you told the customer and when.
What to measure
- WISMO share of tickets: order-status contacts divided by all contacts, tagged consistently.
- Contacts per order: order-status contacts divided by orders shipped.
- Repeat contacts: customers who ask about the same order more than once. This measures whether your updates and first replies worked.
- Late-delivery rate by lane: orders delivered after the promised window, split by destination and carrier.
A hypothetical example
The numbers below are invented for illustration. They are not benchmarks or CXharbor results.
A store ships 1,500 orders a month to the US and 500 to Germany. It receives 180 order-status tickets from each market. Overall, that is 360 tickets on 2,000 orders, or 0.18 contacts per order. Split by lane, the US runs at 0.12 and Germany at 0.36, three times higher. Most German tickets arrive after a parcel sits between carriers with no new scan. The action is specific: a stall trigger for that lane, a message explaining the handoff, and a realistic window at checkout. Setting that window honestly before purchase is part of answering pre-purchase questions well.
If order-status volume is crowding out harder cases and you want help running the exception queue, talk to CXharbor. Bring your contacts per order by lane and your current exception rules.