Template Messages Management

How to use the Template Management tool for the WhatsApp Business API in the 360 Client Hub.

WhatsApp API Template Management Functions

The Template Management UI in the 360 Client Hub supports both text and media templates and has the following functions:

  • Create and preview new template messages

  • Monitor current approval status of all your templates

  • Copy and Delete templates

  • Add different template Languages

Access the Message Template Window

Every account has their own set of Message Templates. To access your Message Templates, find the WABA Number you would like to add a Message Template to, and click on the Manage Templates button.

Template UI Overview

This is the Template Management home page where you can get an overview of all Templates under your number.

  • Delete Template

  • Replicate Template. Useful for creating variants of a similar template

  • Add different language to a template

Facebook's Template Verification Process for the WhatsApp API

Template messages must be submitted to Facebook for review before they are available to use. The status of this review can be seen by the color of the template language. Please review our tips on Template Messaging before submitting any templates for review.

Draft
Pending
Approved
Rejected
Draft

Templates with a gray background are in draft mode and have not been submitted for review by Facebook yet.

Pending

Pending Templates have a yellow background. Facebook is verifying the template request. Please wait until more information is given by Facebook.

Approved

Your Template has been approved by Facebook and may be used to send Template Messages to your clients.

Rejected

This Template has been rejected. Please review our Template Messaging docs for help with Template Message approval.

Create a WhatsApp Message Template

To create a Message Template, click on the blue Add Template button in the home page.

When creating your template, you will need to include the following information:

  • Template Name

    • Name can only contain lowercase alphanumeric characters and underscores ( _ )

  • Template Category

  • Template Language

    • Language that the template is written in

  • Template Type

    • Standard (text only) or Media Template

Creating Standard (text only) Templates:

Standard Message Templates only have a BODY section. In order to add a variable, insert {{#}} at the given position, where # represents the variable index, which needs to start at {{1}}

Preview feature with variable insertion

Creating Media Templates

The Media Templates have more building blocks and features. It consists of the following building blocks:

Header
Body
Footer
Button
Header

The Header is optional and serves as the title or header of your template. It supports the following:

  • Text

  • Image

  • Document

  • Video

Body

The Body should contain the most important text of your template. Only text is supported.

Footer

The Footer only supports text and can be used to provide less relevant information in your template message.

Button

The button adds interactivity to your templates. There are two main types.

  • Quick Reply Button

    • Used for getting quick answers from your client

    • Max 3 Quick Reply Buttons per Template

  • Call to Action Button

    • Used to send your client to a Website or call a Phone Number

    • Max one URL and Phone Number per Template

All Templates require a Body. Headers, Footers, and Buttons are optional.

Example Media Template with Image, Body, Call to Action Button and Placeholder Variables

Visit our Template Messaging and Message Template API pages for more information on Templates!

🔑 Template API Reference

post
Create Template

https://waba.360dialog.io/v1/configs/templates
Request
Response
Request
Headers
D360-API-KEY
required
string
Response
201: Created
{
"name": "reprehenderit Lorem ad nulla",
"category": "RESERVATION_UPDATE",
"components": [
{
"type": "HEADER", "format":"IMAGE", "example":{
"header_handle":["https://url-to-media-file/media.file"]
}
"buttons": [
{
"type": "in qui magna",
"text": "in magna sint",
"URL": "minim reprehenderit"
},
{
"type": "irure non proident laboris amet",
"text": "adipisi"
},
{
"type": "dolore deserunt",
"text": "sit qui mollit proident",
"phone_number": "ipsum occaecat laboris reprehenderit"
},
{
"type": "Excepteur tempor nisi ad",
"text": "ad eiusmod exercitation id"
}
]
},
{
"type": "HEADER",
"text": "minim ullamco enim non ut",
"format": "DOCUMENT"
},
{
"type": "BODY",
"buttons": [
{
"type": "sed est in",
"text": "ex dolor Lorem",
"example": [
"dolor dolor"
],
"phone_number": "tempor sed irure laboris",
"URL": "anim"
}
],
"text": "adipisicing id non"
}
],
"language": "occaecat cillum aute"
}

The handle for examples has to be a valid URL to your media file.