⚡Quick answer -
Nine times out of ten, the wrong IVR plays because either
(a) The DID is mapped to a different call-flow or
(b) The live call-flow was edited but not published.
Check Manage → DIDs for the exact call-flow, edit that flow, update the audio file, then click Save → Publish. New prompts take 2-5 minutes to propagate.
Use these steps if callers report hearing an outdated greeting, language, or after-hours message on any service number.
• Admin rights to Manage and Design Call-flow
• Exact DID/toll-free number callers dial
• Correct audio file ready (MP3, mono, ≤ 128 kbps; e.g., Main_IVR_EN_v3.mp3)
• You edit a draft instead of the live flow
• You forget to publish changes
Expected result: Correct IVR plays in all scenarios, and Call Logs show the intended call flow.
• Edited the flow actually mapped to this DID?
• Clicked Publish (not only Save)?
• Dialing the same DID you checked?
• Time-based rule sending after-hours to another IVR?
• Audio file unsupported? Re-encode to MP3 mono ≤ 128 kbps.
Issue | Cause | Fix |
Multiple DIDs with similar names | Edited Flow A; callers dial DID for Flow B | Repeat Steps 1-2 for the correct DID |
Missing language file | System falls back to the default prompt | Upload audio for each language node |
Draft vs Live | Changed draft only | Publish or switch to live flow |
Forwarding from personal line | Calls bypass IVR | Ensure the forwarding destination is the correct DID |
Keywords: wrong IVR, call-flow mapping, publish call-flow, MyOperator IVR troubleshooting