> For the complete documentation index, see [llms.txt](https://docs.salesrook.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.salesrook.com/salesrook-core/how-to-create-an-interactive-whatsapp-template.md).

# How to: Create an interactive WhatsApp template

This guide shows you how to create WhatsApp templates in SalesRook for initiating contact, re-engaging leads, sending broadcasts, and saving frequently used messages.

{% embed url="<https://salesrook.clarityflow.com/c/97f93c8c75741588182bbb039>" %}

### Step 1: Access the WhatsApp Settings

1. **Log into SalesRook**: Start by logging into your SalesRook Core account.
2. **Go to Settings**: In the bottom left corner of your screen, click on **Settings**.
3. **Navigate to WhatsApp**: From the left-hand menu, select **WhatsApp**.

### Step 2: Open the Template Section

1. **Click on Templates**: In the WhatsApp settings, you will see two tabs: **Numbers** and **Templates**. Click on **Templates** to view and create new templates.

### Step 3: Create a New Template

1. **Click Create Template**: Click the blue **Create Template** button on the right side of the screen.
2. **Enter Template Name**: Choose a unique internal name for the template (e.g., **September Broadcast**). This name will not be visible to customers.
   * The template name should only use lowercase letters and underscores.
3. **Select Template Category**:
   * **Marketing**: Choose **Marketing** for general templates (commonly used).
   * **Utility**: Choose **Utility** for notifications, though Meta may reject these templates more often.
4. **Choose Language**: Select the language you want the template to be in (e.g., **English**).

### Step 4: Set the Header (Optional)

1. **Choose Media for Header**:
   * The **Header** section allows you to attach media like text, images, videos, documents, or locations.
   * If you don’t need a header, toggle it off. If you want to include a document, toggle the header on and select **Document**.
2. **Upload Your File**: Click to upload your document. This will be shown in the message preview.

### Step 5: Write the Message Body

1. **Compose the Message**: Enter the body of your message in the text field.
   * You can format the text with **bold**, **italic**, **strikethrough**, or **monospace**.
2. **Add Variables**:
   * To personalize your message, click **Add Variable** to insert dynamic content (e.g., contact’s first name).
   * Place the variable in the message where it makes sense (e.g., "Hi, {Contact First Name}").
   * **Mapping Variables**: Select the relevant variable, such as **Contact First Name** or **User First Name**.

### Step 6: Add Footer (Optional)

1. **Add Opt-Out Footer**: If needed, include a footer for opt-out messages (e.g., "Reply STOP to unsubscribe").
   * The footer text will appear in paler text and has a character limit of **60 characters**.

### Step 7: Add Buttons (Optional)

1. **Click Add Button**: You can add buttons to your template for quick replies or actions.
   * **Custom Buttons**: You can create a custom quick reply button (e.g., "Rent" or "Buy").
   * **Action Buttons**: You can also add buttons like **Visit Website**, **Call Phone Number**, or **Copy Offer Code**.
2. **Add Multiple Buttons**: Up to 10 buttons can be added, and you can rearrange them as needed.

### Step 8: Save and Submit the Template

1. **Click Create**: After finalizing your template, click **Create** to save and submit it.
   * The template will be pending approval, and it usually gets approved within a few seconds.
2. **Check Approval**: Once the template is approved, it will be available for use. Refresh the page to see the status change to "Approved."

***


---

# 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://docs.salesrook.com/salesrook-core/how-to-create-an-interactive-whatsapp-template.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.