Event Reminders WhatsApp Template for Hospitality

Why Utility is the right category (and cheaper)

Meta classifies templates by intent, and that classification now drives what you pay. Since 1 July 2025, WhatsApp bills per delivered message by category — marketing, utility or authentication — rather than by conversation. An event reminder for a booking the guest already made is a textbook Utility message: it is transactional, tied to a specific action, and contains no promotional content. That keeps it in the lower-cost Utility band and, just as importantly, keeps approval fast. The moment you add a discount code, a 'book your next stay' plug or any upsell, the template flips to Marketing — a higher rate and a mandatory opt-out line. Keep this one strictly informational and you get the best of both: reliable delivery and the cheapest applicable rate, with InfiQ's transparent ₹ pricing on top (ex-GST).

Personalise it so it reads like a 1:1 message

Generic reminders get skimmed; specific ones get acted on. The four variables in this template exist so the message reads as if a host wrote it personally. Use the guest's first name in {{1}}, the actual event name in {{2}} ('the Sunday Jazz Brunch', not 'your event'), a human-readable date in {{3}}, and a combined venue-and-time value in {{4}} so the guest sees exactly where and when in one glance. Attach the ticket or pass as a media header so it travels with the message. The buttons carry the next action: 'View ticket' opens the pass, 'Add to calendar' captures the slot, and 'Get directions' removes the most common day-of friction for a venue guest. Each button is a single tap — no typing, no menu-hunting.

• {{1}} guest first name — pull from the booking record, never leave blank
• {{2}} the specific event name, exactly as marketed
• {{3}} a friendly date format like 'Sat, 12 Jul' rather than a raw timestamp
• {{4}} venue plus start time together, e.g. 'The Terrace, 12:30 PM'

Getting it approved on the first try

Most reminder templates that get rejected fail on avoidable details. Submit this under the Utility category and provide realistic sample values for every variable — Meta's reviewers check that {{1}} looks like a name and {{3}} looks like a date, not a coupon code or a URL stuffed into a placeholder. Keep the language strictly informational: no emojis-as-marketing, no 'limited seats left', no discount mention. Avoid putting a variable at the very start or very end of the body, and don't chain two variables with no words between them. If you want a promotional variant later, create it as a separate Marketing template with an opt-out line rather than bending this one. In InfiQ's template manager you draft, preview and submit in one place, and approvals typically land within a day.

Variations you can copy

One template rarely fits every event type, so keep a small library. A shorter build strips the reminder to a single variable for high-frequency, low-detail events. A multilingual build serves the reality of Indian hospitality guests — the same reminder in Hindi, Tamil or Marathi lands far better than English for a lot of audiences, and each language version is submitted as its own approved template. A promotional build (a genuinely separate Marketing template) can tempt lapsed guests back with a time-bound reason to return, and by law must carry an opt-out line such as 'Reply STOP to opt out'.

• Shorter: 'Hi {{1}}, reminder — {{2}} is today at {{3}}. See you soon!'
• Regional language: the same Utility body approved in Hindi or your guests' language
• Marketing variant (separate template): adds an incentive and a required opt-out line