Template Categories
Categories
Templates must be categorized. The category you designate at the time of template creation will be validated during template review. Templates will be rejected if there is a mismatch between the designated category and the category we determine based on template content.
Templates support the following categories:
AUTHENTICATION
Business-initiated conversations that enable businesses to authenticate users with one-time passcodes at multiple steps during the login process, such as account registration, account recovery, and integrity challenges.
MARKETING
Business-initiated conversations to market a product or service to customers, such as relevant offers to customers who have opted in. Any business-initiated conversation that does not qualify as an authentication or utility conversation would also fall under this category.
UTILITY
Business-initiated conversations relating to a transaction, including post-purchase notifications and recurring billing statements to customers who have opted in.
Templates are made up of four primary components which you define when you create a template: header, body, footer, and buttons. The components you choose for each of your templates should be based on your business needs. The only required component is the body component.
Some components support variables, whose values you can supply when using the Cloud API or On-Premises API to send the template in a template message. If your templates use variables, you must include sample variable values upon template creation.
Template Components
Templates are composed of various text, media, and interactive components, based on your business needs.
Headers
Headers are optional components that appear at the top of template messages. Headers support text, media (images, videos, documents), and locations. Templates can have only one header.
Body
Body components are text-only components and are required by all templates. Templates are limited to one body component.
Footer
Footers are optional text-only components that appear immediately after the body component. Templates are limited to a single footer component.
Buttons
Buttons are optional interactive components that perform specific actions when tapped. Templates can have up to 2 Call-to-Action buttons (phone number buttons, URL buttons, or a mix of the two) or 3 quick reply buttons.
Call-to-Action buttons cannot be mixed with Quick Reply buttons.
Phone Number Buttons
Phone button numbers call the specified business phone number when tapped by the app user.
URL Buttons
URL buttons load the specified URL in the device's default web browser when tapped by the app user.
Quick Reply Buttons
Quick reply buttons are custom text-only buttons that immediately message you with the specified text string when tapped by the app user. A common use case-case is a button that allows your customer to easily opt-out of any marketing messages.
When using the Cloud API or On-Premises API to send a template that has multiple quick reply buttons, you can designate the order in which buttons appear in the template message.
Example Requests
Seasonal Promotion
An example request to create a marketing template with the following components:
a text header with a variable and sample value
a text body with variables and sample values
a text footer
two quick-reply buttons
Limited Time Offer
An example request to create a marketing template with the following components:
an image header with a sample value
a text body with variables and sample values
a text footer
a phone number button
a URL button
Order Confirmation
An example request to create a utility template with the following components:
a document header with a sample value
a text body with variables and sample values
a phone number button
a URL button
Last updated