Skip to main content
RoutMe
All posts
WhatsApp3 min read

Why your WhatsApp templates keep getting rejected

Template review failures are boringly predictable. The same handful of mistakes account for most of them, and all are fixable before you submit.

SM

Sushma Madan

WhatsApp platform

Template rejection is the most common thing standing between a team and their first WhatsApp send, and it is almost always one of a small set of causes. Here they are in roughly the order we see them.

1. The category is wrong

This is the big one. Teams label a promotional message as utility because utility is cheaper, and review catches it. The test Meta applies is not what you call the message, it is whether the message would exist if the customer had not done something specific.

  • 'Your order #1042 has shipped', utility. It exists because of an order.
  • 'Your order shipped! Here's 10% off your next one', marketing. The offer is the point of the second half.
  • 'We miss you, come back', marketing, unambiguously.
  • 'Your appointment is tomorrow at 3pm', utility.

Mixing a promotion into a transactional template gets the whole template categorised as marketing, at marketing rates. If you want both, send two templates or accept the category.

2. Unbounded variables

A template that is mostly placeholders reads to a reviewer as a blank cheque, because they cannot tell what will actually be sent.

Rejected:  {{1}} {{2}} {{3}}
Rejected:  Hi {{1}}, {{2}}
Approved:  Hi {{1}}, your order {{2}} is out for delivery
           and should arrive by {{3}}.

Keep the sentence structure fixed and let variables fill nouns and values. Never start a template with a variable, and never place two variables adjacent with nothing between them.

3. Sample content that does not match the shape

The samples you provide are what the reviewer reads. Supplying 'test', 'abc', or '123' for a variable that will hold a delivery date is a rejection waiting to happen. Provide realistic samples of the actual data.

4. Asking for things you should not ask for over WhatsApp

  • Full card numbers, CVVs, or bank credentials, never approved, and correctly so.
  • Passwords or full government ID numbers as free text.
  • Anything implying the customer must reply to avoid a penalty.

5. Formatting and length problems

  • Excessive capitals. A shouted word or two is tolerated; a shouted sentence is not.
  • Emoji used as structure rather than punctuation.
  • Body copy over the character limit, usually caused by a variable that turns out longer than the sample.
  • URLs in the body when they belong in a button, especially shorteners, which review treats with suspicion.

6. Buttons that do not match the body

A 'Track order' button on a template whose body talks about a discount is an inconsistency, and inconsistency reads as a repurposed template. Buttons should be the obvious next action for the message they sit under.

When you are rejected anyway

  1. 1Read the actual rejection reason rather than guessing. It is usually more specific than teams assume.
  2. 2Change one thing. Resubmitting three edits at once tells you nothing about which one mattered.
  3. 3If you believe the category call was wrong, appeal rather than resubmitting the same template under a different name, duplicates hurt your quality rating.
  4. 4Watch quality rating after approval, not just at submission. A template can be approved and then throttled because people block or report it, and that signal is more valuable than the review outcome.
  • WhatsApp Cloud API
  • Templates
  • Operations
SM

Sushma Madan

WhatsApp platform

Writes about templates, pricing, and getting things approved on the WhatsApp Business Platform.

See it on your own data

Connect a system, drop an agent node into a flow, and watch it answer from what is actually true in your systems right now.