Number Porting (LNP) for AI Receptionist Setups Across Countries in 2026

AI receptionists fail their first business test when the customer cannot keep their existing main line. Local Number Portability (LNP) is the lifeline; the 2026 cross-country reality is that paperwork, not technology, is what ports succeed or fail on.

What the rule says

flowchart TD
  Out[Outbound campaign] --> Twilio[Twilio Voice API]
  Twilio --> STIR[STIR/SHAKEN attestation]
  STIR --> Carrier[Originating carrier]
  Carrier --> Term[Terminating carrier]
  Term --> Recipient[Recipient phone]
  Recipient --> Webhook[/voice webhook/]
  Webhook --> Agent[AI sales agent]

Local Number Portability (LNP) is a customer right (US Telecommunications Act of 1996, FCC LNP order; UK Communications Act 2003 / Ofcom General Conditions; Australia Telecommunications Numbering Plan 2015; Canada CRTC LNP rules; EU Universal Service Directive Article 30). Each jurisdiction sets its own SLA for porting and its own paperwork. In the US, simple ports of single landline or mobile numbers must complete in one business day under the FCC's Porting Order; complex ports of large blocks or hosted numbers can take 7-15 business days. In the UK, single number ports complete in one business day under Ofcom's GC-C6. In Australia, Cat-A porting (simple) is one business day; Cat-C (complex) is up to five. India requires a UPC code through the losing carrier and a 4-7 day process. Cross-country porting (e.g., US to UK) is generally not possible; numbers stay in their country of origin.

What it means for AI voice agent operators

Three operational realities define LNP for AI receptionist deployments:

First, the Letter of Authorization (LOA) is where ports die. The LOA must match the losing carrier's CSR (Customer Service Record) exactly: business name, billing address, BTN (billing telephone number), phone numbers in the port. A typo in the suite number kills a port; a misspelled DBA name kills a port. CallSphere's experience across 50+ business deployments: 70% of failed ports are LOA mismatches.

Second, you cannot make changes during the port. No carrier changes, no service changes, no address changes during the porting window. Lock the configuration and wait.

Third, there is always a brief outage risk on cutover. AI receptionist deployments should provision a temporary forwarding number that the AI answers, then port the main number on a low-traffic morning. Most US ports complete by 9-10am ET if scheduled the night before.

For multi-country setups, you cannot port a number across borders. A UK +44 stays UK; a US +1 stays US. Build your AI receptionist routing layer accordingly: per-country DIDs in each carrier, joined to one AI brain through SIP forking or a routing rule.

How CallSphere stays compliant

CallSphere ports incoming customer numbers into Twilio across all six verticals. The onboarding flow auto-generates the LOA from the customer's CSR-matched data, validates the BTN, and submits through Twilio's Hosted Number / Port-In API. We schedule cutover for 7am local time, route to a parallel AI-answered temp number for the cutover window, and verify A-level STIR/SHAKEN signing on the ported number within 24 hours of port completion. For multi-country customers, we maintain Twilio sub-accounts per country and a unified SIP-trunk routing layer so the AI brain (OpenAI Realtime via SIP) is one resource, while the numbers stay sovereign. Healthcare AI customers porting from legacy PBXs add a 14-day parallel-run window for dual-routing. With a 14-day trial, customers can test with a Twilio-issued number first and port their main line only when comfortable.

Compliance checklist

1. Pull the losing carrier's CSR before drafting the LOA.
2. Match LOA fields character-for-character: business name, address, BTN, port numbers.
3. Do not change carrier, address, or service during the porting window.
4. Schedule cutover during a low-traffic window; plan for a 30-minute outage.
5. Provision a temporary forwarding number that the AI answers during cutover.
6. Verify e911 records reattach to the new carrier post-port (Kari's Law / RAY BAUM).
7. Verify STIR/SHAKEN attestation A signing within 24 hours of port completion.
8. Update SMS A2P 10DLC bindings if the ported number was used for SMS.
9. Notify the existing carrier of the port; do not cancel service early (kills the port).
10. Test inbound and outbound on the ported number before deactivating fallback.
11. Retain the completed LOA and port confirmation for at least two years.
12. For multi-country, maintain per-country sub-accounts and a unified routing layer.

FAQ

Can I port a US number to a UK carrier? No. LNP is geographically scoped; numbers do not cross borders. Provision per-country DIDs and route through one AI backend.

How fast is porting in the US in 2026? Simple landline or mobile ports complete in one business day per FCC rules. Complex ports (PRI, hosted PBX, multi-number) can take 7-15 days.

What if the losing carrier rejects the port? Common rejections: BTN mismatch, account in non-current status, name mismatch, address mismatch. Fix the discrepancy on the LOA and resubmit.

Do I lose voicemail on porting? Yes. Set up new voicemail on the new carrier or the AI receptionist. Notify customers in advance.

Does porting break STIR/SHAKEN? Briefly. Re-bind the number to the new carrier's trust profile post-port; A-level signing returns within 24 hours typically.

Sources

• FCC: Local Number Portability
• Ofcom: Number Portability General Conditions
• Twilio: Hosted Number / Port-In Documentation

Start a 14-day trial with port-in support, see pricing, or contact us for help.