Why WhatsApp Keeps Rejecting Your Message Templates (The 3 Real Reasons)

You submitted a template, waited, and got back a rejection with no real explanation. You are not doing anything stupid. You are just hitting rules nobody tells you about up front. There are three reasons templates get rejected. Here is all three, how to spot them before you submit, and how to get approved the first time.

Published 18 August 2026 · 7 min read

Watch: the three reasons, explained

This short walkthrough breaks down each reason a template gets rejected and how to fix it, then shows an AI assistant building an approved template live.

Why templates get reviewed at all

One idea makes every rule below make sense. A template is a message you are allowed to send to people before they have messaged you, or after the 24-hour customer service window has closed. That is a privilege, so Meta reviews every template before it goes live.

The reviewer is checking three things, and that is the whole story: does the category match the content, is the message structured correctly, and does it follow policy. The frustrating part is that the rejection almost never tells you which of the three you failed. It just says rejected, sometimes with a vague code. So let us decode all three.

Reason 1: the category does not match the content

This is the most common rejection and the easiest to fix once you get it. Every template has to be filed under a category, and the category has to match what the message actually does. There are three:

• Marketing. Promotions, offers, announcements, anything that sells or re-engages.
• Utility. Tied to something the customer did. Order updates, appointment reminders, receipts.
• Authentication. One-time passcodes and verification codes, that is it.

The classic mistake is to write a promotional message but file it as utility, because utility feels safer and it is cheaper to send. Meta's reviewer reads the actual words, sees marketing dressed up as a receipt, and rejects it for a category mismatch. The rule to remember: category follows intent, not the price you wish you were paying. If the message sells, it is marketing. If it confirms something the customer already did, it is utility.

One recent thing worth knowing: Meta now also re-categorizes some templates automatically instead of just rejecting them, so a template you filed as utility can quietly become marketing and cost more to send. Either way, the fix is the same. Match the category to the content from the start.

Reason 2: the formatting and variable traps

This is the sneaky one, because your message reads perfectly fine to a human and still gets a hard invalid-format rejection. It is almost always the little placeholder slots, the double curly braces, that break it. These are the exact traps that catch people:

• A variable at the very start or end. "Hi {{1}}" as the opening or "...see you {{1}}" as the ending gets rejected. A placeholder cannot sit at the edge of the message.
• Two variables touching. {{1}} {{2}} back to back with nothing between them. The reviewer cannot tell what either one is for.
• A variable floating with no words around it. A placeholder alone on its own line, no context. That slot could be used to send anything, so it is rejected.
• Variables that are not sequential. If you have {{1}}, {{2}} and {{3}} and you delete the middle one, you cannot leave {{1}} and {{3}}. They have to run in order with no gaps.
• Too many variables for too little text. A short message that is mostly placeholders reads like a spam template, so reviewers reject it.

Why all of this exists: every placeholder has to have an obvious purpose. Meta needs to know that {{1}} is a first name and {{2}} is an order number, not a slot you will later stuff with a discount link. Surround every variable with real words that make its job obvious. And the quiet one people forget: when you submit, you have to give an example value for each placeholder so the reviewer sees what it looks like filled in. Leave those out and it gets rejected before anyone reads your copy.

Reason 3: it breaks policy

The third bucket is content that is structurally fine but breaks WhatsApp's business policy. This one gets people who think a template is just an email. The ones that actually trip businesses up:

• Link shorteners. Wrapping your link in a bit.ly or similar gets flagged, because Meta cannot see where it goes. Use your real, full domain.
• Asking for sensitive information. Requesting full card numbers, passwords or ID numbers straight in the message is a policy violation.
• Prohibited or restricted goods. Certain products are not allowed to be promoted over WhatsApp at all.
• Aggressive or threatening tone. Threatening legal action, pressuring or shaming a customer to pay. Reviewers reject that.

WhatsApp is a personal channel and Meta protects it hard. Write like you are messaging a real person you respect, keep your links clean and do not ask for anything sensitive, and this whole category disappears.

The real problem: it is a memory test

Notice that all three rejection reasons are things you have to just know and remember every single time you write a template. That is the actual problem. It is a memory test, and the way to never fail it is to not sit the test by hand.

This is exactly why we built DripRaven. Instead of hand-building a template and hoping, you talk to ChatGPT, Claude or any AI assistant you already use, and describe the message you want in one plain sentence. Something like: create a WhatsApp template reminding a customer about an abandoned cart, personalized with their first name and the product name.

Here is what that kills, automatically:

• It picks the correct category for the intent, so there is no category mismatch.
• It writes the copy with placeholders wrapped in real text, never at the edges, never two in a row, always sequential, so there is no format rejection.
• It maps {{1}} to the first name and {{2}} to the product from your contact data, and fills in the example values for you, so nothing is ambiguous.
• It keeps the links and tone policy-clean by default.

Then it previews the filled-in message with a real contact before anything sends, and it will not let you send with an unmapped placeholder, so you never blast "Hi {{1}}" to a real person. Every rule this article just explained, DripRaven follows for you, because you described what you wanted instead of building a template and hoping.

The short version

• Templates get reviewed because they let you message people first, so Meta checks each one.
• Reason 1: the category does not match the content. Category follows intent, not the cheaper price.
• Reason 2: formatting and variable traps. Wrap every placeholder in words, keep them sequential, give example values.
• Reason 3: policy. No link shorteners, no requests for sensitive info, no aggressive tone.
• Fix those three and you get approved. Or let an AI build compliant templates for you.

Frequently asked questions

Related reading

• WhatsApp is ending free business messaging: what changes on October 1, 2026
• The real WhatsApp broadcast limit, and why your messages are not delivered
• How WhatsApp broadcasts work with DripRaven
• Run WhatsApp campaigns from ChatGPT
• The WhatsApp MCP server for AI agents