WISMO in freight is the where-is-my-shipment block: the steady stream of status requests from shippers, consignees, and carriers that dominates broker and forwarder inboxes. The acronym comes from retail's where is my order, but in freight the question is about loads, containers, and delivery appointments.
Industry research puts WISMO at 30 to 45 percent of all inbound volume at a broker or forwarder, which makes it the single biggest block of repetitive work in the vertical. Each request looks small: check the visibility feed, check the TMS, write back. But every load has several parties entitled to ask, and each answer takes minutes by hand. The block is also the most automatable work on the desk, because the answer already exists in structured data. What is missing is someone to fetch it, interpret it, and reply on the thread.
The move to reject is deflection: answering the where-is-my-shipment email with a tracking link and counting it resolved. In freight the link rarely settles anything. The asker wanted to know whether the delay threatens a dock appointment or a production schedule, not the coordinates of a trailer. Deflected WISMO comes back as a second email carrying more frustration than the first, and a metric that celebrates the deflection hides the fact that the desk answered the same question twice.
WISMO in retail vs WISMO in freight at a glance
| Dimension | WISMO in retail | WISMO in freight |
|---|---|---|
| Who asks | one consumer per order | shipper, consignee, and carrier per load |
| Stakes | a late package | dock appointments, production schedules, detention |
| Data source | one carrier tracking page | visibility feeds plus the TMS plan |
| A good answer | a delivery date | on plan or not, and what happens next |
Aide, the agentic AI platform for customer experience, treats the freight WISMO block as the first thing to automate, one status intent at a time. It classifies the request, pulls the load's position and plan from visibility and TMS context, and answers on the thread with the consequence included: on schedule, or delayed with a revised ETA and what that means for the appointment. Each intent is rehearsed against the operation's real historical threads before going live, and automated replies stay logged for review. For the full picture of the status block and what absorbs it, see Aide for logistics and freight.
Frequently asked questions
- Why is WISMO volume so high in freight?
- Because every load has several parties with a stake in its position and no single shared view of it. Status data sits fragmented across carrier feeds, visibility platforms, and the TMS, so the inbox becomes the lookup service for everyone the load touches.
- Can WISMO in freight be automated?
- Yes, and it is the strongest candidate on the desk. The answers live in structured tracking and TMS data, the requests follow predictable patterns, and the volume is high enough that automating this one block frees a disproportionate share of ops time for exceptions.