Carrying context
What the agent remembers.
System variables, custom constants, and values extracted mid-conversation, referenced anywhere with Jinja, with clear rules about what is in scope.
Capability
04 / 11
Variables & context
Three sources
System variables come from the platform and are always available: the call ID, the caller's number, today's date. Custom variables are constants you set once per agent. Extracted variables come from the caller's own words or from a tool response.
Three ways to extract
The model can pull a value out of free-form speech, a JSONPath expression can pull it out of a structured tool response, or the caller can enter it on the keypad. Keypad capture matters for the things people do not want to say aloud: account numbers, dates of birth, PINs.
Scope is explicit
A value extracted on one branch is not silently available on another. Tool outputs exist only on the success path. Global nodes see system and custom variables but not path-specific ones. Knowing these rules is the difference between a flow that works and one that fails quietly.
Jinja everywhere it matters
Variables can be referenced in what the agent says, in conditions that route the call, and in the URLs and bodies of the requests it sends, with fallbacks for the cases where a value was never set.
The spec
| Variable | What it holds |
|---|---|
| user_number | The caller's phone number |
| call_type | Inbound or outbound |
| call_id | Unique identifier for the call |
| call_start_time | When the call began |
| current_date | Today's date, for booking and eligibility logic |
| agent_name | The agent's configured name |
More capabilities
Designing the conversation
Flow Builder
Design the call as a graph: conversation, tool, router, transfer, and end-call nodes, connected by conditions you define rather than hope the model infers.
Read →Connecting your systems
Tools & integrations
Call your own REST endpoints, connect an MCP server, and map responses into the conversation, with per-node overrides and a test run before anything goes live.
Read →How the call behaves
Call controls
Tune interruption, response delay, silence timeouts, and call duration: the settings that separate a natural call from an awkward one.
Read →


