Overview
Moving a business number to Twilio changes its carrier. It does not by itself establish that the number reaches the right answering workflow. Use a number-by-number acceptance record so an administrative status cannot hide a missing business line. This guide covers planning around Twilio’s documented US non-toll-free Porting API process, which is in public beta.
Separate the number move from the answering-service change
List each public business number, its current carrier, the person authorized to approve its transfer, and the intended destination after the move. Include secondary numbers used on advertisements or branch listings; a successful main-number test says nothing about those lines.
If only the answering destination is changing, ask the phone administrator whether existing routing can support that change without a carrier transfer. Confirm portability and the applicable process with the receiving provider before making the launch dependent on moving a number.
Use individual number status as the acceptance record
Twilio distinguishes the overall port request from the status of each number. Its documentation defines a completed request as one whose numbers have either ported or been canceled. Therefore, inspect every intended number instead of treating the request’s completed label as proof that all lines transferred.
- Record the business purpose, requested outcome, current number status, and owner for each line.
- Treat an intentionally canceled number as a documented scope change, not a successful transfer.
- Keep rejected or pending numbers open in the business migration record until their disposition is confirmed.
Resolve the actual rejection before resubmitting
Twilio’s US guidelines identify mismatched name or address information as a common rejection cause and note that a carrier may require a PIN. Ask the authorized account owner to verify the relevant carrier records rather than repeatedly submitting guessed corrections. Share account documents through the provider’s approved private process.
Keep the rejection reason and corrective action together. In the API workflow, unaffected numbers may continue while another number is rejected; coordinate any revised plan with the administrator so staff know which lines remain on the prior service.
Keep messaging in the cutover plan
Twilio’s Porting and Hosting Numbers documentation states that porting transfers both voice and messaging capabilities. Before moving a line advertised for calls and texts, identify the messaging application and staff inbox that must receive those texts after the transfer. Do not assume that the previous inbox continues handling the number.
For a business that uses messaging, agree a permitted test with the administrator: send an inbound text, locate it in the intended inbox, and verify a reply reaches the test recipient through the configured workflow. Keep the voice result and messaging result separate. If either is unresolved, give the business owner that specific limitation before they announce the cutover as complete.
Verify the caller journey after the transfer
For each transferred line, make an authorized test call and record the greeting, destination, and resulting message or handoff. Test the intended open-hours and closed-hours paths separately. If the number also carries messaging, assign a separate messaging acceptance check; hearing the correct greeting does not prove texts work.
Ask the carrier and phone administrator how to handle a failed cutover before it occurs. Do not assume changing a forwarding setting reverses a carrier transfer. Close the migration only when each required number has both a confirmed transfer outcome and an accepted service test.
