What is WISMO? The support question eating your queue

WISMO stands for "Where Is My Order". It is the shorthand ecommerce support teams use for every message asking about a package in transit: where is my order, has it shipped yet, why is it late, when will it arrive. Together with returns and cancellations, WISMO typically makes up 30 to 50% of an online store's support queue.

What counts as a WISMO ticket

Any contact where the customer already bought and now wants to know where the thing is. The phrasing varies. The underlying question does not.

• "Where is my order?" (the classic)
• "I ordered on Monday and haven't heard anything."
• "The tracking page hasn't updated in four days."
• "It says delivered but I don't have it."
• "Will this arrive before Friday? It's a gift."

Notice what these have in common. The answer lives in your order and carrier data, and answering requires no judgment call. That combination is why WISMO is usually the first thing stores automate.

Why WISMO dominates the queue

Every single order can generate a WISMO ticket. Most support categories scale with problems: a sizing question needs a confused customer, a complaint needs a defect. WISMO only needs a customer who is waiting, and after checkout, every customer is waiting.

The trigger is usually a gap. The order confirmation promised "3 to 5 business days", day four arrives, and the tracking page still says "label created". The customer has no way to tell the difference between "normal carrier lag" and "my package is lost", so they ask you. Reasonable behavior on their side. Pure repetition on yours.

Add returns and cancellations, the two other order-operations questions, and you typically get to 30 to 50% of all tickets. Customers are not being difficult here. The store simply holds information they cannot see.

What WISMO costs: a worked example

The math is simple: tickets times minutes times what a support minute costs you. This is an example calculation, not a benchmark. Plug in your own numbers.

Take a store doing 2,000 orders a month:

• Say 1 in 13 orders triggers a WISMO contact. That is roughly 150 tickets a month.
• Each one takes about 6 minutes: read the message, find the order, open the carrier page, translate the tracking status into a human answer, reply. 150 × 6 = 900 minutes, or 15 hours a month.
• At a loaded support cost of $28 per hour (wage plus employer costs and overhead), that is 15 × $28 = $420 a month, about $5,000 a year.

Five thousand dollars a year to answer one question whose answer already sits in your systems. And the direct handling cost is the small part. Each WISMO ticket interrupts whatever your team was doing, and a slow answer often produces a second, angrier message on another channel. Same customer, now two tickets.

WISMO spikes exactly when you are busiest

WISMO scales with orders, so your best weeks are your worst support weeks. Black Friday and Cyber Monday are the extreme case. Order volume multiplies, carriers get overloaded so delays rise, and many of those orders are gifts with a hard deadline. All of that pushes the WISMO rate per order up, at the exact moment your team is already at capacity.

This is worth planning for now, in July, rather than in the second week of November. A queue that runs fine at 2,000 orders a month can bury a two-person team at 6,000. Hiring temps to copy tracking statuses into emails is an expensive way to solve a data problem.

How stores reduce WISMO

Three approaches work, and they stack. Each one removes a reason for the customer to write in.

1. Proactive tracking updates

Tell the customer before they ask. Order confirmed, shipped, out for delivery, delivered, and crucially: delayed. A short "your package is running two days late, new expected date Thursday" email prevents the ticket entirely. Most WISMO contacts happen because the store went silent between "shipped" and the doorbell.

2. A self-service order lookup

A page on your own domain where the customer enters an order number or email and sees live status. This catches the customers who want to check for themselves at 11pm. It only works if it shows real carrier data in plain language. A page that repeats "label created" just moves the confusion.

3. Automation that answers with the actual delivery window

Some customers will still write in, and this is where most automation falls short. A bot that replies with a tracking link has done nothing. The customer had the link. They wrote in because the link did not answer their question.

The automation that works reads the live order and carrier data and answers the question directly: "Your order shipped Tuesday with DHL and is out for delivery. Expected today between 10:00 and 12:00." That resolves the ticket. A link deflects it, and deflected tickets have a habit of coming back.

Automating WISMO end to end

Because WISMO is high volume and fully answerable from data, it is the ideal first candidate for an AI support agent. The bar to set for any tool you evaluate: it should pull the actual order, read the actual carrier status, and give the customer a concrete delivery window in the channel where they asked. If it can only hand out tracking links, it is a signpost, and your queue needs an answer.

Nousu is one way to do this end to end. It connects to your Shopify or WooCommerce store, reads live order and carrier data, and resolves WISMO questions in chat and email without a human touching them. Exceptions, like a package marked delivered that never arrived, go to your team with the context already gathered. You can read how that works on the order status automation page.

If you are weighing what kind of tool can actually do this, the difference between answering and acting is the subject of chatbot vs AI agent.