WhatsApp Business API
Tips to Avoid WhatsApp Template Rejection: A Practical Guide
A rejected WhatsApp template blocks your campaigns and slows down automations. Here are the rules to follow and mistakes to avoid for fast approval.
In this article Why WhatsApp Templates Get Rejected and How to Avoid It +
Why WhatsApp Templates Get Rejected and How to Avoid It
In short: a WhatsApp template is rejected when it violates Meta's policies on content, format or category. To avoid rejection you must meet four core criteria: choose the correct category among Marketing, Utility and Authentication; avoid promotional language in Utility templates; never use ambiguous or uncontextualised variables such as {{1}} without a real example value; and never include shortened links or unverified URLs. Meta evaluates every template through an automated system that analyses tone, structure and consistency between the declared category and the actual content. Marketing templates have broader margins but must still comply with anti-spam rules. Utility templates, used for order confirmations, shipping updates and transactional notifications, cannot contain commercial offers. Following these rules drastically reduces review times and lets you activate automations without interruptions.
The Kuba Labs platform manages template sending via WhatsApp Business API and supports merchants in structuring messages correctly before submission to Meta. This means you can build the template directly inside the Kuba interface, verify compliance with Meta policies and submit it for approval without manually accessing Meta Business Manager.
Understanding the causes of rejection is not just a technical matter: every rejected template delays campaigns, blocks automated flows and requires a new review cycle that can take anywhere from a few hours to several days. Investing time in structuring the template correctly before submission is always more efficient than correcting it after rejection.
What Are the WhatsApp Template Categories and How Do You Choose the Right One?
Meta classifies templates into three main categories: Marketing, Utility and Authentication. Choosing the wrong category is one of the most frequent causes of rejection, especially for ecommerce merchants who tend to use Utility templates for messages that contain promotional elements.
Marketing templates include promotions, offers, new product announcements and re-engagement messages. They can contain commercial CTAs, discounts and links to landing pages. Utility templates cover transactional communications: order confirmation, shipping update, return notification, appointment reminder. They must not contain offers or sales-oriented persuasive language. Authentication templates are used exclusively for OTPs and verification codes.
A typical mistake is adding a phrase like 'Enjoy 10% off your next order' at the end of a shipping confirmation inside a Utility template. This hybrid is almost always rejected. If you want to add a commercial incentive, you must create a separate Marketing template and send it at a distinct moment.
- Marketing: promotions, offers, re-engagement, product announcements
- Utility: order confirmations, shipping updates, return notifications, reminders
- Authentication: OTPs, verification codes, secure login
- Practical rule: if the message sells or persuades, it is Marketing; if it informs about an action already taken, it is Utility
How Should You Structure Variables in Templates to Avoid Rejection?
Dynamic variables in WhatsApp templates use the syntax {{1}}, {{2}}, {{3}} and so on. Meta requires that every variable be accompanied by a concrete example at the time of submission. If you submit a template with {{1}} without specifying a sample value such as 'John Smith' or 'Order #12345', Meta's automated system rejects it because it cannot evaluate the content context.
A second frequent issue involves variables that are too generic or potentially abusable. A variable that could contain any text, including links or unverified content, is treated with suspicion. For this reason it is good practice to limit variables to structured and predictable data: customer name, order number, delivery date, amount, specific discount code.
Avoid building templates where the entire main sentence is a variable. For example, a template like 'Hello {{1}}, {{2}}' with a second variable that could contain any message is almost always rejected. The fixed text of the template must be sufficient to communicate the context, with variables only completing the personalised information.
- Always provide a real example for every variable at submission time
- Use variables only for structured data: name, order number, date, amount
- Do not build templates where the main message is entirely a variable
- Avoid variables that could contain unverified URLs or free-form text
Which Words and Phrases Increase the Risk of Rejection?
Meta uses a language analysis system that identifies patterns associated with spam, phishing and deceptive content. Certain words and syntactic constructions significantly increase the risk of rejection, even in Marketing category templates where promotional language is permitted.
Phrases that promise easy earnings, extreme artificial urgency or absolute guarantees are among the riskiest. Concrete examples to avoid: 'Earn money now', 'Offer valid only for you', 'Click now or lose everything', '100% guaranteed', 'Free with no conditions'. Excessive use of capital letters, multiple exclamation marks and aggressive emojis such as repeated money symbols can also trigger the automated filters.
For Utility templates, the risk increases with any phrase that sounds like a purchase invitation. Even an apparently neutral formulation such as 'Discover more similar products' at the end of a shipping notification can be interpreted as undeclared promotional content. The practical rule is: if you are unsure about the category, choose Marketing and structure the template accordingly.
- Avoid: 'Earn money now', 'Only for you', 'Click now or lose out'
- Avoid: excessive capitals, multiple exclamation marks, repeated money emojis
- In Utility templates: no purchase invitations, no links to related products
- Prefer direct, informative language free of hyperbole
How Long Does Approval Take and How Can You Speed It Up?
Meta states that template review generally happens within 24 hours, but in practice timelines vary significantly. Simple templates with clear text, well-documented variables and the correct category are often approved within a few hours. Templates with borderline content, ambiguous variables or unusual structures can take 2 to 3 days or be placed in manual review.
To speed up approval, the most effective strategy is preventing errors before submission. Check that the category is correct, that every variable has an example, that links point to verified domains and that the tone is consistent with the declared category. A rejected template resubmitted without substantial changes tends to be rejected again just as quickly.
Another factor that influences timelines is the reputation of the WhatsApp Business account. Accounts with high phone number quality, indicated by a green rating in Meta Business Manager, and a low rate of user reports tend to receive faster approvals. Maintaining high number quality by avoiding unsegmented mass sends is therefore an indirect but effective strategy for speeding up future approvals.
What Should You Do When a Template Is Rejected?
When Meta rejects a template, it provides an error code and a generic reason. The most common reasons are: 'Content violates WhatsApp Commerce Policy', 'Incorrect category', 'Variable parameters are not defined'. Reading the error code carefully is the first step: each code corresponds to a specific category of problem and indicates where to focus your changes.
Do not resubmit the template without modifications. Even if the reason seems vague, Meta has identified a specific problem. Analyse the template section by section: body text, buttons, variables, category. If the problem is the category, change it and verify that the content is consistent with the new category. If the problem is the variables, add more specific examples and reduce ambiguity.
In some cases the fastest solution is to rewrite the template from scratch with a more conservative approach, removing any borderline element. A simpler and more direct template gets approved faster than an elaborate one with many variables and buttons. Once the base template is approved, you can create more elaborate versions with greater confidence about the rules applicable to your specific case.
- Read the specific error code before changing anything
- Do not resubmit without substantial modifications
- Check category, variables, links and tone in sequence
- If the problem persists, rewrite the template from scratch with a conservative approach
How Does Kuba Labs Simplify Template Management and Approval?
Kuba Labs integrates the WhatsApp Business API and provides an interface to create, manage and send templates directly from the platform, without having to manually access Meta Business Manager for every operation. Ecommerce merchants can build templates for order confirmations, shipping updates, abandoned cart recovery and promotional campaigns, with a real-time preview of the final message.
The platform is structured to guide merchants in choosing the correct category and filling in variable examples, reducing the most common errors that cause rejection. Meta and WhatsApp conversation costs are included in the Kuba subscription, which starts from Tier 0 at 9 euros per month, eliminating the need to manage conversation billing with Meta separately.
For merchants generating significant volumes, Kuba applies a model based on approximately 3% of revenue attributed to orders generated through the platform. This means the cost grows proportionally to the results achieved, with no high fixed costs in the early stages. Centralised template management, combined with automated ecommerce flows, helps maintain high message quality and reduces the risk of rejections that would block critical automations such as post-purchase notifications.