# Message templates: best practices & examples

## Best practices

Improve the chance of your templates being approved by following the guidelines below.

{% hint style="success" %}
Remember that someone outside of your business will be reviewing your templates. Providing more clarity gives reviewers context around how the template will be used.
{% endhint %}

When creating a new message template, please ensure you follow these best practices:

#### **Template name**

A unique name to identify the template use case for the business. 

* Must be in lowercase.
* Maximum of 512 characters.
* May not contain any spaces. Use an underscore to indicate a space.
* Make your message template name clear. E.g., instead of using a name like “*template\_014*” rather use “*order\_update*”.

#### **Template category & language**

The type of information contained in the template (e.g., marketing, utility) and the language of the content. Select these from a predefined set of categories and languages during registration.

**Template parameters**

* A template message must contain at least one parameter.
* Parameters cannot have new line/tab characters. 
* Parameters may not have more than four consecutive spaces. 
* All parameters will be defined within curly open/close braces and listed in chronological order starting at {{1}} (use the *+ Variable* button as a shortcut to easily add these). 

**Template content**

* Limited to 1024 characters.

{% hint style="warning" %}
For possible reasons why your message template was rejected, [see here](/whatsapp-channel/channel-capabilities/whatsapp-message-templates/message-template-rejection-reasons.md).
{% endhint %}

## Template examples

<table><thead><tr><th width="189">Template name</th><th width="144">Template Tag</th><th width="197">Template message</th><th>Parameter details</th></tr></thead><tbody><tr><td>optin_confirmation</td><td>Marketing</td><td>Dear {{1}}. You are now subscribed to receive account-related alerts for your account ending in {{2}}.</td><td><p>{{1}} – Name of the recipient, eg. John </p><p>{{2}} – Last 4 digits of the account, eg. 1234</p></td></tr><tr><td>transfer_update</td><td>Utility</td><td>Your funds transfer request of {{1}} from account ending in: {{2}} has been initiated.<br><br></td><td><p>{{1}} – Total amount, eg. $50 </p><p>{{2}} – Last 4 digits of the account, eg. 1234</p></td></tr></tbody></table>

{% hint style="success" %}
For more examples, see Meta's documentation [here](https://www.facebook.com/business/help/722393685250070).
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://guides.clickatell.com/whatsapp-channel/channel-capabilities/whatsapp-message-templates/message-templates-best-practices-and-examples.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.