> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tranthor.com/llms.txt
> Use this file to discover all available pages before exploring further.

# WhatsApp

> Send WhatsApp messages from journeys and broadcasts, with templates approved by Meta.

Tranthor sends WhatsApp messages from your journeys and broadcasts. You write a template in Tranthor, Meta approves it, and then you can send it. Tranthor sets up the WhatsApp sender for your workspace, so there are no provider keys for you to enter.

## Turn on WhatsApp

1. Go to **Settings**, **Integrations** and open the **WhatsApp** card.
2. Select **Request WhatsApp**. This sends us a request to set up a sender for your workspace.
3. When the sender is ready, the card says WhatsApp is on, and **Open templates** takes you to your WhatsApp templates.

One WhatsApp number belongs to one workspace.

## Write a template

Go to **Templates**, open the **WhatsApp** tab and select **New WhatsApp template**. The settings panel has:

* **Sent to Meta as:** the template's name at Meta. Lowercase letters, numbers and underscores only, like `welcome_message`. Meta won't take a name it rejected before. You can change the name until you first submit, and again if the template is rejected, paused or disabled.
* **Language:** English (also US and UK), Spanish (also Spain and Mexico), French, German or Portuguese (Brazil).
* **Type:** what the message looks like. See below.
* **Category:** **Utility** for order, delivery and account updates, or **Marketing** for offers and news. Marketing needs the customer's opt-in and costs more.

**Write with AI** asks the WhatsApp agent to draft or change the message for you.

### Types

| Type | What it is | Limits |
| - | - | - |
| **Text** | Words only. | Up to 1024 characters. |
| **Image** | A picture with a caption. | JPG or PNG, up to 5 MB. |
| **Video** | A short clip with a caption. | MP4, up to 16 MB. |
| **Document** | A PDF, such as a lookbook or an invoice. | PDF, up to 16 MB. |
| **Card with buttons** | A picture, text and links. | Optional header (text up to 60 characters, or an image) and footer (up to 60 characters). Up to 2 website or call buttons. |
| **Coupon code** | A discount with a **Copy code** button. | Always Marketing. |
| **Carousel** | Swipeable product cards. | 2 to 10 cards. Each has a picture or a video, an optional title and text (160 characters together), and 1 or 2 buttons. All cards use pictures or all use videos, with the same buttons in the same order. Always Marketing. |
| **Quick replies** | Tap-to-answer buttons. | Up to 3 buttons. |
| **Call to action** | Website and call buttons. | Up to 2 website buttons, 1 call button and 1 **Copy code** button. Message up to 640 characters. |

**Catalog**, **Form** and **Verification code** are shown as coming soon.

For a carousel, **Fill from a collection** builds the cards from your synced store catalog.

### Buttons

* A quick reply label can be up to 25 characters. A label on a card or carousel button can be up to 20. Labels can't hold a variable.
* A website link must start with `https://`. It can end with one variable, like `https://your-store.com/orders/{{1}}`.
* A call button's number needs the country code and no spaces, like `+14155550123`.

### Pictures, videos and documents

Upload the file, or paste a public link. Uploaded files are saved to your workspace's assets. Meta fixes the kind of file when it approves the template, so an image template always sends an image.

To send a different picture to each customer, put a variable after the domain, like `https://your-store.com/products/{{1}}`, and map it to a customer property that holds the file's path. Its sample must end in the file type, like `products/linen.jpg`.

## Variables

Meta's templates use numbered variables: `{{1}}`, `{{2}}` and so on. Select **Add variable** in the message, then for each one:

* **Choose a customer property** that fills it in, for example the customer's first name.
* Enter a **Sample for Meta**. Meta's reviewers see the sample. It is never sent to a customer.

A new template starts with `{{1}}` mapped to the customer's first name, with "there" for customers who have none.

**Every variable must be mapped to a customer property.** Until it is, the template can't be submitted or published, and a broadcast that uses it can't be sent. When a message is sent, a customer who has no value for a variable is skipped, and in a journey moves on to the next step.

Meta also has rules of its own: the message can't start or end with a variable, and two variables can't sit side by side.

## Get it approved by Meta

Select **Submit for approval**. Tranthor publishes the template and sends it to Meta. The template then moves through:

| Status | Meaning |
| - | - |
| **Draft** | Not sent to Meta yet, or edited since it was. |
| **In review** | Meta is checking it. Meta usually replies within a few minutes, and sometimes takes a day. |
| **Approved** | Ready to use in journeys and broadcasts. |
| **Rejected** | Change the message and submit it again. The editor shows Meta's reason. |
| **Paused** | Meta paused it after customer feedback. |
| **Disabled** | Meta turned it off. It can't be sent. |

Tranthor checks with Meta on its own while a template is in review. **Check status with Meta** checks now. In the Templates list, the **Meta status** column shows the same state for every template, and the **Needs you** filter shows the ones waiting on you.

Common reasons for a rejection:

* **The format is not accepted.** Check the variables.
* **The words don't match the category.** Try the other category.
* **It reads as promotional.** Choose **Marketing**.

If you change the message, language, category, name or type of an approved template, it needs Meta's approval again. Changing which customer property a variable uses, or its sample, does not: **Publish changes** is enough.

A rejected, paused or disabled template is never sent.

## Send a test

**Send test** in the editor sends the template to a number you enter. Start with `+` and the country code.

Before Meta has approved the template, you can still test it with **Send as normal message**. WhatsApp only delivers a normal message to a number that has messaged your sender in the last 24 hours.

## Send it

* **Journeys:** add a message step and choose the WhatsApp channel, then an approved template.
* **Broadcasts:** choose WhatsApp on the Message step.

WhatsApp messages go to the customer's `phone` property, the same one SMS uses. A customer with no phone is skipped.

## Opt-outs

Each workspace has a **WhatsApp** [subscription group](https://docs.tranthor.com/resources/subscription-groups.md). A customer who replies **STOP**, **STOPALL**, **UNSUBSCRIBE**, **CANCEL**, **END** or **QUIT**, or taps an opt-out button, is unsubscribed from every WhatsApp subscription group in the workspace. A reply of **START**, **UNSTOP** or **YES** subscribes them again.

Tranthor does not act on other replies from customers.

## Results

For each WhatsApp message Tranthor records whether it was **sent**, **delivered**, **read** or **failed**. These show on the journey's **Results** tab and in **Messages**.

## AI agents and assistants

* In the editor, **Write with AI** drafts and changes a WhatsApp template.
* Tranthor's own agents do not send WhatsApp by default.
* Connected assistants such as Claude and ChatGPT can list and read your WhatsApp templates, including a rejection reason. They can't draft a WhatsApp template, and they can't send a broadcast whose template has an unmapped variable.

## Current limits

* Use approved templates in journeys and broadcasts. A carousel can't be sent at all, even as a test, before Meta approves it.
* Link clicks are not tracked for WhatsApp.
* Tranthor does not check WhatsApp's 24-hour rule for you. A normal message to a number outside it is not delivered.
* Replies other than opt-out and opt-in words are not processed.
* **Catalog**, **Form** and **Verification code** templates are not available yet.

> [!NOTE]
>
> Questions about WhatsApp for your workspace? Write to [support@tranthor.com](mailto:support@tranthor.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.