A rejected message template is one of the most common frustrations for anyone new to the WhatsApp Business API, mostly because the rejection reason Meta gives is often terse — “Invalid Format” or “Marketing violation” — without much explanation of what to actually change. The good news is that template review isn’t arbitrary: there’s a specific, checkable set of rules behind almost every rejection.
The five most common causes
1. Wrong category
The most common rejection is a marketing template disguised as something else, usually a utility or authentication category chosen because it has a lower cost or friendlier free-tier treatment. Meta’s reviewers check the actual content against the claimed category, not just the label a business picks — a template offering a discount, promoting a sale, or nudging a purchase gets rejected (or later re-classified and billed differently) if it’s submitted as “utility” instead of “marketing,” regardless of intent. The fix is simple but non-negotiable: categorise by what the message actually does, not by what category is cheaper.
2. Variable misuse
A template with placeholders like {{1}} and {{2}} that don’t have enough surrounding static text for a reviewer to understand what’s actually being sent, or a template that’s essentially just one giant variable with almost no fixed content around it, gets flagged. WhatsApp requires templates to have real, meaningful static text — a variable-only template reads as a way to send arbitrary unreviewed content through an approved template, which is exactly what the review process exists to prevent.
3. Formatting and character issues
Excessive capitalisation, excessive emoji, non-standard Unicode characters used to bypass filters, or a header/body that looks visually broken when rendered all get flagged, because they’re common patterns in spam and phishing templates. A template that superficially resembles that pattern gets rejected even with entirely legitimate content — toning down formatting is often enough to pass on resubmission.
4. Requesting sensitive information
A template that asks a customer to reply with a password, full card number, or other sensitive personal data — even for a legitimate reason like account recovery — is rejected on policy grounds. If a flow genuinely needs to collect sensitive information, a WhatsApp Flow with proper field types is the compliant way to do it, not a plain-text template reply.
5. Resubmitting a near-duplicate
Submitting a near-duplicate of a template that was already rejected, with only a cosmetic change, is easy to miss but counterproductive. Meta’s system recognises repeated resubmission of essentially the same rejected content as a pattern worth flagging further, which can slow down or complicate approval of a business’s other, unrelated templates too. If a template gets rejected, address the specific reason rather than resubmitting with a single word changed.
The practical checklist
Before submitting: is the category honest about what the message does; does the template have enough static, meaningful text around any variables; is formatting clean and non-spammy; does it avoid asking for sensitive data in a plain reply; and if it was rejected before, has the actual underlying issue been fixed rather than papered over? Templates that clear all five submit-review-approve in hours, not days — most delays come from resubmitting the same problem repeatedly rather than the review process itself being slow.
Takeaway
Template rejections feel arbitrary until you check them against this list — almost every one traces back to one of these five causes, and almost every one is fixable without changing what the message is actually trying to achieve.
Full detail is on the WhatsApp Hub blog: Why WhatsApp Business Templates Get Rejected.
Leave a Reply