WISMO stands for "Where Is My Order?", and if you work in logistics, you're probably sighing because you know exactly what it means. WISMO queries are the bane of customer support in logistics. A customer places an order. They wait. They get anxious. They have tracking information in their email, but they don't open it. So they call customer service, send a WhatsApp message, or email: "Where is my order?" The support team has to look up the tracking data, find the package status, and tell the customer where it is.
This happens thousands of times per day across India's logistics ecosystem. A major logistics player processes 50,000 deliveries daily. If even 20% of those customers reach out with a WISMO query (and that's conservative), that's 10,000 inbound customer service interactions per day. At an average handling time of 3–5 minutes per query, that's 500–800 hours of support team capacity consumed per day. For a 24/7 operation, that means hiring 30–50 full-time support agents who do nothing but answer WISMO queries.
Now imagine if 80% of those queries never came in. Imagine if the customer knew their package status before they thought to ask. That's the opportunity. It's not hypothetical. it's achievable with a different communication architecture.
The Cost of Reactive Tracking Communication
Let's talk about the real economics. A logistics company with 50,000 daily deliveries operates a customer support center. Peak inquiry load is during the evening (5–8pm) and on delivery day itself. Support staff are scheduled based on peak demand, which means you're paying for capacity whether it's used or not.
During peak seasons. Diwali, year-end sales, Big Billion Day, the first week of every month when salaries are paid. WISMO volume spikes. A normal day might have 10,000 WISMO queries. A peak day might have 25,000. That's a 2.5x spike, and the company has to staff for it. You can't fire agents on the 15th because there are fewer queries. You've hired them for the month.
On top of the labour cost is the infrastructure cost. A customer service platform that handles 10,000 concurrent chats or calls during peak requires significant capacity. You're paying for compute, network, and software licenses that scale with peak demand, not average demand.
But the biggest hidden cost is the expectation gap. Customers have been trained by Amazon Prime, Flipkart, and other e-commerce giants to expect proactive tracking notifications. When a shipment departs the warehouse, you get a notification. When it's out for delivery, you get a notification. When it's delivered, you get a notification. The logistics company has all this data. the warehouse system, the in-transit GPS, the final mile app all know where the package is.
Yet many customers still don't get these notifications. The notifications might exist but be delivered through a low-engagement channel (email). Or they're sent via SMS but the customer ignores them. Or the customer never received the notification because they don't check email or SMS regularly. So they revert to calling.
Proactive vs. Reactive: The Model Shift
The economic shift happens when you move from reactive to proactive notification. Instead of waiting for the customer to ask "Where is my order?", you tell them before they ask.
Here's what that looks like operationally. Your warehouse system sends a package out. Immediately, an AI agent sends a WhatsApp message to the customer: "Your order of 2 tee shirts from XYZ Brand has just left our warehouse. Expected delivery: [date]. Track here: [link]." The customer receives this proactively, understands the status, and doesn't need to ask.
The next day, when the package is out for delivery in the customer's area, the agent sends another message: "Your package is out for delivery today between 2–4pm. Driver name: Rajesh. Contact: 98765-43210. Track live: [link]." Again, the customer knows before they think to ask. No support ticket needed.
If the delivery attempt fails (door not answered, address issue), the agent sends a notification immediately: "Delivery attempt failed. We'll reattempt tomorrow. If you want to reschedule, reply here." This creates a two-way channel. Customers who need to reschedule can do so without calling support.
The data points that matter are straightforward: warehouse departure, delay risk flagging (if the package is behind schedule), out-for-delivery status, failed delivery attempts, rescheduling, successful delivery, and return initiation. Most of these can be triggered automatically by events in your logistics system.
For India, WhatsApp is the critical channel. It's where your customers are already communicating. SMS open rates are low. Email is ignored. In-app notifications only reach customers who actively use your app. WhatsApp reaches everyone. rich, poor, urban, rural, tech-savvy, and non-tech-savvy alike.
The Last-Mile Communication Stack
A full AI communication layer for a logistics operation looks like this: All shipment status events (departure, en-route, out for delivery, etc.) trigger a notification workflow. Each event has a message template in multiple languages. Hindi, Tamil, Telugu, Kannada, Marathi, etc. Each template is personalised with the customer's name, package contents, and relevant details.
The agent sends the message via WhatsApp. If the customer responds, the conversation continues. If they confirm "I'll be home at 4pm," that information goes back to the driver's app. If they say "I can't take delivery today," the system offers alternatives. This two-way loop is critical.
For exceptions. packages delayed beyond SLA, damaged packages, lost packages. the logic is different. These aren't simple status updates. They require customer care intervention. But the AI still plays a role. It detects the exception, sends an immediate notification: "We've detected an issue with your delivery. Our support team will contact you within 2 hours," and flags the case to the appropriate ops team.
The POD (Proof of Delivery) collection agent is a separate workflow. After delivery, many logistics companies struggle to get drivers to actually submit their POD evidence (photo, signature). This leads to disputes with customers who claim non-delivery. An AI agent can follow up with the driver: "We need your POD for delivery XYZ123. Upload photo here: [link]." It can also follow up with the customer if there's a mismatch.
All of this runs on top of your existing TMS (Transport Management System) and OMS (Order Management System). The AI agent is an orchestration layer, not a replacement system. It reads the status from your existing systems and coordinates communication.
B2B Logistics: The Consignee Communication Gap
Most logistics AI articles focus on B2C. direct-to-consumer e-commerce deliveries. But B2B logistics has an even larger communication gap. A freight company ships goods to a warehouse or retail store. The shipper knows the status because they're in regular contact with the freight company. But the consignee (the warehouse that's receiving the goods) is often left in the dark.
The warehouse calls repeatedly: "Has my shipment left the hub?" "Is it in transit?" "When will it arrive?" The operations team at the freight company handles these calls manually, looking up tracking data and calling customers back. It's the same WISMO problem, but in B2B format.
An AI agent solves this too. The warehouse receives automatic notifications: "Your LTL shipment SHIP-123 of 8 pallets is in transit from Delhi Hub. Current location: Agra. Expected delivery: Thursday 3pm." No phone calls needed. The operations team can focus on exceptions.
Customer Experience in Logistics: Exceptions Are the Differentiator
Here's the hard truth about logistics: most shipments move smoothly. They're picked, packed, loaded, in-transit, out-for-delivery, and delivered within the promised timeframe. For these shipments, the customer doesn't need much communication. just a simple status update.
The brand differentiator is how you handle the 3% of shipments that go wrong. A package is delayed. A driver can't find the address. A package gets damaged. In these situations, the customer's experience with your support team is what determines whether they use you again or switch to a competitor.
An AI communication layer makes the 97% frictionless and frees your operations team to focus on the 3%. You're not paying support agents to answer status queries. You're paying them to solve problems. That's a much higher-value use of labour.