Engati Product Docs

⌘K
Engati - User Guide
Getting started with Engati
Registration
Login
Forgot Password
Navigation
Creating your first bot
Building your bot
Harnessing conversational intelligence
Deploying the bot
Simplified Broadcast
Tracking & Analytics
Activating Live Chat
Managing your account
Engati for Shopify - What’s in it for you?
Engati for WooCommerce - Onboarding and Deployment
Engati APIs
What's New?
Docs powered by
Archbee
Engati - User Guide
...
Simplified Broadcast
Message Templates

Restrictions for WA template message

1min

To avoid abuse and spam attacks, WhatsApp recommends following some of the instructions in their WhatsApp template message approval process. Here are a few possible causes for why Meta will reject templates.

  • The goal of the template is not precise, clear, or well-written. Hi, {{1}} {{2}} I'm Thankful. is ambiguous and it's unclear how it would be utilised, and what the placeholder values mean.
  • The placeholders inside a template are not ordered sequentially. For example, the placeholder {{3}} is missing from the template, but {{1}}, {{2}}, and {{4}} are all present.
  • The placeholders for the template cannot be placed close to one another, as {{1}}{{2}}.
  • Submissions for templates with Media headers (video, picture, document) must also provide a sample.
  • The content of the template is similar to the other existing templates.
  • A placeholder cannot begin or end a template body.
  • The \n newline character is not allowed in the template body.
  • If the template contains messages that threaten to prosecute a user or are abusive and threatening in nature.
  • Emojis as well as the \n newline character are not allowed in the template footer.
  • Emojis, asterisks, formatting markup, and the \n newline character are not allowed in the text header of the template.



Updated 01 Mar 2023
Did this page help you?
PREVIOUS
Best practices for WA template message
NEXT
External Broadcast API
Docs powered by
Archbee
Docs powered by
Archbee