Skip to main content
The Press Digit Node is used to navigate through IVR (Interactive Voice Response) systems. Instead of speaking, the agent evaluates whether it should press a digit and determines which specific digit to press.
The agent stays silent and only presses digits. While in this node, the agent never speaks. It only listens to the IVR and presses the right digit.One node can navigate multiple IVR menus. The Press Digit Node doesn’t stop after a single digit press. It stays active and keeps navigating through multiple menus until a transition condition is met.
The node evaluates whether to press a digit each time the phone menu finishes speaking. This timing is also affected by the Pause Detection Delay setting. If a digit press is needed, the agent will infer the appropriate digit and press it. Example: To reach billing in English, the agent can press 1 at a language menu (“Press 1 for English, 2 for French”), then press 2 at the department menu (“Press 1 for Support, 2 for Billing, 3 for Reception”). Both selections happen within the same Press Digit Node. The node can enter a sequence of keys, such as an extension or account number, and can press # and *.
Press digit settings for an existing IVR navigation node, with instructions for choosing a department and Pause Detection Delay set to 1000 milliseconds.

Configure instructions and pause detection in Press digit settings.

When to use it

Place the node where an outbound call is expected to reach an automated phone menu. Once the agent reaches its destination, for example a live person in billing, a transition moves the call to the next node, such as a conversation node that talks to the person or a transfer. Start → Press Digit Node (navigate to billing) → Conversation node (talk to billing agent) If a live person answers, what happens next depends on your transition conditions. Write one that covers reaching a person so the call moves on.

Configure Press Digit Behavior

1

Set up IVR Navigation Instructions

Select the node, open Node settings, and expand Press digit settings. Provide clear instructions so the agent knows whether and what digit to press. Include keywords or phrases to listen for, as well as which ones to avoid.Sample prompt:
2

Configure Pause Detection Delay

Some IVR systems speak slowly, so to make sure the agent does not make any decision prematurely, set Pause Detection Delay so the whole menu is captured. We recommend 1000 ms (1 second).
3

Configure Transitions

Transition conditions are checked each time the phone menu finishes speaking. If none match, the agent stays in the node and handles the next menu. When writing your transitions, ensure you cover both successful navigation and potential failure scenarios or edge cases.Success scenario: Define when the agent has successfully navigated to the target. Set the success condition to the final destination, such as Reached the billing department or Connected to a live person in billing, rather than the first digit press. This keeps the node navigating subsequent menus until it reaches that goal. If the digit press was correct, the IVR response will confirm this.Edge cases: Cover scenarios like getting stuck in loops. For example, write conditions like Menu repeated 3 times to handle repetitive menus.Example transition conditions:

Other node settings

  • Global Node: read more at Global Node
  • LLM: Choose a different model for this node. This model decides whether to press a digit and which one.
  • Fine-tuning examples: Add example conversations to train your AI agent how to handle specific scenarios. Read more at finetune examples.