The three context objects
initial_context
Data available to the agent before the call starts — the contact’s name, account details, appointment information, anything the agent should know upfront. It can be set from several places:- API trigger — pass it in the request body when calling
POST /public/agent/{uuid}orPOST /telephony/initiate-call - Campaign CSV — columns beyond
phone_numberautomatically becomeinitial_contextfields for each contact’s call - Dashboard — set default template context variables on the agent, used when no external context is provided
Template variables
Values frominitial_context are available in your agent’s prompt using {{double_brace}} syntax.
gathered_context
Data the agent collects during the call. You configure what to extract in the agent node’s extraction settings — each variable has a name, type, and a prompt that tells the LLM what to look for.
gathered_context is returned in the run record after the call completes and is available in webhook payloads for downstream processing.
Data flow example
Where variables are available
| Location | Variables available |
|---|---|
| Agent node prompts | initial_context fields via {{variable_name}} |
| Edge conditions | Evaluated against the live conversation — no explicit variable syntax needed |
| Webhook payload templates | All context objects via {{initial_context.field}}, {{gathered_context.field}} etc. |
| Campaign CSV columns | CSV columns beyond phone_number become initial_context fields automatically |