WhatsApp template approval process: common rejections and how to fix them

A WhatsApp message template is a pre-reviewed message format on official Cloud API. You need one whenever you start a conversation outside the customer-care window, or when you send a structured, billable notification at scale. Free-form chat inside an open window is different. Templates are how businesses start chats on the WhatsApp Business Platform without turning the app into an unreviewed bulk inbox.

Meta reviews templates because the channel is personal. Approval is the filter against unsolicited blasts, phishing-shaped links, and copy that does not match the category you claimed. It is mandatory on Cloud API. Skipping review with a WhatsApp Web scraper is a ban risk, not a shortcut.

WatsBerry is a WhatsApp Marketing and Automation platform and a Meta Verified Technical Provider. You create or import templates in the workspace, submit them on your WABA, then send from campaigns, Shopify recovery, and order alerts. Replies land in Team Inbox. This page is the approval and rejection companion to the message templates guide and the shorter templates without the headaches overview.

We will not invent an approval-rate percentage, a “#1” rank, or a guaranteed minute count. Meta reviews the copy. WatsBerry surfaces the status.

Meta currently groups business-initiated templates into three categories. The label you pick is both a policy claim and a billing band. Filing the wrong category is one of the most common rejections, and Meta can later recategorise or restrict a template that does not match.

India rate and policy context: marketing vs utility in India. Live rupee rates sit on Meta’s WhatsApp pricing. WatsBerry’s 0% markup model (Meta per-message vs platform fee, 0% WhatsApp marketing markup) is on 0% markup pricing.

Authentication is the strictest: short parameters, a copy-code or one-tap button, and no URLs, media, or emoji in the content. If the job is “here is 15% off,” that is marketing, even if you mention an OTP-looking code.

Category mismatch is not a formatting typo. Reviewers (and the automated check) read the purpose. A shipping update that ends with “use code FESTIVE20” is no longer a clean utility template.

The approval path is the same whether you start in WatsBerry or in Meta Business Manager / WhatsApp Manager. Status always lives on the WABA.

1. Draft the template. In WatsBerry, open Templates, create a template, and fill header (optional), body, footer (optional), and buttons. Or compose the same components in WhatsApp Manager.
2. Choose category, language, and samples. Language must match the body. Samples must look like real {{1}} values (a first name, an order id, a checkout URL), not xxx or leftover [NAME].
3. Submit to Meta. WatsBerry sends the template on official Cloud API. You are not posting to an unofficial bulk API.
4. Automated check. Meta’s system screens format, policy, and category fit. Many clean templates never leave this step.
5. Possible manual review. Flagged copy can wait for a person. Do not hammer resubmit while status is still pending.
6. Approved or rejected. Approved (active) templates can send. Rejected templates cannot. Later, quality feedback can pause or disable an already-approved template.
7. Sync status in WatsBerry. Use sync / import so campaigns, recovery, and alerts see Meta’s current state, not a stale draft.

Quick replies from an approved template still need a human or bot on the other side. That is Team Inbox, not a second personal phone.

Buying context if you are still choosing software: best WhatsApp marketing software in India 2026.

Clean templates often clear in minutes. If the copy, category, or links look risky, review can take longer.

Meta’s developer documentation has described an in-review state that can last up to 24 hours. That is Meta’s published guidance as of this writing, not a WatsBerry service clock, and not a promise that every template returns in 15 minutes.

What to do while you wait:

• Leave pending templates pending. Duplicate-spamming the same body slows you down and can look like abuse.
• Prepare samples and the campaign audience. Do not schedule a send against a rejected name.
• If status is stuck, sync from WatsBerry, then check WhatsApp Manager. The workspace reads Meta; it does not invent a second review queue.

We do not publish an invented “approval rate.” Your copy, category, opt-in quality, and WABA health decide the outcome.

These are review-time problems (the template never becomes sendable) plus one after-approval quality pause. Send-time issues such as messaging-limit caps or a recipient on an old WhatsApp version are not the same as Meta rejecting the template. Do not treat a failed broadcast as a template-format bug.

Use numbered placeholders in the {{1}} form. Square brackets like [NAME] are not Meta variables.

1. Spammy tone, ALL CAPS, and excessive punctuation

Reviewers (and filters) treat shouty urgency as low-quality marketing, even when the category is correctly set to marketing.

