How do I get a WhatsApp template approved fast?
Most WhatsApp templates that get stuck in review or rejected fail for boring, fixable reasons: the wrong category, a variable with no sample, a button that points nowhere, or promotional wording sneaked into a utility message. Meta's review is largely automated, so a clean, correctly categorised, policy-safe template can clear in minutes rather than the stated 24-hour window. This guide walks through exactly how to structure and validate a template so it sails through the first time — and why getting the category right also protects what you pay per delivered message.
Quick answer
Choose the correct category (marketing vs utility vs authentication), write one clear purpose with a single CTA, give every variable a realistic sample, strip out policy triggers, and run a validator before you submit. Correct categorisation is the single biggest factor in both speed of approval and your per-message cost.Get the category right first — it decides everything
Category is the number-one reason templates are rejected or silently re-categorised by Meta, and it is also what determines your cost, because WhatsApp bills per delivered message by category (marketing, utility, authentication) since Meta moved off per-conversation billing on 1 July 2025. A utility template must be tied to a specific transaction or account event the customer already expects — an order confirmation, a shipping update, a payment receipt, an appointment reminder. Authentication is strictly for one-time passcodes and login verification. Marketing covers everything promotional: offers, launches, re-engagement, catalogue pushes. If you dress up a promotion as a utility message to save money, Meta's classifier will catch it, re-categorise it, and slow your review — so pick honestly.
- Utility: transaction or account updates the customer is already expecting (order, delivery, payment, booking)
- Authentication: OTPs and login codes only — no marketing content, no extra links
- Marketing: offers, promotions, announcements, win-back, cart reminders
- When in doubt, Meta treats mixed intent as marketing — don't fight it
Structure the template so a reviewer (and a bot) can't misread it
A template that reads cleanly to an automated reviewer clears faster. Keep one message to one purpose with a single, obvious call to action — two competing CTAs or a wall of links reads as spammy. Every variable placeholder such as {{1}} or {{2}} must be supplied with a realistic sample value at submission; a variable left blank, or padded with a URL or emoji, is an instant rejection. Match the header, body and footer to real content: don't stuff the header with promotional copy in a utility template, and don't leave dangling formatting. Buttons should do what they say — a 'Track order' button must go to a working tracking link, and a phone-number button must be a real number.
- One template, one purpose, one primary CTA
- Give every {{n}} variable a concrete, representative sample (a name, an order ID, a date)
- Never put URLs, phone numbers, or emojis inside a variable placeholder
- Keep buttons functional and honest — the label must match the destination
Avoid the policy triggers that cause silent rejections
Many rejections have nothing to do with formatting and everything to do with content. Avoid absolute claims, misleading urgency, and anything that reads as unsolicited. Don't reference restricted or prohibited categories, and don't imply an official relationship with Meta or WhatsApp that you don't have. Grammatical sloppiness, ALL-CAPS shouting, and excessive punctuation all raise the automated risk score. Crucially, sending templates only to opted-in, relevant recipients keeps your quality rating high — and a healthy quality rating is what unlocks higher messaging tiers and keeps future templates approving quickly. A single template is reviewed in isolation, but your sender reputation follows every template you submit.
- No misleading urgency, guaranteed-outcome claims, or bait-and-switch offers
- No implied endorsement by Meta or WhatsApp
- Clean grammar, normal casing, minimal punctuation — sloppiness reads as spam
- Only message opted-in, relevant users to protect your quality rating
Validate before you submit — don't learn from a rejection
A rejected template costs you a review cycle and can nudge your quality signals down, so catch problems before Meta does. Run every template through a validator that checks category fit, variable/sample completeness, button configuration, character limits, and common policy flags. Preview the message with the sample values filled in so you can see exactly what the customer receives. If a template does get rejected, read the specific reason Meta returns rather than guessing — usually it points to category or a variable issue you can fix in one edit and resubmit. With InfiQ you build and validate templates inside one dashboard as an official Meta Business Partner, with transparent ₹ pricing (ex-GST) and full ownership of your account and BSUID, so you're set up correctly and pricing is predictable from day one.
- Validate category, variables/samples, buttons, and limits before hitting submit
- Preview with real sample values to see the delivered message
- Read Meta's exact rejection reason and fix that one thing, then resubmit
- Reuse approved templates as patterns for new ones to stay consistent
Frequently asked questions
How long does WhatsApp template approval actually take?+
What is the single most common reason templates get rejected?+
Do I need a sample value for every variable?+
Does the category affect how much I pay?+
Can I edit and resubmit a rejected template?+
Does one rejection hurt my other templates?+
How do I get authentication (OTP) templates approved quickly?+
Can InfiQ help me build and validate templates?+
Build templates that get approved the first time
Create, validate and preview your WhatsApp templates in one dashboard with an official Meta Business Partner — talk to InfiQ and get set up correctly from day one.