Count your support messages for a week and one question will dominate: "order kahan hai?" It isn't really a question — it's a symptom. The customer paid, heard nothing, and anxiety did the rest. Every one of those messages is a failure of proactive communication, and every one was preventable with three automatic updates.
The three messages that end the question
Good news {{name}} — order #{{order}} aaj dispatch ho gaya 🚚 Courier: {{courier}}. Track: {{tracking_link}}. Expected delivery: {{date}}.
On dispatch (AWB assigned){{name}} ji, aapka order aaj delivery ke liye nikla hai 📦 COD amount: ₹{{amount}} — ghar par koi rahega na? Koi change ho to yahin bata dein.
Out for delivery — the RTO killer (see below)Delivered! 🎉 {{name}}, hope everything is perfect. Koi bhi issue ho to seedha yahin message karein. Product pasand aaye to review de dein: {{review_link}}
On delivery — support + review in oneAll three are utility templates — transactional updates about an existing order — so they cost paise, not the marketing rate (the difference is explained in our WhatsApp API pricing guide).
The COD-RTO angle nobody automates
For COD-heavy D2C, returns-to-origin are the silent margin killer: you pay forward shipping, return shipping, and repacking on an order that earned nothing. A large share of RTO is simply the customer wasn't ready — not home, no cash, forgot ordering during a late-night scroll.
Message 2 attacks exactly that: it names the COD amount and asks for a confirmation before the courier reaches the door. The customer who replies "aaj nahi, kal bhejo" just saved you a failed delivery attempt. The one who replies nothing at least saw the amount and kept cash ready.
How the plumbing works in Yantra
Shiprocket is a built-in connector: connect once with your API credentials, and the shipment-updates template wires the flow — order ships, Yantra tracks the AWB, and each status milestone fires the right WhatsApp message from your own number. Statuses arrive, messages go out, and the run log shows every send. If Shiprocket's API hiccups, the step retries by itself, and a failed run is never billed.
Close the loop with the GST invoice automation (invoice PDF into the same chat) and a review request two days after delivery — one order, one chat thread, zero manual messages.
Retire "order kahan hai?" this week
Start free — 1,000 runs. Shiprocket connector + tracking template included.
Start free