Short answer: Place a controlled test call, exercise each menu path (including no‑input and invalid input), and confirm the expected routing in Call Logs. Use the checklist and troubleshooting table below.
Glossary
DTMF: Keypad tones from digits 0–9, * and #.
Timeout (no input): Caller doesn’t press a key within the set time.
Invalid input: Caller presses a key that isn’t mapped to a menu option.
Number → Weekdays IVR → 1 Sales → Queue → Answered).Caption: Click Save to preview to move on to testing
Issue | Possible cause | Fix |
No call received | Device on Do Not Disturb, spam filter blocked, weak signal | Disable DND, whitelist the test caller, retry on a stable network |
Wrong routing | Menu option mapped to the wrong destination | Re‑check IVR mapping in the call flow; republish and retest |
Key press not detected | Wi‑Fi calling/VoIP interferes; noisy/low‑quality prompt masks tones | Turn off Wi‑Fi calling/VoIP for the test handset; upload a cleaner prompt at normal volume |
Region/time rules not applied | Overlapping rules or incorrect account time zone | Fix time zone; remove overlaps; ensure rule priority is unambiguous |
Loops/repeats endlessly | No max repeats or no operator escape configured | Set repeat count (e.g., 2–3) and add an Operator/Agent escape (e.g., 0 = Operator) |
Tip: If you use speech recognition, add a quiet room test and include synonyms (e.g., “Support,” “Help”).
Subject: IVR testing – routing checkAccount/Workspace: <name or ID>Service number: <DID>Defined schedule: <paste rules>Issue: <no input / wrong routing / timezone>Timestamps tested (IST): <YYYY‑MM‑DD HH:MM>Expected vs observed: <brief>Screenshots: <call logs / schedule / IVR mapping>