WISMO is support shorthand for "where is my order", the shipping-status question that is typically the single highest-volume intent in an ecommerce queue. Every order a store ships can generate one, and during carrier delays and peak season most of them do.
The customer who sends a WISMO ticket usually has a tracking link already. They write because the link stopped answering: the page has not updated in days, the estimated date came and went, the package shows delivered but never arrived, or the order split into shipments the tracking page does not explain. Answering properly means reading the live order and fulfillment state: what the order system says was picked and packed, what the carrier scan history actually shows, and whether anything is off plan. That is why WISMO fills agent queues even at stores with good tracking pages: it is a lookup a human has to do across systems, order by order.
The popular response is a chatbot that replies with the same tracking link the customer already checked, then counts the exchange as deflected. That is the tracking-page loop: the customer asked a question the link could not answer and got the link again. They write back more frustrated, or open a chargeback instead. A template with a tracking URL is not an answer to WISMO. The order's actual state is.
Tracking-link reply vs order-aware answer at a glance
| Dimension | Tracking-link reply | Order-aware answer |
|---|---|---|
| What it reads | nothing, it pastes the link | live order, fulfillment, and carrier state |
| What the customer gets | the page they already checked | the actual status of their delivery |
| Stalled or lost packages | the same link again | recognized as exceptions and handled |
| Repeat contacts | likely, the question still stands | rare, the question was answered |
Aide, the agentic AI platform for customer experience, answers WISMO from the order itself. It reads the live order and fulfillment state before it writes a word, tells the customer what is actually happening with their delivery, and flags stalled or lost shipments to the team instead of papering over them. Every automated reply is logged, and because each conversation is classified by intent, the team can see exactly how much of its queue is status traffic and what is driving it. See Aide for ecommerce customer service for how WISMO gets resolved on live order data.
Frequently asked questions
- Why do customers send WISMO tickets when they already have a tracking link?
- Because the link stopped answering. Tracking pages go quiet between carrier scans, miss delivery-date changes, and say nothing about split shipments or packages marked delivered that never arrived. The customer is asking a question the page cannot answer.
- Can AI handle WISMO requests?
- Yes, and it is usually the first ecommerce intent worth automating: high volume, answerable from order and carrier data, and easy to bound. The requirement is that the AI reads live fulfillment state rather than templating a tracking link, and escalates the genuine exceptions.