1. Incorrect WhatsApp Template Category

One common reason for rejection is selecting a category that does not match the actual purpose of the message.

WhatsApp template categories generally include Marketing, Utility, and Authentication. A message about a completed order may qualify as Utility, while a message promoting a new product is generally Marketing.

Example of a potential mismatch

Submitted template:

“Your order has been confirmed. Shop our new arrivals today and get exclusive offers!”

The first sentence is transactional, but the second promotes products. That promotional content can make the overall template unsuitable for the Utility category.

How to fix it

• Separate transactional notifications from promotional campaigns.
• Select the category that matches the message’s actual purpose.
• Remove promotional content from templates intended for Utility use.
• Review Meta’s current category definitions before submitting.

For more context, see FlyingStars’ WhatsApp Business API Solutions.

2. Promotional Content in a Utility Template

Keep transactional messages focused on the transaction

Utility templates are intended for specific, non-promotional interactions, such as order updates, appointment reminders, or account-related notifications that meet Meta’s requirements.

Adding discounts, product recommendations, upselling language, or unrelated offers may cause a message to be classified as Marketing instead.

Example that may create a problem

“Your payment was successful. Get 20% off your next purchase with our exclusive offer!”

Better Utility example

“Your payment of ₹{{1}} for order {{2}} was received successfully. Thank you for your purchase.”

The revised message focuses on the payment rather than introducing a separate promotion.

How to fix it

Keep Utility templates relevant to the specific transaction or request. If you want to include promotional content, create a separate Marketing template and ensure you have the appropriate customer permission.

3. Vague or Misleading Message Content

Make the purpose immediately clear

A template that uses unclear language may be difficult for reviewers and recipients to understand. Messages should explain why the customer is receiving them and what action, if any, is required.

Example

“Your request has been processed. Click here to continue.”

This message does not identify the request or explain what the recipient will find at the link.

Improved example

“Your support request {{1}} has been updated. View the latest status in your support account.”

How to fix it

• Identify the transaction, service, or request.
• Explain the reason for contacting the customer.
• Use a clear and relevant call to action.
• Avoid misleading urgency or claims that cannot be substantiated.

4. Incorrect or Unclear Variables

Give every dynamic value a clear purpose

WhatsApp templates can contain variables that are replaced with customer-specific information at send time. Problems can arise when placeholders are unclear, incorrectly formatted, or used without enough context.

Example of weak wording

“Hello {{1}}, your {{2}} is ready.”

The message does not explain what the second variable represents.

Improved example

“Hello {{1}}, your order {{2}} is ready for dispatch.”

How to fix it

• Use variables only where dynamic information is required.
• Make the surrounding text explain what each value represents.
• Follow the required variable syntax.
• Provide realistic sample values when the submission workflow requests them.
• Check that your integration replaces variables correctly when sending messages.

5. Missing Context for Dynamic Content

Help reviewers understand how the message will appear

Even when variables are correctly formatted, a template can be difficult to evaluate if the submitted examples do not show what the final message will communicate.

For example, “Your {{1}} has been approved” may be unclear if the reviewer cannot tell whether the variable represents a loan, account, booking, or application.

How to fix it:Write the message so its purpose remains clear without relying entirely on dynamic values. Where requested, provide representative sample values that accurately demonstrate the intended use.

Example : “Your application {{1}} for the {{2}} service has been approved.”
Ensure the sample values reflect the actual business workflow. Do not use misleading examples to make a template appear compliant.

6. Spelling, Grammar, or Formatting Errors

Review the message as a customer would read it

Typographical errors, broken formatting, excessive punctuation, and inconsistent wording can make a template look unprofessional or unclear.

Example
“Hi {{1}}!!! Your order has been confimed… click link now!!!”

Improved example
“Hi {{1}}, your order {{2}} has been confirmed. You can review your order details using the link below.”

How to fix it

• Check spelling and grammar.
• Remove unnecessary punctuation and repeated symbols.
• Use consistent capitalization.
• Keep the message concise and readable.
• Test how the final message looks on a mobile device.

