Skip to content

Flow editor

Build conversation logic without engineering

Drag nodes onto a canvas, connect them, and watch data move through your workflow node by node. The ops lead who owns the process owns the flow — no engineering ticket, no release train.

Inbound Call+962 6 500 1180
Succeeded
Claims AgentCollect FNOL details
Running
IFTotal loss suspected
Queuedtruefalse
Open ClaimPOST /claims
Human HandoffClaims desk

The motor FNOL flow. Green is the true branch, red the false — here, a suspected total loss routes straight to the claims desk instead of auto-opening.

What you get

How it works

Nodes for the work that matters

Triggers, AI agent turns, conditions, HTTP calls into your core systems, data transforms, custom code, and human handoff. Enough to model a real claims journey.

See the data at every step

Click any node after a run to inspect exactly what went in and what came out. Debugging a conversation stops being guesswork.

Branch on anything

Total loss suspected? Route to the desk. Under the auto-approval limit? Settle in the call. Conditions read any field the agent has gathered.

Test before it touches a customer

Run the whole flow against a sample payload and watch each node succeed, fail or skip before it goes live on a phone number.

Questions

Frequently asked

Do I need a developer to build a flow?

No. The editor is built for the ops or CX lead who owns the process. A developer is only needed if you want a custom code node for logic no built-in node covers.

What happens if a step fails mid-conversation?

The failing node is marked and its branch is skipped, while unrelated branches carry on. The error and the exact failing item are visible in the inspector.

See Heard on your own calls

A 30-minute call. Bring a recording of a real customer conversation and we will show you what the agent does with it.