Designing the conversation
A conversation you can see.
Nine node types on a canvas, wired by transitions you control. The graph is the agent, and every branch is visible before a single call lands.
Capability
01 / 11
Flow Builder
Nodes do one job each
A conversation node speaks and extracts what the caller said. A tool node calls your API and maps the response into variables. A router branches without saying anything. Transfer nodes hand off to a person or another agent. Because each node has one job, you can read a flow and know what it does.
Transitions decide what happens next
Five transition types cover the ways a call moves forward: deterministic conditions on a variable, natural-language judgement for ambiguous intent, keypad input, automatic advance, and an always-fallback. Transitions carry priority, so the specific case is evaluated before the general one.
Global nodes catch what the graph did not
Mark a node global and it is reachable from anywhere in the conversation: the escalation path, the "I want a human" request, the out-of-scope answer. You design the happy path and let global nodes absorb everything that leaves it.
Broken flows surface in the builder
Missing transition targets, conditional branches without a fallback, and variables referenced where they cannot be set are visible while you build. The alternative is finding them on a live call, which is a much more expensive place to learn.
The spec
| Node | What it does |
|---|---|
| start | Entry point. Opens with dialogue or fires a tool first |
| conversation | Speaks, listens, and extracts variables from the reply |
| tool | Calls a function or web tool and maps the response into variables |
| web_tool | Simplified HTTP call for straightforward endpoints |
| router | Branches on conditions without saying anything |
| set_local_variables | Sets values and advances automatically |
| transfer_call | Warm or cold transfer to a phone number |
| transfer_agent | Hands the caller to another Hamsa agent |
| end_call | Closes the call with a final message |
More capabilities
Carrying context
Variables & context
Extract a value once, like a booking reference or a plan name, and use it in any later prompt, condition, or request body, with 17 call variables available for free.
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 →The fast path
Single-prompt agents
Not every conversation needs a graph. Write one persona prompt, attach a knowledge base, and the agent handles the call, with the same tools and reporting as a flow agent.
Read →


