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.

01

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.

02

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.

03

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.

04

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

VariableWhat it holds
user_numberThe caller's phone number
call_typeInbound or outbound
call_idUnique identifier for the call
call_start_timeWhen the call began
current_dateToday's date, for booking and eligibility logic
agent_nameThe agent's configured name

More capabilities

Partner ecosystem

Trusted Across the
Technology Ecosystem

Hamsa works with leading technology companies, integrators, and solution providers to bring enterprise Voice AI to organizations across the region.