In almost every WhatsApp Business API build we deliver, the step that slips the timeline is not the CRM integration or the chatbot logic. It is template approval. A flow is designed, tested and ready, and then sits waiting because the message it depends on was rejected, or approved in a different category from the one it was written for.
This applies whichever platform you use. BotSpace, WATI, Respond.io and every other provider submit templates to the same Meta review, so the rules below hold regardless of the tool on top.
Why templates exist at all
WhatsApp separates conversations the customer starts from messages the business starts. When a customer messages you, a 24-hour customer service window opens and you can reply freely inside it. Outside that window, every message you send has to be a pre-approved template: a fixed message with optional placeholders that Meta has reviewed in advance.
That covers most of what businesses want to automate: appointment reminders, order and delivery updates, payment receipts, follow-ups after an enquiry goes quiet, re-engagement and promotions. Every one of them needs a template, which is why template design belongs at the start of a project rather than the end.
The three categories, and why the choice matters
| Category | What it is for | What gets it reclassified |
|---|---|---|
| Marketing | Promotions, offers, announcements, re-engagement, anything meant to generate a sale | Nothing. This is where reclassified templates end up |
| Utility | A specific transaction or request the customer already made: order status, booking confirmation, payment reminder | Any promotional content, including a discount or a cross-sell line added at the end |
| Authentication | One-time passcodes for logging in or verifying an account | Anything beyond the code and the fixed wording Meta provides |
Meta checks the category as part of review and can move a template it considers promotional into marketing. Because the categories are priced differently, that is a billing change, not just a label. A booking confirmation with a single line advertising another service is a marketing template, and it costs the marketing rate every time it is sent.
The rejection reasons we see most often
Meta's rejection notices are brief, so it helps to know the usual causes before submitting:
- A variable at the very start or very end of the message. Templates are expected to open and close with fixed text, so a message beginning with the customer's name placeholder is a common rejection.
- Variables with no sample values. Reviewers need to see what each placeholder will contain. Without examples, they cannot tell a delivery date from a discount code.
- Too many variables for the amount of fixed text. A template that is mostly placeholders cannot be reviewed meaningfully, because almost anything could be sent through it.
- Placeholders numbered out of order, mismatched braces, or two variables side by side with nothing between them.
- Content that breaks WhatsApp's Business or Commerce policies, or that asks the customer for sensitive information such as full card numbers or identity document numbers in a reply.
- Shortened or disguised links. Use your full domain so the reviewer and the customer can both see where a link goes.
- Wording that does not match the chosen category, especially utility templates that read like promotions.
How to write a template that passes
- 1Start from the trigger. Write down exactly what event sends this message and what the customer did to cause it. If you cannot name the customer's action, it is not a utility template.
- 2Write the fixed text first, as if there were no variables, then add placeholders only where the content genuinely changes per customer.
- 3Open and close with fixed words. "Hi {{1}}" becomes "Hello {{1}}, thank you for booking with us."
- 4Provide realistic sample values for every variable, in the same format the live system will send.
- 5Use buttons for the next step: quick replies for answers you can route on, call-to-action buttons for a link or phone number. Buttons are easier to automate on than free text.
- 6For marketing templates, include a way to stop receiving promotions, such as an opt-out quick reply, and connect it to the contact record so the opt-out is honoured everywhere.
- 7Name templates so a person can tell what they do from the list, and record which flow each one belongs to.
For a business messaging customers in both English and Arabic, each language is a separate version of the template under the same name and goes through review in its own right. Write the Arabic properly rather than machine-translating the English after approval. A clumsy translation is a quality problem even when it passes review.
Approval is not the end: quality and pausing
Once a template is live, the people receiving it keep reviewing it. When recipients block the business or report messages, Meta lowers that template's quality, and a template with consistently poor signals can be paused or disabled. Every automation that depends on it then stops sending, often without anyone on the team noticing until a customer asks why their reminder never arrived.
- Send only to people who opted in to WhatsApp messages from you, and keep a record of when and how they did.
- Keep marketing frequency low and the content relevant to what each person bought or asked about.
- Watch template quality and status in your platform, and alert a named person when a template drops or is paused.
- Have a fallback for critical utility messages, such as email or SMS, so a paused template does not mean a missed appointment.
Templates belong in the flow design, not after it
The fastest WhatsApp projects we run treat templates as part of the flow design. Each step in the flow names its trigger, whether it runs inside or outside the 24-hour window, which template it needs and in which category, and what happens when the customer replies or does not. Templates are drafted and submitted while the integration is being built, so approval runs in parallel instead of becoming the last step on the critical path.
It also makes the running cost predictable. Once every template has a category, you can see which flows bill as utility and which as marketing before the first message goes out, rather than discovering it on the first invoice.
Common questions
Most often because of formatting rather than content: a variable at the start or end of the message, variables without sample values, placeholders out of order, or too few fixed words around the variables. After that, the common causes are policy issues such as requests for sensitive information, shortened links, or wording that does not match the chosen category.
Because the content reads as promotional. A utility template must relate to a specific transaction or request the customer already made. Adding an offer, a discount or a cross-sell line makes it marketing, and it is then billed at the marketing rate. Send the promotion as a separate marketing template instead.
Not inside the 24-hour window that opens when the customer messages you. Within that window you can reply freely. Outside it, any message your business starts has to be an approved template.
Yes. If recipients block or report messages sent with it, its quality drops and Meta can pause or disable it. Any automation using that template stops sending until it is fixed, so monitor template status and keep a fallback channel for critical messages.
Each language is a separate version of the template and is reviewed separately. Write each language properly rather than translating after approval, since poor wording affects how recipients respond even when a template passes review.