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

# Broadcasts: variables in the message

> Personalize each Broadcast message with the contact's name and fields.

## What it is for

In **Broadcasts**, each recipient gets the message with their own data in place of the variables, such as the name and the contact fields.

## Where to click

**Chats › Broadcasts** (the tab shows up if the agency enabled the Broadcasts module for the organization). Click **New campaign** and go through **Who to send to**, **What to send**, **When and pace** and **Review and start**. In **What to send**, the **Variables:** line sits right below the text.

## Variables you can use

Write the variable in the text, with single braces (`{nome}`) or double braces (`{{nome}}`):

| Variable | What goes in |
| - | - |
| `{nome}` | The contact's name. With no name, "Cliente" goes in. |
| `{primeiro_nome}` | The first name. |
| `{sobrenome}` | The last name. |
| `{telefone}` | The phone number. |
| `{email}` | The contact's email. |
| `{empresa}` | The contact's company. |
| Contact field | The value of the custom field, by the field's name. |

The English names `{name}`, `{firstName}` and `{lastName}` also work, and both styles can be mixed in the same campaign.

A variable with no value on the contact comes out empty, never raw: nobody receives `{primeiro_nome}` written in the message. This applies to every variation of the broadcast, including media captions.

## What happens next

* The preview in **Review and start** shows the first recipient's name (or an example) in place of the name variables.
* If the system cannot build a recipient's message, that recipient is marked as failed, with the reason, and the campaign moves on to the others.

## Next step

* [Lists and segments](https://docs.stchat.app/en/subcontas/listas-e-segmentos.md)
* [Number warm-up](https://docs.stchat.app/en/subcontas/aquecimento-do-numero.md)


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