OTP Authentication WhatsApp Template for Food Delivery

How the copy-code button and variables work

WhatsApp authentication templates use a fixed, security-first structure: a short body that states the code and its validity, an explicit 'do not share' warning, and a one-time-password button. Our template exposes two variables — {{1}} for the numeric code your system generates, and {{2}} for your brand name — so the same approved template serves every verification event without a fresh submission each time. The [Copy code] button is a special one-time-password button type: tapping it copies the code straight to the clipboard so the customer can paste it back into your app in a single motion, which measurably lifts completion rates over asking someone to memorise six digits. Keep the code numeric, keep validity realistic (10 minutes is the sweet spot for food delivery), and never add order details, offers or links — Authentication templates reject any marketing content.

• {{1}} — the one-time code generated by your auth system (e.g. 492071)
• {{2}} — your brand name, used twice for consistency (e.g. HungryBox)
• Button: a one-time-password 'Copy code' button, not a URL or quick-reply
• No emojis, links, media or promotional language are permitted

Getting approved fast (and staying approved)

Submit the template under the Authentication category — do not mislabel it as Utility to save on rate, because Meta's classifier reads the copy-code button and OTP wording and will re-categorise or reject it. Authentication templates are among the fastest to clear review, often within a day, because their format is standardised. To avoid the common rejection reasons, keep the body to the code, its expiry and the security warning; use the built-in copy-code (or zero-tap/one-tap) button rather than a custom URL; and make sure the brand you name in {{2}} matches your verified WhatsApp Business display name. If you operate in multiple languages, submit a separate approved version per locale rather than translating on the fly. Once live, monitor delivery quality in InfiQ — repeated failed deliveries to invalid numbers can dent your sender quality rating, so validate numbers before you fire an OTP.

• Choose Authentication, not Utility or Marketing
• Use the native copy-code / one-tap OTP button
• Match {{2}} to your verified display name
• Submit a distinct template per language (Hindi, Tamil, etc.)

What it costs to send

Since Meta moved off per-conversation billing on 1 July 2025, WhatsApp charges per delivered message and prices it by template category. This OTP template is billed at the Authentication rate every time it is delivered, which is Meta's lowest business-initiated tier in India — well suited to high-volume login and verification traffic. Through InfiQ you pay Meta's live authentication rate plus InfiQ's own transparent ₹ platform pricing, quoted ex-GST, with no surprise per-conversation charges. Because verification is a cost of doing business rather than a revenue lever, the practical goal is to keep OTP volume clean: send only on real verification events, deduplicate rapid retries, and fall back sensibly so you are not paying to deliver codes no one asked for. Use the cost calculator to model your monthly food delivery login volume against the current authentication rate.