Guides

5 Tips to Get Your WhatsApp Message Templates Approved Faster

Meta rejects a surprising number of message template submissions. Learn the five most common pitfalls and how to avoid them.

StartMessaging Team Updated

WhatsApp message templates are the gateway to reaching your customers proactively on WhatsApp. But Meta’s review process can feel like a black box — submissions get rejected without much explanation, and revisions take time.

Meta reviews every template and sets the review time, so the fastest approval is the one you don’t have to resubmit. These five patterns help a template pass the first time.

1. Match category to content — precisely

Template categories are not suggestions. Meta checks whether your template text actually matches the category you chose.

  • Utility = transactional updates about something the customer already did (order shipped, appointment reminder, payment received)
  • Authentication = one-time codes only. Meta writes the body text itself; you choose the language, the security warning, the code expiry and the copy-code button
  • Marketing = anything promotional, offer-based, or re-engagement focused

If your “utility” template says “your order shipped — and check out our new collection!”, Meta will reject it or move it to Marketing. Meta can also recategorise an approved template later, which changes what each message costs, because Meta prices templates by category. Since 1 October 2026 Meta charges every delivered template, utility included, so pick the right category upfront.

2. Keep variable usage minimal and meaningful

Every {{1}} placeholder is a point of scrutiny. Templates with more than 3–4 variables often fail the review because Meta can’t verify how they’ll be used.

Best practice:

Hello {{1}}, your appointment with {{2}} is confirmed for {{3}}.

Avoid vague placeholders like {{1}} that could contain anything — Meta wants to infer context from the surrounding text. Named variables ({{first_name}}) read more clearly, and Meta needs a sample value for every variable, so give realistic ones. A template keeps the variable style it was created with; duplicate it to switch.

3. Avoid restricted phrases

Meta maintains a (mostly unpublished) list of phrases and patterns that trigger automatic rejection:

  • “Click here” or “Tap here” in CTAs — prefer a clear action like “Track your order”
  • Urgency language in utility templates: “Act now”, “Limited time”
  • ALL CAPS text beyond brand names

When in doubt, read the template aloud. If it sounds like a spam SMS from 2010, revise it.

4. Use a clear call-to-action for button templates

If your template includes buttons (URL or quick reply), the button label must clearly describe what happens when tapped:

AvoidPrefer
”Click""Track my order"
"Learn more""View appointment details"
"OK""Confirm booking”

Ambiguous button labels are one of the most common rejection reasons.

5. Submit in the right language with correct locale code

Always match your template’s content to the language you choose for it. Writing Hindi copy in a template set to en_US, or Hinglish in a template set to hi, invites a rejection. The same name in another language is a separate template, and when you send it over the API you pass that exact language code (for example en_US or hi) as template.language.

Also: do not mix languages in a single template. If your audience is bilingual, create two separate templates — one per language.


Following these five guidelines won’t guarantee approval, but they remove the most common reasons for a rejection.

If a template is rejected, the dashboard shows Meta’s rejection reason. Fix it and resubmit, or contact our support team for help. The message templates docs list every category, component limit and button type.

S

StartMessaging Team

StartMessaging Team