WISMO — “where is my order?” — is retail’s name for the status-question flood, commonly benchmarked at 20–40% of e-commerce support tickets at roughly $5 per contact (retail-side figures; freight has no equivalent public number). Freight’s cousin is “where is my container?”, and it arrives on WhatsApp at 9 a.m., marked urgent, from customers who each believe they asked once. The fix retail converged on applies directly: updates that land before the question make the queue collapse.
What does retail actually know about WISMO?
That it is measurable, and huge. Industry benchmarks put WISMO at 20–40% of all e-commerce support tickets, with a cost per contact around $5 — retail numbers, from a world of parcels and consumers, so carry them across to freight carefully. But the structural insight travels intact: a status question is pure waste, because the answer already exists somewhere. The customer is paying attention-tax to extract information the seller already had.
What does the freight version look like?
Fourteen customers, one question, forty times a day. Each answer means a coordinator visiting a carrier portal, re-keying a container number, interpreting the event trail, and typing a reply — per shipment, per ask. TMS vendors have named the customer status loop a churn driver, and there is no published figure for the hours a forwarder’s customer-service team burns on it, which says less about the size of the problem than about who has bothered to measure it.
Retail knows its WISMO share to the percentage point. Nobody has published the freight equivalent — hours per week a forwarder’s CS desk spends answering “where is my container?”. Every operator we ask knows their own number is too high; the category just hasn’t written it down yet.
Why does proactive kill the queue?
Because a status question only exists while the customer lacks the status. Deliver the milestone before it is asked for and the question has nothing to attach to. Vendor studies claim proactive notifications cut inbound status inquiries by 35–55% — vendor figures, but the direction is unanimous — and a Logixboard-commissioned FreightWaves survey found 81% of shippers call visibility table stakes, and 46% have left a forwarder for one with better technology (vendor-commissioned, read accordingly; the switching risk is the point). The forwarders winning that trade are the ones whose updates arrive first.
What does killing the queue look like?
Every milestone that matters — departed, transshipped, arrived, out for delivery, exception, POD — becomes an update on the customer’s channel, in their language, drafted by the desk and approved by your team until you dial it to auto. The storm stops not because customers were trained to wait, but because there is nothing left to ask. Watch an update land before the question on how it works, put your inquiry volumes into the calculator, or start from the complete guide.
Put the watch on your boxes.
Everything on this page runs live in a working tracking desk. Bring ten shipments on the water and watch the updates land before the questions do.
Book the working session