Skip to main content

Transitions: five kinds and their priority

Module goal: stop guessing why the dialog went the wrong way — and learn to read the transition evaluation order.
The evaluation order is fixed, and it is described in the tooltip next to the Transitions heading in the node inspector: Always → equation → prompt → Default. Equations are evaluated top to bottom, and the first true one wins — so the order of transitions in the list matters; you can drag them by ⋮⋮. The only thing checked before all of a node’s transitions is a global node with Check on every client turn enabled.
Pitfall: Default on a speaking node is deadThe classifier of a speaking node sees only prompt conditions. If the client says something unexpected, the node simply replies on its own and stays put — a Default without a timer never fires. Validation warns about this: “default edge of a speaking node never fires in dialogue (the fallback is STAY — the node generates its own reply)”. The behavior you need is set with a prompt condition or an equation, not with Default.
Three forms of the timerThe seconds live in the condition field (Waiting time, seconds), so the timer comes in three forms:
  • Timer — a separate transition “the client has been silent for N seconds”.
  • Prompt + timer — the transition fires on two inputs: “the client said this” or “the client stayed silent”. This is how you draw the scenario “pick a time… or just stay silent and I’ll call you back” with a single transition.
  • Default + timer — a fallback transition of a speaking node that fires when the client stays silent.
A timer cannot be set on Always or on an equation. If end-call-on-silence is enabled in the call settings, the node’s timer must be shorter than its threshold, otherwise publishing will fail.