> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/additonal-channels/whatsapp-calling/business-initiated-calling-on-doubletick-complete-guide/how-to-create-a-call-permission-request-template-on-doubletick.md).

# How to Create a Call Permission Request Template on DoubleTick

**Introduction:**\
Before your team can call customers, they need **explicit permission**. This article walks you through **creating an approved template** in simple, easy-to-follow steps.

***

#### **Step-by-Step Guide**

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2F1y3sHM2QilA2CQhibBFF%2FUntitled%20design%20(6).gif?alt=media&amp;token=c1a90bb9-cd55-4ee2-8330-d1cc691393ce" alt=""><figcaption></figcaption></figure>

1. **Login** to [DoubleTick](https://web.doubletick.io/).
2. Click **Templates → New Template**.
3. Name your template, e.g., **Outbound Calling\_DoubleTick**.
4. Select **Utility** as the category.
5. Choose **Create a call permission request template to send users outside the service window.**
6. Write your message:
   * *Example:* “Hi {{customer\_name}}, our team would like to call you regarding your request.”
   * Add **Yes/No Quick Reply Buttons**.
7. Add dynamic variables like `{{customer_name}}` to personalize each message.
8. Click **Save & Submit**.
9. Wait for **Meta approval**.

**Tips:**

* Keep messages short, polite, and professional.
* Clearly **state the purpose of the call**.
* Make it easy for customers to respond with **one tap**.


---

# 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://learn.doubletick.io/additonal-channels/whatsapp-calling/business-initiated-calling-on-doubletick-complete-guide/how-to-create-a-call-permission-request-template-on-doubletick.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.
