WhatsApp template messages: getting and staying approved
Templates are the only way to reach a customer outside the service window, and they are reviewed before use. Rejections are predictable once you know what the review checks.
Key takeaways
- Templates are required to message outside the twenty-four hour customer-initiated window, and are reviewed before use.
- Placeholder abuse and category mismatch are the two most common rejection causes.
- Submit each language as its own template and check variable placement in right-to-left rendering.
- Templates and numbers carry quality ratings; poor reception reduces how many people you may message at all.
A template message is pre-written content, submitted to Meta for review, that you may send to a customer outside the twenty-four hour window opened by their own message. Review usually completes within minutes to a day. Rejections cluster around a small set of causes, nearly all of which are avoidable if you write the template knowing what the review is looking for.
Why templates rejected get rejected
- Placeholder abuse. A template that is almost entirely variables, or that opens or closes with one, is rejected because the reviewer cannot tell what will actually be sent.
- Category mismatch. Submitting promotional content under a utility or authentication category. Categories carry different pricing, so this is checked carefully and it is the most common substantive rejection.
- Missing context. A message that does not make clear who is writing and why the recipient is receiving it.
- Formatting and content faults. Broken or excessive punctuation, all capitals, spelling errors, or content that misrepresents what the business does.
Writing one that passes first time
Name the business in the message body rather than relying on the display name. State the reason for contact in the first sentence. Keep variables to the specific facts that change, an order number, a date, an amount, and surround them with fixed text that makes their purpose obvious. Submit the category that honestly matches the intent; a promotional message submitted as utility will either be rejected or, if it slips through, will attract a policy problem later.
For bilingual programmes, submit each language as its own template rather than mixing languages in one. Arabic templates should be written in Arabic rather than translated at send time, and the variable placement needs checking in right-to-left context, where a number or Latin product name at the start or end of a line can render in an unexpected position.
Staying approved
Approval is not permanent. Templates carry a quality rating driven by how recipients respond, and a template accumulating blocks and reports can be paused or disabled. Your number carries its own quality rating too, and a low one reduces how many customers you may message. This is the mechanism that makes aggressive broadcasting self-defeating: the punishment is capacity, not a fine.
Monitor the ratings rather than discovering a problem when a campaign fails to send. If a template's rating drops, stop sending it and rewrite it; continuing to send a poorly received template drags the number's rating down with it.
Operational advice
Build the approval delay into every campaign timeline, and maintain a small library of approved general-purpose templates so an urgent message is never blocked waiting on review. Keep templates few and well-used rather than many and marginal; a large library is harder to monitor and every unused template is a rating you are not watching.
The punishment for aggressive broadcasting is capacity, not a fine. You lose the ability to send.