Dialog variables

When to use a dialog variable

Use it for data belonging to one conversation: for example a deal ID, selected order, or discussion stage. One customer can have several dialogs, each with its own value. In a group dialog, this is one value for the whole conversation, not a separate field for each participant.

Store customer data that should be independent of the conversation in lead variables. Store shared company data in project variables.

Open the list

In project settings, select Variables, then the Dialog variables tab. This is where you create definitions: a field's name, type, and purpose. Values for individual conversations are not in this list; they are in dialog information.

Create a field

Select Create definition. In the definition form, enter:

1. Name — for example deal_id. It cannot be changed after creation.
2. Type — string, number, boolean, array, object, JSON, or date. String is suitable for deal identifiers that may contain letters and leading zeros.
3. An optional description of what the field stores.
4. An optional AI instruction, such as “Save the ID of the deal currently being discussed in this dialog.”

Select Create. Cancel closes the dialog without creating anything.

Creating a definition does not fill in every dialog. A value appears only where an operator, agent, automation, or application assigns one.

Use the field

• An operator sets the value in dialog information.
• In an agent instruction, {{dialog.deal_id}} inserts the current conversation's value. For independent reading or writing, configure agent access.
• In a For dialogs automation, select the Dialog scope. The value persists after the process ends and is available to later runs in that conversation. A background automation has no current dialog, so this scope is unavailable.

Edit or delete a definition

Open the field row. You can change its description and AI instruction. The type can change only when no dialog has a saved value for this variable. If data already exists, create a new field for a different type.

If the definition is no longer needed, select Delete.

In the dialog, check the variable name and confirm the action. If other resources use the field, Senler rejects deletion and lists the dependencies.

Stored dialog values are not erased with the definition. Restore access by creating a definition with the original name, type, and the same data schema if one was set through the API. To delete only one conversation's value, use the dialog editor.

Transfer a field to another project

Copying and sharing by link transfers the definition, not conversation values. You can also include the field in an agent package. See Copying and sharing resources.