> For the complete documentation index, see [llms.txt](https://docs.messageflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.messageflow.com/rcs/rcs-flow-studio-creating-messages-and-scenarios/variables-personalizing-the-conversation.md).

# Variables - personalizing the conversation

Variables let you store information during the conversation and use it later — e.g. in the message content or in a condition. You insert them into the text in double curly braces, e.g. {{first\_name}}.

Rules to keep in mind:

* The name must be unique within the conversation — the editor will not let you create two variables with the same name.
* Each variable has a type (text, number, date, e-mail, phone, URL and others) — the available conditions depend on the type.
* You cannot delete a variable that is used in nodes — the editor will show you exactly where it is used.

{% hint style="info" %}
Example: you save the recipient’s choice to the {{category}} variable, and in the next message you write: “Great choice! Check out our picks from the {{category}} category”.
{% endhint %}

<figure><img src="https://1762163817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDIGjHYIXYoHyJoOeeUgD%2Fuploads%2FLNTg5t56LvTeTqmohDH5%2FZrzut_5.png?alt=media&amp;token=ed00075d-9fc9-4874-8fc5-707660ee23f6" alt=""><figcaption></figcaption></figure>

Other flow settings in the Properties panel

You create variables in the Properties panel, which opens when you click an empty area of the canvas (with no node selected). In addition to the Flow name, Status (Draft / Ready) and the list of variables, you will find two global settings there that apply to the whole conversation:

* Error handling — defines what should happen when an error occurs during the conversation and the node where it occurred has no error handling of its own (e.g. an HTTP Request or Dynamic Carousel integration error). In the Action field, choose Null (the conversation stops at this point) or Go to and select the node the recipient should be taken to — e.g. a text with an apology and customer service contact details. Optionally, turn on Retry on failure and set the Number of retries (up to 3).
* Reaction to inactivity — the default setting for the whole flow: what should happen when the recipient does not react to a message within a set time. The default is Null — the conversation simply waits. If you set an action here, it applies to all content nodes that do not have their own reaction to inactivity; you can configure the reaction for a single node in its properties (section 3.9).

Node-level settings always take precedence over global flow settings — the global ones act as a safety net wherever you have not planned a separate path.
