> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/sms/writing-messages/use-variables-in-sms-flows.md).

# Use Variables in SMS Flows

Explains how to personalize SMS messages with variables like first name, support email and support phone number. Your site name is added automatically.

Variables personalize your messages. Each one is replaced with real details - like the subscriber's first name - when the message is sent.

### Your site name is added automatically

Every SMS message starts with your site name, followed by a colon - for example, "Recart Demos: Hey Sasha, ...". Recart adds it automatically and it can't be removed, so subscribers always know who the message is from.

### Available variables

You can add these variables anywhere in your message:

* Site name
* First name
* Last name
* Nick name
* Support email
* Support phone number
* Order number (in Order & Receipt messages, like receipts and order canceled messages)

Name details are collected through your opt-in tools - for example, with form fields on your popup - and from imported lists.

### Add a variable to a message

1. Open the SMS message you want to edit, or create a new one
2. Click the **{x}** icon in the message editor and select the variable you want to add

<figure><img src="https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FRuSetPjS7YO2JYv5nVvW%2Fvariables-menu.png?alt=media" alt="The SMS message editor next to the Variable panel, with the variable dropdown open showing Site name, First name, Last name, Nick name, Support email and Support phone number"><figcaption></figcaption></figure>

3. Enter a **Fallback value** - the text to use if a subscriber's details aren't available - and click **Insert variable**

<figure><img src="https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FOLwjozTixUZJim0uQInB%2Fuse-variables-in-sms-flows-2.jpg?alt=media" alt="The Variable panel with First name selected and the fallback value set to there, above the Insert variable button"><figcaption></figcaption></figure>

4. The variable is added to your message

<figure><img src="https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FKQb2RDfLFCBv7chcWEU8%2Fuse-variables-in-sms-flows-3.jpg?alt=media" alt="A message preview starting Recart Demos: Hey {First name}, with the site name and first name variable highlighted"><figcaption></figcaption></figure>

<figure><img src="https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FtfpANwdozPu5UhKoM9uu%2Fuse-variables-in-sms-flows-4.jpg?alt=media" alt="The same message received on a phone, reading Recart Demos: Hey Sasha, with the variables filled in"><figcaption></figcaption></figure>

If you have any questions, do not hesitate to [contact the Recart Support team](/contact-recart-support.md). We'd be happy to help!


---

# 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://help.recart.com/sms/writing-messages/use-variables-in-sms-flows.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.
