WhatsApp Business17 min read

Why WhatsApp Templates Get Rejected in India

The main WhatsApp template rejection reasons in India are incorrect category selection, missing or unclear customer consent, promotional wording in utility…

#template approval#rejected templates#Meta policies#India

WhatsApp Template Rejection Reasons in India: A Practical Guide

The main WhatsApp template rejection reasons in India are incorrect category selection, missing or unclear customer consent, promotional wording in utility messages, invalid variables, policy-sensitive content, and low-quality messaging behaviour. Most rejected templates can be fixed by making the message more specific, matching its category, using approved variables correctly, and documenting how the recipient opted in.

WhatsApp Business Platform templates are pre-approved message formats used when a business starts a conversation or sends a message outside the 24-hour customer service window. They are different from normal replies sent within an active customer conversation.

For an NGO, school, clinic, D2C brand, agency or small business, a rejected template can delay an important workflow. This may include appointment reminders, donation receipts, order updates, payment reminders, admissions communication or customer support follow-ups.

The rejection is usually related to the template itself, the business use case, or the way recipients have been contacted. Improving only the wording may not be enough if the opt-in process or messaging practice is the real problem.

How WhatsApp Template Approval Works in India

Businesses generally use the WhatsApp Business Platform through Meta’s Cloud API or an approved Business Solution Provider. The template is submitted through the provider’s dashboard or Meta’s business tools, along with its category, language and message components.

Meta reviews the template against its business messaging policies and WhatsApp Commerce Policy. The review may consider:

  • The message wording
  • The selected category
  • The sample values for variables
  • The use of links, buttons and media
  • Whether the content is promotional, transactional or authentication-related
  • The business’s industry and use case
  • Recipient feedback and previous messaging quality

A template can initially be approved and later paused, restricted or disabled if users block the business, report messages, or mark them as unwanted. Approval is therefore not a permanent guarantee that the message can be used without limits.

The three common template categories

Meta commonly distinguishes between marketing, utility and authentication templates. Category names, review rules and available features can change, so the current options shown in your WhatsApp Business Platform account should be treated as the final reference.

Marketing templates promote a product, service, event, offer, donation campaign or business relationship. They may include discounts, new product announcements, lead-nurturing content, re-engagement messages and fundraising appeals.

Utility templates communicate information connected to a user’s existing request, transaction, account, appointment or service. Examples include order confirmations, shipping updates, appointment reminders, application status messages and payment confirmations.

Authentication templates are used for identity verification, such as one-time passwords or login codes. They have more specific formatting and content expectations because they are part of a security flow.

A common mistake is describing a marketing message as utility because utility templates may be treated differently by Meta and, in some cases, by the business’s messaging cost structure. The category should reflect the actual purpose of the message, not the category that appears most convenient.

The Most Common WhatsApp Template Rejection Reasons in India

1. The template is placed in the wrong category

A template may be rejected or recategorised when the wording does not match the selected category.

For example, this is likely to be treated as marketing:

Your order is on the way. Get 20% off your next purchase with code SAVE20.

The first sentence is utility, but the discount makes the message promotional. Combining transaction information and an offer can create category confusion.

A safer approach is to separate the messages:

  • Utility: “Your order {{1}} has been shipped and is expected to arrive on {{2}}.”
  • Marketing: “Enjoy {{1}} off your next order with code {{2}}. Shop now: {{3}}.”

The same principle applies to schools, clinics and NGOs. An appointment reminder should not include an unrelated promotional message. A donation receipt should not add a fundraising appeal in the same template unless the message is correctly submitted as marketing and the recipient’s consent covers such communication.

2. Promotional content is hidden inside a utility message

Words such as “offer”, “sale”, “limited time”, “buy now”, “best price”, “refer a friend”, “upgrade”, “exclusive” and “free” often indicate marketing intent. The problem is not that these words are always prohibited. The problem is that they can conflict with a utility category.

Examples of mixed or risky wording include:

  • Your consultation is confirmed. Buy our wellness package at a special price.
  • Your donation receipt is ready. Donate again today to help more children.
  • Your school application is received. Enrol in our paid test series now.
  • Your order is delivered. Leave a review and get a discount.

Some of these messages could be submitted as marketing if the business has the appropriate consent and the message is clearly promotional. They should not be labelled utility merely because the first sentence refers to an existing transaction.

3. The customer’s opt-in is unclear or missing

Businesses need a reasonable basis for sending WhatsApp messages to a person. Adding a phone number to a customer list, exporting contacts from another system, or assuming that an SMS opt-in automatically covers WhatsApp can create compliance and quality problems.

