Builder

Build the conversation your agent will have, then run it on a real call.

The builder is a drag-and-drop canvas. The graph you draw is the agent — there is no separate configuration behind it, and nothing to deploy. Change the graph, save, publish, and the next caller reaches the new version.

Core components

• Node — one step in a call: what the agent opens with, a question it asks, a system it calls, how it ends. Nodes catalogues all ten types.
• Edge — the rule that moves the call from one node to the next. An edge fires when the model judges the caller's goal met, when a keypad digit is pressed, or when a condition on gathered data holds.
• Start Call — the single entry point. Every workflow has exactly one, it cannot be deleted, and nothing can point an edge into it.
• Draft — your unpublished edits. Real callers never reach a draft.
• Run — one execution of the graph against one caller. Runs carry the transcript, the recording, the cost and the outcome; the workflow itself carries none of those.

Building a workflow

A new workflow arrives with one node and no edges: Start Call. Everything else you add.

1. Add a node from the node panel, or right-click the canvas and pick a type. Start Call is absent from both lists, because a second one is not allowed.
2. Drag from a node's handle to another node to draw an edge, then label it with the condition that should fire it.
3. Open a node to write its prompt and attach whatever it needs — tools, documents, variables to extract.
4. Save. Saving records a draft; it does not change what callers hear.

Select a node and delete it from its toolbar, or with the Backspace key. Start Call has neither affordance.

Routing

A node does nothing on its own. It runs when an edge leads into it, and it hands off when one of its outgoing edges resolves.

Most workflows are a chain of Agent Nodes, each with a focused prompt, joined by edges that describe the transition between them. Two nodes sit outside that chain:

• A Global Node contributes persona and standing rules to every node that opts in. It is never a step, so no edge touches it.
• An API Trigger node is an entry point from outside the call rather than a step within it.

Start Call may sit on the canvas with no outgoing edge at all — a one-node workflow is valid and publishable. That is what you get on creation, and it is why a brand-new workflow can be tested immediately.

Draft and published

Edits on the canvas are held as a draft until you publish. The published version keeps running for every real caller while you keep editing. Publishing promotes the draft and archives the version it replaces. See Versions.

Testing

The Test menu holds three ways to hear a change, and all three run your draft rather than the published version:

• Web Call places a call over WebRTC from the browser. It opens a full-page run screen — microphone controls on one side, a live transcript building on the other — so the canvas is not on screen while the call is up.
• Phone Call places an outbound call to a number you type.
• Text chat runs the same graph as typed messages instead of speech.

The menu stays disabled while the workflow has unsaved changes or validation errors. Save and fix the errors first.

Next steps