Rejected: FLASH SALE!!! LAST 2 HOURS ONLY!!! BUY NOW BUY NOW OR LOSE 70% FOREVER!!!

Better: Hi {{1}}, the extra 15% off {{2}} ends tonight. Shop with code {{3}} if you still want it.

Fix: Write like the storefront. Title case, one exclamation mark at most, no fake scarcity. Marketing is allowed. Shouting is not a strategy.

2. Missing or wrong variables

Meta expects positional placeholders {{1}}, {{2}} in order. [NAME], {{name}}, {{1}}{{2}} jammed together, a gap ({{1}} then {{3}}), or a body that starts or ends on a bare variable, are common format failures. Samples must match the placeholders.

Rejected: Hello [NAME], your order [ORDER_ID] is packed. Pay here: bit.ly/pay1

Better: Hi {{1}}, order {{2}} is packed and ready for pickup. Pay at {{3}}. with samples such as Ananya, WB-1842, and a full https:// checkout URL.

Fix: Number variables in sequence. Put words before and after each placeholder. Give real sample values at submit time. A fully static utility line with no variable can still be valid. Do not add fake placeholders just to “look personalised.”

3. Shortened or suspicious URLs

URL shorteners, cloaked redirects, and domains that do not match the business are phishing-shaped.

Rejected: Track it: http://bit.ly/trk99 or wa.me/9198xxxxxxx

Better: Track shipment {{1}} at https://shop.yourbrand.in/orders/{{2}} on a URL button, or the same full HTTPS link in the body.

Fix: Use HTTPS on a domain you actually operate. Skip bit.ly, tinyurl, and random redirectors. Do not put a wa.me chat link inside a template CTA when a phone button or a shop URL is the real action.

4. Unclear purpose or a vague CTA

If a reviewer cannot tell what the message is about or what the customer should do, the template looks like a generic blast.

Rejected: Hi {{1}}, {{2}} needs your attention. Reply YES or NO.

Better: Hi {{1}}, your fitting at {{2}} on {{3}} is still on our calendar. Reply CONFIRM or RESCHEDULE.

Fix: Name the object (order, slot, invoice). Name the action. Quick replies should be the actual next step, then a human in Team Inbox should honour them.

5. Asking for sensitive data

Do not collect passwords, full card numbers, CVV, OTP-for-your-bank, or Aadhaar in a template. That fails policy and trains customers to get phished.

Rejected: Reply with your 16-digit card number and CVV so we can complete payment.

Better: Invoice {{1}} of ₹{{2}} is due. Pay on this Razorpay link: {{3}}. (marketing or utility depending on context; never ask for the raw card.)

Fix: Send people to a hosted payment page. Partial identifiers (last four digits of an order, not the PAN) are the most you should echo back. Payment rails: Razorpay WhatsApp payment link.

6. Category mismatch (marketing filed as utility)

This is the rejection Indian D2C teams hit most often during festive weeks.

Rejected (filed as utility): Your cart misses you. Unlock 25% off with code HOLI25. Shop now.

Better (filed as marketing): Hi {{1}}, your {{2}} is still in the bag. Checkout with {{3}} if you want the extra 10% we set aside for you.

Better utility (only if it is a real order update): Hi {{1}}, order {{2}} shipped via {{3}}. Tracking: {{4}}. with no coupon tacked on.

Fix: If the reason for the ping is an offer, it is marketing. Budget the marketing band. Do not “save” utility rates by lying about the job. Details: marketing vs utility.

7. Formatting, length, and readability

Bodies that are a single wall of text, extra blank lines, tabs, or long runs of spaces get format rejects. Extremely long copy is hard to read on a phone and easier for filters to treat as spam.

Rejected: A 1,200-character paragraph with double spaces, a header that repeats the entire offer, and four stacked URL buttons that all say “Click”.

Better: Short paragraphs, one job, a body under Meta’s component limits (the body cap is 1,024 characters), one primary URL or phone button with a clear label.

Fix: Proofread. Cut the second offer. Use a line break between the greeting and the action. Do not pad with decorative unicode.

8. Language and locale mismatch

The language you select at submit time must match the body. An “English” template written only in Hindi, or a mixed Hinglish block with no clear primary language, is a frequent fail. Locale also matters for examples: do not paste UPI lines onto a UAE number.

Rejected: Language set to English. Body: Namaste {{1}} ji aaj ka flash deal sirf 2 ghante ke liye!!!

