OTP Authentication WhatsApp Template for Logistics

How to personalise the variables

This template is deliberately lean — authentication templates cannot carry marketing language, extra links or promotional copy, so keep the customisation to the two variables. {{1}} carries the one-time code your system generates; pass a fresh 4-to-8 digit value on every send and never reuse it. {{2}} is your brand or product name so the recipient instantly recognises which login the code belongs to — use something clear like 'InfiQ Logistics' or your app's public name rather than a legal entity nobody recognises. The 10-minute validity line and the 'do not share this code' warning are part of the standard authentication format and help both trust and approval, so leave them in. If you want a shorter version, you can drop {{2}} and submit a one-variable variant, but keeping the brand name almost always improves open confidence and reduces support calls.

• {{1}} = the code — always fresh, never logged in plain text where it can leak
• {{2}} = a recognisable brand or app name, not a legal entity
• Keep the validity window and 'do not share' warning intact
• Match the code length to what your app actually validates

Getting it approved the first time

Submit this exactly as the Authentication category — not utility, not marketing. Meta reviews authentication templates against a tight format: a verification code, an expiry, a security warning, and an optional copy-code or one-tap autofill button. Attach a Copy code button (a URL, add-to-cart, or promotional button will get it rejected in this category), and do not add emojis, marketing phrases, tracking links or any second call to action. Name the template something descriptive like logistics_login_otp so it is easy to manage later. If you serve customers in Hindi, Tamil, Bengali or another language, submit a separate language version of the same template rather than mixing scripts in one body. Through InfiQ's template management, you draft, preview and submit from one place, and most authentication templates clear review within a day.

• Category must be Authentication — never marketing or utility
• Only a Copy code / autofill button is allowed here
• No emojis, promo copy, or extra links in the body
• Submit each language as its own approved version

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 one of the lowest-priced categories on the rate card — which is exactly why moving login OTPs off SMS and onto WhatsApp usually pays for itself quickly. With InfiQ you get transparent ₹ pricing (ex-GST), so you can see the authentication rate per delivered message and model your monthly volume before you commit. The free 24-hour service window does not change your OTP economics — each authentication message is billed on delivery regardless of any open window — so your cost scales simply and predictably with the number of codes you actually send.

• Billed per delivered authentication message, by category
• Authentication is among the lowest categories on the rate card
• Transparent ₹ pricing, ex-GST
• No per-conversation charge — the 24h window is a free service window

Variations you can copy

The base template covers most logistics logins, but you may want a few approved variants ready. A shorter one-variable version trims the brand name for high-volume driver app sign-ins where speed matters most. A regional-language version — for example a Hindi or Tamil copy of the same body — lifts trust and reduces failed logins among customers who prefer their own language. And if your security policy needs a different expiry, you can adjust the validity line (say to 5 minutes for sensitive dashboards) and resubmit. Whatever you change, keep it inside the authentication category rules: no marketing content, no extra buttons, and a resubmission for re-approval whenever you edit the wording.