> 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/introduction.md).

# Introduction

## Overview

**WhatsApp Templates** are predefined message formats that allow businesses to send **automated and structured messages** to customers through the WhatsApp platform.

These templates are commonly used for:

* **Notifications and alerts**
* **Order updates and confirmations**
* **Promotional and marketing messages**

{% hint style="warning" %}
All templates must be **approved by WhatsApp** before they can be used.\
Approval may take up to **72 working hours**, so plan your campaigns accordingly.
{% endhint %}

Templates support **dynamic fields** (e.g., customer name, order details), allowing messages to be **personalized** while maintaining a consistent format.

Using templates helps businesses:

* Ensure **message consistency**
* Stay **compliant with WhatsApp policies**
* Save time and effort in creating messages

{% hint style="danger" %}
**Picky Assist** does not have any role in the **approval or rejection** of WhatsApp templates.Template approval is handled entirely by **WhatsApp (Meta)**.
{% endhint %}

### Billing & Usage Note

* Template messages are **chargeable**, and pricing varies based on the **recipient's country**.
* Ensure that your **wallet has sufficient balance** before sending template messages.

WhatsApp Templates are essential for **automated, scalable, and policy-compliant communication**, especially when interacting with users outside the active session window.


---

# 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/introduction.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.