An opt-in should explain what the user is agreeing to receive and from whom. Depending on the use case, it may cover:

  • Order and delivery updates
  • Appointment reminders
  • School or course communication
  • Donation receipts and programme updates
  • Payment reminders
  • Promotional messages
  • Customer support replies

Promotional consent should be distinguished from essential service communication where appropriate. A person who gave a number to receive an invoice may not have agreed to receive every future offer from the business.

In India, businesses should also review their consent and notice practices in light of the Digital Personal Data Protection Act, 2023 and applicable rules when they come into force or are updated. WhatsApp template approval is not a substitute for privacy compliance. Keep records of when consent was collected, what the user saw, and how they can withdraw it.

4. The message contains prohibited or restricted content

Meta applies restrictions to categories such as regulated goods, illegal products, adult services, deceptive schemes and certain financial activities. The exact treatment depends on the business, country, product, wording and applicable policy.

India-specific businesses should be particularly careful with:

  • Loans and lending offers
  • Investment or trading claims
  • Insurance promotions
  • Gambling or betting
  • Medicines and medical treatment claims
  • Alcohol and tobacco-related products
  • Adult products or services
  • Multi-level marketing or get-rich-quick schemes
  • Political or sensitive social issue messaging
  • Products that require licences or regulated distribution

A clinic should avoid claims such as “guaranteed cure”, “permanent result” or “100% success”. A financial services business should not use a generic message that promises approval or returns. A wellness brand should avoid presenting a supplement as a guaranteed treatment.

If the business operates in a regulated sector, template approval is only one part of the review. Licensing, advertising standards, sectoral rules, consent, record keeping and customer complaint handling may also apply.

5. Variables are used incorrectly

Variables allow a business to insert values such as a customer name, order number, amount, date or tracking link. Poor variable design is one of the most preventable template rejection reasons in India.

Common problems include:

  • A variable appears at the beginning or end of the message
  • Two variables appear next to each other without clear text
  • The number of sample values does not match the variables
  • The sample values are vague or unrealistic
  • The variable is being used to hide most of the message
  • The message does not make sense when the variable is empty
  • A variable is used where a fixed label would be clearer

Weak example:

{{1}} {{2}} {{3}}

Better example:

Hello {{1}}, your appointment with {{2}} is confirmed for {{3}} at {{4}}.

The sample values should represent real usage. For example:

  • Name: “Asha”
  • Department: “Dental Clinic”
  • Date: “18 March”
  • Time: “4:30 pm”

Do not use samples such as “test”, “123”, “abc” or “value”. Reviewers need to understand the final message without guessing.

For amounts, include the currency in the fixed text where possible:

Your payment of ₹{{1}} for invoice {{2}} has been received.

The business should still check how the provider handles the rupee symbol, decimal formatting and regional language display.

6. The template is vague, misleading or difficult to understand

Templates should tell the recipient why they are receiving the message. A message such as “Important update regarding your account” is too broad if the recipient cannot identify the business, event or action involved.

Clearer wording might be:

Your application for the {{1}} programme has been received by {{2}}. We will share the next update here.

The message should not create false urgency or imply an action that has not happened. Avoid wording such as:

  • Your account will be closed today
  • Final warning: pay immediately
  • You have won a reward
  • Confirm now to avoid permanent loss

unless the business can support the claim and the content is allowed under policy. Fear-based and deceptive messages may lead to rejection or user reports.

7. Links or buttons create a policy or trust problem

A URL in a template does not automatically make it unacceptable. However, the destination should be relevant, secure and consistent with the business identity.

Check that:

  • The domain belongs to the business or an authorised service
  • The link uses HTTPS
  • The page works on a mobile phone
  • The landing page matches the message
  • The URL does not redirect to unrelated content
  • The page does not ask for unnecessary personal information
  • The link is not a disguised or suspicious short URL

A delivery update should lead to a genuine tracking page. A payment reminder should lead to a secure payment page or the organisation’s official website. An NGO donation message should use a recognised, authorised donation path and clearly identify the organisation.

Buttons should have a clear purpose. “View receipt”, “Track order”, “Book appointment” and “Pay invoice” are more understandable than vague calls to action such as “Click here” or “Do it now”.

8. The template uses language or translations poorly

India has a wide range of language preferences. A template submitted in English may not work well for users who expect Hindi, Marathi, Tamil, Bengali or another language. Poor translation can also create review issues when the translated message changes the original intent.

Do not translate word for word without checking the actual customer meaning. Pay attention to:

  • Date and time formats
  • Formal and informal language
  • Names and address fields
  • Regional scripts
  • Currency display
  • Gendered or culturally inappropriate wording
  • English words commonly used in Indian business communication
  • Transliteration, such as Hindi written in Roman script

