Events, jumps and notes

React to silence and time passing, keep a large graph readable, and document it for the next person who opens it.

Event

Fires on something that happens to the conversation rather than in it: silence, time passing, the call ending. Its outgoing edges are what happens then.

After 10 seconds of silence, say "Are you still there?"

Only Say, System Message and Tool Call — without arguments — can hang off an event, because events are carried out by the voice provider itself.

Jump

A stand-in for an edge to a distant node. It behaves exactly as that edge would, without a line dragged across the whole canvas.

An evaluation branch on the far right jumps back to the greeting state on the far left.

Note

An annotation for whoever opens the flow next. It does nothing at runtime — the assistant never sees it.

Legal asked for the recording notice here — do not remove without checking.

Scenario

One example journey through the graph, with its steps numbered in order. It records what a typical call looks like, in your words, so a reader can follow one path instead of working it out from every possible branch.

Tip

A graph with a few scenarios and notes is one a colleague can change safely. It is also where to write down why a branch exists.