WhatsApp Templates for Hotels: Approved Examples for 2026

WhatsApp templates exist because Meta does not let businesses message guests freely. Outside a 24-hour window after the guest's last inbound message, every outbound message has to be a pre-approved template. That one rule shapes how hotels can use the channel, what each message costs, and how often Meta will quietly throttle your number when something feels off.

Meta is the gatekeeper. WhatsApp is owned by Meta, and the WhatsApp Business Platform runs on their template approval system. Your Business Solution Provider (BSP) submits the template, Meta reviews it (usually inside a few minutes, sometimes a day), and once approved you can send it to opted-in guests. Get it wrong and the template sits in REJECTED with a reason like "Content violates policy" that tells you almost nothing.

The 24-hour rule is the one most ops teams miss on day one. If a guest messages you at 09:00, you can reply with anything, free-form text, images, voice notes, the lot, until 09:00 the next day. After that, only approved templates. And if you want to start a conversation cold, say a pre-arrival nudge two days before check-in, that opening message has to be a template too. No negotiation.

The three template categories

Meta classifies every template into one of three buckets. The category determines pricing (see the pillar on WhatsApp costs for hotels for the per-message numbers), what content is allowed, and how strict the review is.

Utility

Transactional messages tied to a specific action the guest has taken or expects. Booking confirmations, check-in details, folio summaries, late check-out approvals. The bar Meta applies: the message must relate to a real, named transaction. No upselling tucked at the bottom.

Marketing

Promotional content. Spa offers, restaurant week, returning-guest discounts, seasonal packages. Priced higher and reviewed more strictly. They also cap quickly if your quality rating drops.

Authentication

One-time passwords and verification codes. In hospitality this is rare, but it shows up with digital key issuance, smart-lock onboarding, or loyalty account verification. Meta enforces a fixed structure on these and rejects anything that drifts.

Utility templates that get approved

Below are five examples that hotels we work with have had approved without revisions. Variables are shown as {{1}}, {{2}} and so on. Keep them short, name a real transaction, and resist the urge to add a marketing line at the end.

1. Booking confirmation
Hi {{1}}, your reservation at {{2}} is confirmed. Check-in {{3}}, check-out {{4}}, room type {{5}}. Booking reference {{6}}. Reply to this message if you need anything before arrival.

2. Pre-arrival reminder
Hello {{1}}, we are looking forward to welcoming you at {{2}} on {{3}}. Check-in opens from 15:00. If you would like to share an estimated arrival time or request an early room, just reply here.

3. Check-in details
Welcome {{1}}. Your room at {{2}} is {{3}} on floor {{4}}. WiFi network {{5}}, password {{6}}. Breakfast runs 07:00-10:30 in the {{7}} restaurant. Reply if anything is unclear.

4. Late check-out confirmation
Hi {{1}}, late check-out at {{2}} is confirmed for {{3}}. Your new departure time is {{4}}. The additional charge of {{5}} has been added to your folio.

5. Folio notification
Hi {{1}}, your folio for stay {{2}} is ready. Total {{3}}, paid {{4}}, balance {{5}}. A PDF copy has been emailed to {{6}}. Reply here if you spot anything off.

Notice what these have in common. Each one names a transaction, uses variables for the dynamic bits only, and ends with a quiet invitation to reply rather than a call to book or buy. That last detail is what keeps the template inside the utility category at review time.

Marketing templates: when they work and when Meta rejects them

Marketing templates are where most hotels first run into trouble. The content is allowed, but the review is unforgiving and the failure modes are not always obvious. Two examples that tend to clear:

Returning-guest offer
Hi {{1}}, it has been a while since your last stay at {{2}}. We have kept 15% off direct bookings for returning guests through {{3}}. Use code {{4}} at {{5}} to book.

Seasonal package
Hello {{1}}, our winter package at {{2}} is open: two nights, dinner for two, and late check-out from {{3}} per room. Available {{4}} to {{5}}. Reply BOOK or visit {{6}}.

And here are the rejection patterns we see most often. Most properties hit at least one on their first marketing submission.

• Vague variables. Templates with {{1}} as the entire body get rejected because Meta cannot see what you are sending. Variables need surrounding context.
• Mixed category. A "booking confirmation" with a spa offer at the bottom reads as marketing dressed as utility. Meta will either re-categorise it (so you pay marketing rates) or reject it.
• Promotional language in a utility template. Words like "exclusive", "special offer", "don't miss" inside what claims to be a transactional message. Move them to a marketing template or cut them.
• No clear opt-in context. If the template implies a relationship the guest never agreed to ("Welcome back!" sent to someone who has never stayed), it gets flagged once volume picks up.
• URL shorteners. Bit.ly and similar are routinely rejected. Use your own domain.

Authentication templates

