A rejected template is rarely a mystery. In our experience the same handful of causes account for most of them, and all of them are avoidable at drafting time rather than at resubmission time.
The leading cause is the category
Meta describes incorrect category selection as the single biggest reason templates get rejected. It is not close.
The specific pattern: promotional content submitted as Utility. Phrases like “limited-time offer”, “shop now”, “don’t miss out” are marketing intent, and they will be read as marketing intent regardless of what the dropdown says. Submit them under Marketing and they sail through. Submit them under Utility and they come back.
We wrote about how the three categories differ separately, because getting this right upstream removes most of the pain downstream.
Hybrid templates
A template must have one clear, singular purpose. A receipt that also carries a coupon is two messages wearing one coat. So is a delivery notification that ends with a cross-sell.
If you find yourself writing “and also” in a template brief, you have two templates.
Authentication templates with personality
Authentication is the strictest category by some distance. Passcode delivery is a format, not a canvas. Brand voice, extra reassurance copy, a friendly sign-off — each of these increases rejection risk without improving the message.
The customer wants six digits. Give them six digits.
Unclear variables
Variables that are not obviously bounded cause rejections, because the reviewer cannot tell what the message will actually say when it is sent.
Hi {{1}}, your {{2}} is {{3}}. is a template that could render into almost anything. Hi {{1}}, your order {{2}} was delivered on {{3}}. is a template with a shape. The second one tells a reviewer what they are approving.
Two related habits:
- Never start or end the body with a variable. A message that opens with an unresolved placeholder reads as broken.
- Provide realistic sample values. They are part of what gets reviewed.
Formatting that mimics the system
Avoid all-caps blocks and formatting that makes a commercial message look like a system alert or a security warning. This sits under the same policy logic as the authentication rules: the platform protects the visual vocabulary that users rely on to tell real alerts from marketing.
URL shorteners
Avoid them. A shortened link hides the destination from review, which is exactly the property review exists to defeat. Use the full HTTPS URL.
What to do when one is rejected
Meta usually returns a brief reason. Read it literally before rewriting anything — the most common wasted cycle is a team rewriting the whole message when the objection was to one word or one placeholder.
Then:
- Fix the specific issue, not the whole template.
- Resubmit. Approval often lands within minutes; 24–48 hours is normal if it goes to manual review.
- If the objection was the category and you disagree, request a category review through WhatsApp Manager rather than resubmitting the same content and hoping for a different reviewer.
The habit that prevents most of this
Draft templates in batches, well ahead of the campaign or the incident that needs them, and submit them early.
The reason is not efficiency. It is that review latency is unpredictable in exactly the wrong direction — a template flagged for manual review takes longest at the moment you most need it to be fast. A library approved three weeks ago has no latency at all.
Approval is also final in one direction worth remembering: you cannot edit an approved template’s text. Every change is a new submission. That is an argument for getting the first draft right, and for writing inside the character budget deliberately rather than discovering it at 1,024 characters.