Guides
Step-by-step guide to replacing your legacy IVR with a Thoughtly AI voice agent. Covers call forwarding, BYOC import, conversation flow design, compliance routing, CRM sync, and measuring conversion lift.
Last updated
If your business still routes callers through a touch-tone menu — press 1 for sales, press 2 for support — you're losing leads at the door. Legacy IVRIVRInteractive Voice Response — a phone menu system that routes callers using keypad or spoken inputs. AI agents often replace or augment rigid IVR trees. systems were built for call deflection, not conversion. They frustrate callers, drop qualified prospects into voicemail queues, and give you zero visibility into what happened on the call.
This guide walks through how to replace a legacy IVR with a Thoughtly AI voiceAI voiceAn artificially generated, natural-sounding voice produced by a TTS model. Thoughtly supports a library of AI voices and brand-specific cloning. agent that answers every call, qualifies intent in natural conversation, routes hot leads to the right human, and writes the outcome back to your CRMCRMThe system of record for leads, contacts, deals, and activity. Thoughtly reads from and writes to your CRM continuously. — all without ripping out your existing phone number.
We'll cover the three deployment paths (call forwarding, BYOC import, and new number), how to map your IVR menu structure to Thoughtly's node-based conversation flowConversation flowThe designed path an AI agent follows through greeting, intent capture, qualification, routing, objections, fallback, and next-step confirmation., how to handle compliance and after-hours routing, and how to measure whether the migration actually improved conversion.
Before starting the migration, make sure you have:
Before touching Thoughtly, build a complete inventory of what your IVR does today. This becomes the blueprint for your new agent.
Most legacy IVRs have accumulated dead branches, outdated extensions, and menu options that no longer map to real departments. Now is the time to prune. If a branch handles fewer than 5% of calls and doesn't serve a compliance purpose, consider folding it into a broader category that your AI agent can handle conversationally.
For example, a typical insurance agency IVR might have six menu options (new quote, existing policy, billing, claims, agent directory, after-hours). A Thoughtly agent can collapse all six into a single natural conversation: “Thanks for calling. How can I help you today?” — then use Variables and Outcomes to route based on what the caller actually says, not which button they pressed.
Thoughtly's Agent Builder uses a node-based canvas. Instead of a rigid menu tree, you build a conversation graph with four node types: Start, Speak, Transfer, and End. Outcomes route the conversation between nodes based on what the caller says.
Take your IVR inventory from Step 1 and translate it:
| Legacy IVR element | Thoughtly equivalent |
|---|---|
| Opening greeting + compliance disclaimer | Start node (spoken verbatim) |
| “Press 1 for X, press 2 for Y” menu | Speak (Prompt) node with prompt-based Outcomes |
| DTMF input collection | Variables (extract from natural speech) |
| Queue transfer to extension | Transfer node (Phone Router mode) |
| Voicemail box | End node + post-call Automation (Send SMS or email) |
| After-hours closed message | Time-based Automation trigger + Speak node with closed message |
| Recorded FAQ announcements | Genius knowledge base (retrieval-augmented answers) |
The key shift: instead of forcing callers into a menu, your agent asks an open question and uses prompt-based Outcomes to classify intent. Callers who would have pressed “1” for a new quote and callers who say “I want to get a quote” end up in the same branch — but the conversational path feels natural, not robotic.
Don't try to replicate every IVR branch as a separate node. Group related intents and let the agent's prompt handle variation. A single Speak node with well-written prompt instructions can handle “I need help with billing,” “I want to pay my bill,” and “What's my balance?” — all routes that would have been separate menu options in a legacy IVR.
Variables extract structured data from what the caller says, before outcomes evaluate. Outcomes then route the conversation based on those variables or on AI-classified intent.
For a typical high-consideration consumer funnel (insurance, mortgage, healthcare, legal), you'll want variables like:
intent — what the caller wants (new quote, existing account, billing, claims, etc.)call_reason — more specific classification for routingSet extraction instructions explicitly. Instead of “Get their contact info,” write: “Extract the caller's phone number in format +1-555-555-5555. If not provided, leave empty.” Vague extraction leads to empty variables and broken routing.
Use prompt-based outcomes when you need natural-language classification. Use rule-based outcomes when you're branching on extracted variables or action results.
Always include a default/fallbackFallbackA safe backup path used when the caller says something unexpected, an integration fails, or the agent cannot confidently complete the intended step. outcome. Without it, the agent gets stuck when it can't classify the caller's intent. The safest fallback is a transfer to a human — better to hand off than to loop indefinitely.
You have three options for pointing your existing phone traffic at the new Thoughtly agent. The right choice depends on how much control you want over the number and whether you can tolerate a brief cutover.
Keep your existing business number with your current carrierCarrierA telecommunications provider that routes phone calls and SMS over its network. Twilio, Telnyx, and Bandwidth are the three most common in the AI voice space. and configure it to forward all calls to a new Thoughtly phone number. This is the quickest path — no porting, no carrier changes, and you can roll back instantly by disabling forwarding.
If your numbers live in TwilioTwilioA cloud communications platform widely used as the carrier layer for voice and SMS. Thoughtly supports Twilio for inbound and outbound traffic. or TelnyxTelnyxA telecommunications provider competing with Twilio for cloud-native voice and SMS. Thoughtly supports Telnyx as a carrier., you can import them directly into Thoughtly using Bring Your Own Carrier. The number stays with your carrier account — Thoughtly just takes over the telephony layer.
Buy a fresh number from Thoughtly's number pool, assign it to your agent, and update your marketing materials, website, and listings. This gives you the cleanest setup but requires updating everywhere your number appears.
For most migrations, start with call forwarding (Option A) to validate the agent, then transition to BYOC import (Option B) for production. This gives you a rollback path and lets you fix agent issues before they affect every inbound call.
Legacy IVRs typically have a time-of-day rule that plays a closed message and routes to voicemail after hours. Thoughtly handles this through Automations with time-based triggers.
Your legacy IVR probably dumped calls into a voicemail box or a spreadsheet. Thoughtly's Automations framework lets you build a post-call workflowWorkflowAn automated, multi-step process — usually triggered by an event (form fill, new lead) and orchestrating one or more voice / SMS / email actions. that writes every conversation back to your CRM — automatically.
Use the On Call Completed triggerTriggerThe event or condition that starts an automated workflow, such as a new lead, missed call, CRM status change, calendar booking, or completed call. in Automations to:
The On Call Completed trigger can be scoped to a single agent, multiple agents, or all agents. For your migration, start with a single-agent scope so you can validate the workflow before extending it.
Don't flip the switch on your production number until you've tested the agent thoroughly. Thoughtly gives you two testing modes.
If the agent misroutes a call, check your Outcome labels for overlap. Prompt-based outcomes need clearly distinct descriptions — if two outcomes are too similar, the AI can't reliably tell them apart.
Once testing passes, it's time to point your production traffic at the new agent.
Keep your old IVR configuration documented and intact for at least 30 days. If something goes wrong, you need a rollback path — even if that means temporarily re-enabling the old menu.
Don't build a Thoughtly agent that says “Say 1 for sales, 2 for support.” The whole point of migrating is to replace menu navigation with natural conversation. Ask open-ended questions and let Outcomes handle the routing.
Every Speak node with Outcomes needs a default/fallback branch. Without it, the agent has nowhere to go when it can't classify the caller — and the call stalls. Always add a fallback that transfers to a human or takes a message.
“Get their info” is not an extraction instruction. Be specific: “Extract the caller's zip code as a 5-digit number. If not provided, leave empty.” The AI fills variables based on what you tell it to look for.
In testing, it's easy to focus on the qualification and scheduling flows. But the transfer path — handing a hot lead to a human rep — is the highest-stakes moment in the call. Test it with a real call every time.
Your sales reps are used to voicemail slips and call transfer notifications from the IVR. After migration, they'll get call summaries, CRM updates, and Slack notifications from Thoughtly. Brief them on what to expect, where to find transcripts, and how to handle warm transfers.
After 30 days, compare these metrics against your pre-migration baseline:
| Metric | What to measure | Target improvement |
|---|---|---|
| Call abandonment rate | Percentage of inbound calls that hang up before reaching a human or completing their goal | 30–50% reduction |
| Speed-to-lead | Time from inbound call to first meaningful contact (qualification, booking, or transfer) | Under 60 seconds for 100% of calls |
| Lead qualification rate | Percentage of inbound calls that result in a qualified lead, booked appointment, or useful outcome | 15–30% increase |
| After-hours coverage | Percentage of after-hours calls that receive a useful response vs. voicemail | 100% answered, 40%+ result in callback or booking |
| CRM data completeness | Percentage of calls with outcome, transcript, and variables written to CRM | 95%+ (vs. near-zero for legacy IVR) |
| Transfer accuracy | Percentage of transferred calls that reach the right person on the first try | 85%+ (vs. 50–70% for IVR directory transfer) |
Track these in Thoughtly's Analytics dashboard or export call data to Google Sheets via Automation. The biggest early wins are usually in after-hours coverageAfter-hours coverageHandling inbound calls outside of business hours. Thoughtly works 24/7, so prospects don't bounce to voicemail at 2am. and call abandonment — legacy IVRs lose a significant percentage of after-hours leads to voicemail, and an AI agent that answers and qualifies at 11 PM will capture calls that were previously lost.
Yes. You have three options: call forwarding (keep your number with your carrier and forward to a Thoughtly number), BYOC import (bring your Twilio or Telnyx number into Thoughtly while keeping it on your carrier account), or purchase a new number and update your listings. Call forwarding is the fastest and lowest-risk option for migration.
A straightforward migration — auditing your IVR, building the agent, testing, and cutover — typically takes 1–2 weeks. The agent build itself can be done in a day if your IVR map is clean. Budget more time for compliance review, CRM integration setup, and team training.
With call forwarding, there's no downtime — you enable forwarding and calls route to the Thoughtly agent immediately. With BYOC import, there's a brief window while the number transfers. Plan cutover for a low-traffic period (e.g., Sunday at 2 AM) and have your old IVR config documented as a rollback path.
Yes. Use prompt-based Outcomes to classify the caller's intent and route to the appropriate Speak node or Transfer node. A single agent can handle sales, support, billing, and general inquiries — the caller just says what they need instead of pressing a button.
No. BYOC import keeps your number on your existing Twilio or Telnyx account — Thoughtly just manages the telephony layer. Call forwarding keeps your number with whatever carrier you use. Porting is not required for any deployment path.