Why your WhatsApp template was rejected, and how to fix it

A WhatsApp message template is a pre-written message that Meta reviews before you may send it to customers who are outside the 24-hour service window. Until it is approved, any automation that depends on it cannot run — which is why a rejection is not a paperwork problem, it is an outage.

The good news is that rejections cluster. In practice a handful of causes account for most of them, and each has a specific, mechanical fix.

Cause 1: the content does not match the category

This is the most common rejection, and it is usually reported as an incorrect category error. The pattern is a message with promotional content submitted as utility, or — less obviously — a message containing a credential or code submitted as anything other than authentication.

We hit the second version ourselves. A template that told a customer their account name, with a "Sign in" button, was auto-rejected: a credential plus a login button reads as an authentication template, and that category only accepts Meta's fixed wording, which cannot carry a custom value. The fix was to reframe the message as an account-details lookup rather than a credential delivery, which kept it in utility.

The fix: decide the category from the content, not from what you want to pay. Our guide to utility versus marketing templates has the working test.

Cause 2: variables with no example values

Every placeholder in your template needs a sample value at submission so the reviewer can see what the finished message looks like. A template reading "Hi {{1}}, your order {{2}} is on its way" with no examples gives the reviewer nothing to assess, and is commonly rejected.

The fix: fill in a realistic example for every variable — "Sarah", "#1042" — not placeholder text like "name" or "xxx".

Cause 3: the message starts or ends with a variable

A template whose entire content is variables, or that opens or closes with one, is treated as unreviewable — the reviewer cannot tell what will actually be sent.

The fix: anchor every variable in fixed text. "{{1}}, {{2}}" becomes "Hi {{1}}, your order {{2}} has shipped."

Cause 4: it breaks the Commerce Policy

Some goods cannot be sold or promoted over WhatsApp at all, and a template referencing them will be rejected regardless of how it is written. Meta's Commerce Policy covers weapons and ammunition, tobacco and vaping products, alcohol, drugs, adult goods, real money gambling, counterfeit goods, multi-level marketing schemes, and body parts or fluids. The policy applies to your catalog, your message threads, your business profile and your templates alike.

The fix: if you sell in a restricted category, this is not a wording problem. See what you cannot sell on WhatsApp before you invest further.

Cause 5: formatting and length

How long approval takes

Meta does not publish a guaranteed turnaround, and in practice it varies from minutes to a day or more. Two things follow from that. First, do not submit a template on the morning of a campaign. Second, if a template has been pending far longer than your others, a small edit and resubmission is usually faster than waiting.

How many templates you are allowed

Rejections sometimes come after a limit rather than because of content. Meta's template documentation sets these ceilings per WhatsApp Business Account:

If you create one template per product or per campaign, 250 arrives faster than you expect. See how many WhatsApp templates you can have.

A checklist before you submit

1. Read the message aloud. Does it sound like a person, or like a mailshot?
2. Could this message exist if the customer had never bought anything? If yes, it is marketing — submit it as marketing.
3. Does every variable have a realistic example value?
4. Does the body start and end with fixed text?
5. Is the body under 1,024 characters?
6. Do all links open?
7. Do the button labels match what happens when they are tapped?
8. Does anything in it touch a restricted category?

What to do while you wait

An automation whose template is not yet approved should stay unpublished — our builder blocks publishing a flow with an unconfigured template step for exactly this reason. In the meantime you can build and test everything else in the flow; testing an automation safely covers how to exercise a flow without messaging real customers.

And if the template is approved but messages still are not arriving, the problem is downstream — start with the error code guide.