WhatsApp shipping update templates
WISMO ('where is my order') tickets are the single largest support cost for e-commerce brands — 30-40% of total ticket volume. Proactive WhatsApp shipping updates cut that by 50-60% by removing the customer's need to ask.
All shipping updates are UTILITY category. Set up triggers from your shipping aggregator (Shiprocket, Delhivery, ShipStation, EasyPost) and fire one template per status change: shipped, in-transit, out-for-delivery, delivered.
When to use
On status webhook from carrier. Don't batch — fire each event as it happens.
Approval tips
- • UTILITY category — pure logistics updates.
- • Don't include 'rate us' or 'reorder' CTAs in the same template.
Best practices
- Out-for-delivery (OFD) is the most important — customers want to be home for it.
- Include tracking number and a one-tap track button.
- Don't send 'in-transit' updates from multiple hub scans. One per major status change.
- Delivery confirmation with a 'Was your package OK?' button catches damaged shipments early.
6 copy-paste templates
Submit each as a new template in your WhatsApp Business Manager. Variables ({{1}}, {{2}}) populate from your CRM at send time.
Hi {{1}}, your order #{{2}} has shipped.
Carrier: {{3}}
Tracking: {{4}}
ETA: {{5}}Shipped notification with tracking.
Hi {{1}}, your order #{{2}} is out for delivery today.
Delivery agent: {{3}}
Contact: {{4}}OFD alert. Most-opened shipping message of the entire flow.
Hi {{1}}, order #{{2}} has been delivered.
Thanks for shopping with {{3}}.Delivery confirmation. Issue button catches damage / wrong-item early.
Hi {{1}}, your order #{{2}} is delayed.
New ETA: {{3}}
Reason: {{4}}
We apologize for the inconvenience.Proactive delay notification. Reduces support tickets by 70%.
Hi {{1}}, we attempted to deliver order #{{2}} but couldn't reach you.
Next attempt: {{3}}Failed-delivery recovery. Prevents return-to-origin.
Hi {{1}}, return pickup for order #{{2}} is scheduled for {{3}} between {{4}}.
Please keep the package ready.Return pickup confirmation.
FAQs
Should I send updates from every carrier hub scan?
No. One per major status change (shipped, OFD, delivered). Hub-by-hub updates feel like spam.
What's the cost per shipping update?
Standard UTILITY pricing. India: ₹0.30-0.40 per delivered conversation.
Do I need a carrier integration?
Yes — fire templates from carrier webhooks. Shiprocket, Delhivery, EasyPost all support outgoing webhooks.
Can WhatsApp embed live tracking?
Not natively. Use a URL button linking to your carrier's tracking page or your own branded tracking microsite.
What if my carrier doesn't support webhooks?
Poll the carrier API every 30 minutes and diff statuses. Most BSPs have this prebuilt.
Should I include marketing offers in shipping updates?
No — splits intent and reclassifies the template as MARKETING. Send offers in a separate post-delivery message.
Skip the manual setup. Use LandinChat.
Official Meta Tech Partner powering WhatsApp marketing for 500+ businesses worldwide. Pre-built shipping update flows, broadcasts, chatbot, shared inbox — one flat plan.
See pricing