OTP Authentication WhatsApp Template for Insurance
Insurance journeys are full of moments that need a verified identity: a first policy login, a claim intimation, a nominee change, an e-KYC step, or a premium payment on a new device. Sending the one-time passcode over WhatsApp instead of SMS gets it read faster, cuts drop-off at exactly the moment a customer is trying to act, and uses Meta's low-cost authentication category with a tamper-resistant copy-code button. This page gives you a ready, Meta-compliant OTP template built for Indian insurers — with the right category, the right variables, sample values, and the approval notes that keep it from getting rejected. Copy it, drop in your brand and code, and you can be sending from your own verified WhatsApp number within a day of approval.
Variables
{{1}}= 482915{{2}}= InfiQ Insurance
Verified business
10:24
Preview · as customers see it
When to use this template in an insurance journey
Reach for an authentication template only when the customer is completing a genuine, sensitive action — never as a broadcast. In insurance, the highest-value trigger points are: signing in to the policyholder portal or app on a new device, starting a claim or checking claim status, changing a registered mobile number or nominee, e-KYC and re-KYC verification, and authorising a premium payment or auto-debit mandate. Because the OTP is tied to a real request the customer just initiated, delivery is contextual and expected, which is exactly why WhatsApp read and completion rates beat SMS. Send the code the instant the action is requested, keep validity short (10 minutes is a sensible default for financial verification), and let the copy-code button do the work so the customer never fat-fingers a six-digit code.
- New-device login to the policyholder portal or mobile app
- Claim intimation, status checks, and settlement authorisation
- Nominee, address, or registered-mobile changes
- e-KYC / re-KYC identity verification
- Premium payment or e-NACH / auto-debit mandate confirmation
What the variables do and how to personalise safely
The authentication category is deliberately strict, so personalisation is limited to two variables — and that is by design. {{1}} carries the one-time code your system generates (for example 482915); {{2}} carries your brand name (for example InfiQ Insurance) and appears twice so the security warning reads naturally. You cannot add marketing lines, offers, emojis, or extra call-to-action buttons in this category, and you should not try to slip the customer's name or policy number into an authentication template — that content belongs in a utility template. Keep {{2}} consistent with your verified WhatsApp Business display name so customers recognise the sender at a glance. Generate the code server-side, expire it after the stated window, and never log or echo it back in a follow-up message.
- {{1}} — the OTP itself, generated server-side and single-use
- {{2}} — your brand / display name, used twice for the trust line
- No offers, emojis, links, or customer names in this category
- Match {{2}} to your verified WhatsApp display name
Getting it approved on the first try
Submit this as Authentication, not Utility or Marketing. Meta reviews authentication templates against a tight pattern: a code variable, a validity statement, a security warning not to share the code, and a copy-code (or one-tap autofill) button — no promotional wording whatsoever. Rejections almost always come from mixing categories: adding a discount, a 'Track your claim' link, or a marketing footer will get the template bounced or silently reclassified, which changes how it bills. Keep the body short, keep the warning line intact, and use the built-in copy-code button rather than a custom URL button. Approvals in this category are usually fast — often within a day — because the format is so well understood. If you localise, submit each language as its own template and keep the same structure.
- Choose the Authentication category explicitly
- Keep the validity line and 'do not share' warning
- Use the copy-code button, not a custom link
- Submit each language variant separately
- Never add marketing content — it triggers rejection or reclassification
What it costs to send
WhatsApp bills per delivered message by category, and authentication is the category built for exactly this use case. Since Meta retired per-conversation billing on 1 July 2025, you are charged for each authentication message that is delivered — there is no 24-hour 'conversation' bundle anymore; the 24-hour service window remains only as a free window for replying to inbound customer messages, not as a billing unit. With InfiQ you get transparent ₹ pricing layered on Meta's live authentication rate card (ex-GST), so you can forecast cost per verified login or claim step precisely. For high-volume insurers, the copy-code format also reduces failed verifications versus manual SMS entry, which quietly lowers the number of re-sends you pay for.
- Authentication rate, billed per delivered message
- Per-conversation billing ended 1 July 2025
- 24-hour window is a free service window, not a billing unit
- Transparent ₹ pricing, ex-GST
Variations you can copy
The template above is the safe default, but you can adapt the wording within authentication rules. A shorter form drops the extended warning for a leaner message where you already surface security guidance elsewhere. A tighter-validity form suits high-risk actions like nominee changes, where a 3–5 minute window reduces exposure. And a regional-language form lets you serve customers in Hindi, Tamil, Marathi, or any language your book skews toward — submitted as its own template with the same code, validity, and warning structure. Whatever you change, keep the one-time code, the expiry statement, the do-not-share warning, and the copy-code button; those four elements are what keep the template inside the authentication category.
- Shorter: core code line + validity, minimal warning
- Tighter validity: 3–5 minutes for sensitive changes
- Regional language: Hindi or your customers' language, same structure
Like this template? Send it live in 24 hours.