How to handle template rejection on the WhatsApp Business API
A rejected message template is one of the most common blockers when you start sending on the WhatsApp Business API — and one of the easiest to fix once you understand *why* Meta rejected it. A template can be knocked back for the wrong category, promotional wording in a utility template, broken variables, formatting problems, or a policy issue with the content itself. This guide walks you through reading the exact rejection reason, correcting it, and resubmitting, so your template gets approved on the next attempt. InfiQ surfaces the rejection reason in plain language and lets you edit and resubmit without touching Meta's dashboard directly.
What you'll do
When a WhatsApp template is rejected, find the exact rejection reason in InfiQ, fix the real cause — usually a category mismatch, promotional wording, a broken variable, or a policy issue — then edit and resubmit. Most templates pass on the second attempt once the right cause is addressed.Step 1 — Read the exact rejection reason (don't guess)
Meta never rejects a template without a machine reason, and the single biggest mistake is resubmitting the same template with a tiny cosmetic tweak instead of fixing the actual cause. Start by opening the template in InfiQ's Template Manager, where a rejected template is flagged in red with the rejection reason attached. Match that reason to what Meta actually checks so you fix the right thing the first time.
- INVALID_FORMAT — a variable is malformed, placeholders aren't sequential ({{1}}, {{2}}…), or the body starts/ends with a variable.
- ABUSIVE_CONTENT / policy — content that reads as spam, contains prohibited claims, or violates WhatsApp Commerce Policy.
- INCORRECT_CATEGORY — the content is promotional but was submitted as Utility (or vice versa), the most frequent reason of all.
- SCAM / THREATENING / misleading — urgency-baiting, fake offers, or content that could be read as deceptive.
- TAG_CONTENT_MISMATCH — the header/footer or sample values don't match the declared template type.
Step 2 — Fix the category mismatch (the #1 cause)
Since Meta bills per delivered message by category — marketing, utility, and authentication — the category you declare is scrutinised closely, and mislabelling a marketing message as utility is the most common rejection of all. Utility templates must relate to a specific transaction the user has already engaged in: an order confirmation, a shipping update, an appointment reminder, an OTP follow-up. The moment you add a discount code, a 'shop now' nudge, a cross-sell, or any language designed to drive a new purchase, it becomes marketing and must be submitted as such. If your template was rejected for INCORRECT_CATEGORY, decide honestly what the message is trying to do: if it informs about something the customer initiated, keep it utility and strip any promotional phrasing; if it promotes, re-submit it as marketing. Getting this right also protects your costs, because utility and authentication messages are priced differently from marketing.
Step 3 — Clean up wording, variables and formatting
Once the category is correct, tighten the content itself. Rejections here are almost always mechanical or tonal, and both are quick to correct before you resubmit.
- Give every variable a realistic sample value (e.g. {{1}} → 'Priya', {{2}} → '#INF2043') — placeholder gibberish or empty samples get rejected.
- Never open or close the body with a variable, and keep placeholders numbered in order with no gaps.
- Remove aggressive urgency and ALL-CAPS shouting ('BUY NOW!!!'), excessive emojis, and unverified claims like 'guaranteed' or '#1'.
- Check character limits — body up to 1024 characters, header text up to 60, footer up to 60 — and avoid double spaces or trailing newlines.
- Make sure any button URLs and phone numbers are real and reachable, not example.com placeholders.
Step 4 — Edit and resubmit in InfiQ
You don't need to delete the template or create a fresh one from scratch — a rejected template can be edited in place. In InfiQ's Template Manager, open the rejected template, apply your corrections to the body, category, header/footer, buttons, or sample values, and click resubmit. The template goes back into Meta's review queue and typically returns an approved or rejected status within minutes, occasionally up to 24 hours during heavy review periods. Because InfiQ sits on top of the official Cloud API as a Meta Business Partner, the review is Meta's own — InfiQ just makes the submission, the reason codes, and the resubmission loop far easier to work with than the raw Graph API.
Step 5 — Confirm approval and go live safely
When the status flips to Approved, the template is immediately usable for sends. Before you blast it to your whole list, send it to your own number first to confirm the variables render correctly and buttons behave as expected. Then ramp volume gradually rather than sending to tens of thousands on day one — new numbers and newly approved templates benefit from a warm-up, and sudden spikes can drag down your quality rating. Keep an eye on delivery and read status after going live; a template that was approved can still be paused by Meta if recipients block or report it, so relevance and opt-in quality matter as much as passing the initial review.
Frequently asked questions
Why was my WhatsApp template rejected?+
How long does a resubmitted template take to get approved?+
Can I edit a rejected template or do I have to make a new one?+
What is the difference between marketing and utility, and why does it cause rejections?+
How many times can I resubmit a template?+
Does a rejected template cost me anything?+
My template was approved before but got paused — is that the same as rejection?+
Do I need a developer to fix and resubmit a template?+
Stuck on a rejected template?
InfiQ's India-based team will read your exact rejection reason and get your template approved — book a demo or start free today.