How to Reduce WISMO ("Where Is My Order?") Tickets: A Merchant Guide
Short answer: To reduce WISMO tickets, answer "where is my order?" before customers ask: send a branded tracking page link in every shipping email, notify shoppers proactively about delays, show split shipments and return status on the same page, and route only exceptions such as lost parcels to your support team.
Updated 2026-11-10
What WISMO means
WISMO stands for "Where Is My Order?". It covers every contact a shopper makes to check on a purchase after checkout: emails, chat messages, DMs and calls. A close cousin, WISMR ("Where Is My Refund?"), covers the same anxiety after a return. Both are usually the largest category in an ecommerce support queue.
Why WISMO tickets happen
Almost every WISMO ticket traces back to one of five gaps in post-purchase communication:
- No update between "order confirmed" and "delivered", so silence reads as a problem.
- Carrier tracking links that show codes like "In transit - arrived at facility" with no expected date.
- Split shipments: one package arrives, the customer thinks the rest is lost.
- Delays the merchant knows about but the customer discovers first.
- Returns and refunds with no visible status after the parcel is sent back.
Which WISMO fixes work best
Rank fixes by how many tickets they remove for the effort involved:
| Fix | Tickets it removes | Effort |
|---|---|---|
| Branded tracking page linked in every email | Routine status checks | Low |
| Proactive delay and exception alerts | "It's late" contacts | Low-medium |
| Package-level view for split shipments | "Only part of my order came" | Low with the right tool |
| Return and refund status on the same page | WISMR ("where is my refund?") | Low-medium |
| Self-serve lookup by order number and email | Guest-checkout status checks | Low |
| AI agent or macro for remaining tickets | Exceptions and edge cases | Medium |
What to measure
Track WISMO rate as WISMO tickets divided by orders shipped in the same period, tagged consistently in your helpdesk. Also watch tracking-page visits per order (higher is good: customers are self-serving) and median first-response time on the tickets that remain. Compare the 30 days before and after each change, ideally excluding peak-sale weeks.
Step by step
- Baseline your WISMO rate: Tag every "where is my order" and "where is my refund" ticket in your helpdesk for two weeks, then divide by orders shipped to get your starting WISMO rate.
- Launch a branded tracking page: Give customers one page on your own domain that shows each package's timeline and an expected delivery date in plain language, not raw carrier codes.
- Replace carrier links in every email: Point the tracking link in order confirmation, shipping and delivery emails at your tracking page so customers land on your brand, not the carrier's site.
- Turn on proactive notifications: Send an email or WhatsApp update on dispatch, out-for-delivery and especially on delays or exceptions, before the customer notices.
- Show returns and refunds on the same page: Add return, exchange and refund status next to package tracking so WISMR questions are answered in the same place.
- Route only exceptions to humans: Send lost, damaged or stuck-in-customs parcels to an agent with a clear macro or credit rule, and review the WISMO rate monthly.
Use case
Example: an apparel brand before and after a branded tracking page
Illustrative example. A Shopify apparel brand ships around 3,000 orders a month, often in two packages because some sizes ship from a second warehouse. Shipping emails link to the carrier site, and returns are handled over email.
Before
- Customers who receive one of two packages write in assuming the rest is lost.
- Carrier pages show status codes without a delivery date, so shoppers ask the store instead.
- After sending a return, customers email to ask when the refund will arrive.
- Agents copy tracking numbers into carrier sites to answer each ticket by hand.
After
- Shipping emails link to one branded page that shows both packages separately, with dates.
- Delay alerts go out automatically when a carrier flags an exception.
- Return pickup date, reverse tracking and refund status appear in a second tab on the same page.
- Agents only handle genuine exceptions such as lost or damaged parcels.
How to do it with EcoTrack
EcoTrack is Saara's free order and returns tracking page for Shopify and other storefronts. It covers steps 2 to 5 of this guide out of the box, with no monthly fee, no per-order fee and no shipment cap.
- Install EcoTrack from the Shopify App Store and connect your store; open orders sync automatically.
- Shipments are matched to 100+ carriers including USPS, UPS, FedEx, DHL, Royal Mail and Australia Post.
- Brand the page with your logo and colours, and host it on Saara or embed it in your storefront.
- Swap the tracking link in your shipping emails for your EcoTrack URL and enable email and WhatsApp notifications.
- The My packages tab shows split shipments package by package; the Returns tab shows return reason, pickup date, reverse tracking and refund status.
- Pair it with EcoReturns for self-serve returns and exchanges, or EcoAgents to auto-answer the WISMO tickets that still arrive.
Frequently asked questions
What does WISMO stand for?
WISMO stands for "Where Is My Order?" - customer contacts asking about the status of a purchase after checkout. WISMR is the returns equivalent: "Where Is My Refund?".
How do you calculate WISMO rate?
Divide the number of tagged WISMO tickets in a period by the number of orders shipped in the same period, then multiply by 100.
Does a tracking page really reduce WISMO tickets?
Yes, when it is linked in every shipping email and shows plain-language dates and package-level detail. A tracking page nobody is sent to removes very few tickets.
Is there a free way to reduce WISMO on Shopify?
Yes. EcoTrack by Saara is a free branded order and returns tracking page for Shopify with no per-order fee or shipment cap.
Can AI answer WISMO tickets?
Yes. An AI agent can read the order, check the carrier status and reply in-thread. It works best after a tracking page has removed routine status checks, leaving it the exceptions.