Only 8 spots left$15 $2/seat/month for life for the next 8 founding teams.Claim your spot →

Twilio dialer

How to port a number to Twilio, then call from it

To port a number to Twilio, run the Portability Checker, file a port-in request under Communications > Numbers & senders > Port and host with the details your current carrier has on file, and have the account holder sign the Letter of Authorization Twilio emails. A standard US port takes 5 to 15 days (Twilio porting guidelines). Keep the old service until calls reach Twilio. Rapidialer then imports the number, and reps call from it.

Updated · Reviewed by Jaffar Jawed

Key takeaways

  • A standard US port takes 5 to 15 days with complete information, up to four weeks or longer after a rejection, and 4 to 6 weeks for more than 50 numbers (Twilio US porting guidelines, checked November 2026).
  • Twilio emails the Letter of Authorization to the authorized representative, who has 30 days to sign before the request is canceled.
  • A name or address that doesn’t match the carrier’s Customer Service Record is the most common reason a port is rejected.
  • One port request can include up to 1,000 numbers.

What’s at stake when you move a number?

  • People already know your business number, and a new one throws away the recognition and callbacks it has built.
  • A port is rejected when the name, address or PIN doesn’t match the current carrier’s records, and each rejection adds days (Twilio porting guidelines).
  • Canceling the old service before calls reach Twilio risks a gap with no service at all (Twilio Help Center).

How do you go from port request to calling from the number?

  1. Check the number and gather details (30 minutes)

    Run the Portability Checker in the Console, then ask your carrier for the account number, any port PIN, a bill from the last 30 days, and the name and address exactly as they appear on the Customer Service Record (Twilio porting guidelines).

  2. Submit the port request

    In the 2026 Console, go to Communications > Numbers & senders and select Port and host (Twilio port and host docs). Add the numbers, upload the bill and name the authorized representative.

  3. Sign the Letter of Authorization

    Twilio generates the LOA from your request and emails it to the authorized representative, who signs it electronically within 30 days (Twilio port-in docs).

  4. Keep the old line until the port completes

    Leave the current service active and paid. Twilio confirms a port date with the losing carrier; cancel the old service only after calls show up in your Twilio logs.

  5. Import it into Rapidialer (1 minute)

    An owner or admin chooses Import from provider in Telephony settings. The number is synced, and its voice webhook now points at Rapidialer.

What do you need from your current carrier to port a number?

Five things, and the name and address matter most. Twilio’s US porting guidelines list them (Twilio porting guidelines, checked November 2026), and the carrier you are leaving holds every one, so ask them before you file:

  • Account number for the account the number is on.
  • PIN or passcode, if the carrier requires one to port; most mobile carriers do.
  • Name and address on the account, exactly as they appear on the Customer Service Record (CSR). Twilio says incorrect name or address information is the most common rejection.
  • A copy of a bill dated within the last 30 days, uploaded as proof of ownership.
  • The authorized person on the account, whose email receives the Letter of Authorization.

How long does it take to port a number to Twilio?

A standard US port takes 5 to 15 days once Twilio has complete information. Each rejection adds time, so a port that is rejected can take four weeks or longer, and bulk ports of more than 50 numbers take 4 to 6 weeks barring rejections (Twilio porting guidelines). Twilio confirms a port date with the losing carrier once a number reaches Port Pending (Twilio port-in docs), but a port can still finish a few days early or slip. Reps don’t have to wait: they can keep dialing with the power dialer from other Twilio numbers and switch caller ID once the port lands.

Twilio US port timelines and limits (Twilio porting guidelines and port-in docs, checked November 2026)
SituationTypical timeWhat to do
Standard port, details correct5 to 15 daysKeep the old service running until calls arrive
Port rejected by the carrierUp to 4 weeks or longerFix the CSR mismatch and resubmit
Bulk port, more than 50 numbers4 to 6 weeksStart well before a phone system cut-over
Letter of Authorization unsignedCanceled after 30 daysConfirm the representative’s email first

What is the Letter of Authorization for a Twilio port?

The Letter of Authorization (LOA) is the account holder’s signed permission to move the number. For US non-toll-free numbers, Twilio generates it electronically from your request, so there is no PDF to fill in, and emails it to the authorized representative to sign; if it is still unsigned after 30 days, the request is canceled (Twilio port-in docs).

