WhatsApp template approval: categories, common rejections and how to fix them

Updated 2026-09-19 · 5 min read · By the Convo360 team

Prerequisites before creating a template

You need a connected WhatsApp Business Account (see our WhatsApp API setup guide if you haven't connected yet) and access to WhatsApp Studio inside Convo360. It also helps to know exactly which real-world event will trigger the message (an order placed, an appointment booked, a payment received), since that decides both the category and the wording you'll need.

Spend a few minutes upfront listing every message your business currently sends manually outside a live conversation, such as payment reminders, delivery updates and feedback requests, since each of these will eventually need its own approved template once you automate it. Planning the full list before you start submitting avoids discovering gaps one rejection at a time.

The three template categories

• Utility: transactional, expected messages tied to a specific action the customer took: order confirmations, appointment reminders, delivery updates, payment receipts. Generally the cheapest category and most likely to be delivered without friction.
• Marketing: promotions, offers, announcements, re-engagement messages. Requires stricter opt-in and typically costs more per message.
• Authentication: one-time passwords and verification codes only. Has a specific, restricted format and cannot contain promotional content.

Choosing the wrong category is one of the fastest ways to get rejected. A discount code sent as 'Utility' will almost always bounce back, since Meta's reviewers actively check that the category matches the actual content, not just the label you pick.

A useful rule of thumb: if the message would still make sense to send even without any discount or offer attached, a simple confirmation of something the customer already agreed to, it's Utility. If the whole point of the message is to persuade the customer to do something they haven't already committed to, it's Marketing.

Why templates actually get rejected

Building an approvable template in WhatsApp Studio

1. Go to WhatsApp Studio → Templates → Create.
2. Pick the correct category: Utility, Marketing or Authentication.
3. Write the body text, adding variable placeholders where content changes per customer (name, date, amount).
4. Fill in a realistic sample value for every variable: this is what Meta's reviewer actually reads, and vague placeholders like 'text' or 'name' are one of the fastest ways to get flagged.
5. Add buttons if needed: quick reply (e.g. 'Confirm', 'Reschedule') or call-to-action (e.g. 'Track Order' linking to a real URL).
6. Preview the rendered message exactly as a customer will see it.
7. Submit for review; approval typically returns within a few hours to a day.

A worked example: two templates, two outcomes

A clinic submits two templates on the same day. The first, filed as Utility: 'Hi {{1}}, this is a reminder for your appointment at {{2}} on {{3}}. Reply CONFIRM or RESCHEDULE.' with sample values 'Priya', '4:00 PM', '12 September': specific, transactional, matching its Utility category exactly. It's approved within two hours.

The second, also filed as Utility, reads: 'Hi {{1}}, we have a special 20% off dental cleaning this month, book now!', and despite being filed under Utility, this is clearly promotional content, so it's rejected the same day. The fix is simple: refile it under Marketing, where that kind of offer belongs, and it goes through on the next attempt.

If it gets rejected

Meta's rejection notice usually names a policy reason, though sometimes only in general terms. Common quick fixes: move promotional language out of a Utility template, add realistic sample values, or clarify vague wording. Edit the template in WhatsApp Studio and resubmit. There is no penalty for resubmitting a corrected version, though repeated policy violations across many templates can affect your number's overall messaging quality rating with Meta, so avoid resubmitting the exact same rejected wording repeatedly without changing anything.

If a rejection reason genuinely isn't clear from Meta's notice, the fastest diagnostic is to compare the rejected template against a similar one that was approved. Differences in category, tone or button setup usually point straight at the issue, faster than guessing from the policy wording alone.

Using approved templates in a flow, and what to test

Once approved, use the Send Template block in the Flow Builder to fire it from any trigger, such as a booking confirmation, a Wait/Delay drip step, or a webhook from your CRM. Map your flow's variables (customer name, date, amount) directly to the template's placeholders so each message is personalised automatically. Before relying on it, send a test to your own phone from the actual flow (not just WhatsApp Studio's preview) to confirm variables render correctly with real data, buttons work as expected, and the message arrives promptly.

It also helps to keep a running list of your approved templates and their exact purpose in one place, such as a shared note or sheet, so that as your team grows, nobody submits a near-duplicate template under a slightly different name, which just adds clutter and confusion to WhatsApp Studio over time.

Step by step

1. Choose the right categoryPick Utility for transactional messages, Marketing for promotions, or Authentication for OTPs — this decision drives most approval outcomes.
2. Write specific body textAvoid vague or generic wording; be precise about what the message is for.
3. Fill realistic sample valuesGive every variable a real-looking example, not a placeholder like 'text'.
4. Add matching buttonsMake sure any button's action genuinely matches its label.
5. Preview before submittingCheck the rendered message looks correct with your sample values filled in.
6. Submit and wait for reviewApproval typically returns within a few hours to a day.
7. Fix and resubmit if rejectedEdit the flagged issue — usually category or wording — and resubmit through WhatsApp Studio.

Example conversation

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.