WISMO stands for "where is my order?", and it covers every message a customer sends asking about the status of an order. For most online stores it is the largest single group of support tickets. You handle WISMO in two layers: prevent most of it with clear delivery estimates, a tracking link in every shipping email and a message the moment a parcel is late, then answer the rest fast with saved replies, a findable tracking page and clear rules for lost or stuck parcels.
This guide walks through both layers for a small store team, with message templates, an escalation table and the numbers to watch once you make changes.
What WISMO means and why it dominates store support
Every WISMO question is a customer filling a gap in what they know. They paid, they expected a date, and nothing in front of them answers "when?". The more often that gap opens, the more tickets you get.
WISMO tickets come in five shapes, and they need different answers:
- Not shipped yet: "I ordered on Monday, has it gone out?"
- In transit, on time: "Where is it now?" The tracking link would have answered it.
- Delayed or stuck: tracking has not moved for days, or the estimate has passed.
- Delivered but not received: the carrier says delivered and the customer has nothing.
- Address problems: a typo, a move, or a parcel returned to sender.
The first two are almost entirely preventable. The last three need a person, a policy and sometimes a carrier claim. Most of the work in this guide is moving tickets out of the first group and handling the second group faster.
WISMO also spikes after sales. A promotion that doubles orders brings a wave of order-status questions a week or so later, when the warehouse is behind and couriers are full, so plan your staffing and messages for that week before the sale starts.
Measure your own share of order-status tickets
Before changing anything, find out how big the problem is in your store. Industry figures vary wildly and none of them describe your customers.
- For two weeks, tag every conversation about order status, by chat or email, with one of the five shapes above.
- Count the tags and divide by all conversations in the same period. That is your WISMO share.
- Divide WISMO conversations by orders shipped. That gives contacts per 100 orders, a number you can compare month to month even as sales grow.
- Note when each one arrived relative to the order: day 1, day 3, after the estimated date. The timing tells you which message is missing.
A hypothetical example: a store ships 600 orders in two weeks and receives 210 support conversations, 84 of them about order status. WISMO share is 40%, and there are 14 WISMO contacts per 100 orders. If most of the 84 arrive on days 2 to 4, customers are not getting or not reading the shipping confirmation. If most arrive after the estimated date, the problem is delays with no warning.
Our free support KPI calculator keeps these numbers next to response time and resolution, so you can see the effect of each change.
Prevent WISMO: the five messages every order needs
Most order-status questions are answered by a message the customer should have received but did not, or received without the one fact they needed. Five messages cover the whole journey:

