OTP Authentication WhatsApp Template for Hospitality
Guest logins, booking-portal sign-ins and check-in verifications only work if the code actually arrives — and arrives fast. This is a ready-to-submit, Meta-compliant WhatsApp OTP authentication template built for Indian hotels, resorts, restaurants and travel brands. It uses the correct Authentication category, a secure copy-code button, and time-boxed wording so codes land on the phone your guest is already holding. Copy it below, drop in your two variables, and once Meta approves it you can fire it instantly through InfiQ.
Variables
{{1}}= 482913{{2}}= Lakeview Grand Hotel
Verified business
10:24
Preview · as customers see it
When to send this OTP template
Trigger this message the instant a guest requests verification — never on a schedule and never as a broadcast. In hospitality the moments that call for an OTP are specific: signing into your booking portal or loyalty app, confirming a phone number at online check-in, authorising a change to a reservation, resetting a members' password, or validating a device before releasing a digital room key. Because Authentication templates are tied to a genuine user-initiated action, the code should be generated and sent within seconds of the request, while the guest is still on the screen waiting for it. That immediacy is exactly why WhatsApp beats SMS here — delivery is near-instant, the message sits in a chat the guest already trusts, and the copy-code button removes the friction of retyping digits under a 10-minute clock.
- Portal or loyalty-app login and re-authentication
- Phone-number confirmation during online check-in
- Password or PIN reset for members and staff
- Authorising reservation changes or refunds
- Device verification before issuing a digital key
Personalisation and variables
Authentication is a deliberately tight category, so you get exactly two variables and no promotional freedom — and that is by design. {{1}} carries the one-time code itself and {{2}} carries your brand name, so the guest can see at a glance which property the code belongs to. That brand token matters more than it looks: guests who hold memberships across several hotels or restaurant groups will trust a code far more when it clearly reads as coming from your property. Keep the code numeric and short (4–6 digits is standard), keep the validity window realistic (10 minutes is a sensible default), and never try to smuggle in a greeting, an offer, or a room upsell — that content belongs in a separate Utility or Marketing template and will get an Authentication submission rejected.
- {{1}} — the one-time verification code (e.g. 482913)
- {{2}} — your property or brand name (e.g. Lakeview Grand Hotel)
- Do not add names, offers, or extra links inside an Authentication body
- Match the stated validity to your actual code expiry logic
Approval tips for the Authentication category
Submit this as Authentication, not Utility, and use WhatsApp's authentication template format with a copy-code button rather than a free-text body with a URL. Meta approves these quickly — often within a day — when the wording stays strictly transactional: a code, a validity window, and a do-not-share security line. The most common rejection reasons are trying to include marketing or brand-building language, adding buttons other than copy-code or a one-tap autofill button, or mismatching the language locale you selected. If you serve guests across regions, submit a separate approved version per language (Hindi, Tamil, Marathi and so on) rather than mixing scripts in one template. InfiQ's template management flow validates category and button rules before you submit, so you catch these issues before Meta does.
- Choose Authentication category and the copy-code button type
- Keep the body purely transactional — no offers or greetings
- Submit one template per language locale you support
- Let InfiQ pre-validate the format to avoid avoidable rejections
What it costs to send
Since Meta moved off per-conversation billing on 1 July 2025, WhatsApp charges per delivered message by category. This template bills at the Authentication rate every time a code is delivered — a genuinely low-cost category, which is one reason moving OTPs off SMS onto WhatsApp usually pays for itself quickly on high-volume login and check-in flows. There is no separate charge for the free 24-hour service window; that window only affects whether follow-up service replies are free, not how this template is priced. Through InfiQ you get transparent ₹ pricing (ex-GST), so you can forecast a month of guest verifications against your real login and check-in volume before you commit.
- Billed per delivered message at the Authentication category rate
- Authentication is among the lowest-cost WhatsApp categories
- The free 24-hour service window is not a billing unit
- Transparent ₹ pricing, ex-GST
Like this template? Send it live in 24 hours.
Frequently asked questions
Which category is this template?+
Do OTP templates need opt-in?+
Can I edit the wording?+
How fast can I send it after approval?+
Why WhatsApp instead of SMS for OTPs?+
Can I send OTPs in Hindi or regional languages?+
How is this billed?+
Do I keep control of my WhatsApp account and BSUID?+
Send your first OTP in 24 hours
Submit this Authentication template through InfiQ today and start delivering secure, near-instant verification codes to your guests on WhatsApp — with transparent ₹ pricing and full ownership of your account.