Delivery Tracking WhatsApp Template for Events

How to personalise it well

The four variables do the heavy lifting, so populate them from your order system rather than hard-coding anything. Use the customer's first name in {{1}} so it reads as a one-to-one note; pass your real order reference in {{2}} so support can look it up instantly if they reply; give a concrete ETA in {{3}} (a time window like '4:00–6:00 PM today' beats a vague 'soon'); and name the courier and partner in {{4}} so the recipient trusts the call when it comes. Keep the tone plain and factual — the strength of a Utility template is that it looks like an operational update, not a campaign. Resist the urge to add 'and don't miss our next event!' inside this body; cross-sell belongs in a separate Marketing template.

• {{1}} name — first name only, from your CRM field
• {{2}} order id — the exact reference the customer already knows
• {{3}} time — a real ETA window, localised to the customer's timezone
• {{4}} agent — courier name plus logistics partner for trust

Getting it approved by Meta

Submit this as a Utility template. Meta reviews the wording and the sample values you provide, so fill every variable with realistic examples (a plausible name, a real-looking order id, a proper time, an actual courier) — templates with empty or placeholder samples are a common cause of rejection. Keep the body strictly informational: any promotional phrase, discount, or invitation to a future event will get it re-classified as Marketing and likely bounced. Name your template clearly, for example events_delivery_tracking_v1, so you can version it. Approval typically lands within a day; once approved you can send immediately through InfiQ, and any later wording edit simply re-enters review as a new version.

• Choose category Utility, language your customers read
• Provide filled, realistic sample values for all four variables
• Strip out any promotion, coupon, or event invite
• Match every {{n}} in the body to a defined variable — no gaps or duplicates

What it costs to send

WhatsApp bills per delivered message by category. Since 1 July 2025 Meta charges on the message's category — marketing, utility, or authentication — rather than per 24-hour conversation; the 24-hour service window remains, but as a free window for replying to customer-initiated chats, not as a billing unit. Because this template is Utility, each delivered send is charged at Meta's Utility rate, which is meaningfully lower than the Marketing rate. Through InfiQ you pay transparent ₹ pricing (ex-GST), so your per-message cost tracks the published Utility rate for India. Proactive delivery tracking usually pays for itself by deflecting inbound 'where is my parcel?' queries that would otherwise tie up a support agent per contact.

• Billed per delivered message, at the Utility category rate
• Utility is cheaper than Marketing for the same volume
• Transparent ₹ pricing, ex-GST
• Savings come from fewer support contacts and fewer failed deliveries

Variations you can copy

Keep the approved original as your default and branch from it deliberately. A shorter build trims to the name, order id, and ETA for markets where brevity performs better and drops the second and third buttons. A regional-language build re-creates the exact same structure in Hindi, Tamil, Marathi, or whichever language your attendees read — each language is a separate template submission with its own approval. If you genuinely want to promote your next event on the back of a delivery, do it as a distinct Marketing template sent separately, and remember Marketing templates must carry an opt-out line — never bolt a promotion onto this Utility body.