Moving a phone number is mostly forms. Then one morning, it's just done.

Can’t I just forward it?

The first question in September was the lazy one: could I leave the number in Google Voice and just forward everything to Telnyx? No. Telnyx won’t attach its texting service to a Google Voice number. To own the texting, I had to own the number. That meant porting.

The 10DLC boss fight, round two

This round, Orion (ChatGPT’s Codex) drove the paperwork with me. On September 8, in one long evening:

1. ID check. Telnyx verified my identity with a photo ID and selfie, which unblocked the account.
2. Business details. We caught that a draft of my business info didn’t match my actual IRS letter, threw it out, and used the real paperwork instead. Mismatched tax details are one of the most common reasons a 10DLC brand gets rejected.
3. Brand submitted at 4:51 PM. Verified at 8:47 PM.
4. Website pages. The carriers want to see SMS terms and a privacy policy on your site, including how STOP, START and HELP work. Those went up on my business site the same night.
5. Campaign submitted at 9:02 PM as “Customer Care,” which is exactly what my texting is: talking to people who already know me.

The fees, so you know what you’re in for: $4.50 for the brand, $15 for each campaign review, and $10 a month for the Customer Care campaign. The campaign sat in “pending” with the carriers for two days, then went active on September 10.

The letter

Porting a number runs on a Letter of Authorization (LOA). It’s a signed statement that you own the number and want it moved, plus proof, usually a screenshot or bill showing the number on your account. Google Voice also has you unlock the number for transfer first.

By September 11 the port order was filled out and waiting on one thing: my signature. We asked for the earliest activation slot: Tuesday, September 15, at 10 AM Mountain.

Port day

There’s no fanfare when a number ports. Nobody calls you. At some point in the morning, the old carrier lets go and the new one picks it up.

Here’s the message I sent my AI teammate at 10:42 that morning:

Ten years in Google Voice, gone from the app in one quiet refresh. Texts to my number were now landing on Telnyx and getting passed to my server. The first test texts went in and out. It worked.

The 2FA scare

One thing did rattle me that afternoon. A service I use refused to send a login code to my number, with an error saying it doesn’t send codes to VoIP numbers.

That’s a real thing to plan for. Some banks and apps won’t text verification codes to internet-based numbers. If you do this, check where your two-factor codes go before port day, and move the important ones to an authenticator app.

Six hours later

The number was mine. The texts were reaching my server. There was just one problem: I had nothing good to read them on. That afternoon I asked the question that started the second half of this story.

Free is a great price until you want to do something the free thing doesn't allow.

A great deal, for a while

I got my business number through Google Voice in November 2015. It was perfect for a one-person shop. One number rang every device, texts showed up on my phone and my PC, voicemails got transcribed, and it cost nothing.

So everything went there. Customers. Vendors. Family. Every “your appointment is tomorrow” and “your package was delivered.” When I finally exported it all in June 2026, the archive held:

• 86,252 texts
• 10,900 calls
• 3,014 voicemails
• 5,045 contacts

That’s not a phone number anymore. That’s the memory of my business.

The wall

The trouble started when I wanted my computers to help with any of it.

I run a lot of automation. I have AI assistants that read my email, track my tasks, and draft replies. They can do all of that because email has real tools for it. Google Voice has none. There’s no official API for texts or calls. Your own software can’t read your own messages.

There was one crack in the wall: Google Voice can forward received texts to email. So for months I had a scraper pulling text notifications out of Gmail every day. It was held together with tape:

• Sent texts were invisible. Email forwarding only covers what comes in. Half of every conversation, my half, never made it out.
• Group texts arrived empty. The notification email for a group message has no message in it. Just “you have a new message.”
• Sending was off the table. Google’s rules don’t allow automated sending, and I wasn’t going to risk the number on a hack.

I had a note in my to-do list for a long time that said, more or less, find an unofficial way to scrape Google Voice until I migrate. “Until I migrate” was doing a lot of work in that sentence.

The part that kept me up

The bigger worry wasn’t convenience. It was this: the number my whole business depends on was tied to a free consumer Google account.

If that account ever got locked, or Google changed the product, or decided to retire it the way Google retires things, the failure would be silent. Clients would call, nobody would answer, and they’d never learn why. When I sat down and listed the single points of failure in my business, that number was near the top of the list.

I didn’t need Google Voice to be bad. I needed it to stop being the only door.

What I wanted instead

Written down, the wish list was short:

1. Own the number, with a carrier that sells to businesses and has an API.
2. Own every message, sent and received, in a database I can search and back up.
3. Let my tools in. My AI assistants should be able to read a text and draft a reply without anyone screen-scraping anything.
4. Never miss anything. Whatever replaced Google Voice had to be at least as reliable on my phone as Google Voice was.

Number 4 turned out to be the hard one. Next up: before I touched my real number at all, I built a whole phone system on a brand-new number to practice on.