IVR Node: Caller Input

The Caller input node (CallerInput type) plays a prompt and then waits for the caller to enter a multi-digit sequence, ending with a specific key (default #) or on timeout. The captured value is stored in a variable so other nodes (Branch, Condition) can use it downstream.

Unlike Wait DTMF, which only reads a single digit for a menu choice, Caller input is built for longer sequences: ID numbers, order numbers, account numbers, verification codes, and so on.

Configuration

• Prompt: the text/audio played before waiting for input.
• Min digits / Max digits: the accepted length range for the sequence.
• Terminator (1 char): the key the caller presses to signal they're done entering digits. Defaults to #.
• Timeout (seconds): how long to wait before treating it as no response.
• Store in variable: the name of the variable where the captured sequence is stored, for later use in a Branch or Condition node.

Example

A collections flow asks for the customer's ID number: "Enter your ID number followed by the pound key", with Min digits = 10, Max digits = 10, Terminator = #, Timeout = 15 seconds, and Store in variable = customer_id. A downstream HTTP request node uses ${customer_id} to look up the account status in your system.

Tips

• Pick a descriptive variable name (e.g., customer_id, order_number) — you'll need to type it exactly, character for character, in whatever node reads it later (Branch uses "From variable"; Condition references the variable directly in its expression).
• If "Min digits" is greater than "Max digits", the flow is misconfigured — check the range before publishing.

Troubleshooting

If the flow doesn't react after the caller enters the number, check whether they pressed the terminator key (# by default) — without it, the node only advances once it hits "Max digits" or the timeout expires.