Before you can send a WhatsApp message outside an open conversation, the template behind it has to pass Meta's review. Most templates come back in minutes; some take longer, up to about a day. Either way, a rejected template stalls whatever you were about to send, so it's worth knowing what actually trips up review before you submit.
What review is actually checking
Review checks two separate things: does the template's content match the category you filed it under, and does it follow WhatsApp's general content policy (no illegal content, no content that violates the platform's commerce and messaging policies). It is not checking grammar or tone, and it will not warn you if the wording is confusing. That part is on you.
The most common reasons templates get rejected
- Category mismatch. The single biggest cause. An Authentication template with a promotional line, or a Utility template that reads like an ad, gets rejected or reclassified. The content has to match the category, not just the intent behind it.
- Variables with no surrounding context. A template that is mostly a variable, like "{{1}}" on its own line with nothing explaining what it is, often gets flagged. Give every variable a sentence around it so a reviewer, and a recipient, can tell what it means.
- Variables placed back to back. Two or more variables next to each other with no fixed text between them makes the template hard to review and easy to abuse, so it's a common rejection trigger.
- Formatting that reads as spam. ALL CAPS, excessive punctuation, or emoji-heavy marketing language in a non-marketing category reads as promotional even when the intent wasn't.
- Authentication templates that stray from the standard format. Authentication templates use a simplified, largely fixed format across the platform: a code, an expiry note if relevant, nothing promotional. Adding branding language or extra marketing copy is a frequent rejection reason here specifically.
Quality rating and why it matters after approval
Approval isn't the finish line. Every template, and the phone number sending it, accumulates a quality rating based on real recipient behavior: blocks, reports, and negative feedback push it down. A template or number with a low rating can get paused or throttled even after passing initial review. Two practical implications:
- Only send templates to people who actually expect them. Sending a marketing template to a list that never opted in is the fastest way to tank a quality rating.
- If a template's real-world wording surprises recipients, e.g. it looks nothing like what they expected after seeing the preview, expect more blocks than a template that matches expectations exactly.
A practical checklist before you submit
- Match content to category. Read the template back and ask whether it is genuinely a code, a transaction update, or a promotion. Pick the category that description matches.
- Give every variable context. Write full sentences around placeholders so the purpose is obvious without needing the filled-in value.
- Keep Authentication templates plain. Code, optional expiry note, nothing else.
- Preview it as a recipient would read it. If it reads like an ad and it isn't filed as Marketing, that mismatch is the problem.
- Only send to people who expect it. Consent and relevance protect your quality rating more than clever copy does.
Wevlix mirrors each template's review status in your dashboard as Meta processes it, so you can see whether something is pending, approved, or rejected without checking a separate system. For more on how categories work in the first place, see WhatsApp Message Categories Explained on the blog.
The Wevlix Team