call flow builder

Design the call before writing the prompt.

Build a linear first version of the customer journey, reorder steps, and export it for engineering review. Keep policy decisions and human escape routes visible.

Step 1
Step 2
Step 3
Step 4
Step 5
Step 6

The shareable URL contains the step labels. Do not place customer data or credentials in a flow.

flow preview

Caller journey

  1. sayIdentify the business and reason for calling
  2. decisionCaller agrees to continue
  3. listenCollect the required details
  4. toolCheck CRM or booking availability
  5. transferTransfer when policy or caller asks
  6. endConfirm next step and end the call
diagram exportcall-flow.mmd
flowchart TD
  n0["Identify the business and reason for calling"]
  n1["Caller agrees to continue"]
  n2["Collect the required details"]
  n3["Check CRM or booking availability"]
  n4["Transfer when policy or caller asks"]
  n5["Confirm next step and end the call"]
  n0 --> n1
  n1 --> n2
  n2 --> n3
  n3 --> n4
  n4 --> n5

Attach a success condition and failure path to every tool

The linear flow is the review baseline. Production logic still needs timeouts, retry limits, invalid responses, tool failure, transfer failure, after-hours behavior, and a safe end state.