Good writing does not guarantee approval, but it improves clarity and helps avoid preventable errors.

7. Unsupported or Misleading Claims

Make sure every claim can be justified

Templates containing exaggerated promises, deceptive offers, or unsupported claims can create policy concerns.

Examples may include guaranteed financial returns, claims of instant approval when approval is not guaranteed, or statements suggesting that a customer must act immediately when no such requirement exists.

How to fix it
Use accurate wording that reflects the actual service or transaction. Explain genuine deadlines and requirements clearly, and avoid claims that cannot be verified.

For example, replace “Your loan is guaranteed” with “Your loan application status has been updated,” if that accurately describes the event.

The exact acceptability of a message depends on its content, context, and applicable policies.

8. Unclear or Suspicious Links

Ensure links are relevant and trustworthy

Templates that contain unexpected links, misleading destinations, or URLs unrelated to the message may raise concerns.

Example

“Your delivery is delayed. Claim your compensation here: [unrelated link]”

The destination does not clearly match the stated purpose.

How to fix it

• Use links that lead to relevant business pages or customer account workflows.
• Make the destination consistent with the message.
• Avoid disguising the real purpose of a link.
• Test URLs before submission.
• Use approved domain and link practices relevant to your WhatsApp setup.

For a shipping notification, the link should lead to a relevant tracking or order-status page, not an unrelated promotional destination.

9. Inappropriate or Non-Compliant Content

Review the message against applicable policies

A template may be rejected if its content promotes prohibited activities, violates applicable commerce or messaging policies, or otherwise conflicts with Meta’s requirements.

Approval may also depend on the industry, product, service, and specific claims used in the message.

How to fix it

Review the relevant WhatsApp Business Messaging Policy and any applicable commerce or industry-specific restrictions. Remove prohibited or misleading content, and do not attempt to bypass review by disguising the message’s purpose.

If the use case is restricted, changing a few words may not resolve the underlying problem.

10. Excessive or Unnecessary Promotional Language

Keep the message aligned with its declared purpose

Marketing templates can contain promotional content, but they should still accurately represent the offer and comply with applicable policies. Utility templates should not be used to disguise marketing campaigns.

Example of a mixed-purpose message

“Your appointment is confirmed. Buy our premium package now and save 30%!”

The first sentence communicates an appointment update; the second introduces an offer.

How to fix it

Use separate templates for separate purposes.

• Use a Utility template for an eligible appointment confirmation.
• Use a Marketing template for a promotional offer.
• Ensure that marketing messages follow the applicable consent and messaging requirements.

Separating these messages can make the purpose of each template easier to understand.

11. Template Structure or Button Configuration Problems

Check every component, not just the message text

A template can contain a body, header, footer, buttons, and dynamic variables, depending on its design. Problems may arise from unsupported component combinations, invalid button settings, or mismatches between the submitted template and the message sent through the API.

How to fix it

• Confirm that the selected format supports your intended components.
• Check button labels, destinations, and configuration.
• Validate variable positions and sample values.
• Ensure your API integration uses the approved template structure.
• Check current Meta documentation for component-specific requirements.

If a template is approved but sending fails, investigate the API request and configuration as well. An approval issue and a message-delivery issue are not necessarily the same problem.

12. Repeated Resubmissions Without Fixing the Root Cause

Change the underlying issue before trying again

Resubmitting the same template with minor cosmetic edits may not resolve the reason for rejection. Repeated attempts can also delay the launch of a campaign or workflow.

How to fix it

• Read the rejection reason carefully.
• Identify the specific wording, category, variable, link, or policy issue.
• Rewrite the affected part of the template.
• Confirm that the revised category matches its purpose.
• Review the entire message, not just the changed sentence.
• Resubmit through the supported workflow and monitor the status.

If the reason remains unclear, consult the relevant WhatsApp Manager information, API error details, or available support channels rather than guessing at the cause.