Every message you send outside an active customer conversation needs a Meta-approved template. Getting templates approved on the first try saves days of back-and-forth — most rejections trace back to the same few mistakes.
If you mark a template as "Utility" but it reads like a promotion ("50% off today only!"), Meta will reject or recategorize it. Be honest about what the message is — transactional updates as Utility, promotions and offers as Marketing, login codes as Authentication.
A template that's just "Hi {{1}}, {{2}}" with no surrounding text gets rejected because Meta's reviewers (and their automated systems) can't tell what it's for. Give variables descriptive surrounding text: "Hi {{1}}, your order {{2}} has been shipped and will arrive by {{3}}."
A template starting with "{{1}}, here's your update" or ending in a bare "{{1}}" is a common rejection trigger, since it looks like it could be used to insert arbitrary/spam content. Anchor variables inside a full sentence instead.
Certain patterns — ALL CAPS urgency, excessive emojis, phrases that resemble phishing ("verify your account now") — get auto-flagged. Write templates the way you'd write a normal, professional message to a customer.
A template named "order_update" containing a discount offer is an easy, avoidable rejection. Name templates for what they actually say, using a consistent naming pattern (like "order_shipped_v2") so your team can tell templates apart at a glance later.
Templates aren't limited to plain text. You can also build templates with a header (an image, video, or document attached to the message), a footer line, and interactive buttons — quick-reply buttons, a call button, a link button, or a button that opens an in-chat form (a WhatsApp Flow) for things like appointment booking. Each of these is reviewed the same way plain-text templates are, so the same rules about honest categorization and natural-sounding copy still apply.
If your template includes an image, video, or document header, make sure the file itself is directly relevant to the message content and doesn't contain text that contradicts the declared category — a "utility" order update with a header image that's actually a discount banner is a mismatch just like mismatched body text would be. Keep header files reasonably sized and in a standard format; oversized or unusual file types are more likely to cause delivery issues even after the template itself is approved.
A quick-reply button should reflect a genuine next step ("Track my order," "Reschedule," "Yes / No") rather than a generic label unrelated to the message. If you're using a button that opens a WhatsApp Flow — for appointment booking or a short form — make sure the button text describes that action clearly, since a mismatched button label is a common source of user confusion even when the template itself gets approved.
Once a template is approved, send it to a small internal or pilot list first rather than your full contact base immediately. This catches formatting issues that only show up on real devices — a variable that renders oddly, a header image that crops unexpectedly, or wording that reads differently once real customer data fills in the variables — before it reaches your whole audience.
Templates go through Meta's automated and, occasionally, manual review process. Most straightforward templates that follow the guidelines above get approved without needing changes — the templates that get stuck in review or rejected are almost always the ones tripping one of the patterns above, not random bad luck.
Meta returns an error code with the rejection — read it before resubmitting blindly. A template manager that shows you the exact reason (like OneClickMsg's) turns a guessing game into a five-minute fix, rather than repeated blind resubmissions that each cost another review cycle.
Q: Can I edit an already-approved template? A: No — any change to the wording requires submitting it as a new template (or a new version) for review; you can't silently edit approved copy.
Q: How many templates can I have approved at once? A: There's no meaningful practical limit for most businesses — you can maintain a library of templates for different scenarios (order confirmation, shipping update, appointment reminder, promotion) and reuse each one repeatedly once approved.
Q: Do templates need to be in English? A: No — templates can be submitted in the language your customers actually use; matching your audience's language is generally better for both engagement and approval.
Q: Can a template include more than one button? A: Yes, multiple buttons are supported (within Meta's limits on button count and type per template) — just make sure each one maps to a distinct, genuine action rather than duplicating the same option.