How to Port a Phone Number to Your Voice Agent
You already have a phone number that customers know. Your main line, published on your website, business cards, Google. You can't afford to change it.
You already have a phone number that customers know. Your main line, published on your website, business cards, Google. You can't afford to change it. Porting that number to a voice-AI-friendly carrier so your agent can answer it is the standard migration path for most businesses deploying voice AI. The process takes about 2 weeks, requires specific paperwork, and has a handful of gotchas that cause delays. This piece walks through it.
TL;DR
- Number porting is the process of moving a phone number from one carrier to another.
- Timeline: 5โ15 business days typically. Local numbers faster than toll-free.
- Required: LOA (Letter of Authorization), recent phone bill, account info from losing carrier.
- Watch for porting delays and temporary call-routing issues during transition.
- Plan the cutover to minimize downtime.
Why port
Alternatives to porting:
- Forward from your existing number to a new voice-AI number. Simpler but loses features (number display, SMS ownership).
- Get a new number and use both. Confuses customers.
- Port. Clean. Number moves entirely.
For production deployments, porting is usually the right call.
The process
Simplified steps:
- Choose your new carrier. The one your voice AI vendor uses (Twilio, Bandwidth, etc.).
- Gather info:
- Current carrier's name.
- Current carrier's account number.
- Current carrier's PIN/password (may require contacting them).
- Recent phone bill (showing the number and account name).
- Signed LOA.
- Submit port request. Through your new carrier's portal.
- Wait. Losing carrier reviews, approves, or rejects.
- Cutover. Number activates on new carrier.
- Test. Verify inbound calls reach your voice AI.
- Close old account. Once porting complete.
Timeline
- Local 10-digit numbers: 5โ10 business days.
- Toll-free numbers: 7โ15 business days (sometimes longer).
- International: highly variable, can be 30+ days.
Build the timeline into your deployment plan. Don't commit to "live next week" if porting is on the critical path.
The LOA
Letter of Authorization. You sign it to authorize the new carrier to pull the number.
Requirements:
- Company name and address matching current carrier records.
- Phone number being ported.
- Authorized signer's name and title.
- Date.
Your new carrier provides the template.
Common rejection reasons
- Info mismatch. Company name on LOA doesn't match losing carrier's records. Even minor differences (LLC vs Inc.) trigger rejection.
- Account number wrong. Not the phone number โ the account number from the losing carrier.
- PIN wrong. Some carriers require a PIN; you may need to contact them to set/reset.
- Recent changes. Porting blocked if the account was recently changed (e.g., new owner, recent billing change).
- Pending balance. Unpaid bills can block porting.
Fix and resubmit. First submission often bounces.
Pre-port preparation
A week before submitting:
- Verify account details with your losing carrier.
- Set up number on new carrier so it's ready to activate (configurations, voice endpoint).
- Plan cutover time. Off-hours to minimize business impact.
- Notify internal stakeholders. Reception, sales, etc.
- Backup plan. If porting delays, what's your communication?
The cutover window
When your number actually moves:
- Losing carrier releases the number.
- Winning carrier activates it.
- Brief window (minutes to hours) where calls may not route reliably.
- Full propagation across carriers can take 24โ48 hours.
Schedule cutover off-hours if possible. Have a message ready if customers report issues.
Post-port verification
- Inbound calls reach voice AI. Test from a different network.
- Caller ID displays correctly.
- SMS works (if applicable; may require separate A2P registration with new carrier).
- 911 services. Ensure E911 registration is correct on new carrier.
- Fax services (if applicable; separate consideration).
SMS considerations
Porting a number that sends SMS requires:
- A2P 10DLC re-registration on new carrier.
- May have a gap in SMS capability during transition.
- Customers expecting SMS from that number may have delayed delivery briefly.
Plan for this. See A2P 10DLC explained for voice agent builders.
Toll-free specifics
Toll-free porting is slower and more finicky:
- RespOrg (Responsible Organization) change is the mechanism.
- Specific rules per toll-free prefix.
- Re-verification often required.
Budget more time.
Emergency porting
Sometimes you need to port fast (compromised account, lost access):
- Expedited porting options exist with some carriers.
- Additional fees typically.
- Still 1โ3 business days minimum.
Not a regular option; for emergencies only.
Porting out (if you leave)
If you ever leave your voice AI vendor, you can port out:
- Same process, reversed.
- You own the number; vendor must cooperate.
- Don't let vendor lock โ ensure contract allows number portability.
This is a BYO Twilio advantage โ the number is in your Twilio account, fully portable.
Multiple number porting
For large operations porting many numbers:
- Batch porting available with most carriers.
- Submit a CSV of numbers + LOAs.
- Timelines extend with volume.
- Stagger cutover for critical numbers.
Common pitfalls
Setting up voice AI only after porting. Number goes live on new carrier pointing to... nothing. Calls fail. Set up first, then port.
Not testing post-port. Assume it works without verifying. Customers discover issues before you do.
Forgetting about SMS. Voice works; SMS doesn't. Missed the A2P registration.
Ignoring billing overlap. Old carrier charges through end of billing cycle. Factor in.
Losing carrier pushback. They may try to "retain" you. Be firm.
Working with your vendor
Your voice AI vendor (or Twilio, etc.) should guide:
- Pre-porting checklist.
- LOA preparation.
- Submission.
- Coordination during cutover.
- Post-port verification.
Good vendors make this painless. Bad vendors leave you holding the bag.
Related reading
- Sending SMS Follow-Ups from Voice Agents
- Twilio + Voice Agents: A Complete Guide
- Sending Voice Agent Transcripts to Slack
- Connecting Voice Agents to Snowflake or BigQuery
- Setting Up Toll-Free Verification for AI Calling
FAQ
Can I port any number? Most US numbers, yes. Some legacy PBX setups or specialty numbers have restrictions.
Does porting cost anything? Usually a small fee ($5โ$25) per number. Some carriers waive.
Can I keep my existing number with my existing carrier and add a new one? Yes. Forward from old to new, or run both. Simpler short-term, adds complexity long-term.
What if porting fails? Losing carrier rejects โ new carrier tells you why โ fix and resubmit. Not permanent.
Can I port a number back later? Yes โ porting is bidirectional. The number follows the owner, not the carrier.

