WhatsApp Business
WhatsApp Message Templates: Why They Get Rejected and How to Write Approvable Ones
Templates power every business-initiated WhatsApp message. How I choose categories, use variables safely, and write templates that pass review.
Why WhatsApp templates matter
Templates power every business-initiated WhatsApp message: booking confirmations, delivery updates, reminders, and one-time codes. Outside the 24-hour customer service window, a template is the only way to reach a customer. If templates are rejected or paused, a core part of the product stops working.
Meta reviews each template, usually quickly, and continues to monitor how customers react after approval.
Choose the correct template category
- Utility: related to a specific transaction or account the customer requested, such as a booking confirmation or delivery update.
- Marketing: promotes products, offers, or re-engagement. Anything that is not clearly utility or authentication is usually marketing.
- Authentication: delivers one-time passcodes with a fixed format and optional copy-code or one-tap buttons.
Choosing the wrong category is a common reason for rejection or automatic recategorization. A utility template that includes a discount or a call to buy is treated as marketing. Keep utility templates strictly about the transaction.
Using template variables correctly
- Do not start or end the template body with a variable.
- Do not place variables next to each other without text between them.
- Provide realistic sample values for every variable when submitting.
- Keep enough fixed text so the purpose is clear without the variables.
- Do not use variables to inject whole sentences or promotional text.
Examples: rejected vs approved templates
Likely rejected (vague, variable-heavy, mixed purpose):
{{1}}
{{2}} Use code {{3}} for 20% off your next ride!
Likely approved (clear utility):
Hi {{1}}, your ride on {{2}} is confirmed.
Your driver {{3}} will pick you up at {{4}}.
Reply HELP if you need to change the booking.The approved version describes a specific transaction the customer requested, uses variables inside clear sentences, and gives the customer a way to respond, which reopens the customer service window.
Buttons, headers, and media
Templates can include a header with text or media, a footer, and buttons. Quick reply buttons are especially useful for booking flows, because a tap counts as a customer message and opens the window for free-form follow-up. URL buttons work well for tracking pages or receipts. Keep the number of buttons small and the labels short and specific, such as Change time or Cancel booking.
Common WhatsApp template rejection reasons
- The category does not match the content.
- Formatting issues: variables at the start or end, adjacent variables, or missing sample values.
- Content that looks like spam, threats, or misleading urgency.
- Requests for sensitive information such as full card numbers or passwords.
- Spelling and grammar problems that make the message look unprofessional.
- A template that duplicates an existing one with different wording.
Managing templates as code
In production systems, I keep template names, languages, categories, and variable order in a configuration file, versioned in the repository. The backend refuses to send a template that is not defined there, and it validates the variable count before calling the API. This prevents mismatched variables, which otherwise appear as runtime errors only when a customer is waiting for a message.
I also store the approval status per template and language, synced from the API, so the product can fall back or alert operations if a template is paused.
Writing templates in multiple languages
For products serving several languages, each language is a separate template version that needs its own approval. I write the English version first, get it approved, and then translate it with a native speaker rather than a direct machine translation. Templates that read naturally in the customer's language are approved more reliably and perform better.
The backend selects the template language from the customer's preference, with a fallback to a default language if a translation is missing or paused. Variable order must be identical across languages, which is another reason to manage templates as configuration instead of hard-coding them in the codebase.
Protecting quality after approval
Approval is not the end. If customers block or report messages, template quality drops, and Meta can pause the template or lower the number's limits. Send templates only to customers who opted in, at times that make sense, and only for messages they expect. Monitor template status and quality changes from the webhook stream so you can react quickly.
Frequently asked questions
How long does WhatsApp template approval take?
Many templates are reviewed within minutes to hours, but some take longer. Submit templates well before launch.
Can I edit an approved template?
Edits are limited and trigger a new review. For larger changes, create a new template version.
Why was my utility template recategorized as marketing?
It probably contained promotional content, such as offers or upsells. Keep utility templates focused on the requested transaction.
Do I need a template for every language?
Yes. Each language is a separate template version that must be approved.