Reducing WISMO questions in your webshop

WISMO stands for Where Is My Order: the question a customer gets stuck on the moment an order leaves the warehouse. In many webshops this is not just one question among many, but the single largest category in the inbox. Teams often see that between 30% and 50% of all incoming contacts are about the status of a delivery. Each question is small on its own, but the volume makes it one of the most expensive and demoralising flows in customer service.

What is distinctive about WISMO is that it is rarely about the service itself. The customer is happy with the product and the order went through. What is missing is certainty about when the parcel will arrive. That uncertainty appears at predictable moments. Right after checkout, on the promised delivery day, and the moment a deadline starts slipping. Anyone who knows those moments can get ahead of the question.

This article covers the complete playbook to reduce WISMO questions, from the expectation you set up front to proactive updates and AI that fetches the status itself. The goal is explicitly not to answer the question faster, but to make it largely disappear. A team that solves WISMO by working harder keeps the problem alive. A team that solves WISMO with better information flows sees the volume drop structurally.

The cost of WISMO rarely sits in a single conversation, it sits in the sum. A WISMO question costs an agent a few minutes on average. Read the message, look up the order number, log into the carrier, report the status, close the ticket. Multiply that by hundreds or thousands of questions a month. That is a full-time role relaying information the customer could have found themselves.

Then there is the hidden cost. WISMO questions tend to arrive in peaks: after a sale, around holidays, during delays caused by weather or carrier congestion. Exactly when your team is already busy, the volume rises hardest. The result is longer wait times on every question, including the complex ones where your team genuinely adds value. WISMO crowds out the work that matters, and that is a cost no ticket report shows.

There is also an effect on the team itself. Typing the same answer to the same question dozens of times a day is exhausting and offers little satisfaction. It is work nobody enjoys and that simultaneously eats the most time. A team relieved of that burden can focus its attention on the conversations where empathy and judgement genuinely make the difference.

Finally there is customer satisfaction. A customer who has to ask about their order already feels a lack of control. If that person then has to wait hours or a day for an answer, frustration compounds at an already tense moment. Reducing WISMO is therefore not only a cost saving, but a direct improvement to the experience at the moment the customer is most vulnerable.

The following six steps together form a funnel. Each step catches the questions the previous one let slip, so that by the end only a fraction remains that genuinely needs human attention. The steps increase in effort and impact: the first are mostly a matter of better copy, the last call for automation and integrations. Together they bring the volume down layer by layer.

Step 1: Set realistic expectations before the purchase

WISMO does not start after the order, but before it. A customer who sees a vague or overly optimistic delivery time at checkout is quicker to doubt once that window approaches. So show a concrete, honest delivery time on the product page and in the cart, not just a generic promise like ‘fast delivery’. Be explicit about what happens with stock shortages, pre-orders and weekend delivery.

A concrete example: a webshop that shows a fixed promise of ‘delivered tomorrow’ on every product triggers a WISMO question for every item that is out of stock. A webshop that shows a current delivery time per product based on real stock prevents that disappointment before the order is even placed. An expectation that holds up prevents the question that would otherwise inevitably follow.

Step 2: Send a confirmation that reassures the customer

The order confirmation is your first chance to answer the question before it arises. Mention not only what was ordered, but also when the customer can expect the next update and through which channel. Most confirmation emails miss exactly this: they confirm the purchase but say nothing about what comes next, leaving the customer in an information vacuum.

A line like ‘you will receive tracking as soon as the carrier picks up your parcel, usually within one business day’ removes the uncertainty. The customer now knows that silence is normal and waits calmly. Without that line, the customer interprets silence as a problem, and that is exactly the moment the first WISMO email gets sent.

Step 3: Make tracking findable and self-service

Many WISMO questions arise simply because the customer has lost their tracking link. The email has vanished into a full inbox, or the customer ordered as a guest and does not know where to look. Make the status available in several places. In the confirmation email, in the customer account, and on a status page where an order number and postcode show the current state straight away.

The lower the threshold to check themselves, the fewer people ask you. A good rule of thumb. If a customer can see the current status within two clicks and without logging in, half of the potential WISMO questions are already caught. Information that exists but cannot be found counts as absent to the customer.

Step 4: Inform proactively at every status change

This is the step with the biggest impact. Don't wait until the customer grows anxious. Send a message automatically at the relevant moments: picked up, in transit, out for delivery, delivered. Each update removes a reason to reach out, because the customer gets the answer before the question even forms.

The crucial one is the delay notification. A customer who proactively hears that their parcel will arrive a day later and why does not send an angry email. A customer who has to discover for themselves that the promised day has passed does, and often with more frustration than the delay itself warrants. Proactive transparency about bad news is stronger than silence about good news.

Step 5: Catch the remaining questions with AI that fetches the status itself

Even with perfect communication a stream of questions remains. People who email anyway, edge cases and exceptions. And customers who would rather ask a person than check a status page. You solve that last layer by having the question handled automatically. An AI agent recognises the customer and links the question to the right order. It then fetches the current status from the carrier and gives a concrete answer, with no agent involved.

The difference with an ordinary chatbot is that the AI consults the real data instead of returning a canned line. The customer gets no ‘check your tracking’, but ‘your parcel was sorted at the depot this morning at 9:14 and will be delivered tomorrow between 1pm and 3pm’. Only for a genuine exception, such as a missing parcel, does a human take over with the full context already prepared.

Step 6: Close the loop with a follow-up action where needed

Sometimes the answer to WISMO is not the end, but the start of something. A parcel stuck with the carrier for a week calls for an investigation; a parcel marked as delivered that the customer never received calls for a claim. By automatically turning such a question into a task with a deadline, the follow-up does not slip through.

This way the hardest WISMO category, the exception that genuinely goes wrong, is also handled cleanly instead of vanishing into a full inbox. The customer sees that something is happening, and the team has a clear next action with an owner and a deadline. That completes the funnel: from expectation to exception, every layer is caught.

Without measurement you cannot tell whether your effort has any effect. So track a few concrete numbers. The most important is the share of WISMO in your total contact volume. Count how many of your tickets are about delivery status and follow that percentage over time. If it drops after enabling proactive updates, the approach is working. If it rises in a particular period, that is a signal something is going wrong in the chain, for instance with a specific carrier.

Also look at contacts per order. A healthy webshop sits comfortably below one; if you are above it, every order generates more than one question on average and there is ground to gain. Track the automatic resolution rate too: what share of WISMO questions is resolved without a human being involved. That figure shows how much work you have actually taken off the team.

And finally, measure customer satisfaction on status questions separately, because a fast but impersonal answer can still irritate. High automatic resolution with low satisfaction means the answers are too cold or too incomplete. Improvement is iterative. Start with the biggest lever, usually the proactive delay notification. Measure the effect, then tackle the next layer. WISMO does not disappear all at once, but it does disappear structurally.

WISMO is not an inevitable cost, but a design problem. The question arises from uncertainty, and uncertainty is solved with clear expectations, timely information and self-service. The six steps together form a funnel that catches the volume layer by layer, until only a fraction remains that genuinely needs human attention. Whoever only gets faster reactively keeps the problem alive; whoever improves the information flow sees WISMO disappear structurally.

With Cuego for WISMO you automate the last and heaviest layer. The AI recognises the customer, fetches the status itself and answers directly. Your team only sees the real exceptions. Explore how to automate shipping questions, how the live chat handles this in the webshop and which webshop integrations are possible, or request a demo.