Docs
Assistants
Variables
Make each conversation relevant. Add live values to messages, tools and workflows with {{double braces}}.
#Built-in variables
These are filled in on every call:
| Variable | Value |
|---|---|
{{business.name}} | Your business name. |
{{assistant.name}} | The assistant's name. |
{{customer.number}} | The caller's number, when known. |
{{customer.name}} | The caller's name, when your contacts know it. |
{{now}} | Date and time in your time zone, such as "Tuesday, October 6, 2026, 2:15 PM". |
{{date}} | The date, such as "October 6, 2026". |
{{time}} | The time, such as "2:15 PM". |
{{day}} | The weekday, such as "Tuesday". |
{{hour}} | The hour from 0 to 23. |
{{business.open}} | yes while you are open, otherwise no. |
{{business.timezone}} | Your time zone, such as America/New_York. |
#Your own variables
Write any name in double braces, such as {{first_name}} or {{order_number}}, and give it a default under Advanced → Default variables. An assistant can have up to 50 defaults. Each call can then supply its own values:
| Where the call starts | How to pass values |
|---|---|
| REST API | The variables object when you start a call. |
| Campaign | Extra columns in the contact list. See Contact lists. |
| Workflow | Collected from the caller, set by a Set block, or returned by code, HTTP and app blocks. |
First message
Hi {{first_name}}, this is Ava from {{business.name}}. I am calling about your appointment on {{appointment_day}}.#Which value wins
- A value passed with the call.
- The assistant's default.
- The built-in value.
A variable nobody sets is left empty, so write sentences that still read well without it, or give it a default.
#Where variables work
Instructions, the first message, API request tool URLs and bodies (with {{call.*}} for call details), text tool messages, and every workflow block that takes text.