Skip to main content

What Are Context Variables?

Context variables let you personalize each call with dynamic information. Instead of generic conversations, your agent can address callers by name, reference their account details, or mention specific products they’ve purchased.

How It Works

When you trigger a call (via campaign or API), you pass context data that the agent uses during the conversation. Example: Instead of saying “Hello, how can I help you?”, the agent says “Hello John, I’m calling about your order #12345.”

Using Context Variables

In the Workflow Editor

Reference variables using double curly braces:

Example Variables

Common business variables you can declare and pass:

Custom Variables

You can define any custom variable. Declare it first in the agent’s Template Context Variables (the variables button of the editor), then use it in your workflow and provide the value when triggering calls.
Saving is refused when a text uses a variable that does not exist, and the error names that variable. A variable exists when Tala provides it (such as {{ phone_number }}, {{ first_name }}, {{ greeting_name }}, or {{ email }} once the caller has confirmed it), when an earlier step of your agent collects it with extraction turned on, or when it is declared in the agent’s variables under exactly that name. Without this check, a misspelled variable would stay empty during the call.
Example workflow text:
Data you provide:

Passing Variables

Via Campaigns

When uploading a CSV for campaigns, each column becomes a variable:
These become {{ first_name }}, {{ appointment_date }}, and {{ doctor_name }} in your workflow. Declare the columns you use in the agent’s variables (first_name is already provided by Tala) so that your texts can be saved.

Via API

Vous pouvez déclencher des appels et passer des variables de contexte via l’API. L’accès est disponible sur demande — contactez notre équipe pour obtenir vos identifiants.

Best Practices

Provide Fallbacks

Handle missing data gracefully with fallback syntax

Keep It Natural

Don’t overload conversations with too many variables

Test Variations

Test with different data to ensure natural flow

Verify Data Quality

Ensure your data source has clean, accurate information

Common Use Cases

Appointment Reminders

Order Follow-ups

Lead Qualification

Next Steps