IVR Split Logic: Menu Options and Keypad Selection

Voice (IVR) flows use keypad input and audio recordings instead of text replies. To support this interaction style, IVR flows rely on specialized Split Actions designed for phone calls. This guide explains the three main IVR-specific split actions and how to use them to collect input and route callers correctly.

Route callers using IVR-specific split actions

If you just need the essentials, follow this quick path:

  1. Understand how IVR splits differ from messaging splits
  2. Use Wait for Menu Selection for single-digit choices
  3. Use Wait for Multiple Digits for numeric input
  4. Use Wait for Audio to record voice messages
  5. Review and replay recorded audio

These patterns ensure callers are routed correctly during a live phone call.

Step-by-Step Process

1
Understand how IVR splits differ from messaging splits

In Voice (IVR) flows, contacts respond using:

  • Keypad digits (DTMF)
  • Voice recordings

Standard text-based split actions are not available. Only IVR-compatible split actions appear in the editor.

⚙️
Technical Detail: IVR Split Actions are optimized for synchronous phone interactions and real-time input during a call.

2
Use “Wait for Menu Selection”

Goal: Let callers choose from a menu using a single keypad digit.

  • Supports up to 10 options (digits 0–9)
  • Each option maps to one key
  • Routes callers based on the digit pressed

Example prompt:

“To make a deposit, press 1. To update your card details, press 2. To cancel your last deposit, press 3. To speak with a representative, press 4. To replay this message, press 5.”

  1. Add a Wait for Menu Selection split action.
  2. Enter labels for each menu option.
  3. (Recommended) Set a result name.
  4. Connect each option to the next step.
⚙️
Technical Detail: If you define a result name (for example menu_choice), you can reference it later as @results.menu_choice.

💡
Tip: Keep menus short and explicit to reduce call duration and confusion.

3
Use “Wait for Multiple Digits”

Goal: Collect structured numeric input such as IDs or reference numbers.

  • Collects multiple digits via keypad
  • Caller must press # to submit
  • Supports validation rules

Example prompt: “Please enter your member ID number, followed by the pound key.”

  1. Add a Wait for Multiple Digits split action.
  2. Select validation rules (length, pattern, starts with).
  3. Assign a result name to store the value.
  4. Route valid and invalid inputs.
💡
Tip: Validation rules prevent incorrect input and reduce follow-up calls.

4
Use “Wait for Audio”

Goal: Record a voice message from the caller.

  • Plays a beep
  • Records the caller’s voice
  • Saves the recording as a flow result

Common use cases include feedback collection, open-ended responses, and voicemail-style messages.

  1. Add a Play Message explaining what the caller should say.
  2. Add a Wait for Audio split action.
  3. Save the recording as a result.
⚙️
Technical Detail: Voice recordings are stored as links in flow results and exports. They are not transcribed automatically.

5
Review and replay voice recordings

You can listen to recorded audio from:

  • The flow’s Results page
  • The contact profile (phone icon next to “Made a recording”)
  • Exported results (open the recording URL)
⚠️
Warning: Voice recordings may contain sensitive data. Handle links and exports according to your data protection policies.

Common Issues & Quick Fixes

Menu selection does not route correctly
  • Confirm each option is connected.
  • Ensure prompts clearly explain which digit to press.
  • Avoid duplicate or empty menu entries.
Multiple digit input is rejected
  • Check validation rules.
  • Confirm callers press # to submit.
  • Add a fallback for invalid input.
No audio is recorded
  • Use Wait for Audio, not messaging splits.
  • Confirm the caller hears the beep.
  • Check Call Logs for dropped calls.
Callers get stuck in a split
  • Ensure all branches are connected.
  • Configure retries or timeouts.
  • Provide a clear exit or handoff.