How to Switch Voice Agent Vendors Without Losing a Number or a Booking

Switching voice agent vendors is more migration project than software swap — and the difference shows up on cutover day. This episode walks through the exact sequence to move phone numbers, calendar connections, and live traffic without dropping a single booking.

Show Notes

Most teams treat a voice agent vendor switch like a software evaluation: compare features, run a demo, pick a winner. The episode "How to Switch Voice Agent Vendors Without Losing a Number or a Booking" argues that framing gets you into trouble fast. The real challenge isn't the product — it's the migration, and the migration is actually three separate decisions that have to happen in the right order. The vendor migration guide this episode is based on lays out exactly what those decisions are, and the episode walks through each one with the kind of operational detail that saves you a very bad cutover morning.

Here's what the episode covers:

• Port the number first, before anything else. The phone number is the one asset the losing vendor controls, and the porting clock is set by the losing carrier — not by you. Local numbers can move in as little as one business day once accepted, but rejections are common; the account name on your letter of authorization must match the billing record character for character. Toll-free numbers move through the Somos registry via a RespOrg change and can take up to 21 business days, making them the longest dependency in any migration.
• Rebuild the agent prompt — don't paste it. The routing rules, persona, business hours, and after-hours behavior are a half-day of writing on any modern platform. The old prompt carries the failure modes of the old vendor; rewriting from scratch is faster and cleaner than inheriting those assumptions. Building a voice agent from a clean brief produces a better result than porting a legacy configuration.
• Calendar and CRM reconnections are manual and can't be skipped. Every OAuth grant is scoped to the old vendor's client ID. The new vendor has to re-request consent with its own credentials, one account at a time. Skip this step and bookings simply don't land.
• Run a parallel week on a secondary line, not a hard cutover. Port a spare marketing or department number to the new agent first. Main line stays put. Measure booking completion rate, human handoff rate, and appropriate deflection rate across both agents against the same call mix before any traffic shifts.
• Export recordings and transcripts before cancelling. Most vendors delete everything within 30–90 days of account closure. Keep raw audio and structured outcome fields separately — a transcript has no value until the booking, callback request, or complaint has been extracted from it.
• Know what actually breaks on cutover day. Rarely the port itself. What breaks is downstream: calendar tokens go silent without alerting anyone, recording consent disclosures drop if the new agent isn't yet configured, and outbound caller ID shows "Unknown" for up to 72 hours while carrier name databases update. Each of these has a concrete fix — but only if you know to check.

If you're still evaluating vendors and haven't committed to one yet, the episode 14 Questions to Ask a Voice AI Vendor Before You Sign Anything is the right place to start before returning to this one. Both episodes are available wherever you listen to Phony.ai.

Phony.ai

What is Phony.ai?

AI phone and voice agents, explained through the constraints that actually decide whether one works: end-to-end latency and where it comes from, interruption and barge-in handling, telephony plumbing and call control, transfer design, and the disclosure and recording rules around automated calls.

Each episode takes one design decision and works through it concretely — provider-neutral, comparing approaches rather than selling one. Written for teams evaluating, buying or building voice AI who need to know what breaks before it breaks in production. Five or six minutes an episode.

Topics include end-to-end latency and where it comes from, barge-in and interruption handling, telephony and call control, transfer and escalation design, prompt and turn design, evaluation and call review, and disclosure, consent and recording rules.

Produced by Phony.ai, provider-neutral AI phone and voice agents. Full details, services and further reading at https://phony.ai