Graph agents
Control what happens inside one conversation. Nodes are conversation states; transitions decide when the caller moves between them.
Workflows (beta)
Orchestrate a sequence of steps around calls — run a call, branch on the result, wait, message, call again.
Choosing
They compose. A workflow step can run a graph agent, so a strict in-call script and a multi-day sequence are not competing choices.
A rule of thumb
Ask where the branching lives.- Branching inside the call, decided by what the caller says → graph agent.
- Branching between calls, decided by the call outcome → workflow.
- Branching only in your own backend, because you already have an orchestrator → neither. Use a standard agent and drive it from the API.
Cost of each choice
A graph agent adds design work up front and makes behavior predictable and testable — see testing and validation. Workflows are in beta: the builder, the API surface and campaign behavior are still changing, so prefer them for internal or lower-risk sequences until they are generally available.Next steps
Build a graph agent
Nodes, transitions, routing
Build a workflow
Steps, conditions, campaigns
Just use one prompt
The simplest option that works