Delivery Tracking WhatsApp Template for Banking

Why utility is the right category here

A delivery tracking message is transactional and tied to an action the customer already initiated, which is precisely what Meta means by utility. That matters for two reasons. First, utility templates are read almost instantly because customers recognise them as genuinely useful, not marketing — open and read rates on dispatch alerts are consistently high. Second, since Meta moved to per-message billing by category on 1 July 2025, each delivered utility message is charged at the utility rate, which is materially lower than the marketing rate. Keeping this template clean and informational is therefore both a compliance decision and a cost decision. Note that messages you send inside an open 24-hour service window (for example, replying after the customer taps a button) are free — that free window is a service concept, not a billing unit.

Personalising it so it reads 1:1

The difference between a template that feels like a mass blast and one that feels like a personal update is in the variables. Use the customer's first name in {{1}}, name the exact item in {{2}} so there is no ambiguity between a card and a cheque book, and put your own tracking reference in {{3}} so support can look it up in one search. The ETA in {{4}} should be a real time window pulled from the courier's out-for-delivery scan, and {{5}} should name the actual courier partner so the customer trusts the follow-up call. The three buttons turn the message into a self-service moment: Track live opens the courier's live map, Reschedule lets the customer move an inconvenient slot, and Call courier removes a support ticket entirely. Every variable you fill accurately is one fewer 'where is my card' call to your branch.

• {{1}} — customer first name, from your CRM
• {{2}} — exact item so there's no ambiguity
• {{3}} — your internal tracking or AWB reference
• {{4}} — real ETA window from the dispatch scan
• {{5}} — the actual courier partner name

Getting it approved on the first attempt

Submit this template under the utility category with all sample variable values populated — Meta reviews the filled-out message, so realistic samples like a name, an item, and a time window speed approval and avoid a rejection for missing examples. Keep the body purely informational: no discount, no cross-sell, no 'upgrade your card' line, because any promotional element reclassifies it as marketing and invites a bounce. Match the variable order in your template to the order in your API call so the message never renders with a name where the ETA should be. Buttons should be quick-reply or URL actions that genuinely relate to the delivery. Done this way, banking delivery templates typically clear Meta review within a day, after which you can send instantly through InfiQ.

• File under Utility, not Marketing
• Populate every sample variable value
• Keep it informational — no offers or upsell
• Keep API variable order identical to the template
• Use buttons that relate directly to the delivery

What it costs to send

This template bills at Meta's utility per-message rate for every message delivered — there is no per-conversation charge, as Meta retired that model on 1 July 2025. On InfiQ you pay transparent ₹ pricing (ex-GST), so your finance team can forecast spend from delivered volume with no guesswork. Because utility rates are lower than marketing rates, keeping delivery alerts in this category directly controls cost at scale. Use the cost calculator to slide your monthly dispatch volume and see the ₹ figure and typical payback from the branch calls and re-delivery attempts this template removes.