Why WhatsApp Templates Get Rejected: 18 Reasons & Fixes (2026)

A WhatsApp message template gets rejected when it breaks one of Meta's template rules during the automated review that runs after you submit it. The most common reasons are a category mismatch (promotional content submitted as Utility or Authentication), an incorrect variable format (using {1} instead of {{1}}), missing or low-quality samples, formatting problems (extra spaces, stray line breaks, emoji-only content), and policy violations (prohibited goods, requests for sensitive data, or misleading claims).

The good news: almost every rejection is fixable in minutes. Meta usually reviews templates within 24 to 48 hours, and when a template is rejected you can edit it and resubmit, or appeal if you believe the decision was wrong. This guide lists the 18 reasons templates get rejected in 2026, gives you the exact fix for each, and ends with clear guidance on when to edit versus when to appeal.

If you are still setting up, start with our broader WhatsApp template approval tips, then come back here when something gets rejected.

Scan this table to find your rejection reason fast, then jump to the detailed fix below.

The majority of rejections come down to category and samples. Fix these first.

1. Category mismatch. Meta has three categories: Marketing, Utility, and Authentication. If you put promotional content — discounts, offers, "buy now", upsells — inside a Utility or Authentication template, it gets rejected. Utility is strictly transactional (order updates, appointment reminders, account notices). Authentication is only one-time passcodes. Fix: if your message sells anything, resubmit it as Marketing. If you want the cheaper Utility rate, strip every promotional word and keep it purely transactional.
2. Wrong variable format. WhatsApp variables must be double curly braces: {{1}}, {{2}}. Single braces {1}, square brackets [name], or percent signs all fail. Fix: replace every placeholder with sequential double-brace variables.
3. Missing or weak sample values. When you use variables, Meta asks for a sample value for each one so reviewers can see how the final message reads. Blank or nonsense samples (like "x" or "test") often trigger rejection. Fix: provide realistic samples — a real-looking name, order ID, date, or amount — so the rendered preview makes sense.

Getting the category right the first time matters because, once a template is approved, you cannot freely change its category — Meta may auto-reclassify it instead. Our approval tips guide covers category strategy in depth.

Even with correct braces, how you place variables can sink a template.

4. Variable at the very start or end of the body. A template that begins or ends with a bare variable (for example, "{{1}}, your order shipped") is frequently rejected because reviewers cannot judge the message without fixed context. Fix: wrap variables in static words on both sides — "Hi {{1}}, your order shipped."
5. Skipped or out-of-order variables. Numbering must be continuous: {{1}}, {{2}}, {{3}}. Jumping from {{1}} to {{3}} breaks the template. Fix: renumber so there are no gaps and they appear in order.
6. Too many variables relative to text. A template that is mostly variables with very little fixed copy looks like a fill-in-the-blanks spam shell. Fix: add meaningful static text so the variables sit inside a real, readable message.
7. Extra spaces and stray line breaks. Double spaces, tabs, and trailing newlines at the end of the body or between every line trigger formatting rejections. Fix: remove duplicate spaces, delete empty trailing lines, and keep spacing tidy and consistent.

Meta filters templates that look like spam or hide their destination.

8. Emoji-only or all-caps content. Messages that are mostly emoji, written in ALL CAPS, or stuffed with "!!!" read as spam. Fix: write in normal sentence case, use at most a couple of relevant emoji, and drop the shouting.
9. URL shorteners. Links using bit.ly, tinyurl, and similar shorteners are commonly rejected because they hide the real destination. Fix: use your full branded domain — for example https://yourstore.com/offer instead of a shortened link.
10. Risky dynamic URLs. If you make the entire URL a variable, or put a variable in the domain, Meta cannot verify where it leads. Fix: keep the base URL static and put the variable only in the path or query — for example https://yourstore.com/track/{{1}}.

Clean, branded links also protect your quality rating over time, because recipients trust messages whose links they can read.

These rejections are about WhatsApp's Business and Commerce policies, not formatting. They are the hardest to overturn because they reflect a genuine rule, not a typo.

