The rejection that nobody explains
You submit a WhatsApp message template. It gets rejected with a policy violation notice. The notice is vague. You edit the template slightly and resubmit. Rejected again. You're not sure what changed.
This pattern is more common than it should be, and most of the confusion comes from a basic misunderstanding: Meta's template review is not primarily a grammar or format review. It's a spam and deception review.
Once you understand what the reviewers are actually looking for, approvals become much more predictable.
What the template review actually checks
Meta's template approval process is designed to filter out three categories of content:
**Content that enables spam.** Templates written to send unsolicited promotional messages at scale. The tell is usually a generic message that could apply to any recipient โ no personalisation variables, vague value proposition, clear broadcast intent.
**Content that could deceive recipients.** Misleading claims, urgency manufactured without real cause, offers that aren't genuine, messages that impersonate other businesses or institutions.
**Content that violates category policies.** Financial services, healthcare, alcohol, gambling, and similar regulated categories have additional rules. A template from a health clinic that mentions a "limited time offer" on a medical procedure has a different review standard than the same template from a restaurant.
What the review does not penalise: straightforward business communication that is clearly transactional, clearly identified as coming from your business, and clearly relevant to the recipient in the context described.
Template categories and why they matter
Every WhatsApp message template has a category. The category matters for both approval likelihood and per-message pricing.
**Utility templates** cover things a customer expects to receive: order confirmations, appointment reminders, payment receipts, shipping updates, support ticket updates. These are the easiest to approve because the business justification is obvious and the expectation of receipt is clear.
**Authentication templates** are one-time passwords and login verification codes. Narrow use case, straightforward approval.
**Marketing templates** are the hardest category. Any message that promotes a product, service, or offer falls here. Marketing templates get more scrutiny, have stricter content requirements, and require a clear opt-in record for the contacts receiving them.
A common mistake: writing what is effectively a marketing message but categorising it as utility. Meta's reviewers catch this. "Your account has been updated โ check out our new features!" is a marketing template wearing utility clothes.
Patterns that reliably get rejected
Manufactured urgency without substance
"Act now โ offer expires soon!" โ Rejected. "Your 20% renewal discount expires March 31st" โ Usually approved.
The difference: specific claims with real business backing versus vague urgency designed to pressure action. If the urgency is real and specific, you can usually write it. If it's manufactured, reviewers can tell.
Vague promotional language
"Exclusive offer just for you!" โ Rejected. "Your personalised price for [product name] renewal: [amount]" โ Approved.
Templates that read like mass spam broadcasts โ no personalisation, no specific context โ fail the utility test even if you intend to personalise the variables at send time.
Missing opt-in context
Templates sent to contacts who haven't opted in to WhatsApp communication from your business are a policy violation, not just a template problem. Meta can't detect this at the template review stage, but it shows up in quality ratings and can lead to account restrictions.
Approval of a template doesn't mean you can send it to anyone. It means you can send it to contacts who have opted in.
Impersonation flags
Any template that implies association with Meta, WhatsApp, government bodies, or financial institutions gets elevated scrutiny. This includes templates with language like "Verified by WhatsApp" or anything that suggests official endorsement.
Double opt-in language that looks fake
"You've requested to receive messages from us" as a template โ even for genuine double opt-in flows โ can read as manufactured consent to reviewers. Document your opt-in process separately and write the actual message content to be operationally clear.
What a high-approval-rate template looks like
The templates that get approved quickly share common traits:
1. **Clear sender identification.** The business name is in the template, either as a variable or as fixed text. 2. **Specific context.** The recipient knows why they're receiving the message. "Regarding your order #{{1}}" is specific. "We have an update for you" is not. 3. **One clear action or one clear piece of information.** Not a list of five things the customer should do or check. 4. **Variables that make sense.** If you're using personalisation variables ({{1}}, {{2}}), the template should read coherently with realistic placeholder values. Review the template as if the variables are filled in. 5. **Footer text that matches the category.** Marketing templates benefit from clear opt-out instructions ("Reply STOP to unsubscribe"). Utility templates don't need this but including it doesn't hurt.
The category selection mistake that costs the most time
The most expensive mistake in template management: selecting the wrong category at submission.
We see this regularly. A business submits a template as "utility" that is clearly marketing content. It gets rejected. They rewrite the template to fit utility, submit again. Rejected again because the core message is still promotional. Then they switch to the correct marketing category and the same content that was rejected twice gets approved in one day.
Saving the category selection conversation until after writing the template content โ then honestly assessing what the message is โ avoids most of this churn.
A quick test: if a customer received this message without having just completed a transaction or made a specific request, would they consider it unsolicited? If yes, it's marketing, regardless of what you call it.
Multi-language templates and what changes
If you're sending templates in regional languages โ Hindi, Tamil, Malayalam, Telugu, others โ the approval process is the same but the review timeline can be slightly longer.
One thing that trips up regional language templates: machine translations of English templates often produce unnatural phrasing that looks like spam to a native speaker reviewer. Templates translated by someone who actually speaks the language perform better.
For Indian markets specifically, including the business name in the regional script (not just romanisation) in templates aimed at non-English-speaking recipients improves both approval rates and recipient trust. We're still gathering data on the exact impact, but the directional result is consistent.
Managing templates at scale
If you're running multiple WhatsApp campaigns or managing templates across product lines, a few practices reduce the compliance friction:
**Maintain a template library with status tracking.** Know which templates are approved, pending, rejected, and paused. Without this, teams end up resubmitting variations of the same rejected template multiple times.
**Document the opt-in source for each template.** Which contact list is this template intended for? What was the opt-in mechanism? This documentation matters both for Meta compliance and for your own quality ratings.
**Review quality ratings weekly.** Meta assigns a quality rating to your WhatsApp Business account based on recipient feedback โ blocks, reports, and message quality signals. A declining quality rating is a warning signal before restrictions. Catching it early is much easier than recovering from a restricted account.
**Separate promotional sends from transactional sends.** Running high-volume promotional templates on the same number as critical transactional messages (order confirmations, payment receipts) creates risk. If the promotional sends generate complaints and lower the account quality rating, your transactional messages also get affected.
The businesses with the smoothest WhatsApp API operations aren't necessarily the ones sending the most messages. They're the ones with the tightest compliance practices and the clearest distinction between what their contacts have opted in to receive.
For businesses connecting WhatsApp messaging to their broader customer experience โ especially review generation โ [RatingE](https://ratinge.com) integrates well with WhatsApp review request flows. The timing logic of a review request template sent after a resolved support interaction is one of the higher-performing use cases for utility templates that doubles as business development.
*Image suggestion: a side-by-side comparison of two template versions โ one that would get rejected (vague, no context, manufactured urgency) versus one that would get approved (specific, named business, clear context) โ annotated to show why each would be treated differently.*