Wait

What it does

Pauses the flow for a fixed number of seconds (a pause the caller hears as silence, or as whatever is still playing), then continues on Wait elapsed (wait.elapsed). The duration is rendered (a {{config.x}} template works) and clamped to 0.1-3600 seconds.

Nothing else routes out of a wait. If an agent answers a queued or ringing caller, the caller is bridged and the wait is simply abandoned; if the caller hangs up, the call is over and nothing on it runs. Older flows' call.bridged and call.hangup edges on this node are retired: put after-the-call logic under After the call ends. With Wait elapsed unwired the flow takes a plain next edge, else it ends.

Configuration

Pauses the flow for a fixed duration, then continues on "Wait elapsed". An agent answering a queued or ringing caller still interrupts it (the caller is bridged). Use it to express max-wait-then-fallback in a queue: enqueue → playAudio (loop) → wait → voicemail.

Outgoing events: wait.elapsed

Examples

Max-wait fallback in a queue

The wait fires after ten minutes; if an agent answers first, the caller is bridged and the wait never fires.

{
  "id": "max-wait",
  "type": "wait",
  "config": { "durationSecs": 600 },
  "on": {
    "wait.elapsed": "voicemail"
  }
}

Tiny gap between TTS and digit-collect

A two-second gap between a TTS prompt and the gatherDigits step gives the caller time to start speaking before the DTMF window opens.

{
  "id": "settle",
  "type": "wait",
  "config": { "durationSecs": 2 },
  "on": { "wait.elapsed": "collect-digits" }
}

Gotchas

• Duration is clamped to 0.1-3600 seconds. A value above 3600 is capped at one hour; chain waits for longer holds, or rethink the design.
• Only Wait elapsed routes. There is no hang-up or bridged edge: a bridged caller leaves the flow, and a hung-up call runs nothing more.