Phone numbers · 2026

Use your own phone number with a power dialer: port it, verify it, or forward to it

Last updated September 3, 2026

The question behind "can I use my own number with a dialer" is usually one of two fears: prospects will not recognise a new number, or the dialer will own the number and hold it hostage when you leave. Both are reasonable. Most dialers answer by renting you a number from their pool, which solves neither. On your own Twilio account there are three real routes, each with a cost, a wait and a thing it quietly breaks. This page lays them out from Twilio's own porting and caller-ID documentation as read in September 2026, then explains what happens to a rented number when you cancel.

Route A: port your existing number into your Twilio account

Porting moves the number itself, so afterwards it behaves exactly like a number you bought from Twilio: the dialer places calls from it, callbacks ring in the browser or forward wherever you say, every call is logged and can be recorded, and texting works after A2P 10DLC. Twilio's US porting guidelines accept local numbers (landline, VoIP and, with extra carrier authentication, mobile) and toll-free numbers.

The process in the console: Phone Numbers → Port & Host → Portability Check, which reports within seconds whether each number can move and why not if it cannot. Then create the port-in request. You will need the account holder's name and service address exactly as the current carrier has them on the Customer Service Record, the carrier account number and any port-out PIN, a bill dated within the last 30 days, and a signature on the Letter of Authorization, which Twilio now generates and sends for e-signature rather than asking you to upload a form. Twilio charges no fee for a standard US local or toll-free port (Twilio support, checked September 2026); the number then bills the usual ~$1.15/month. Your old carrier may charge an exit fee or an early-termination penalty, and that is the only money in it.

Timeline: Twilio quotes 5 to 15 days for a US port and warns it can run to four weeks or more if the losing carrier rejects it. The most common rejection, per Twilio's US guidelines, is a name or address that does not match the carrier record, so pull the CSR from your current provider before you type anything. What breaks: at cutover, every service on the old carrier ends at once (voicemail, hunt groups, the desk phone), so plan where inbound goes on day one. SMS routing lands two to three business days after the voice port, and business texting still needs the A2P 10DLC registration. And the rule everyone breaks: do not cancel the old account until the port is confirmed complete, because a cancelled number cannot be ported and may be released to the pool.

Route B: verify it as an outgoing caller ID

A Verified Caller ID leaves the number where it is, on your cell plan or office PBX, and lets Twilio present it on calls the dialer places. Console: Phone Numbers → Manage → Verified Caller IDs → Add a new Caller ID. Twilio calls the number, you enter the six-digit code shown on screen, done. DialSheet lists verified caller IDs beside your Twilio numbers when you choose which number leads should see.

What it does not do is the whole story. Inbound calls to that number never reach Twilio, so the dialer cannot answer, record, transcribe or log a callback; it rings your phone as it always did. SMS from the dialer is impossible because the number is not on Twilio. And there is an attestation cost that almost no vendor explains: under Twilio's SHAKEN/STIR rules, a non-Twilio number can reach at most B attestation, because Twilio cannot attest your right to use a number it does not host. Calls from a Twilio number attached to your Business Profile sign at A. Carrier analytics treat B with more suspicion than A, and B is also what the big rental dialers typically deliver. The mechanics are in STIR/SHAKEN attestation for cold calling. Verify a caller ID when the number is a personal cell you will not port and your volume is modest.

Route C: buy a local number and forward callbacks to your cell

The boring option is the right one for most cold callers. Buy a Twilio number in the area code you call (~$1.15/month, sixty seconds, no paperwork), dial from it, and set its inbound to forward to your cell during working hours so every callback still reaches a human. Prospects were not going to recognise your old number anyway: they have never heard of you, which is what makes it a cold call. What they respond to is a local area code and a caller-ID name, both of which a fresh number gets. You also gain the thing a personal cell can never have: disposability. A number that earns a spam label after a bad month costs ~$1.15/month to replace and your cell is never the one that got burned.

A forwarded call bills an inbound leg ($0.0085/min) and an outbound leg to your cell (~$0.014/min), both from Twilio's US voice pricing page, checked September 2026. Pro adds $29 per 3-seat pack for teams. Size the 600 minutes to yourself with how many minutes cold calling uses.

The three routes side by side

What a rented dialer number actually is

When Kixie, JustCall or Aircall gives you a number, it is provisioned on the vendor's carrier account, under the vendor's business profile, signed with the vendor's attestation, and scored by carrier analytics alongside every other customer in that pool. You are paying roughly $19 to $89 a user a month (list ranges, see JustCall, Kixie and Aircall) for the use of it. The vendors are not hiding this; it is in their help centres, read September 2026:

• Kixie: its terms of use state that on cancellation all phone numbers are released and users, settings and dashboard access are removed. Porting out is not mentioned in the terms; third parties describe port-outs from Kixie taking about two weeks.
• JustCall: allows port-outs and asks you to email its porting address so it can approve the request when the new carrier asks for ownership confirmation. Its own port-in fee is $10 per number.
• Aircall: charges no port-out fee but notes some numbers cannot be ported because of operator agreements, requires the account to stay active until the port completes, and reminds you to delete the number afterwards to stop billing.

So the honest description of a rented number is: usable while you pay, portable in most cases if you start the port before you cancel and wait out the process on the vendor's account, and gone if you let the subscription lapse first. A number in your own Twilio account is the opposite. Nobody needs to approve anything; you paste the same Account SID and Auth Token into the next tool and the number, its history, its caller-ID name and its attestation come along. Every route above ends in that position, which is the point of doing it on your own account rather than inside a dialer.

Which route, in one paragraph each

Port if the number is on your business cards, your website and your Google listing, and you expect to be dialing from it in three years. The two-week wait is a one-off; A attestation, logged callbacks and SMS are permanent.

Verify if the number is your personal cell, you will not move it off your carrier, and you make a few dozen calls a week to people who might reasonably recognise it. Accept B attestation and no inbound logging as the price of keeping the phone in your pocket.

Buy and forward in every other case, which is most cases. It is the cheapest, the fastest, the only one that lets you match the prospect's area code, and the only one where a burned number is a ~$1.15/month problem. If you would rather not have a Twilio account at all, a $49 managed line does the same forwarding on our carrier account, but then the number is ours rather than yours, which is the trade this whole page is about.

Questions people actually ask