OTP Authentication WhatsApp Template for Healthcare

Why WhatsApp beats SMS for healthcare OTPs

Delivering the verification code on WhatsApp typically earns far higher open and read rates than SMS, and the native copy-code button removes the manual re-typing that causes patients to abandon a login. There is no DLT template registration or operator-route unpredictability to manage as with Indian SMS, and the message carries your verified business name and green-tick presence, which reduces the phishing anxiety patients feel around health data. For older or less tech-confident patients — common in diagnostics and hospital settings — a single tap to autofill the code is a meaningfully gentler experience than reading a six-digit string off a crowded SMS inbox.

Personalising it correctly

Authentication templates are deliberately rigid, so personalisation lives in the two variables and in how naturally the brand name reads. Put the numeric code in {{1}} and your business name in {{2}}, and reuse {{2}} in the security warning so the message feels like it is genuinely from your clinic. Do not add the patient's name, appointment details, product references or any marketing hook — Meta rejects authentication templates that stray into personal or promotional content. If you serve multiple regions, create a parallel Hindi or regional-language version rather than mixing languages in one template.

• {{1}} — the one-time code, e.g. 482913
• {{2}} — your registered brand or clinic name, e.g. CityCare Diagnostics
• Keep validity realistic (10 minutes is standard) so patients are not rushed
• Avoid emojis, links and promotional lines — they trigger rejection

Getting it approved the first time

Submit the template under the Authentication category and use the standard OTP structure with a copy-code button — Meta reviews authentication templates against a tight pattern, and matching it is the fastest path to approval, often within a day. Keep the body focused on the code, its validity and a security caution; remove any URL, offer or patient-specific data. Once approved, the same template ID can be sent instantly and at scale through InfiQ. If you edit the wording later, the template must be re-submitted and re-approved before those changes go live, so lock the copy before you scale.

What it costs to send

Since Meta moved off per-conversation billing on 1 July 2025, WhatsApp charges per delivered message by category, and OTPs fall under the authentication rate. Every delivered code is billed at Meta's live authentication rate for India, and InfiQ applies its own transparent ₹ pricing on top of Meta's live rate card, quoted ex-GST. The 24-hour service window is a free re-engagement window for replies, not a billing unit — so a burst of resend attempts within a session are still each billed as delivered authentication messages. Use the cost calculator to slide your monthly login and verification volume and see the ₹ estimate for your healthcare workflow.