> For the complete documentation index, see [llms.txt](https://docs.yaeris.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yaeris.com/software/whatsapp-cloud-blaster-software/whatsapp-module/button-template.md).

# Button Template

<figure><img src="/files/hWIvX8VWk73Xvqr4UbHZ" alt=""><figcaption></figcaption></figure>

Fill up the details of the template to create the button template message

1. **Name**: Insert a template title (*for your reference purpose only*)
2. **Main Image**: Insert your media. Support image, video and PDF.
3. **Main Description**: Insert your caption/message you want to deliver to your customer
4. **Footer**: Insert any footer message. For eg, *Terms and Condition applied*.
5. **List button**: Create button for your message
   * Text button: Insert a quick reply message in the button. So when your customer clicks on the button, the message (*which you have inserted in the first place*) will be automatically reply back to you.&#x20;
   * Link button: Insert link in the button
   * Call action button: Insert your phone number in the button so that your customer can call you.


---

# 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://docs.yaeris.com/software/whatsapp-cloud-blaster-software/whatsapp-module/button-template.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.