Most delays here are about the email, not the signature. If the person on the carrier account has left the company, update the account with the carrier first, because a signature from someone else doesn’t match the records the losing carrier checks.

Which numbers can’t be ported to Twilio?

Run Twilio’s portability check before you file: it shows whether Twilio can take a number (Twilio portability check). Plan around these cases, which each need a different route:

  • Numbers already in a Twilio account can’t be ported in. One in your own account can be moved to a subaccount instead (Twilio Help Center).
  • Numbers in a country, rate center or carrier Twilio doesn’t support (Twilio Portability resource).
  • Numbers disconnected at the current carrier, or tied to carrier services that block a port (Twilio error 22159).
  • Toll-free and non-US numbers, which follow separate processes; Twilio’s port-in API covers US non-toll-free numbers only.
  • Numbers you only want for texting can be hosted instead: hosting keeps the number with its carrier for messaging, not voice (Twilio port and host docs).

How do you call from a ported number in Rapidialer?

Import it, then give it a job. Rapidialer doesn’t buy or port numbers; once the port completes, the number sits in your own Twilio account, and an owner or admin clicks Import from provider in Telephony settings. That brings in up to 200 of the account’s numbers and repoints each one’s voice webhook at Rapidialer.

  • Assign it to a rep on the Team page. It becomes their caller ID, and calls to it ring that rep on any page of the app, plus their forwarding mobile if one is set, before the rest of the team.
  • Make it the default caller ID with Set default.
  • Let local presence use it. With local caller ID on, leads in the same area code are called from it unless the rep picks another number.
  • Register it for trusted calling. After a port, complete Twilio’s voice compliance steps, such as STIR/SHAKEN, before you dial from it at volume.

When should a ported number stay out of Rapidialer?

When it is a main line with a phone menu or a queue. Rapidialer rings a number’s assigned rep, then the team, then an optional voicemail box with inbound call handling; it has no IVR or queues. Importing replaces the number’s existing call flow, so keep such a line in a Twilio subaccount Rapidialer isn’t connected to.

Porting also isn’t worth it for a fresh outbound line nobody knows yet. If you only need caller IDs for cold calling, buying a new Twilio number takes minutes instead of weeks and costs $1.15 a month for a US local number. Port the numbers that customers already call back, and see choosing Twilio numbers for cold calling for how many new ones a team needs.

Which Rapidialer features does this use?

Which teams use it this way?

Port a number to Twilio: questions and answers

How long does it take to port a number to Twilio?

A standard US port typically takes 5 to 15 days once Twilio has complete information. A port the losing carrier rejects can take four weeks or longer, and bulk ports of more than 50 numbers take 4 to 6 weeks. The Letter of Authorization must be signed within 30 days, or the request is canceled.

Why was my Twilio port request rejected?

Usually because the name or address on the request doesn’t match the losing carrier’s Customer Service Record, which Twilio names as the most common cause. A missing or wrong port PIN, an old bill, or a number disconnected at the carrier also cause rejections. Fix the detail in the rejection reason and resubmit.

Can I use my number while the port is in progress?

Yes. The number stays with your current carrier until the port completes, so calls keep ringing where they do today. Keep that service active and paid until calls appear in your Twilio logs, because canceling it early risks a gap in which the number has no service at all.

Does Rapidialer port numbers for me?

No. You port numbers into your own Twilio account, and Twilio handles the request with your carrier. Once the number arrives, an owner or admin imports it into Rapidialer with Import from provider in Telephony settings, which takes about a minute, and assigns it to a rep or sets it as the default caller ID.

Can Rapidialer use a number that stays with my current carrier?

No. Rapidialer imports only numbers held in your Twilio account. Twilio’s hosting option keeps a number with its carrier for messaging only, not voice, so porting is how a number’s calls move to Twilio. Until then, you can buy a Twilio number for outbound calls and port the main line later.

How many numbers can I port to Twilio at once?

Up to 1,000 numbers in one port request, according to Twilio’s US porting guidelines. Bulk ports of more than 50 numbers take 4 to 6 weeks barring rejections, so split a large move by carrier account if one account’s details are uncertain, and a rejection then holds up fewer numbers.

Start today

Import your list and make your first call today

Connect Twilio, upload a CSV and start dialing.