OTP Authentication WhatsApp Template for Fitness

How to personalise the two variables

This template is deliberately lean: {{1}} carries the one-time code and {{2}} carries your brand name, so the member instantly sees whose login they are approving. Authentication templates do not allow free-form personalisation like the member's first name, promotional lines, or emojis inside the body — that is a category rule, not an InfiQ limit, and breaking it is the fastest way to get a rejection. Keep {{2}} consistent with the exact business name shown on your WhatsApp Business profile so the message reads as trustworthy and the copy-code button lands the digits straight onto the member's clipboard.

• {{1}} = the generated OTP, e.g. 482913 — pass it exactly as your auth system mints it
• {{2}} = your brand name, e.g. FlexFit Studio — keep it identical across all your OTP templates
• Do not add names, offers, class times or emojis to the body; move any of that to a separate utility or marketing template

Getting it approved on the first submission

Submit this in the Authentication category, not Utility and never Marketing. Meta's newer authentication flow expects the standard OTP structure — a fixed security message plus a Copy code button (or a one-tap autofill button if your app is set up for it) — and it reviews these fast because the format is predictable. The most common rejection reasons are pasting an OTP template into the wrong category, adding marketing or brand-building copy to the body, or leaving the security warning ('Do not share this code') out. Keep the wording within the authentication rules and, if you tweak the validity window or add an expiry warning, re-submit and let it re-approve before you rely on it in production.

• Category: Authentication — confirm it before you hit submit
• Include the copy-code button; add the autofill button only if your Android app declares the matching package name and signing hash
• Keep the 'do not share' security line — it is expected in this category
• Re-submit after any wording change; approval is usually quick but is required each time

What it costs to send

Since Meta moved off per-conversation billing on 1 July 2025, WhatsApp charges per delivered message by category — and authentication is billed at the authentication rate, separate from utility and marketing. That means every OTP you deliver is priced individually, so a gym running thousands of monthly logins can forecast spend precisely against volume rather than guessing at conversation bundles. The free 24-hour service window still applies to your ongoing member replies, but it is not a billing unit for these codes. InfiQ shows you transparent ₹ pricing (ex-GST), so you can slide your monthly login volume and see the real per-message authentication cost before you commit.