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

# Guidelines

## Overview

WhatsApp templates must follow **Meta guidelines** to ensure messages are **clear, relevant, and compliant**, improving approval and user experience.

### General Guidelines

* Use **clear, simple, and meaningful content**
* Maintain proper **grammar and spelling**
* Avoid **spam-like or misleading messages**
* Ensure content matches the **selected category** (Utility, Marketing, Authentication)

### Content Rules

* Messages should provide **value to users**
* Avoid Offensive or irrelevant content
* Marketing templates must follow **WhatsApp Commerce Policy**

### Variable Guidelines

* Use format: `{{1}}, {{2}}`
* Variables must be **clear and meaningful**
* Avoid incorrect or excessive variable usage

### Formatting Guidelines

* Avoid Unnecessary line breaks, tabs, or extra spaces
* Keep proper **sentence structure**
* Limit excessive emojis or symbols

### URL & Language Rules

* Use **valid, complete URLs** (avoid short links)
* Ensure **language matches content**
* Provide proper translations for multi-language templates

### Category & Compliance

* Select the **correct category**
* Do not mix Utility and Marketing (will become **Marketing**)
* Follow **WhatsApp Business & Commerce policies**
* Avoid restricted or sensitive content

### Common Rejection Reasons

{% hint style="warning" %}
Wrong category\
Poor formatting or grammar\
Variable misuse\
Spam-like or unclear content
{% endhint %}


---

# 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://help.pickyassist.com/setting-up-guide/connecting-channels/whatsapp-templates/guidelines.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.