Create separate language versions where needed. Test them on actual devices, especially when using Devanagari or other Indic scripts. A message that looks acceptable in a dashboard may wrap badly or display an unexpected character on a phone.

9. The template is too close to a previous rejected template

Changing punctuation or replacing one word may not resolve a rejection if the underlying issue remains. Repeatedly submitting near-identical templates can also make the review process more difficult.

Instead, identify the actual problem:

  • Was the category wrong?
  • Was the content promotional?
  • Was consent missing?
  • Was the industry restricted?
  • Was the call to action unclear?
  • Was the sample value incomplete?
  • Did the link create a trust concern?

Then rewrite the message around the genuine use case. Do not try to bypass review by changing the template name while keeping the same risky content.

Utility, Marketing and Authentication: Examples for Indian Businesses

Business use case Likely category Safer example Common mistake
Order confirmation Utility Your order {{1}} has been confirmed and will be processed by {{2}}. Adding a discount in the same message
Delivery update Utility Your order {{1}} is out for delivery. Track it here: {{2}} Using an unrelated tracking link
Clinic appointment Utility Reminder: your appointment with {{1}} is on {{2}} at {{3}}. Adding a package promotion
School application Utility Your application {{1}} has been received. View the next steps: {{2}} Asking for payment without context
Donation receipt Utility Thank you for your donation of ₹{{1}}. Your receipt is available here: {{2}} Treating a new fundraising appeal as a receipt
Product offer Marketing Get {{1}} off selected products until {{2}}. Shop here: {{3}} Calling it an order update
Re-engagement Marketing We have new {{1}} products that may interest you. Explore: {{2}} Sending without suitable promotional consent
Login verification Authentication Your verification code is {{1}}. Do not share this code. Adding sales copy or unnecessary links

These examples are starting points, not guarantees of approval. The business’s industry, opt-in process, account history and final content still matter.

How to Reduce Rejected Templates Before Submission

Start with the business event

Write down the event that triggers the message:

  • A customer placed an order
  • A patient booked an appointment
  • A student submitted an application
  • A donor completed a contribution
  • A user requested a login code
  • A customer agreed to receive offers

If there is no clear event or consent basis, the message may be a marketing communication rather than utility.

Write the fixed text first

Do not begin with variables. Write a complete message using realistic details, then replace only the parts that change.

Instead of:

Hi {{1}}, your {{2}} is {{3}}. {{4}}

write:

Hello Asha, your appointment at Sunrise Clinic is confirmed for 18 March at 4:30 pm. View directions here: https://example.in/map

Then convert the changing fields into variables. This makes the message easier to review and reduces accidental ambiguity.

Keep one purpose per template

A message should usually do one main job. Combining an invoice, a promotional offer, a feedback request and a referral scheme makes categorisation and user understanding harder.

Create separate templates for separate events. For example:

  1. Payment confirmation
  2. Invoice link
  3. Appointment reminder
  4. Feedback request
  5. Promotional offer

This also helps the business measure which messages are useful and which ones lead to blocks or opt-outs.

Make opt-out easy

For promotional messages, provide a practical way for recipients to stop receiving marketing communication. The exact implementation may depend on the platform setup, but the business should honour requests such as “stop”, “unsubscribe” or “do not send offers”.

Do not continue sending promotional templates to a number that has opted out. Maintain suppression records in the CRM or messaging system, and make sure future campaigns check those records.

Test the full workflow

Before requesting approval or sending at scale, test:

  • The message on Android and iPhone
  • The display of rupee amounts
  • Links and buttons
  • Regional language rendering
  • Missing or unusually long names
  • Order IDs and invoice numbers
  • Time zones and date formats
  • Delivery failure handling
  • Opt-out processing
  • The message a customer receives after replying

A clinic, school or NGO should also check whether sensitive information is being exposed in notifications. For example, a message may confirm an appointment without displaying a medical condition or other unnecessary personal detail.

What to Do When a Template Is Rejected

First, read the rejection reason in the Meta or provider dashboard. Save the submitted version and the reason so that your team does not repeat the same error.

Next, classify the problem:

  • Content issue
  • Category issue
  • Variable issue
  • Link or button issue
  • Industry or policy issue
  • Consent or messaging-quality issue

Make a meaningful revision. If the issue is promotional language, remove the promotion only if the actual message is genuinely utility. Do not turn a marketing message into a misleading utility template by deleting one offer word.

If the business believes the rejection is incorrect, use the available review or appeal process through the provider or Meta tools. Explain the business event, the recipient’s relationship with the business, the consent method and the purpose of each variable.

Avoid submitting many versions at once. That can create confusion and does not replace a clear compliance explanation.

If approved templates are being paused or message delivery is declining, inspect quality signals. Review block rates, reports, opt-outs, message frequency, audience selection and whether the content matches what users expected when they opted in.