Tyler Weitzman is co-founder and Head of AI at Speechify. He has spent the past decade building the speech-synthesis stack that powers millions of users. Tyler writes about the engineering of real-time conversational systems โ text-to-speech, speech recognition, latency budgets, model serving, and the architectural choices that separate prototypes from production-grade voice agents.
More from Tyler Weitzman
View all โOpen-Source vs Proprietary Voice Agent Stacks
The open-source voice AI stack in 2026 is genuinely good. Whisper and its derivatives handle STT. Open-weight LLMs like Llama 3/4, Qwen, Mistral handle the reasoning. Open-source TTS (XTTS, StyleTTS, Orpheus-class) handles output.
Build vs Buy: When to Build Your Own Voice Agent
Build-vs-buy for voice agents in 2026 is a different conversation than it was two years ago. Then, the open-source stack was rough and most serious deployments ended up building.
Voice Agents for Developer Support
Developer support is a strange category. Developers don't generally want to call anyone. They want Stack Overflow, they want clear docs, they want an LLM that can read their code.
Related reading
Sending SMS Follow-Ups from Voice Agents
SMS follow-ups are one of the highest-ROI additions to any voice agent deployment. The caller just had a conversation; they know the appointment time, the tracking link, the next step. But people forget.
Sending Voice Agent Transcripts to Slack
Slack is where most teams live in 2026, and for voice agent deployments, getting call transcripts and key events into Slack closes a critical ops loop. Escalations land in the right channel with context. QA reviews happen where the team already works.
Connecting Voice Agents to Snowflake or BigQuery
Voice agent deployments generate a lot of data. Every call produces a transcript, metadata (duration, outcome, caller info), function-call traces, sentiment signals, and operational metrics.
Voice AI, twice a month.
Get the best of the SIMBA resources hub โ new articles, trend notes, and operator guides. No spam.
