Shipping Updates WhatsApp Template for Logistics
A "where's my order?" ticket costs you an agent's time and the customer's patience. This ready-to-use, Meta-compliant WhatsApp shipping updates template answers the question before it's asked — the moment a parcel leaves the hub, your customer gets their name, order ID, courier, ETA and a live-tracking button, all in one tap-friendly message. It's built for Indian logistics, courier, D2C fulfilment and 3PL teams, submitted under the correct utility category, and ready to send within 24 hours of onboarding with InfiQ.
Variables
{{1}}= Rahul{{2}}= #ORD-48213{{3}}= Delhivery{{4}}= Wed, 10 Jul by 8 PM
Verified business
10:24
Preview · as customers see it
When to fire this template — and why timing beats copy
The shipping update earns its keep at exactly one moment: the first-mile scan, when the parcel physically leaves your hub and a tracking ID becomes real. Send it earlier and the tracking link shows nothing; send it later and the customer has already opened a ticket. Because it's tied to a genuine order event and carries no promotion, it qualifies as a utility template — the transactional category — and lands in a chat customers actually check rather than an ignored SMS inbox. In practice logistics teams wire this to a courier webhook or manifest event so it triggers automatically per shipment, at scale, with zero manual sending.
- Trigger on the first-mile / dispatch scan when the AWB is live
- Keep one shipping update per parcel to avoid notification fatigue
- Follow up with an 'out for delivery' utility template on the last mile
- Route the 'Need help?' button to a live agent or your support flow
Personalise every variable so it reads 1:1, not as a blast
The template ships with four variables and each one should be populated from your order system, never left generic. {{1}} is the customer's first name as they entered it at checkout — 'Good news Rahul' outperforms a cold 'Dear Customer'. {{2}} is the human-readable order ID the customer already recognises from their confirmation, not an internal SKU or database key. {{3}} is the actual carrier handling the shipment (Delhivery, Blue Dart, Ekart, India Post) so the tracking experience matches reality. {{4}} is a concrete, plain-language ETA — 'Wed, 10 Jul by 8 PM' rather than a raw '2026-07-10T20:00'. The 'Track shipment' button should carry a dynamic URL with the live AWB so the customer reaches their own parcel, not a generic homepage.
- Use the first name only in {{1}} for a natural, conversational tone
- Match {{2}} to the order ID shown on the order-confirmation message
- Populate {{3}} from the assigned carrier, not a default value
- Format {{4}} as a readable date and window, localised to IST
Getting it approved by Meta the first time
This template is designed to sail through review, but a few things protect that. Submit it as Utility — it is transactional and tied to a shipment event — and keep the body strictly informational. The moment you add a discount code, an upsell or a 'shop again' line, it becomes marketing, needs an opt-out, and risks rejection under the wrong category. Provide realistic sample values for all four variables when you submit, because reviewers reject templates whose placeholders look like spam or make no sense. Keep the button labels functional ('Track shipment', 'Need help?') rather than promotional. InfiQ's template management handles the submission, tracks the approval status, and flags anything Meta is likely to bounce before you send.
- Category: Utility — never tag a shipping update as Marketing
- No offers, coupons or cross-sells in the body
- Attach sensible sample values for {{1}}–{{4}} at submission
- Let template management pre-check formatting before it goes to Meta
What it costs to send
Since Meta moved off per-conversation billing on 1 July 2025, WhatsApp charges per delivered message by category. This template is billed at the utility rate — the cheaper transactional tier — for each message that reaches a customer. If a customer replies and you respond within the 24-hour service window, that window is free to use for support; it is not itself a billing unit. Your all-in cost is the live Meta utility rate plus InfiQ's transparent ₹ platform pricing on that rate card (ex-GST), so you always know the per-message number before you scale. Because a single proactive shipping update deflects a support contact that would otherwise cost far more in agent time, the payback on utility sends is usually immediate for high-volume logistics operations.
- Billed per delivered message at the utility rate
- The 24-hour service window is free to use, not a billing unit
- Transparent ₹ pricing, ex-GST
- Deflected 'where is my order' tickets typically cover the send cost
Variations you can copy and adapt
Start from the core template and branch by use case. A shorter version trims to just the name and order ID for teams that want the leanest possible ping. An 'out for delivery' variant reuses the same utility structure but swaps the ETA for a same-day delivery window and an agent's name — ideal for the last mile. A delay or exception variant, still utility, proactively flags a slippage with a revised ETA before the customer chases you. And a regional-language version in Hindi, Tamil, Bengali or your customers' preferred language dramatically lifts read and comprehension rates across India — each localised template is submitted and approved separately.
- Shorter: name + order ID + tracking button for minimal sends
- Out for delivery: last-mile window and delivery agent details
- Delay notice: proactive revised ETA to pre-empt support tickets
- Regional language: Hindi, Tamil, Bengali and more, approved per locale
Like this template? Send it live in 24 hours.