The Template That Kept Getting Rejected
A retail client came to us with a template they'd submitted four times. Meta kept rejecting it. Their message: "Your order is ready for pickup. Click here to view order details."
Standard. Clean. Genuinely useful. Rejected four times.
The issue wasn't the content โ it was that "Click here" as a call-to-action phrase triggers a flag in Meta's automated review system. Change it to "View your order details" and the same template clears in under 24 hours.
That's the kind of thing that's genuinely annoying when you discover it after four rejections. It's also entirely preventable if you know the pattern.
How Meta Reviews Templates
WhatsApp Business API templates go through two layers of review: automated policy checks (immediate) and a human review queue for anything the automation flags or approves (1-24 hours in most cases, sometimes longer during high-volume periods).
The automated system is checking against WhatsApp's commerce policy and business messaging guidelines. It's pattern-matching against specific language, structure, and category assignments. The human review is looking at whether the overall message fits the stated category and has a clear, legitimate business purpose.
Understanding this two-layer structure explains why small phrasing changes can flip a rejection to an approval โ the automated patterns are specific, not contextual.
The Most Common Rejection Reasons (And How to Avoid Them)
Promotional content in a non-promotional category.
This is the most frequent issue we see across AutoChat accounts. Template categories matter: MARKETING templates are for promotional content; UTILITY templates are for transactional messages; AUTHENTICATION templates are for OTP flows.
When you submit a message like "Your order is confirmed! While you wait, check out our new arrivals" as a UTILITY template, it will be rejected โ not because it's bad, but because the promotional element doesn't match the category. Either remove the promotional content (if the message should be UTILITY) or submit it as MARKETING.
The category mismatch is often unintentional โ businesses submit what seems like a service update but include a single cross-sell sentence that moves it into MARKETING territory.
Vague or missing call-to-action buttons.
Buttons in templates (Quick Reply or Call-to-Action type) get reviewed separately from the body text. Common rejections:
"Click here" โ flagged as generic. Use specific action descriptions: "Track my shipment", "Confirm appointment", "View invoice".
Buttons that don't match the message content โ a template about delivery confirmation shouldn't have a "Learn more about our products" button. Consistency between body and CTA is checked.
Buttons with promotional text in utility templates โ "Claim your offer" as a button on a UTILITY template will get the whole template rejected.
Variables that aren't bounded or explained.
Template variables ({{1}}, {{2}}, etc.) need to be identifiable from context. A template that's just "Hi {{1}}, your {{2}} is {{3}} and {{4}}" will be rejected because the reviewer can't determine what's being substituted or whether it could be used to send harmful content.
Best practice: enough body text that the variables are obviously defined by context. "Your order #{{1}} from {{2}} has been dispatched and will arrive by {{3}}" โ each variable is clear from the surrounding content.
Language that reads as promotional in a utility context.
Certain phrases consistently trigger review flags regardless of category: "Exclusive", "Limited time", "Don't miss", "Act now", "Free", "Win", "Offer expires". If your utility or authentication template includes these words, expect manual review at minimum and potential rejection.
For legitimate promotional templates in the MARKETING category, these phrases are generally fine โ but even there, templates that read as high-pressure or spam-like take longer to approve.
The Category Decision: MARKETING vs. UTILITY
This is where many businesses get stuck. The rule Meta applies:
**UTILITY:** Sends information about a specific transaction or action the customer has already taken or requested. Order confirmations, appointment reminders, payment receipts, delivery notifications, account verification, OTP codes.
**MARKETING:** Anything that promotes products, services, or the business. Promotional offers, product launches, seasonal campaigns, abandoned cart nudges, re-engagement messages.
The edge case that trips people up: appointment reminders that include a "while you're thinking about us" promotional element. Meta reads this as MARKETING even if the primary purpose is a reminder. Keep utility messages clean โ one purpose per template.
Pricing difference matters too: UTILITY conversations cost significantly less than MARKETING conversations on the WhatsApp API. Getting the category right isn't just about approval โ it affects what you pay per message.
What "Sample Content" for Variables Should Look Like
When you submit a template with variables, Meta requires sample values for each variable. These samples are used to evaluate whether the fully rendered message complies with policy.
The samples should be representative of what you'll actually send. If variable {{1}} is a customer name, your sample should be "Priya" or "Rahul" โ not "CUSTOMER_NAME" in all caps. Samples that look like placeholder text (TEST_VALUE, VARIABLE_1, etc.) slow down review and sometimes trigger rejection for insufficient context.
For templates with document or media headers (PDF attachments, images), the sample media file should actually represent what you'll send. A placeholder image with "sample" written across it is fine; an unrelated stock photo may raise questions.
The Approval Timeline (Realistic Expectations)
Standard first-time template submissions: 1-24 hours for most cases. Meta's target is under 24 hours for straightforward templates.
Templates that trigger manual review (anything with promotional language, templates for financial services, healthcare, or other regulated categories): 24-72 hours, sometimes longer during Meta's high-volume periods.
Rejection and resubmission: the clock resets on each submission. A template rejected three times and resubmitted is not deprioritized โ each submission is reviewed independently.
We're still working out the pattern for templates that clear automated review but sit in manual queue for 3+ days. Our current working theory is that category-ambiguous templates (genuine utility messages that include light promotional elements) land in a slower queue. The fix is to separate them: one pure-utility template, one separate marketing template, submitted in different categories.
Building a Template Library That Minimises Rejection
The approach we recommend to AutoChat clients building out their template library:
Start with your highest-volume use cases and submit them one at a time until you understand what sails through and what gets flagged. Don't submit 20 templates simultaneously before you've validated your approach โ a pattern of rejections can trigger additional scrutiny.
Separate utility and marketing content rigorously from the start, even if the template could theoretically serve both purposes. The small extra effort in content creation pays off in faster approvals and lower per-message costs.
For any template involving sensitive categories โ health, finance, legal services โ add a line that makes the legitimate business purpose explicit. "As your registered account holder, here is your monthly statement summary" is more clearly utility than "Your statement is ready."
[AutoChat handles template submission and management as part of the platform](https://autochat.in) โ including category guidance before submission to reduce rejections. If you're building a WhatsApp business messaging setup from scratch and want to avoid the trial-and-error phase, [our onboarding process](https://autochat.in/contact) covers template strategy as a specific step.
For reputation-sensitive businesses where customer communication quality matters: [RatingE integrates with WhatsApp outreach](https://ratinge.com) to manage review request sequences โ and those templates have their own approval requirements worth getting right.