Better: Set language to the language you actually wrote. Keep one primary language in the body. If you serve Hindi and English, submit two templates.

Fix: Match the dropdown to the copy. Translate fully. Do not mix scripts inside one body unless that is truly how you write and the selected language still fits.

9. Policy and prohibited content

Gambling and raffle-shaped “you won” copy, get-rich schemes, certain supplements, adult content, and other Commerce Policy blocks will not approve on Cloud API. Fake official-looking “WhatsApp will ban you unless you click” scams fail as well.

Rejected: You are selected for a lucky draw. Pay ₹99 to claim iPhone.

Better: Do not send that template. If the real job is a legitimate, permitted product restock, write a plain marketing body with a shop URL and an honest category.

Fix: Read WhatsApp’s Commerce Policy and Business Policy before you submit. Software cannot launder a banned vertical.

10. Quality pause after approval (blocks and reports)

This is not a first-submit rejection. The template was approved, you sent it, then too many people blocked, reported, or ignored it. Meta can mark the template low quality, pause it, or later disable it. A green phone quality score does not save a red template.

What it looks like: Status moves from active to paused or disabled. Sends using that name fail until Meta lifts the pause.

Fix, then recover:

• Stop blasting the paused name. Fix opt-in quality (DPDP-compliant opt-ins).
• Honour STOP. Shrink the audience to people who recently engaged.
• Rewrite if the body was baity. If the template is locked, create a new template with clearer purpose and a smaller first send.
• Number-level limits and quality: quality rating and messaging limits.

WatsBerry cannot override a Meta pause. The workspace can show the status and keep you on official Cloud API while you repair list hygiene.

Run this list before you hit submit. It is cheaper than a reject-and-rewrite loop.

• Category is honest: Marketing, Utility, or Authentication, and the body matches.
• Language dropdown matches the body. One primary language.
• Variables use {{1}}, {{2}} in order. No [NAME], no gaps, no adjacent placeholders.
• Samples are realistic (name, order id, HTTPS URL), not test / xxx.
• URLs are full HTTPS on a domain you operate. No shorteners.
• Purpose and CTA are obvious in one read on a phone.
• No passwords, full card numbers, CVV, or other sensitive capture.
• Tone is conversational. No ALL CAPS walls, no stacked exclamation marks.
• Length and spacing are clean. Body within Meta’s component limits.
• Authentication templates have no URL, media, or emoji in the body.
• Display name / brand in the copy matches the WABA.
• You are not submitting a duplicate of an already-approved body under a new name unless Meta’s duplicate rule allows it (auth is the usual exception).

Starter drafts in WatsBerry Templates can save typing. They are starting copy, not a shortcut around Meta review, and not a “100+ already-approved library.” Every name still goes through this checklist.

1. Read the reason. Meta returns a category of problem (format, policy, category mismatch, and similar). Fix that problem. Do not only rename the template.
2. Edit if the draft is still open. Some rejected names stay editable. Change the body, samples, buttons, or category, then resubmit.
3. Create a new template if it is locked. Approved copy is locked. Many submitted names are locked too. Duplicate the idea under a new name with the corrected text. Do not keep a graveyard of identical rejects.
4. Resubmit once. Then wait. Rapid identical resubmits do not jump the queue.
5. Sync in WatsBerry so campaigns do not keep targeting a rejected name.
6. If the same policy reject repeats, the vertical or the claim may be the issue, not the comma. Recheck Commerce Policy rather than opening a second unofficial number.

Anatomy of components if the reject was structural: WhatsApp message templates guide. Workspace overview: templates without the headaches.

WatsBerry is WhatsApp marketing and automation first: official Cloud API, approved templates, campaigns, and Team Inbox, with Omni Channel extras around that core. You manage templates in the product (create, submit, sync). You still pay Meta’s live template rates when messages deliver, plus the WatsBerry plan, with 0% markup on WhatsApp marketing. See 0% markup and pricing.

If you are comparing stacks, start with best WhatsApp marketing software in India 2026. We will not invent a #1 badge.

Ready to create templates on a Meta Verified Technical Provider workspace? Join the waitlist for invite-only beta (14-day free plan after invite; Meta fees still apply). Then read features and the templates guide.

40 WhatsApp template examples for Indian businesses (marketing, utility and authentication).