Dynamic Variables: How to Customize Each Call
How to have the agent announce the name, details, and amounts for each individual contact using variables enclosed in double curly braces.
Written By Product
Last updated 4 months ago
Dynamic variables allow the agent to say different things to each contact—their name, their case number, the amount applicable to them—instead of repeating the exact same text to everyone.
They are always written within double curly braces: {{nome_variabile}}. When the call actually goes through, the placeholder is replaced with the actual data for that contact.
Two Types of Variables
Your variables. These come from the columns in the contact file (CSV or Google Sheet) that you upload for the campaign. You choose the name: if the column is called nome_cliente, write {{nome_cliente}} in the script.
Predefined variables. These are available without needing to be uploaded and have predefined names in English. They cannot be renamed: they must be referenced exactly by their name. There are two types, explained below.
Variables for customizing the conversation
These are the ones you’ll use most often. You’ll find them in the Variable Manager, and they’re configurable.
{{agent_name}}— agent name{{user_name}}— name of the person they’re talking to{{company_name}}— your company’s name{{user_email}}— contact’s email{{user_phone}}— contact’s phone number{{current_date}}— current date{{current_time}}— current time
💡
{{current_date}}and{{current_time}}are useful for having the agent say things like “I’ll call you back tomorrow” without having to update it manually.
System Variables
These are technical variables automatically populated by the platform for each call. You don’t need to set them yourself; they’re mainly used for reports and integrations.
{{system__agent_id}}— ID of the agent who initiated the conversation{{system__current_agent_id}}— ID of the current agent (changes after a transfer between agents){{system__caller_id}}— the number that initiated the call{{system__called_number}}— Number dialed{{system__call_duration_secs}}— Call duration in seconds{{system__time}}— local time{{system__time_utc}}— UTC timestamp{{system__timezone}}— time zone{{system__conversation_id}}— call ID{{system__call_sid}}— technical call identifier on the carrier side
An example
The contacts file has the following columns: nome_cliente, numero_pratica, importo_dovuto. In the script, write:
"Good morning, {{customer_name}}, I’m calling regarding case {{case_number}}..."
During the call, the agent will state the name and case number for that specific contact.
How to set them up
Prepare the file with clear column headers. Use
nome_clienteinstead of "Column A": you’ll need this to identify them during mapping.Map the columns when uploading contacts. Standard fields (name, phone, email, company) are mapped automatically; the others become custom contact fields.
Reference the variable in the script using the syntax `
{{ }}`.
If the variable is not assigned a value
If, during a call, the agent reads the placeholder instead of the data, or skips it:
The name doesn’t match. This is the most common cause: the name written in the script must match the mapped name exactly—including uppercase letters, lowercase letters, and underscores. `
{{Nome_Cliente}}` and `{{nome_cliente}}` are not the same variable.You used a single set of parentheses. You need double parentheses:
{{nome}}, not{nome}.That contact’s cell is empty. The variable exists, but there’s no data for that contact: check the file.
You’re using a system variable with a name you created. System variables must be referenced using their original English names.
Related Articles
How to Use the Contact Manager
How to Test Your Agent Before Launching It
Was this helpful?
More in Platform Guides DeepAgent
How to set up your AccountPlatform: Platform OverviewReports: How to Measure Agent Performance Using ReportsAgents: Edit and MonitorStill need help? Share an idea