Introduction: Before you launch a Voice (IVR) flow, you should test it end-to-end to confirm callers hear the right prompts and can navigate menus correctly. RapidPro.app includes an IVR simulator so you can experience the call flow like a real caller and validate both the main path and edge cases (invalid input, fallbacks, retries).
Simulate your IVR end-to-end before going live
If you just need the essentials, follow this quick path:
- Open the Voice (IVR) flow you want to test
- Launch the IVR simulator from the flow editor
- Test the happy path + edge cases (invalid input, no input, fallbacks)
- Fix and re-test until every branch is connected and clear
A good simulation run catches routing issues before real callers experience them.
Step-by-Step Process
- Go to the Flows tab.
- Open the Voice (IVR) flow you want to test.
[CAPTURE: Flows list with a Voice (IVR) flow selected, opening the flow editor.]
- In the flow editor, find the simulator icon (often a green phone icon).
- Click the simulator icon to start the simulation.
[CAPTURE: Flow editor showing the green phone/simulator icon highlighted.]
During the simulation:
- Listen to the played messages (uploaded audio and/or TTS).
- Provide inputs like a caller:
- Press digits for menus (DTMF)
- Record audio when requested
- Test multiple paths, including:
- Valid menu choices
- Invalid choices (wrong digit)
- No input / timeout behavior (if your flow uses it)
[CAPTURE: Simulator running an IVR flow, showing a menu prompt and a keypad input step.]
- Adjust the flow where needed (messages, split rules, branch connections).
- Run the simulator again.
- Repeat until the full experience is clear and every exit path leads somewhere sensible.
[CAPTURE: Flow editor showing edits made, followed by a simulator re-run.]
Common Issues & Quick Fixes
I can’t find the IVR simulator icon
Fix:
- Confirm you are editing a Voice (IVR) / Phone Call flow (not a Messaging flow).
- Ensure the flow has at least one node (some interfaces show the simulator only after the first step exists).
The simulation doesn’t match what happens on real calls
Fix:
- Place a real test call after simulation (recommended for audio quality and network/provider behavior).
- Check Call Logs to compare real call outcomes with your expected routing.
Menu choices don’t route correctly in the simulator
Fix:
- Verify you’re using IVR split actions (Menu Selection / Multiple Digits / Audio), not messaging splits.
- Ensure every exit path is connected (including invalid input and fallbacks).