| Message | When | What it must include |
|---|---|---|
| Order confirmation | At checkout | Order number, a delivery window in dates ("arrives 14 to 17 May"), and a link to the order status page |
| Shipped | When the label is scanned | Carrier, tracking link to your own status page, updated delivery window |
| Delay notice | As soon as you know the window will slip | The new date, the reason in one line, and what the customer can do |
| Out for delivery | Morning of delivery | That it arrives today, and safe-place or pickup options if the carrier offers them |
| Delivered | On the delivered scan | Where it was left, and what to do if they cannot find it |
Use dates, not "3 to 5 business days"
"3 to 5 business days" makes the customer do maths, and they will count from the wrong day. "Arrives Thursday 16 May to Monday 20 May" sets a date they can check before they write to you.
The delay notice is the one most stores skip
Confirmation and shipping emails are switched on by default in most store platforms. The delay message usually is not, and it is the one that prevents the angriest tickets. A short note sent before the customer notices is received very differently from the same news after they chase you.
In the US it is also a legal duty. Under the FTC's mail order rule, if you cannot ship within the time you stated (or within 30 days if you stated none), you must tell the customer, give a new date and offer the option to cancel for a full refund (FTC business guide).
Tell customers what to do if "delivered" is wrong
The delivered message is your chance to deflect the hardest WISMO ticket. One line helps: "Can't find it? Check with neighbours and your building's mailroom, and if it hasn't turned up by tomorrow evening, reply to this email." Parcels marked delivered often turn up with a neighbour or in a mailroom, and the customer already knows the next step if they do not.
Make tracking easy to find on your site
A customer who cannot find the tracking link in their inbox will look on your site next. If they do not find it there in a few seconds, they open chat.
- Put a "Track your order" link in the header or footer of every page, pointing to your order status page.
- Use your own status page instead of sending people to the carrier's site. On Shopify, the order status page lets customers look up an order with the order number and their email or phone number, without an account.
- Add a "Where is my order?" article to your help center with the steps, the usual delivery times by region and what to do if a parcel is late.
- Show the delivery window on product and cart pages, so the expectation is set before payment.
- Mention the tracking page in your chat welcome message during busy periods: "Checking on an order? Track it here."
Answer WISMO tickets fast: saved replies and chat
Prevention will never get WISMO to zero. For the rest, speed matters more than prose. A customer asking where their order is wants a status and a date, ideally in the first reply.
The 60-second lookup
- Find the order by number, email or name.
- Open the tracking and read the last scan and its date.
- Compare against the delivery window you promised.
- Pick the matching saved reply, fill in the facts, send.
If your help desk shows order details next to the conversation, step 1 disappears. If it does not, keep your store admin open in a pinned tab during busy periods.
Saved replies for each case
Not shipped yet, inside the promised window:
Your order #4821 is being packed and will ship by Wednesday. You'll get a tracking link by email as soon as it's scanned, and it should arrive between 16 and 20 May.
In transit, on time:
It's on its way. The last scan was this morning at the Leeds depot, and it's still due between 16 and 20 May. You can follow it live here: [tracking link].
Stuck, no scan for several days:
Thanks for checking. Tracking hasn't moved since Friday, which is longer than it should be, so I've opened a trace with the carrier today. I'll update you by Thursday either way, and if it hasn't moved by then we'll send a replacement.
Delivered but not received:
Sorry, that's worrying. The carrier marked it delivered at 2:14 pm yesterday. Could you check with neighbours, any mailroom and around the door? If it hasn't turned up by tomorrow evening, reply here and we'll open a claim and arrange a replacement or refund.
On live chat, send the status in the first message and the detail in the second. A customer on chat expects an answer while they wait; a customer on email expects a complete answer once. Our canned response examples include more order-status wording.
Handling delays, lost parcels and wrong addresses
Delays
Tell affected customers before they ask. If a warehouse backlog or a carrier strike affects a batch of orders, send one email to everyone in the batch with the new window. Then add a short banner to the site and the chat greeting. One message to 200 customers costs far less time than 60 replies.

Lost parcels
Decide in advance when a parcel counts as lost, so agents do not invent a rule each time. A common approach: open a trace when tracking has not moved for a set number of business days, and treat it as lost if the trace has not found it by a second deadline. At that point, reship or refund straight away and file the carrier claim yourself. The customer should never have to deal with the courier.
Wrong or incomplete addresses
If a customer reports a typo before shipping, fix it and confirm in writing. After shipping, check whether the carrier allows a redirect. When a parcel comes back to you because of a customer's own mistake, your policy should say who pays to resend it, and the agent should quote it.
Where an AI agent helps and where a person must step in
WISMO looks like the perfect job for a chatbot, and partly it is. An AI agent trained on your shipping policy, delivery times and help articles can answer "how long does shipping to Canada take?" or "how do I track my order?" any hour of the day, and point people to the tracking page.
What it can do depends on what it can see. An agent that only reads your website knows your policy, not where order #4821 is. Without a live order connection, it should collect the order number and hand the conversation to a person rather than guess.
A person should always take over when:
- the parcel is marked delivered and the customer does not have it;
- the customer asks for a refund, a replacement or an address change;
- tracking shows an exception or no movement past your threshold;
- the customer is upset, or has asked more than once.
Sellio's AI agent works this way on website chat only: it answers from your own website and documents, hands off to a person when it is unsure, and can be capped so the spend cannot run away. Questions arriving by email or other channels go to the shared inbox for your team.
Escalation rules and carrier claims
Write these rules down before the next sale. A hypothetical set for a small store shipping domestically:
| Trigger | Action | Owner |
|---|---|---|
| Order not shipped within the promised handling time | Send a delay notice with a new date and the option to cancel | Agent |
| No tracking scan for 3 business days | Open a carrier trace, tell the customer the date of the next update | Agent |
| Trace finds nothing after 5 more business days | Reship or refund, file the claim | Agent, within approval limit |
| Delivered, not received, after 48 hours | Reship or refund under $75; above that, review first | Agent, then lead |
| Second WISMO contact on the same order | Assign to one person who owns it until delivery | Lead |
Adjust the days and amounts to your carriers and margins. An agent should never have to ask "what do we do now?" during a busy week. Assigning the case to one owner with a ticket status such as "waiting on carrier" stops the second and third follow-ups from landing with different people; a ticketing system makes that the default.
For claims, keep the order number, tracking number, the delivered scan or last scan, the declared value and the customer's message together. Most carriers ask for the same set, and having it in one place turns a claim into a ten-minute job.
Metrics to watch after changes
Change one thing at a time and give it two to four weeks. Then compare:

