LNP Number Porting Walkthrough for an AI Receptionist in 2026
By Sagar Shankaran, Founder of CallSphere
Porting an existing business line to a Twilio-backed AI receptionist takes 2 to 8 weeks, an LOA, and a CSR pull. Here is exactly what to expect, what blocks ports, and how to keep zero downtime during cutover.
Key takeaways
Most AI receptionist projects stall not on prompt design but on porting: the customer cannot lose their fifteen-year-old business number, the losing carrier drags the LOA, and the FOC date slips into the wrong week. Local Number Portability is a regulated FCC process, but the operational reality in 2026 is two to eight weeks, a battle over CSR data, and a quiet ten-day overlap window where both carriers technically own the number.
Background
Local Number Portability (LNP) is the FCC-mandated right of an end user to keep their phone number when changing carriers, codified in the Telecommunications Act of 1996. Twilio splits porting into two categories: standard LNP for US non-toll-free numbers (up to 1,000 per request via the Porting API) and toll-free porting (RespOrg change, separate workflow). A simple LNP port completes in 2 to 4 weeks; large or complex ports run 6 to 8 weeks. After the losing carrier releases the number, industry practice is a 10-day continued-service window before they fully cut service.
The Letter of Authorization (LOA) is the legal hook that lets the winning carrier pull the Customer Service Record (CSR) from the losing carrier. CSR mismatches (wrong billing address, missing suite number, business name vs DBA) are the single largest cause of port rejections in 2026. Twilio's Porting API generates an electronic LOA, sends it to the authorized representative for digital signature, and submits the request once signed.
Hear it before you finish reading
Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.
Steps and config
flowchart TD
A[Customer signs LOA] --> B[Twilio submits port-in request]
B --> C[Losing carrier validates CSR]
C -->|Match| D[FOC date issued]
C -->|Mismatch| E[Reject - fix CSR data]
E --> B
D --> F[Cutover at FOC]
F --> G[Number live on Twilio]
G --> H[10-day overlap window]
H --> I[Old service terminated]The FOC (Firm Order Commitment) date is set by the losing carrier and is the moment the number actually moves. Schedule cutover for off-hours or low-call windows; once FOC fires, calls route to your new carrier within minutes.
CallSphere implementation
Explore a live demo and compare current plans to find the right fit for your business.
Build steps
- Pull the customer's most recent phone bill and CSR; verify name, address, and number list match exactly.
- Generate the LOA via Twilio Porting API or upload your own; collect digital signature from the authorized representative.
- Submit the port-in request; Twilio queues it with the losing carrier and waits for FOC.
- Configure a temporary Twilio number on the AI receptionist for the trial period; route inbound to your FastAPI bridge.
- On FOC date, swap the Voice URL on the ported number to point at the same bridge.
- Test the ported number from an outside line within 30 minutes of cutover; verify SIP signaling and AI greeting.
- Notify the losing carrier in writing once cutover succeeds; do not cancel until day 11 to avoid breaking the overlap window.
- Update CRM, Google Business Profile, and any printed materials to confirm the number is live on the new platform.
FAQ
How long does an LNP port really take? Simple residential or single-line business: 2 to 4 weeks. Multi-location or PRI-backed numbers: 6 to 8 weeks. Toll-free RespOrg changes: separate workflow, typically 4 to 7 business days.
What blocks a port the most? CSR mismatches. The address on file at the losing carrier must match the LOA exactly, including suite number and DBA spelling. Pull the bill, copy verbatim.
Still reading? Stop comparing — try CallSphere live.
CallSphere ships complete AI voice agents per industry — 14 tools for healthcare, 10 agents for real estate, 4 specialists for salons. See how it actually handles a call before you book a demo.
Can I keep the number live during the port? Yes. The losing carrier continues service until FOC; after FOC, the winning carrier takes over. There is no dark window if you cut DNS or call routing at the same minute.
What if the losing carrier rejects the port? Common reasons: pending account changes, unpaid balance, contract lock-in, mismatched authorized contact. Fix the underlying issue and resubmit; the FCC requires the losing carrier to provide a specific rejection reason.
Does CallSphere charge for port-ins? Twilio passes through carrier port fees ($1 to $15 per number depending on type); CallSphere does not add a markup on any plan. White-glove port assistance is included.
Sources
- Twilio Guidelines for Porting
- Port phone numbers using Twilio APIs
- Twilio Porting API Reference
- How to port a phone number to Twilio - Help Center
Explore a live demo and compare current plans to find the right fit for your business.
Written by
Sagar Shankaran· Founder, CallSphere
LinkedInSagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
Try CallSphere AI Voice Agents
See how AI voice agents work for your industry. Live demo available -- no signup required.
