IVR Explorer / Phone menu migration
Know your phone menu.
Then move beyond it.
Before replacing “press 1,” understand where it takes your callers. Map the paths, review the gaps, and prepare a more useful conversation.
Explore the exampleNo signup. No call. No credits used.
Try the map
Follow a caller’s path.
Select a branch to see the menu evidence and the decisions a replacement needs.
Choose a menu option
A captured prompt is evidence, not a verified business outcome.
Request a service
Example menu prompt
“For a new service request, press 1. For an existing appointment, press 2.”
What this tells you
A caller must choose new service or an existing appointment before describing what they need.
Which service areas and job types can the team accept? Who handles an existing appointment?
From a phone tree to a plan.
- 01 / Discover
Map your current menu
Start an authorized, funded exploration in your workspace. Burki attempts menu paths within the configured limits.
- 02 / Review
Keep evidence and gaps visible
Review discovered prompts and routes. Correct the map and resolve missing policies with the people who know your business.
- 03 / Rebuild
Prepare your assistant
Approve the map and create an editable replacement. Connect its actions and test the conversation before moving real callers.
Your phone system, next
Bring a menu you’re
ready to improve.
Real exploration makes telephone calls. You’ll need prepaid funds, an active supported number and permission to test the destination.
Understand usage and phone chargesMap your current phone tree
New explorations require a signed-in account with prepaid funds. Opening the workspace does not start a call.
Browser practice and telephone exploration are separate. Review your account setup before starting a real exploration.
Before you map.
Is this example a live phone call?
No. The interactive example is an illustrative home-services menu. It makes no calls, uses no credits and contains no customer data. Real exploration starts separately in your workspace.
What do I need to map my own IVR?
A Burki account with prepaid funds, an active supported phone number in your organization, and permission to test the destination. Route, provider and budget checks must pass before exploration starts. Browser trial time does not cover telephone exploration.
Will it find every menu option?
Not necessarily. Exploration is bounded by its configured depth, time and budget. Queues, changing menus, speech-only branches and authentication can leave paths unresolved. Review the map and verify missing behavior with your team.
Does converting a map replace my phone system?
No. Approve the map before creating an editable assistant or workflow. Review the instructions, configure the necessary actions and test the result before assigning a number or routing customer calls. A menu map cannot supply missing business policies or integration credentials.