Delivery Tracking WhatsApp Template for Hospitality

How to personalise it so it reads 1:1

The template uses four variables, and each one carries weight. {{1}} is the guest's first name — always populate it, because a named message reads as a concierge note rather than a system alert. {{2}} is the order or ticket ID that matches whatever the guest can see on your app, folio, or receipt, so support can trace it in one lookup. {{3}} is a concrete arrival time ("8:45 PM", not "soon") — a specific ETA is the single biggest driver of trust and the fastest way to cut "where is my order?" calls to the front desk. {{4}} names the person or partner delivering, which reassures the guest about who will knock. Keep the phrasing warm but factual; the personalisation should come from real data, never from padding the copy with adjectives.

• {{1}} name — e.g. Ananya
• {{2}} order or ticket ID — e.g. RS-4821
• {{3}} exact ETA — e.g. 8:45 PM
• {{4}} delivering agent or partner — e.g. Rahul

Getting it approved as Utility (and staying there)

Submit this template under the Utility category, because it is triggered by a specific transaction and is strictly informational. The most common reason a delivery-tracking template gets bounced or reclassified is a stray promotional line — a discount, an upsell, a 'book your next stay' nudge. Any of those pushes it into marketing, changes the billing tier, and can trigger rejection. Provide realistic sample values for every variable when you submit (Meta reviews the filled-in example, not the raw placeholders), make sure your 'Track live' button points to a genuine, working tracking URL, and keep the body free of ALL-CAPS shouting or emoji clutter. Get these right and utility templates typically clear review within a day.

• Choose the Utility category — it is transactional, not promotional
• Add sample values for {{1}}–{{4}} so reviewers see a real example
• Keep it purely informational — no offers, upsells or CTAs to book
• Point the Track live button at a real, live tracking page

What it costs to send

Since 1 July 2025, WhatsApp bills per delivered message by category, and utility is one of the lowest-priced tiers — which is exactly why keeping this template out of the marketing category matters to your budget. Each send is priced at Meta's utility rate on InfiQ's transparent ₹ pricing (ex-GST). The 24-hour window a guest opens by messaging you is a free service window for your replies, not a billing unit, so a back-and-forth that starts with the guest tapping 'Reschedule' can often be handled at no extra send cost. Because delivery updates are read almost immediately and deflect a real volume of front-desk and call-centre queries, the utility spend usually pays for itself in reduced support load alone. Slide your monthly hospitality volume into the cost calculator on this page to see the ₹ figure and typical payback for your property.

• Billed per delivered message at Meta's utility rate
• InfiQ's transparent ₹ pricing, ex-GST
• Guest-opened 24-hour service window can carry free replies
• Payback comes largely from fewer 'where is my order?' calls

Variations you can copy

Keep the core template as your default, then branch when the context calls for it. A shorter version — name, order ID and ETA only — works well for high-frequency, low-value dispatches like a minibar restock where speed beats detail. A regional-language version in Hindi, Tamil, or whatever your guests speak lifts open and reply rates across most Indian properties; build it as a separate approved template with the same structure. And if you genuinely want to attach an offer (say, a discount on the next room-service order), build that as a distinct marketing template with an opt-out line — do not smuggle it into this utility one, or you will lose both the approval and the cheaper rate.