- WISMO contacts per 100 orders, the main number. It should fall after you add delivery dates and a delay notice.
- WISMO share of all conversations, which shows whether order status is still your biggest topic.
- First response time on WISMO tickets. Our first response time estimator helps set a realistic target for your team size.
- Repeat contacts on the same order. A high number means first replies are missing a date or a next step.
- Satisfaction on order-status conversations, measured separately from returns and product questions.
Tools that help with WISMO
You do not need a dedicated app to start. A store platform's own order status page, its shipping notifications and a shared inbox with saved replies cover most small stores. Add tools when a specific gap shows up:
- A tracking app if your platform's notifications cannot send delay or out-for-delivery messages.
- A help desk that shows order data beside the conversation, such as Gorgias for Shopify stores, if lookups are eating your agents' time.
- Live chat with a help center and an AI agent if most questions are general ("how long to Australia?") rather than about a specific parcel. Our guide to live chat for e-commerce covers the setup.
If you are still choosing a help desk, our comparison of Freshdesk vs Help Scout looks at how two common options fit a five-person team.
Common mistakes
- Sending customers to the carrier's website, where the status codes mean nothing to them.
- Promising "3 to 5 business days" without saying from when.
- Staying silent when an order is late and waiting for the customer to notice.
- Answering "it's on its way" without a date, which guarantees a second message.
- Letting the bot guess at an order's location when it cannot see the order.
- Making the customer file the carrier claim.
WISMO checklist
- Order confirmation shows a delivery window in dates and a status page link
- Shipping email links to your own tracking page
- Delay notice switched on and sent before the customer asks
- Delivered email says what to do if the parcel is missing
- "Track your order" link in the site header or footer
- Saved replies for the five WISMO shapes
- Written rules for traces, lost parcels and delivered-not-received
- WISMO tag on every order-status conversation, reviewed monthly
FAQ
What does WISMO stand for?
"Where is my order?" It covers every customer question about an order's status, from "has it shipped?" to "tracking says delivered but I don't have it".
How do I reduce WISMO tickets quickly?
Put a delivery window in dates on the order confirmation, link the shipping email to your own tracking page, and send a delay notice as soon as an order will be late. Those three changes address the most common reasons customers write in.
Should a chatbot answer where is my order questions?
It can answer general questions about shipping times and point people to the tracking page. Unless it is connected to your live order data, it should hand specific order questions to a person instead of guessing.
When should we treat a parcel as lost?
Set your own threshold based on your carriers: for example, a trace opened after three business days without a scan, and the parcel treated as lost if the trace finds nothing within another five. Then reship or refund without making the customer wait for the claim.
What is a good WISMO rate?
There is no reliable universal benchmark. Track WISMO contacts per 100 orders in your own store and aim to bring it down after each change; a falling number matters more than any industry figure.




