WISMO means 'Where Is My Order'. It is the support ticket a customer sends when a package has not arrived or tracking looks stuck. For most Shopify stores it is the largest ticket category, often 30-50% of inbound volume, which makes it the first thing worth fixing.
Key takeaways
- WISMO tickets often make up 30-50% of a Shopify store's inbound support volume.
- Spikes come from carrier scan gaps, delayed fulfillment, and unclear tracking emails.
- Four deflection levels exist, from a tracking page to AI replies with live order data.
- Exceptions still need a human, so the handover matters.
What does WISMO mean in e-commerce support?
WISMO is short for 'Where Is My Order'. In e-commerce support, it covers every customer message asking for the status, location, or delivery date of an order that has already been paid for. Typically it makes up 30-50% of a Shopify store's inbound tickets.
The WISMO customer support definition is narrow on purpose. It covers questions about an order in transit. It does not cover returns, refunds, or product questions, though those often follow a failed delivery.
Typical WISMO messages look like this:
- 'My order was placed 6 days ago and I have no tracking.'
- 'Tracking says shipped, but it has not moved since Monday.'
- 'It says delivered, but nothing is at my door.'
- 'Can I change the address before it ships?'
The last one is a close cousin. It is not strictly WISMO, but it lands in the same queue and gets the same treatment.
Is WISMO the same as order tracking?
No. Order tracking is a feature: a page or link that shows where a parcel is. WISMO is the demand: a customer asking because the feature failed to answer them. Tracking is one way to prevent WISMO, not a synonym for it.
A store can have a tracking link in every email and still receive hundreds of where is my order tickets. The link may show 'In transit' for nine days. It may not load on mobile. It may never reach the customer's inbox.
So track two numbers separately: how many orders have tracking, and how many orders generate a WISMO ticket. The gap between them is your real problem.
Why do WISMO tickets spike?
WISMO tickets spike when customers lack information, not only when parcels run late. Three causes dominate: carrier scan gaps, delayed fulfillment, and unclear tracking emails. A parcel that is on time but silent for 4 days produces nearly as many tickets as a late one.
Carrier scan gaps. A parcel is picked up, then no scan appears for several days. It is usually moving. The customer cannot tell.
Delayed fulfillment. The order sits unpacked for 3-5 days during a sale or a stock issue. No tracking exists yet, so the customer writes in.
Unclear tracking emails. The shipping confirmation lands in spam, hides the link, or shows a tracking number with no carrier. The customer cannot act on it.
Peaks follow predictable patterns:
- Black Friday and holiday weeks, when carriers slow down.
- Weather or customs disruptions.
- Launches and sales where fulfillment lags behind order volume.
- Cross-border orders, where handoffs between carriers create gaps.
What does a WISMO ticket cost versus preventing it?
A WISMO ticket costs the time to open it, find the order, check the carrier, and write a reply. At roughly 5 minutes of agent time per ticket, 400 tickets a month equals about 33 hours of work. Prevention costs far less per order.
The maths is simple. Take your agent's hourly cost, multiply by minutes per ticket, and multiply by monthly volume. A ticket that takes 5 minutes at a loaded cost of 24 per hour costs about 2 per reply. That is before counting the slower response to tickets that actually need judgment.
Citation capsule: WISMO is expensive mainly because it is repetitive. Each ticket follows the same steps: read the message, find the order in Shopify, open the carrier page, copy the status, and write a reply. At about 5 minutes per ticket, a store receiving 400 WISMO tickets a month spends roughly 33 agent hours on answers that contain no judgment. Prevention changes the unit cost. A proactive shipping email or tracking page costs close to nothing per order, because it is built once and runs on every shipment. The remaining cost is exceptions: lost parcels, wrong addresses, and carrier disputes. These genuinely need a person. The goal is not zero WISMO tickets. It is to ensure humans only touch the ones that cannot be answered from order data.
There is also a hidden cost. While agents answer status questions, refund requests and pre-sale questions wait longer.
What are the four levels of WISMO deflection?
There are four levels of WISMO deflection: a tracking page, proactive notifications, chat widget lookup, and AI replies with live order data. Each level reduces more tickets than the last, but needs more setup and changes who handles exceptions.
- Tracking page. A branded page where customers enter an order number or email. It is passive. Customers must find it.
- Proactive notifications. Emails or SMS at shipped, out for delivery, delayed, and delivered. They answer the question before it is asked.
- Chat widget lookup. A widget on the store where customers enter an order number and see status, often with fixed rules.
- AI reply with live order data. The AI reads the customer's message in email, DMs, or chat, looks up the order, and replies in context.
The table below compares them. Ranges are directional and vary by store, carrier mix, and order volume.
| Level | Setup effort | Typical ticket reduction | Who handles exceptions |
|---|---|---|---|
| 1. Tracking page | Low: an app install and a link in emails | Low (roughly 5-15%) | Human, by email |
| 2. Proactive notifications | Low to medium: templates and triggers | Moderate (roughly 15-30%) | Human, by email |
| 3. Chat widget lookup | Medium: widget plus order matching | Moderate (roughly 20-35%) | Human, after the widget fails |
| 4. AI reply with live order data | Medium: connect store, write playbook | Highest of the four | Human handover on stuck cases |
The levels stack. Most stores benefit from level two as a base, then add level four for the tickets that still arrive.
Where does Heylio fit in WISMO deflection?
Heylio fits at level four. It looks up the order in Shopify, reads the status, and drafts or sends the reply from your WISMO playbook. When a case is stuck or unusual, it hands over to a human, and that handover is free.
In practice this means a customer who writes 'where is my order' by Gmail, Outlook, Instagram DMs, WhatsApp, or the chat widget gets an answer based on their actual order, not a generic link.
What it does not do is replace levels one and two. If your shipping emails are unclear, fix them first. Heylio handles the replies that still come in, which is where the remaining volume sits.
Billing is per AI resolution, meaning a conversation the AI closes on its own. A handover to a human costs nothing. There is a free plan with 25 AI resolutions, so you can test it on real WISMO tickets before paying.
For the step-by-step setup, see our guide on WISMO automation on the Heylio blog. This article stays on definitions.
How do you reduce WISMO inquiries on Shopify?
To reduce WISMO inquiries on Shopify, start by measuring your ticket rate, then fix the cause that produces the most tickets. Stores that send clear shipping emails and flag delays early typically see a noticeable drop within the first 30 days.
A practical order of work:
- Measure. Tag WISMO tickets for 2 weeks. Divide by orders shipped.
- Fix the emails. Put the carrier name, tracking link, and expected date in the first shipping email.
- Flag delays. Message customers before they ask when a parcel stalls.
- Automate replies. Let level three or four handle the repeat questions.
- Review exceptions. Look at lost or stuck parcels weekly, and fix the carrier or process behind them.
Heylio's auto-learning also tracks corrections your team makes and suggests updates to the knowledge base and playbooks, so repeated edge cases get handled better over time.
What should you do next about WISMO?
Start with one number: WISMO tickets divided by orders shipped, over the last 30 days. That rate tells you whether you have a tracking problem, a fulfillment problem, or a communication problem. Fix the cheapest level first, then automate what remains. If replies are your bottleneck, test level four on the free plan.