11. Requesting sensitive personal data. Templates that ask the recipient to reply with an OTP, password, full card number, CVV, PAN, Aadhaar, or bank details are rejected. WhatsApp does not allow you to collect sensitive credentials through templates. Fix: remove those requests entirely; for one-time codes, use a proper Authentication template that delivers a code rather than asking for one.
12. Prohibited goods or services. Promoting categories WhatsApp bans — such as alcohol, tobacco, weapons, gambling where restricted, certain supplements, or other regulated items — will be rejected outright. Fix: do not advertise prohibited categories on WhatsApp; review Meta's Commerce Policy before submitting.
13. Misleading or exaggerated claims. "Guaranteed 100% returns", "cure for...", or fake urgency that is not real can be rejected as deceptive. Fix: make every claim truthful, specific, and verifiable, and avoid promises you cannot back up.

Authentication templates and the header, footer, and button components each have their own constraints.

14. Authentication template with extra content. Authentication templates are meant only for delivering verification codes and must follow Meta's fixed structure. Adding marketing lines, extra links, or unrelated text gets them rejected. Fix: use only the approved OTP structure with the code variable and the standard copy-code/autofill button.
15. Header, footer, or button rule breaks. A text header allows at most one variable and has a tight character limit; footers cannot contain variables; buttons have their own length and count limits, and quick-reply plus call-to-action mixing has rules. Fix: keep the header short with a single variable maximum, use plain static text in the footer, and keep button labels concise within Meta's limits.

The last cluster covers metadata and quality-of-writing rejections.

16. Duplicate template. If a template's content is effectively identical to one you already have, the new one is rejected as a duplicate. Fix: give it a distinct name and genuinely different wording, or reuse the existing approved template.
17. Wrong or unsupported language tag. The language code you select must match the body text. Tagging Hindi copy as English (or picking an unsupported locale) causes rejection. Fix: set the language code to match what you actually wrote — for example hi for Hindi, en for English.
18. Grammar, spelling, or gibberish. Templates full of typos, placeholder junk like "lorem ipsum", or incoherent text get rejected because reviewers cannot tell what the customer would receive. Fix: proofread carefully and submit real, finished copy — never a draft.

When a template is rejected, you have two paths, and choosing the right one saves hours.

1. Edit and resubmit when the rejection is your mistake. If the reason is formatting, variable format, a missing sample, a shortener, category mismatch, or any rule you clearly broke, fix the issue and resubmit. This is the fastest route — corrected templates usually clear the next 24-to-48-hour review.
2. Appeal when you believe the rejection is wrong. If your template genuinely follows the rules and you think the automated review made an error, request a review (appeal) from inside the WhatsApp Manager template screen. Appeals are for false rejections, not for arguing about a real policy you broke.

A practical rule: if you can name the rule you broke, edit and resubmit. If you cannot find any rule you broke after checking this list, appeal. Either way, keep your template names versioned (for example order_update_v2) so you can track which version was approved.

With PayPerWA you submit, track approval status, and resubmit templates straight from the dashboard — no switching to Meta's tools. See how in the features overview and the API docs.

Meta typically reviews submitted templates within 24 to 48 hours, and many clear much faster. During review the status shows as pending; after review it becomes approved or rejected, and rejected templates show a reason you can act on. There is no benefit to resubmitting the same template repeatedly while it is still pending — that does not speed it up.

To minimize round-trips, run a quick pre-submit checklist: correct category, double-brace variables in order, realistic samples, no shorteners, no sensitive-data requests, clean formatting, and proofread copy. Templates that pass this checklist almost always get approved on the first try.

Once a template is approved, you still pay per message to send it — and that is where most platforms quietly mark up the cost. PayPerWA keeps it transparent: a flat PayPerWA fee of just ₹0.20 (about $0.004) per message, plus Meta's own per-message charge, with no monthly subscription.

In India, Meta's per-message charge is around ₹0.86 for Marketing and ₹0.13 for Utility messages; other categories and countries vary — see the live per-message rate card. So a Marketing message costs Meta ₹0.86 + PayPerWA ₹0.20 = ₹1.06 all-in, and we always show those two parts separately so you know exactly what you pay.

Ready to submit, track, and send approved templates without the markup? Create your free PayPerWA account or compare the full breakdown on the pricing page.