Loading model…
Runtime
Campaign graph
One agent runs from contacts, CSV, or triggers. Each hop is a run with stages, wrap-up, and artifacts.
Drag to orbit · scroll to zoom
- Starts
- Campaign / CSV / trigger
- State
- Stages → wrap-up → hangup
- Plan
- Minutes + allotted DIDs
The lattice is the control plane: many calls, one agent definition. Nodes are runs; rings are retries and wrap-up.
Inspect it in wireframe to see the call graph the engine walks instead of an IVR tree you drew by hand.
- Manual, list, file, or trigger start
- Stage graph with a real end call
- Workspace-scoped history
Also in the studio
Agent
Voice agent persona
The on-call operator: language, voice, stages, and hangup rules live on one agent. Same definition for browser tests and phone campaigns.
Telephony
Live outbound call
Phone numbers allot to each client. Campaigns dial from the number you assign so the caller ID is yours.
Speech
Speech in and out
The studio mic is capture and playback: what the caller says, and the agent’s spoken reply — with gain limiting so replies do not clip.