Blog / API & technical

WhatsApp templates rejected by Meta: causes and solutions

Seeing a WhatsApp template rejected by Meta is one of the most common frustrations for those using the official API. You prepare the message, submit it for approval and get a "rejected" without really understanding why. The truth is that Meta follows precise rules, and in most cases the rejection has an identifiable and fixable cause. In this guide we look at why templates get turned down and how to rewrite them to get them approved, ideally on the first attempt.

Why approved templates are needed

With the official Meta API, to be the first to write to a user outside the 24-hour window you must use a pre-approved template. It's the mechanism WhatsApp uses to keep quality under control and protect users from spam. This system is also what gives you the green tick and a reliable anti-ban channel for high volumes. The price to pay is going through approval, and therefore knowing the rules of the game.

The most common causes of rejection

• Wrong category: a promotional message sent as utility or authentication.
• Promotional content disguised as a service notification.
• Badly formatted variables or too many consecutive variables with no fixed text around them.
• Unclear text, with generic placeholders like "{{1}}" and no example.
• Obvious grammatical errors, suspicious links or requests for sensitive data.
• Text that looks like spam: exaggerated promises, excessive capitals, too many exclamation marks.

The number-one cause: the wrong category

The most frequent reason for rejection is choosing the category that doesn't match the content. Meta distinguishes between marketing templates (promotions and offers), utility (updates on a transaction or an ongoing service) and authentication (verification codes). If you write an offer and label it as utility to save money, Meta notices and rejects it. The rule is simple: the category must tell the truth about the content.

How to write a template that passes

The rules for a smooth approval are largely common sense. Be clear about who you are and why you're writing. Put the variables in a context of fixed text, so Meta understands what they're for, and always provide an example value for each. Avoid suspicious shortened links, don't ask for passwords or payment data in the text, and keep a professional tone with no infomercial vibe. Reread and correct the errors: sloppiness is a signal reviewers penalize.

Always provide an example value for each variable (for instance {name} = "Marco"). A template with variables and no example is among the first things that triggers a rejection.

What to do after a rejection

A rejection isn't the end. Read the reason provided by Meta, identify the most likely cause among those listed above and rewrite the template correcting it. In most cases it's enough to change category, rephrase a sentence or add examples to the variables. Resubmit and, if you identified the problem well, it gets approved. Don't resubmit the exact same template hoping for a different outcome: the rules don't change.

How to do it with SendApp

With SendApp Agent, if you use the official Meta API, you create and submit templates for approval directly from the platform, with the {name}, {phone} and {email} variables ready to insert into the text. The interface guides you in choosing the category and in the formatting, reducing the errors that lead to rejection. Once approved, you use the template in broadcast campaigns to contacts segmented by tag. If you prefer to avoid the approval process altogether, with WhatsApp Web via QR code you send free messages without templates, taking into account the relevant limits and usage rules.

How much it costs

SendApp starts at 19 euros a month. With the official Meta API, Cloud API messages are billed by Meta according to its rates (which also depend on the template category), with no markup from SendApp; via WhatsApp Web with QR you don't pay per message. Getting templates approved on the first try saves you days of waiting and puts you in a position to communicate with customers sooner.