Your phone numbers are the business: how porting a business phone number actually works

Your trucks, yard signs, Google profile, mailers and ten years of fridge magnets all point to a handful of phone numbers. When you switch field service software, porting those business phone numbers is the one step where a mistake turns straight into missed calls, and missed calls in a service business are missed jobs (more on that in what the data says about after-hours calls).

The good news is that porting is a regulated, well-worn process with rules on your side. The bad news is that most failed ports fail on paperwork, and most dropped calls come from a shop cancelling the old service too early. This post covers how porting works, why ports get rejected, what happens to texting and call tracking, and a plan that starts with a low-stakes "canary" number before you touch the main line.

Your right to keep your number, in plain terms

Local number portability lets you move a number from one provider to another. The FCC's rules say a carrier must complete a simple port within one business day and a non-simple port within four business days, unless the new provider or the customer asks for a later date.¹ Ports to or from interconnected VoIP services, which is how most cloud phone systems work, are covered too.¹

The catch is the word "simple." The FCC defines a simple port as one that doesn't involve unbundled network elements, involves an account for a single line only, has no complex switch features (Centrex, ISDN, remote call forwarding, multiple services on the line) and doesn't involve a reseller.² A contractor with a main line, a few tracking numbers and a fax line is almost never simple. That's why carriers quote longer times for business ports than the one-day rule suggests. Bandwidth, for example, estimates one to two business days for a simple port and three to four weeks for a complex one.³

Two details from the rule are worth knowing. The business day is Monday to Friday, and a simple port request has to reach the old carrier between 8 a.m. and 1 p.m. local time to be eligible for activation at midnight that day; anything later counts as received the next business morning.¹ And when the FCC streamlined porting, it said validation for simple ports should rely on no more than four fields: the 10-digit number, the account number, the 5-digit ZIP code and a passcode if there is one.² Those four fields are where most of your problems will come from.

Why ports get rejected

Twilio's porting guidelines say it plainly: the most common reason for a rejected port is incorrect name or address information.⁴ The old carrier compares your request against its customer service record (CSR), the account record it holds for your numbers, and any mismatch sends the request back. Each rejection costs days.

The paperwork itself is a letter of authorization (LOA), signed by the account owner or an authorized user, listing the numbers and matching the CSR. With ServiceTitan you don't submit the port yourself: you give your new provider a screenshot of your numbers from Settings, Phone Numbers, and the new provider files the request.⁵

Inventory every number before you port any

Most shops don't know how many numbers they have. Over the years, call tracking adds a number for each yard sign batch, truck wrap, mailer and ad channel, and nobody writes them down. Before you port anything, build a number ledger: one row per number.

That table is an example; your rows will differ. The ledger does three jobs. It makes sure no number is left behind on the old system to be released when the account closes. It tells you which campaign each number belongs to, so call attribution survives the move (see lead source attribution). And it shows you which number is safe to port first.

Port a canary first

Here's the plan we'd use: before you move the main line, port one low-stakes number, such as an old mailer tracking line that still gets a few calls a month. Treat it as a test of everything.

• Did the request go through on the first submission, or was it rejected? If rejected, what was wrong? The same mistake would hit the main line.
• How many days did it take from submission to the confirmed date (often called the FOC date)?
• When the port completed, did calls ring the right phones? Did the campaign show up on the call?
• Did texting work from the number, or only voice?

A canary costs you a week and turns a guess into a known timeline. When the main line goes, you'll know exactly how your old carrier behaves.

1. 1

   Three to four weeks before you need it: build the ledger

   List every number, where it's published, its campaign, and whether it texts. Get the CSR name, service address, account number and PIN from the old provider. Download recent bills.

2. 2

   Same week: register for texting with the new provider

   Business texting from local numbers needs brand and campaign registration. Start it now so it's approved before any texting number moves.

3. 3

   Then: port the canary

   One low-risk tracking number. Note how long it takes and fix anything that was rejected.

4. 4

   Next: port the tracking numbers

   Yard signs, trucks, mailers, ad lines. Map each one to its campaign in the new system before its port date.

5. 5

   Last: the main line, midweek, outside peak

   Pick a Tuesday or Wednesday in a slow week. Have someone ready to test calls and texts the moment the port completes.

The rule nobody should break: don't cancel first

Do not cancel your old phone service, or the software account that holds your numbers, until every port is complete. When a port completes, the number leaves the old provider; that's what ends the service for that number. If you cancel first, the old provider may release the number, and getting it back is not guaranteed. Telnyx, for example, warns that toll-free numbers released by their controlling entity risk disconnection if they aren't activated within one to two weeks.⁶

This is also why phone porting is one of the long clocks in a software switch. If your access to the old platform ends on your renewal date, every port has to be finished before it, with margin. Our 90-day exit calendar puts the port submission about five weeks before renewal for that reason.

Toll-free numbers are a different process

Toll-free numbers don't use the same porting path as local numbers. They're controlled by a "responsible organization" (RespOrg), and the transfer runs through a central system. Telnyx says a toll-free port can take about two business days once accepted, or around seven days end to end without rejections, and recommends starting at least two weeks before you need it.⁶ Bandwidth quotes three to seven business days.³ Texting on a toll-free number also needs its own setup with the new provider. If the toll-free line barely rings, consider whether you need it at all.

Voice moves with the port; texting registration doesn't

This is the part that catches people. A port moves the number. It doesn't move your business texting registration. In the US, business texting from ordinary 10-digit numbers runs under a framework called A2P 10DLC, which carriers use so that texts to customers are "verified and consensual." Every business sending texts from these numbers has to register a brand (who you are) and a campaign (what you send, and how people opt in and out) through its provider. Twilio notes that registered traffic gets lower filtering and higher throughput, while unregistered senders pay additional carrier fees.⁷

So register with the new provider before port day. Otherwise the number arrives, calls work, and appointment reminders and on-my-way texts quietly get filtered or blocked. For the consent side of texting, see texting customers legally.

Forward first, or port right away?

You don't have to port on day one of a software switch. Many providers, including the one you're moving to, will give you a new number that your old numbers can forward to. That buys time, but it isn't free.

Our view: forward for a week or two to prove routing, then port. Never let forwarding become the plan for your renewal date.

A port-day runbook

How this works in TradesWork

In TradesWork you can request a port of your existing numbers from the Phones settings, or forward your old numbers to a new number while you decide. Texting from local numbers needs carrier registration first: you fill in your business profile once, it's submitted for you, and each review step shows on screen. Approval usually takes a few days, sometimes about two weeks, and until then texting shows as limited rather than pretending to work. Ordinary local ports usually take one to two weeks. Toll-free texting verification isn't automated yet, so use a local number for texting. Each number maps to a campaign, so the call pop and your reports keep the attribution. More on TradesWork phones.

Whatever system you're moving to, the order is the same: ledger, texting registration, canary, tracking numbers, main line, and only then cancel.