Why Meta Rejects WhatsApp Templates

Template rejection feels arbitrary the first ten times it happens. It is not. Meta is running a checklist and a classifier, and once you know what each is looking for, the hit rate goes from coin-flip to nearly perfect.

What follows is partly Meta’s documented policy and partly what we have watched happen to our own submissions - including a few behaviours we have never seen written down anywhere, because they only show up if you submit enough templates to spot the pattern.

The hard limits

These are not judgement calls. Break one and the API rejects the request outright, before a reviewer ever sees it.

Variables cause more rejections than content does

This surprises people, who assume review is about tone. In our experience the majority of hard rejections are structural, and they come from the placeholders.

1. Numbering must be sequential with no gaps. Going {{1}}, {{3}} rejects. Meta expects a dense sequence starting at one.
2. No variable may lead or trail the body. A body that starts or ends with a placeholder throws error 2388299. A trailing full stop is sometimes not enough to save it - give the variable real words on both sides.
3. Fixed text should be at least 60% of the body. A body that is mostly placeholders looks like a spam mail-merge, and trips error 2388293.
4. Sample values are inspected, not ignored. This is the one people skip. If you pass "Test" or "xyz" as your example, you are asking a reviewer to evaluate a template they cannot picture. Give real-looking values - Priya Sharma, Crystal Hall, Ground Floor - and approval rates go up measurably.
5. Footers never take variables. Error 2388073, every time.

The category is the expensive decision

Every template is marketing, utility, or authentication. This sets your per-message cost and how much recipient annoyance Meta will tolerate before acting. Since 9 April 2025 you cannot opt out of reclassification - the allow_category_change flag was removed. Submit as utility, and if Meta disagrees, it approves as marketing. There is no rejection to appeal against, and no notification that shouts at you.

Utility survives only when all of the following hold:

• The message is non-promotional - no offers, no upsell, not even a soft one
• It is triggered by something the person did, or is essential to them
• It refers to a specific transaction or event they already have with you
• It carries concrete reference details, not generic copy

Since 1 July 2025 that bar tightened further: utility must be non-promotional and either user-requested or essential. And repeat miscategorisation is not free - Meta restricts accounts that keep trying it from creating new utility templates at all.

What we have actually observed

Here is the part you will not find in Meta’s documentation. These are patterns from our own submission logs, and they changed how we write templates.

The classifier runs at submission, not during review. When you POST a template, the response comes back PENDING - but the category is already decided and already in the payload. So you do not have to wait a day to learn your verdict. Immediately GET /<waba>/message_templates?name=<name>&fields=name,status,category and read the category back. If it flipped, stop and rewrite now, because once review completes the category is locked.

Only the body is classified, so siblings inherit. WhatsApp requires a separate template per attachment type, which means one logical message becomes up to four submissions - text, image, video, document - sharing an identical body. Because the classifier reads the body, they all land in the same category. The practical move: submit the text variant alone first, confirm it came back utility, and only then submit the other three. If the text version flipped, you have saved yourself three wasted names.

Tense does not matter. Tone and structure do. We had two near-identical food announcements, one written in future tense (“will be served”) and one in present (“is now being served”). Both classified as utility. The classifier is not parsing time; it is judging whether the message reads operational or social.

These flipped our templates to marketing:

• Social closers - “See you there!”, “We can’t wait”, “Don’t miss”
• Exclamation marks. A single one is enough of a signal.
• Flowing prose with no labelled fields to anchor it

These survived as utility:

• Labelled structure - Venue: {{2}}, Open until: {{3}} - which reads like a receipt
• Zero exclamation marks
• Operational closers. “Please reach the venue at your convenience” passes, because it tells the reader what to do. “See you there” fails, because it tells them what to feel.

That last distinction is the whole game, and it is a genuinely uncomfortable one to write against. The warmest, most human version of your message is the one most likely to be billed as marketing.

Content that auto-rejects

Meta will not approve templates that request sensitive data (passwords, PINs, card numbers), mimic WhatsApp system messages, use threatening or urgency language (“act now or lose access”), mention competitors, or fall into restricted categories such as alcohol, tobacco, weapons, or gambling.

Two more that catch people out. Spelling and grammar errors are grounds for rejection - reviewers really do act on them. And URL shorteners are banned outright. Since 1 January 2026 every link in a body or button must be a valid, reachable HTTPS URL. A staging link or a 404 will fail review, so run curl -I over your buttons before you submit.

Approval is not permanent

The most costly misconception in this whole area is that approval is a finish line. It is not. Meta keeps scoring a live template on how recipients react, and it can act on that at any time.

Quality pausing matters more than it sounds if your sending is event-shaped. If a critical template gets paused the morning of the event, there is no support queue that will save you. The only real mitigation is a fallback template, already approved, under a different name.

How to submit so you pass

Two habits do most of the work. Submit in batches of three or four, not twelve. Bulk submissions attract pattern rejection. And submit your most obviously transactional templates first - it establishes a track record on the account before you ask it to judge anything borderline.

If a template does get reclassified, you have a 60-day appeal window through Business Support Home. Even when you do not intend to appeal, it is worth opening - it is the only place Meta explains its specific reasoning. For moving fast, though, rewriting and resubmitting under a new name beats waiting on an appeal.

The template system is the platform’s toll gate, and most of the frustration around it comes from treating it as a formatting exercise. It is a classification problem. Write for the classifier - labelled, operational, unexcited - and save the warmth for the messages you send inside the 24-hour window, where nobody is reviewing your wording at all.