“Where is my order?” – reducing WISMO requests before they happen

Open your support inbox and count the first twenty emails. If your shop runs anywhere near normal, six to ten of them are about the same thing: “Where is my order?” In support jargon that is WISMO, *Where Is My Order*. It is the most common request in e-commerce, it does not earn you a cent, and it almost always comes from an information gap you can close yourself.

This article shows where WISMO requests come from, what they really cost you, and in which order to remove them. The order matters. If you install a chatbot before you fix your shipping emails, you are automating a problem that should not exist in the first place.

Why customers ask even though they have a tracking number

A customer rarely writes because they cannot find the tracking number. They write because the number tells them nothing. The typical triggers:

• The shipment is “announced” but nothing moves. The label is printed, the carrier has not scanned the parcel yet. From the customer’s point of view the order has been “on its way” for two days and is standing still.
• The status is cryptic, in the wrong language, or both. “In transit to destination facility” reassures nobody who needs a gift by Friday.
• The delivery time in the shop was a promise the carrier does not know about. “Delivery in 2 to 3 days” means working days from dispatch to you. The customer reads: the day after tomorrow.
• The customer never saw the shipping email. Spam folder, wrong address, buried between twenty newsletters.
• Something really went wrong. Wrong address, parcel at the depot, delivered to a neighbour without a note.

Only the last point needs you. The first four are communication failures, and communication failures can be fixed without someone answering emails every day.

What a WISMO request really costs

Run the numbers once. Suppose you get 300 support requests a month and a third of them are WISMO. That is 100 emails. For each one you open the ticket, find the order, copy the tracking number into the carrier’s site, read the status, write a reply. Realistically that is three to five minutes per case if nothing gets in the way. That is five to eight hours a month for replies that are all the same in substance.

Then there are the hidden costs:

• Second and third follow-ups. Whoever was unsure once asks again at the next stop along the route.
• Reviews. An unanswered delivery question is the most common trigger for a bad review that has nothing to do with the product.
• Attention. Between 100 identical emails you miss the one that is actually urgent.

And the most important part: WISMO is not a support problem, it is a symptom. Every request tells you that a customer was unsure at a point where they should have been certain.

Step 1: Fix the shipping email

Before you automate anything, look at the email your shop sends after dispatch. In Shopify that is the “Shipping confirmation” template. In most shops the default text has been sitting there for years.

What belongs in the email:

1. A date, not a window. “Expected Thursday, 18 September” instead of “2 to 4 working days”. If you do not know the date, take the later end of the window. A customer who gets their parcel earlier does not complain.
2. A link straight to the shipment, not to the carrier’s homepage.
3. One sentence about the first scan. “The parcel is being collected today. The status usually updates in the evening or the next morning.” That one sentence catches a large share of first-day requests.
4. What the customer should do if the date passes. “If nothing has arrived by Friday, just reply to this email.” That sounds like more work, but it is the opposite: you decide when people ask, instead of every customer asking on day two.

If you use a carrier that sends its own status emails, decide who communicates. Two senders with slightly different information create more questions than one.

Step 2: A tracking page in your own shop

The carrier’s page is built for the carrier. It shows scans and terminal codes. Your own tracking page shows what the customer wants to know: roughly where the parcel is, when it arrives, and what to do if it does not.

A good tracking page translates status messages into sentences. “Arrived at destination parcel centre” becomes “Your parcel is in your region and should arrive tomorrow”. It also shows the contact route exactly where the question arises, not somewhere in the footer.

In Shopify the order status page gives you a basic version of this. It is better than nothing, but it shows the raw carrier status. If you seriously want to reduce WISMO, you cannot avoid translating the status texts, either through an app or through the support agent that writes the reply.

Step 3: Answer the requests that still come in automatically

Even with a perfect shipping email and a good tracking page, some customers will write. Some do not read emails, some are nervous, some really do have a problem. These requests are the case for automation, and for a specific kind of it.

An autoresponder that sends “We have received your request” does not help. A chatbot that asks for the order number and then hands out a link to the carrier helps a little. What really helps is an answer that knows the current status.

This is how it works at Humane: the agent reads the email, recognises it as a delivery question, finds the order in Shopify by email address or order number, and fetches the current shipment status from the carrier. Then it writes a reply that explains the status in one sentence and names the expected delivery date. If the carrier has not scanned the shipment yet, the agent says exactly that: the shipment is registered, there is no status yet, and that usually changes by the next morning. It does not claim the parcel is on its way when it is not.

Two rules matter here:

• The agent only replies when it can match the order without doubt. Two orders under the same address, a shipment without a tracking number, a status that points to a problem: in these cases no text goes out automatically. Instead a draft is prepared for you.
• The reply sounds like you. Not “Dear customer, your shipment is in the delivery process”, but the tone you set in your rules.

With WISMO in particular, that is the difference between a reply that closes the ticket and one that triggers the next follow-up.

Step 4: Recognise the cases that need a human

Not every delivery question is harmless. A few patterns should be filtered out automatically rather than answered with a standard reply:

• No scan for more than three working days after dispatch. The parcel is probably lost or sitting somewhere. This needs an enquiry with the carrier, not a status link.
• Status “delivered”, customer has nothing. The most common conflict case. The order here is: ask (neighbours, safe place, parcel locker), then a trace request, then replacement or refund. The customer wants to feel that someone is taking over the problem.
• A second enquiry about the same order. Someone who writes twice is no longer curious, they are impatient. From here on, no more canned text.
• Words like “gift”, “wedding”, “Friday”. A date in the text means the delivery depends on something. That is a case for priority.

A good support agent recognises these cases by status, timing and wording, and puts them in front of you instead of answering them. That is the line where automation has to stop.

How you know it is working

Three numbers are enough:

1. Share of WISMO in all tickets. Count before, then again after four weeks. If you have fixed the shipping email, the share should drop visibly without you having automated a single process.
2. Second enquiries per order. If customers do not write back after your reply, the reply was good. If they do, the date was usually missing.
3. Time to first reply on delivery questions. With WISMO, speed is almost more important than content. A reply after ten minutes with the correct status closes the ticket. The same reply after two days is too late, because the parcel has arrived in the meantime and the customer still feels badly treated.

In short

WISMO requests are not a law of nature. Most of them exist because a shipping email names a window instead of a date and because nobody tells the customer that a parcel often has no status on the first day. Fix the email first, then the tracking page, and only then let the remaining requests be answered automatically, with a real status instead of canned text. What is left are the cases where something actually went wrong. Those are exactly the ones you want to have time for.