> For the complete documentation index, see [llms.txt](https://wamoca.gitbook.io/wamoca-docs-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wamoca.gitbook.io/wamoca-docs-en/our-platform/message-templates.md).

# Message Templates

<mark style="color:purple;">**Before you can set up whatsapp templates, you must connect your account to WhatsApp.**</mark>

Message templates **allow users to create pre-defined message formats for automated communications**, leveraging the WhatsApp Business API.&#x20;

This feature makes it easy to create, sync and delete templates to **streamline messaging workflows and ensure compliance with WhatsApp messaging policies**.

## List of templates

The template list will display all the message templates created in your WhatsApp Business account. The fields that appear in the list are:

* Name: name of the template&#x20;
* Category: there are different message categories in WhatsApp, at the moment we only allow you to create message templates from the Marketing category
* Preview
* **Status**: status of the template in WhatsApp Busines&#x73;**. WhatsApp must approve our templates before they can be sent to customers**. Statuses can be: <mark style="color:orange;">Pending</mark>, <mark style="color:green;">Approved</mark> or <mark style="color:red;">No approved</mark>

From here, we can:

* **Create message templates** and integrate them with our WhatsApp Business account immediately
* **Synchronise templates** with our WhatsApp Business account to keep their status up to date

<figure><img src="/files/cTdt7ndhDUUZ0Xu8PJoM" alt=""><figcaption><p>List of templates</p></figcaption></figure>

## Creation of templates

In the template creation screen there are several sections:

### Basic data (required)

<figure><img src="/files/2oHFgv5IQ4Vk8To4Er7k" alt=""><figcaption><p>Datos básicos plantilla</p></figcaption></figure>

* **Name**: name of the template&#x20;
* **Category**: category of the template (at the moment we only support Marketing)&#x20;
* **Language**: language of the template

### Heading (optional)

This is the header field of the message. It can be of four types:

* **Text**: text field in which we can add a dynamic variable (client's name, client's surname, etc.). This dynamic variable will be configured when creating a campaign.

<figure><img src="/files/CLhjzGjK29hI3hrF46rJ" alt=""><figcaption><p>Text in heading</p></figcaption></figure>

* **Image**: image to be set up when creating a campaign

<figure><img src="/files/PJhSyH85uF7buG6FdrDw" alt=""><figcaption><p>Header image</p></figcaption></figure>

* **Video**: video to be set up when creating a campaign

<figure><img src="/files/TIJpwhgEW7eo7r19Kdr2" alt=""><figcaption><p>Video in header</p></figcaption></figure>

* **Document**: document to be set up when creating a campaign

<figure><img src="/files/qOuy2ny3E4S5hm6GSD8H" alt=""><figcaption><p>Header document</p></figcaption></figure>

### Body (required)

This field is the main text of the message. Here we can format the text (bold, italics, etc.) and add dynamic variables that will be configured in the campaign.

<figure><img src="/files/TexcGflcCXv8XsfSFAm7" alt=""><figcaption><p>Body of the template</p></figcaption></figure>

### Footer description (optional)

<figure><img src="/files/tsvoDfE5KfxbrY2Y9s0f" alt=""><figcaption><p>Template message footer</p></figcaption></figure>

### Buttons (optional)

<figure><img src="/files/tOn5wDGma7cOUCFeK2sw" alt=""><figcaption><p>Buttons template</p></figcaption></figure>

This field is the buttons or CTAs of the message. It is an optional field but highly recommended for conversion. There are four different types of buttons:&#x20;

* **Phone**: button to call a phone or mobile number
* **Website**: external link button
* **Copy offer code**: button to copy a discount code (to be configured in the campaign)
* **Custom button**: button to send message. If the customer presses the button a text message with its value will be sent (set up in the campaign). This is very useful for autoresponders


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wamoca.gitbook.io/wamoca-docs-en/our-platform/message-templates.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.