Delivery Tracking WhatsApp Template for Logistics
Every "Where is my order?" call is a shipment your team is paying twice for — once to deliver, once to explain. This ready-to-use, Meta-compliant WhatsApp delivery tracking template turns that reactive support load into a proactive, one-tap update. It ships in the Utility category, carries clean variables for name, order ID, ETA and rider, and pairs with a live-tracking button so the customer never has to ask. Copy the body below, drop in your logistics fields, get it approved (usually within a day), and start sending the same hour through InfiQ.
Variables
{{1}}= Rahul{{2}}= SHIP-48213{{3}}= 6:30 PM{{4}}= Anil (DA-092)
Verified business
10:24
Preview · as customers see it
When to send this template
Delivery tracking is a status message, not a promotion — which is exactly why it qualifies as Utility and gets read within minutes of landing. Fire it at the single highest-anxiety moment in the journey: when the shipment leaves the last-mile hub and goes 'out for delivery'. That is when the customer starts wondering, and that is when a proactive WhatsApp beats an app push or an SMS that gets buried. If you run a multi-touch flow, keep this template for the out-for-delivery ping and use sibling templates for order confirmation and dispatch, so each message maps to a real, distinct event. Because a status update is tied to a genuine transaction the recipient is expecting, it fits neatly inside WhatsApp's rules for utility messaging and rarely triggers quality complaints.
- Out-for-delivery: the primary trigger for this exact template
- ETA change or delay: re-send with an updated {{3}} time
- Failed attempt: pair the Reschedule button with a fresh attempt window
- Avoid sending it as a daily 'still on the way' blast — one status change, one message
Personalise it so it reads 1:1, not like a blast
The four variables are what turn a generic notice into a message that feels hand-typed. {{1}} is the customer's first name, {{2}} the order or AWB number they can actually recognise, {{3}} a real ETA window rather than a vague 'today', and {{4}} the delivery associate's name and ID so the arrival isn't a surprise knock. Pull these straight from your OMS or courier webhook at the out-for-delivery event so the values are always current — a stale ETA does more damage than no message at all. Keep the rider detail human ('Anil (DA-092)') because a named person on the doorstep converts a nervous customer into a confident one, and it visibly cuts down on 'is this a real delivery?' refusals in tier-2 and tier-3 markets.
- {{1}} name — first name only reads warmer than full name
- {{2}} order/AWB ID — use the reference the customer already has
- {{3}} ETA window — a real time beats 'today'; update it if the route slips
- {{4}} rider name + ID — reduces failed deliveries and refusals
Getting it approved as Utility (and keeping it there)
Submit this template under the Utility category, because it is transactional and tied to a shipment the recipient is expecting. The single biggest approval risk is category drift: the moment you add a coupon, an upsell, a 'shop again' line or any promotional hook, Meta reclassifies it as Marketing and either rejects it or bills it at the higher Marketing rate. Keep the body strictly informational, provide accurate sample values for every variable (Meta reviewers test with them), and make the buttons functional rather than promotional — a live-track deep link, a reschedule flow, a support call. Give each variable a realistic example on submission and name the template clearly (for instance delivery_tracking_out_for_delivery) so your team picks the right one at send time.
- Category: Utility — never bundle offers into it
- Supply real sample values; reviewers validate against them
- Use action buttons (track, reschedule, call), not marketing CTAs
- Name the template by event so operators don't misfire it
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 Utility, so it bills at India's Utility rate — meaningfully lower than Marketing — and the free 24-hour service window means any customer reply, or your follow-up inside that window, carries no extra category charge. Through InfiQ you pay transparent ₹ pricing (ex-GST): you see the Utility line item, your platform fee, and the blended per-message cost before you scale up. For most logistics operators the payback is simple — one avoided 'where is my order' support contact per few tracking messages sent tends to cover the send cost several times over. Use the calculator to slide your monthly out-for-delivery volume and see the ₹ figure for your own operation.
- Billed per delivered message at the Utility rate (not per conversation)
- Replies inside the free 24-hour service window add no category fee
- Transparent ₹ pricing, ex-GST
- Deflected support contacts typically outweigh the send cost
Variations you can copy
The base template covers the out-for-delivery moment, but three quick variants let you cover the rest of the last mile without re-inventing the wording each time. A trimmed one-variable version is ideal for high-volume, low-margin shipments where every character of send cost matters. A delay variant swaps the ETA and adds an apology-plus-reschedule tone while staying inside Utility. And a regional-language version — Hindi, Tamil, Marathi or whatever your customers actually read — lifts read-through in non-metro pincodes far more than an English default ever will. Note that a promotional 'order again' spin is a Marketing template, must live under that category, and must carry an opt-out line; keep it entirely separate from this Utility tracking flow.
- Short: name + ETA only, for high-volume economy shipments
- Delay: updated {{3}} plus a reschedule button, still Utility
- Regional language: localise the body for the destination pincode
- Promotional 're-order' spins belong in a Marketing template, not here
Like this template? Send it live in 24 hours.