India-Specific Compliance and Operations Checks

WhatsApp template approval and Indian legal compliance are related but separate questions. A business should review the full communication process, not only the message wording.

Privacy and consent

Under India’s Digital Personal Data Protection framework, businesses should consider notice, consent where required, purpose limitation, data minimisation, withdrawal and reasonable security safeguards. The exact obligations depend on the organisation, processing activity and applicable rules.

Do not collect more customer information than the workflow needs. A delivery update may need an order number and tracking link, not a full identity document. A school should be careful with children’s personal data and guardian communication.

Consumer communication

Marketing messages should identify the business clearly and avoid false claims. Product prices, discounts, delivery promises and availability should be accurate. If GST is included in a price or invoice communication, display it clearly according to the business’s accounting and consumer obligations.

Do not assume that a WhatsApp message replaces an invoice, tax document, medical record or legally required notice. It may be a delivery channel, while the underlying document still needs to be generated and stored through the appropriate system.

Financial and medical information

Use minimum necessary detail in message previews. A clinic can write “Your appointment is confirmed” without mentioning a sensitive diagnosis. A financial business should avoid exposing account information in a notification that may appear on a shared or locked screen.

Use secure, authenticated pages for documents, payments and account actions. A template should not ask customers to send passwords, card PINs, one-time passwords or other secret credentials in a chat.

Regional language and accessibility

If the audience includes customers from Maharashtra, Hindi-speaking regions or multiple Indian states, plan language versions rather than relying on one English template. Keep instructions clear for users who are less comfortable with digital payments, links or automated workflows.

For older customers and community programme participants, a short message with a clear contact option may work better than a long template containing several buttons and conditions.

Questions to Ask Your WhatsApp Provider or Developer

A reliable implementation should answer more than “Can you send WhatsApp messages?”

Ask:

  • Is this using the official WhatsApp Business Platform?
  • Who owns the Meta Business account and phone number?
  • Where are templates submitted and managed?
  • How are opt-ins stored and audited?
  • How are opt-outs synchronised with the CRM?
  • What happens when a message fails?
  • Can the team separate utility, marketing and authentication use cases?
  • How are user replies routed to staff?
  • How are sensitive details protected?
  • What happens if the provider account changes?

The business should retain access to its Meta assets, templates, customer data and reporting. Avoid a setup where the agency or vendor is the only party able to view or manage the account.

A developer can help with API integration, CRM connections, payment links, order systems and dashboards. However, technical integration cannot compensate for unclear consent or policy-sensitive messaging.

Frequently Asked Questions

Why was my WhatsApp utility template rejected?

The message may contain promotional content, use the wrong category, include unclear variables, or fail to explain the customer event behind the communication. Review whether the message is genuinely connected to an existing order, appointment, application, payment or request.

Can I send an offer in an order confirmation template?

Usually, it is safer to separate the order confirmation and the offer. The confirmation is generally utility, while the offer is marketing. Combining them can create category confusion and may also result in a message that the customer did not expect.

Does collecting a phone number mean I have WhatsApp consent?

No. A phone number may have been collected for an invoice, delivery, account registration or support request without permission for promotional WhatsApp messages. Explain the intended communication and keep a record of the relevant opt-in.

How many times can I resubmit a rejected template?

There is no useful strategy based on repeated submissions. Fix the underlying issue first, then submit a clear revision or use the available review process. Changing only the template name or punctuation is unlikely to resolve a policy problem.

Can an agency guarantee WhatsApp template approval?

No responsible agency should guarantee approval. The final decision depends on Meta’s policies, the business use case, the submitted content, account history and recipient feedback. An agency can improve the structure, consent process and technical setup.

Is WhatsApp template approval enough for Indian compliance?

No. Approval does not replace privacy, consumer protection, sector-specific or information-security responsibilities. The business should review consent, data handling, opt-outs, claims, sensitive information and record keeping separately.

Where to Start

List every WhatsApp use case your organisation needs, such as order updates, appointment reminders, payment confirmations, donation receipts, admissions communication or promotional campaigns. For each one, document the trigger, recipient opt-in, category, variables, link destination and opt-out method.

Then rewrite each template around one clear purpose. Remove hidden promotions, use realistic sample values, test regional language versions and review the workflow under India’s privacy and sector requirements.

If you need help connecting WhatsApp Business Platform with a website, CRM, school system, clinic workflow, donation platform or e-commerce process, talk to the Govindani Infotech team on WhatsApp; project pricing is confirmed by the team there.

Need Help With Your Digital Strategy?

Govindani Infotech helps Indian businesses and NGOs build websites, run ads, and grow online. Contact us for a free consultation.