Authentication is the smallest category for hotels and the easiest to get right, mostly because Meta gives you a fixed structure and you fill in the blanks. Two scenarios where it shows up:

• Digital key OTP. Guest receives a one-time code to activate the mobile key in your app or via your lock provider's flow.
• Smart-lock pairing. Codes for in-room safes, secondary user access on suites, or after-hours self check-in handovers.

Authentication templates are priced lowest in most regions and clear approval quickly when you keep the body to a single sentence with the code variable and an expiry. Anything beyond that and Meta nudges it into utility.

What Meta rejects most often

Pulling the rejection threads together, here is the list we work through with new properties before they ever submit a template:

• Variables without surrounding text ({{1}} as a whole line).
• Marketing language inside utility templates.
• Mismatched category (asking for utility, content reads as marketing).
• URLs shortened through third-party services.
• Emoji-heavy bodies on utility templates (one or two are usually fine, ten reads as spam).
• Generic "Hi {{1}}, click here" templates with no transaction reference.
• Templates in a language different from the one declared at submission.
• Footers or buttons that reference WhatsApp itself ("Message us on WhatsApp"). Meta does not allow self-referential CTAs.

But the most common cause of rejection is simpler than any of these: a human reviewer cannot tell, from the template alone, what real-world event triggered the message. If your template does not make that obvious, rewrite it.

Variable substitution patterns

Variables are positional. {{1}} is the first placeholder, {{2}} the second, and so on. They cannot be reused inside the same template, and Meta now expects you to provide a sample value for each one at submission. A few patterns that hold up well in production:

• Name + property. Hi {{1}}, this is {{2}}... Two variables, immediately clear what each one does.
• Date pairs. Always send dates in a regional format the guest expects. A German guest seeing 03/05 will read it as 3 May; an American guest reads 3 May as well only if you write the month name.
• Currency. Include the currency code or symbol inside the variable: {{1}} = "EUR 240.00", not "240.00". Less ambiguity at quality-rating time.
• Booking references. Keep them in the body, not in a separate header variable. Header variables get truncated on some Android builds.

One thing that catches teams out: if your PMS feeds the template through your BSP, every variable needs a source field mapped. A missing source on {{4}} will silently send "{{4}}" to the guest. Ask me how I know. (For more on getting PMS data flowing cleanly, see integrations and APIs in the hotel tech stack.)

Quality rating impact and how to recover

Every WhatsApp Business number carries a quality rating: green, yellow, or red. It is calculated from how guests respond to your messages. Block, report, ignore, or reply, all weighted differently. Green means you can send up to your current tier limit. Yellow is a warning. Red means Meta is about to drop your tier, which can mean going from 100,000 conversations a day to 10,000 overnight.

The two quickest ways to tank a rating: send a marketing template to a guest who has not opted in, or send the same template too often. Daily promotional pings are a fast track to red.

If you do drop, the recovery playbook is unglamorous. Pause all marketing templates. Send only utility templates triggered by real guest actions for two to three weeks. Quality usually climbs back to green inside a month if your underlying behaviour was healthy. If it does not, the number itself may be flagged and you will need a conversation with your BSP. This is the failure mode that costs you a Saturday morning.

Practical setup checklist

If you are starting from scratch, the order matters more than people realise.

1. Pick a BSP. Twilio, 360dialog, MessageBird, Infobip, and a long tail of smaller players. Pricing varies meaningfully. There is a detailed breakdown in our post on Twilio and WhatsApp Business costs for hotels in 2026.
2. Verify the business. Meta Business Verification takes anywhere from 24 hours to two weeks. Start it before you need it.
3. Submit your first templates. Booking confirmation, pre-arrival, and check-in details. Approval usually arrives in minutes; allow up to 24 hours.
4. Map PMS variables. Every template variable needs a source field in the PMS or CRM. Test with real bookings before going live.
5. Set governance. Decide who can submit a new template. We have seen properties end up with 40 near-duplicate templates because three departments were each adding their own.
6. Track quality weekly. Most BSPs surface the quality rating in their dashboard. Put it on someone's calendar.

Bringing it together

Templates are not the exciting part of WhatsApp for hotels. They are the part that decides whether the channel works at all. Properties that take template hygiene seriously (clear categories, named transactions, modest variable counts, no marketing in utility) end up sending more messages, paying less per conversation, and rarely getting rate-limited.

The rest is workflow. Knowing which template to fire when, keeping copy fresh without re-submitting every fortnight, and making sure the right PMS event triggers the right message. That is the layer Viqal's AI Operator handles for hotels: template selection, variable filling, opt-in tracking, and quality monitoring across your portfolio. If you want the full cost picture before deciding how aggressive to get on the channel, the WhatsApp costs for hotels pillar covers per-message pricing, tier limits, and BSP markups in detail.