> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/setting-up-guide/connecting-channels/whatsapp-templates/template-components.md).

# Template Components

## Overview

WhatsApp templates are built using different **components**, which define the **structure and content** of the message. Each component serves a specific purpose, such as displaying text, media, or interactive elements.

A template can include the following components:

* **Header**
* **Body**
* **Footer**
* **Buttons**

***

### 1. Header

The **Header** is the top section of the template and is used to capture attention.

#### Supported Types

* **Text**
* **Image**
* **Video**
* **Document**

#### Key Points

* Only **one header** is allowed per template
* Media headers enhance **visual engagement**
* Text headers can include **dynamic variables**

***

### 2. Body

The **Body** is the main content of the message.

#### Features

* Supports **text with dynamic variables** (e.g., {{1}}, {{2}})
* Used to convey the **core message**

#### Character Limit

* Up to **1024 characters**

<figure><img src="https://3382165395-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LlJChpzcxtwOYGcBd1q%2Fuploads%2F5m9IWEEUSXHe7lFdUNDp%2Fgit09.jpg?alt=media&amp;token=b31743e3-c0e4-41ad-bffb-81474391e90d" alt=""><figcaption></figcaption></figure>

***

### 3. Footer

The **Footer** is an optional section used for additional information.

#### Features

* Typically used for:
  * Disclaimers
  * Additional notes
* Does **not support dynamic variables**

#### Character Limit

* Up to **60 characters**

<figure><img src="https://3382165395-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LlJChpzcxtwOYGcBd1q%2Fuploads%2F1gRZZUJiALHH2ebnLPI4%2Fgit10.jpg?alt=media&amp;token=5ac79080-2ce3-476b-b3e6-6e768d7aa9be" alt=""><figcaption></figcaption></figure>

***

### 4. Buttons

Buttons provide **interactive actions** for users.

#### Types of Buttons

* **Call To Action (CTA)**
  * Visit Website (URL)
  * Call Phone Number
* **Quick Reply**
  * Predefined responses for user interaction

***

#### Key Limits

* Maximum **10 buttons** (depends on type and template)
* Button text limit: **25 characters**
* ❌ Emojis are not supported in button text

| Component             | Character Limit            | Additional Notes                                   |
| --------------------- | -------------------------- | -------------------------------------------------- |
| **Body Text**         | Up to **1024 characters**  | Mandatory component, supports variables and emojis |
| **Footer**            | Up to **60 characters**    | Optional, text only, no variables allowed          |
| **Button Text**       | Up to **25 characters**    | Applies to button label text                       |
| **Number of Buttons** | Up to **10 buttons total** | Includes Quick Reply + Call-to-Action combinations |

***

### Dynamic Variables

Dynamic variables allow templates to be **personalized**.

#### Format

```
{{1}}, {{2}}, {{3}}
```

#### Usage

* Customer name
* Order details
* OTP codes

***

### Important Notes

* Each component must follow **WhatsApp guidelines**
* Invalid formatting may lead to **template rejection**
* Components and their limits may vary slightly based on **template type (Marketing, Utility, Authentication)**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.pickyassist.com/setting-up-guide/connecting-channels/whatsapp-templates/template-components.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
