The number on your website can move onto a Twilio account. After Twilio finishes that move, you can answer it on the Android phone you already carry. The move and the answering are two different jobs.
Twilio's port-in guide (checked 15 Nov 2026) says porting keeps your number and moves its messaging and voice to Twilio. Twilio becomes the carrier for that number. That page documents the Porting API, which Twilio marks as public beta. The page says beta details can change and beta products have no service level agreement. The Console path is on the US porting guidelines and in the help article linked below.
ReachTo does not submit a port, sign a letter of authorization, or contact your current carrier. It is an Android softphone for numbers already in your own Twilio account. It is $1 a month with that account, or pay as you go with a prepaid wallet. iOS is coming soon. When the number shows up in the Twilio account, you connect that account in the app and answer there. The connection steps are in how to use a Twilio phone number on mobile.
Check that the number can move
The port-in guide says to use the Portability Checker in the Twilio Console before you start. Type the number. No code. The same page points at a Portability API, also in public beta, if you want to check from code.
The United States porting guidelines (checked 15 Nov 2026) say these numbers are portable: geographic local numbers (mobile, VoIP, and landline) and toll-free numbers. Most numbers can move. In rare cases Twilio does not have geographic coverage for a number and cannot port it.
That page also says most mobile operators require the account number and a PIN, and some providers require a PIN to port out. Ask the current provider whether a PIN is required, and include it if it is.
The Console path and the API path do not accept the same numbers. The guidelines say you submit in the Twilio Console, with a maximum of 1,000 numbers per port, and toll-free is on the portable list. The port-in guide says the Porting API creates a request for US non-toll-free numbers, up to 1,000 per request. The PortIn resource (checked 15 Nov 2026) says the country available is the United States, the supported types are landline and mobile, and toll-free is not supported. It also says you must upload a utility bill before you submit, and that this API does not move an existing Twilio number from one Twilio account to another.
If the number is toll-free, follow the Console path on the guidelines page. Do not assume the Porting API will take it.
What you have to send
The US guidelines list the required information:
- A letter of authorization (LOA).
- The name and address that match the Customer Service Record (CSR).
- A copy of a phone bill dated within the last 30 days.
- The current provider's account number.
- A PIN, if the current provider requires one.
The same page says the most common rejection is a wrong name or a wrong address. Ask the current provider for the name and address on the CSR before you type them. The page also says these guidelines are not legal advice.
Twilio's help article How to Port a Phone Number to Twilio (checked 15 Nov 2026) is the Console walkthrough for a US number. It says a request needs:
- The authorized user or owner's first and last name.
- The service address. It has to be a physical address. A PO Box is not valid.
- An LOA signed by the authorized user or the owner. The name and the service address on the LOA have to match what the current carrier has on file. The article links a US LOA PDF.
- A Customer Service Record.
- A phone bill from the last 30 days that shows the account, the owner or authorized user, and the address, for every number in the request.
On the API path you do not write that PDF yourself. The port-in guide says Twilio builds an electronic LOA from the request and emails it to the authorized representative to sign. The PortIn resource says one LOA can cover every number in that single request. The email has to belong to the person named as the authorized representative. For a mobile number, the PIN field is mandatory. For a US local number, the account number is mandatory. The address has to match the address on the losing carrier's account. Customer type is Individual or Business.
The port-in guide's status table says the authorized representative has 30 days to sign. If they do not, Twilio cancels the request.
How long Twilio says it takes
Twilio's own pages do not all give the same figure. Use the number from the page that matches the path you are on, and plan for a rejection to add time. None of these is a promise from ReachTo.
- The US guidelines: once all required information is in, a standard port typically lasts from 5 to 15 days, and it can take up to 4 weeks or longer if the current provider rejects it. More than 50 numbers: 4 to 6 weeks, if the current provider does not reject it.
- The how-to article: porting a US number is a seven step process that can take up to 4 weeks, depending on the type of number and the country.
- The help article How long does it take to port a US number to Twilio (checked 15 Nov 2026) says US porting typically lasts from 5 to 15 days, and can take up to 4 weeks or longer because of carrier rejections. The same article says that with the Port-in API, numbers can port in 3 days, and you can select the port-in date and the activation time.
The how-to article also breaks the Console process into steps, with these times:
- You submit the request with the documents above. The article also says to set the voice URL, the messaging URL, or the SIP trunk before the port date, so the number has a destination when it moves. You can set those at any point during the port.
- Twilio approves the request. If the paperwork is right, the article says to expect approval in 24 hours. It also says the time can vary by number type, and it names toll-free and landline as examples.
- Twilio submits the request to its carrier partner. That can take up to 24 hours. During this time, do not close the account at the current carrier, and keep the numbers active.
- The carrier partner contacts the losing carrier. The article says this can take one week.
- The losing carrier approves or rejects. Approval comes with a port date. A rejection can be a wrong PIN, an address or ZIP code that does not match the carrier's record, or a request from someone who is not authorized on the account. The article says a rejection adds an undetermined amount of time, and that you contact the losing carrier for what they still need.
- Twilio emails you the port date. After that date, and after the email that says the port has completed, you can use the number for voice.
- Messaging on a ported local US number is a further step. See the next section.
If you use the API, the port-in guide names the request statuses you will see: In Review, Waiting for Signature, In Progress, Action Required, Completed, Canceling, and Canceled. In Progress means the request is with the losing carrier. The guide says the only change you can make at that point is the target port date. Action Required means at least one number was rejected. Numbers that were not rejected keep moving unless you cancel them or cancel the whole request.
Voice, texts, and the old account
The how-to article says a port moves both voice and SMS to Twilio. If you want voice to stay with the current carrier and only add SMS on Twilio, that article points at Hosted SMS, which is a different process. Read that before you file a full port.
For messaging on a ported local US number, the same article says you need an approved A2P 10DLC campaign and brand registration. It says to start that campaign when you submit the port and to get the campaign to Verified. It also says to wait until the port is fully complete before you add the phone number to the Messaging Service. Add it earlier and messages may route through Twilio before the port is done. After the port completes and the campaign is Verified, allow 1 to 2 days for SMS routing to update, then add the number. The article says that if SMS is not routed yet, the A2P provisioning process may fail. The port-in guide says to finish the messaging and voice compliance requirements before you use the number for Twilio services. This article does not copy 10DLC prices.
Two other warnings from the how-to article. Leave the current carrier account open and keep the number active until the port completes. If the wireless number is on an iPhone today, de-register iMessage with Apple before the port, or text messages sent from iPhones can fail to reach Twilio. That still matters if you will answer on Android, because customers with iPhones text the business number.
Answering it on your phone
The port puts the number in the Twilio account. It does not install a dialer, and it does not ring a handset by itself.
Twilio's how-to article says to configure the voice URL, the messaging URL, or a SIP trunk before the port date. That is a Twilio Console setting. ReachTo does not file the port and does not replace that step. After Twilio emails that the port has completed, connect your own Twilio account in ReachTo and select the number. Calls then use the phone's Wi-Fi or mobile data. The app is $1 a month with your own Twilio account, or pay as you go with a prepaid wallet. iOS is coming soon.
You can also forward the Twilio number to a personal mobile instead of answering in an app. Forwarding rings the carrier phone. It does not place outbound calls that show the business number. The difference is in call forwarding or a calling app. If the ported number is the work line and the SIM stays personal, see a second business line on Android.
On the day Twilio says the port completed, call the business number from another phone and confirm where it rings. Then call out from the app and read the caller ID on that other phone. Leave the old carrier account in place until that test works. The how-to article says you can begin using the number for voice after the completion email. It does not say to cancel the old account on the morning of the port date.
What this does not do
- ReachTo does not port the number. The request, the LOA, and the dates are in the Twilio account.
- A port does not, by itself, put a business name on the caller ID. A display name is a separate Twilio setup, done in the Twilio account after the number is there.
- The timelines above are the ones Twilio publishes. A rejection, which Twilio says is often a name or address mismatch, adds time the pages do not cap.
Sources
Each page below was read on 15 Nov 2026. The port-in guide and the PortIn resource are marked public beta.
- Port phone numbers using Twilio APIs, checked 15 Nov 2026.
- PortIn resource, checked 15 Nov 2026.
- United States porting guidelines, checked 15 Nov 2026.
- How to Port a Phone Number to Twilio, checked 15 Nov 2026.
- How long does it take to port a US number to Twilio, checked 15 Nov 2026.
Related: what to check before you connect a Twilio number on Android, and what calling from a Twilio number costs. Setup questions: support@reachtoapp.com.