What does WISMO mean?
WISMO means 'where is my order', and it names the post-purchase ticket a customer opens when they want to know where their shipment is or when it will arrive. The term comes from support teams, who needed a short label for the ticket that arrives more often than any other. Variants include 'when will it ship', 'the tracking has not updated' and 'it says delivered but I do not have it', which are the same question at different points in the shipment's life.
The question is reasonable every time it is asked. The customer paid, the parcel is somewhere between the store and their door, and the only person who cannot see where is them.
Why does WISMO dominate store support?
WISMO dominates because it scales with orders in a way no other ticket does. A product question is asked once per shopper who is unsure; a where-is-my-order question can be asked by any customer who has ordered, and during a peak, when carriers slow down and estimates slip, a large share of them ask. Support volume rises with sales precisely when the team is busiest, and the tickets are individually trivial and collectively exhausting.
It is also the ticket customers most resent having to send. A store that answers it well earns little; a store that answers it slowly loses the second purchase.
What causes WISMO tickets upstream?
Most WISMO tickets are caused before the customer writes, by a gap in what the store told them. The causes below are the ones an Order Support FTE tags on every WISMO ticket so the owner can see which one dominates and fix it at the source.
- No tracking link, or a link sent before the carrier has scanned the parcel, so it shows nothing for a day.
- A vague delivery estimate at checkout, so the customer's expectation and the carrier's schedule disagree.
- A shipping notification that did not arrive, went to spam, or went to an old address.
- A carrier delay, exception or missed scan the store did not notify the customer about proactively.
- A 'delivered' scan with no parcel, which is a different problem wearing the same question.
What does a proper WISMO reply contain?
A proper WISMO reply contains the facts the customer could not see: the carrier, the last scan with its time and place, the current delivery estimate, and what happens next if that estimate passes without delivery. It links the tracking page. It does not say the parcel is on its way in a warm tone and nothing else, because that is the reply the customer already assumed and it invites the same question tomorrow.
Where the last scan is stale, the reply says so and states the store's rule: how many days past the estimate the store waits before it treats the parcel as lost and what it does then. Stating the rule prevents the second ticket.
How does the Order Support FTE handle WISMO?
The Order Support FTE on ftes.ai reads the order and the shipment's carrier scans before replying, states the last scan and the estimate plainly, links the tracking, and applies the store's lost-parcel rule where the estimate has passed. Routine WISMO replies are the class of ticket most stores promote first on the autonomy ladder, because the approval record is long and clean fast. A 'delivered but not received' ticket is treated differently: it follows the store's rule for that case and escalates above the goodwill limit.
It also tags every WISMO ticket with its upstream cause, so the monthly review can say that most of them came from a vague estimate at checkout, and propose the fix to the owner.
How should a store reduce WISMO at the source?
A store reduces WISMO at the source by giving customers the answer before they ask: a delivery estimate at checkout that matches what the carrier actually does, a shipping notification with a tracking link that goes out when the carrier scans the parcel rather than when the label prints, proactive notifications on carrier exceptions, and a plainly stated rule for late and lost parcels on the order page. Each of these removes a class of ticket rather than answering it faster.
The Order Support FTE's cause tags are the evidence for which fix matters most in this store. A store whose WISMO tickets are mostly stale-scan questions needs carrier exception notifications; a store whose tickets arrive the day after ordering needs a better estimate at checkout.