Texas toll-free number porting under FCC and NANPA rules

What to take away

Toll-free porting intervals the FCC sets

A toll-free port is not the same transaction as moving a local line. Local number porting runs on rules built for wireline and wireless service. Toll-free numbers sit in a separate database and follow intervals set for that database.

The FCC porting intervals for simple toll-free ports are short. A simple port is one where the number is active, the records match, and no other order is pending on the number. In that case the losing carrier must validate the request quickly, and the port completes on the date the winning carrier asks for.

Complex ports take longer. A complex port is one with a pending order, a recent change, or records that do not line up. The interval stretches because the carriers have to reconcile the record before anyone moves anything.

The FCC's toll-free porting order in WC Docket No. 13-97 sets the figures. A simple port carries a four-business-day interval. A complex port can take up to 30 days. Most of the work is done before the request goes in.

FCC rules also cover what a carrier may not do. A losing carrier cannot hold a number to keep your business, and it cannot refuse a valid request because of an unpaid bill on a different account.

Those limits come from the same numbering authority that governs provider licensing, which the agency describes in its licensing overview.

One more point on timing: the port date is not the cutover date for your call flow. The database moves the number, and your routing has to be ready on the other side. Treat the two as separate events.

NANPA and the resporg role in a toll-free move

NANPA administers the North American Numbering Plan. That plan includes the toll-free codes, from 800 through 888. NANPA does not serve your calls. It assigns numbers and tracks which responsible organization controls each one.

The responsible organization, or resporg, is the entity that can change the routing record for a toll-free number. A resporg is often a carrier, but it can also be a service bureau that does nothing but manage toll-free records.

This is the part that surprises businesses. Your invoice may come from one company while a different company holds the record. The resporg controls where calls land. If you do not know who your resporg is, you do not control your number.

NANPA resporg duties include maintaining the record, processing change requests from authorized parties, and keeping the routing data current. A resporg that sits on a request without cause is the usual villain in a stalled port.

The first practical step in any toll-free move is to identify the resporg on the record. Ask your current provider in writing. If they will not say, use the resporg lookup in the Somos toll-free number registry.

Once you know the resporg, the port becomes a conversation between two record holders. The winning carrier files the request, the losing resporg validates it, and NANPA's database reflects the change when it completes.

For background on how these records behave in practice, our notes on toll-free numbers cover the parts businesses ask about most. The short version: the number is a pointer, and the pointer is the asset.

Steps a Texan business takes to port without losing calls

Texas adds a few wrinkles. The Public Utility Commission of Texas handles complaints about intrastate service, though the numbering record itself is federal. Texan businesses also tend to run one call flow across several markets at once, from the Dallas and Fort Worth area codes to Houston, Austin and San Antonio.

Border markets such as El Paso, Laredo and McAllen share those lines with the petrochemical belt around Beaumont and Corpus Christi. A port that ignores those sites breaks the customer experience.

Work through these steps in order.

A checklist helps here, because the failure modes are administrative rather than technical.

The order matters. Businesses that build routing last end up porting a number into a void. Businesses that confirm the resporg first rarely get surprised.

Texas timing is also worth a note. Hurricane season runs from June through November along the Gulf Coast, and the same months bring heavy storm activity to the Dallas, Fort Worth and Houston metros. A midweek cutover leaves working days on either side of the port, which matters when a storm thins the carrier's support desk.

If you want the general version of this sequence, including the mistakes that recur across carriers, our walkthrough of where it goes wrong covers the same ground for local numbers.

What can stall a port: mismatched records and pending orders

Most stalled ports are not disputes. They are data problems, and they are boring.

The most common cause is a name or address mismatch. The business has moved, rebranded, or been acquired, and the toll-free record still carries the old entity. The losing carrier rejects the request because it cannot match the authorized party to the record.

The second cause is a pending order. If a change is already in flight on the number, a new port request collides with it. The fix is to let the first order complete, then file again.

The third cause is an unpaid balance on the toll-free account itself. Carriers may not hold a number hostage over a disputed charge, but a genuine unpaid balance on that account is a legitimate reason to pause a port.

The fourth cause is a resporg that will not confirm the request. This is where the process turns into a complaint, and the next section covers that route.

There is also a category of problem that has nothing to do with the port: the destination. A business ports the number cleanly and then sends calls to a queue nobody staffs. That is a routing failure, not a porting failure, and it reads to customers exactly the same way.

Our piece on who holds the record explains why the main number and its record matter more than the carrier brand on the invoice.

Two habits prevent most of these stalls. Keep the account name current with the provider, and clear any pending changes before you file. Both take an afternoon.

Testing call flow before and after the cutover

The call-flow test before cutover is the step businesses skip, and it is the one that saves them.

A proper test happens from outside your own network. Call the toll-free number from a mobile phone on a different carrier. Confirm the greeting, the menu, the ring time and the destination. Then call again during the hours your business is closed and confirm the after-hours path.

Test the failover too. If the primary destination is unreachable, where does the call go? A test that only proves the happy path proves half of what you need.

On the port date, the number moves in the database. Your new routing should already be live and waiting. If it is, the cutover is invisible to callers. If it is not, callers hear a dead line or the wrong greeting.

After cutover, repeat the same test from multiple carriers. Mobile, landline and VoIP each route differently, and a problem that shows on one may not show on another. Watch the first full business day before you retire the old configuration.

Keep records of every test: time, calling number, destination reached. If something breaks, that log is what you hand the carrier. It turns a vague complaint into a specific ticket.

Our toll free vs local business number comparison explains the cost side of the same design. A port that raises answered calls raises the bill, which is a success and a budget line at once.

For the record side of the same idea, see our piece on business phone numbers migration and why the record, not the phone line, is what you actually own.

Where to complain if a port is refused or delayed

Start with the carriers. Put the request in writing, state the number and the requested date, and ask for a written reason if the port is refused. A surprising share of refusals dissolve at this stage.

If the losing carrier will not move, escalate inside that company. Ask for the department that handles number portability, not general customer service. Keep the ticket numbers.

When the carrier route is exhausted, the FCC Consumer Help Center accepts complaints about porting, including blocked or delayed ports. You can file there online, and the complaint goes to the carrier with a response requirement. The Consumer Help Center is the right entry point for a blocked port.

Filing a complaint requires the same facts as a port request: the number, the account name, the dates and the correspondence. The agency's forms page lists the filings it accepts, including the complaint forms.

You can also check the carrier's own record before you file. The agency's database search lets you look up carrier and numbering information, which is useful when a provider disputes who controls the number.

If you need the underlying order language to quote in a complaint, the commission's published commission documents include the porting orders themselves. Citing the specific order tends to shorten the argument.

Texas businesses have a second option. The Public Utility Commission of Texas handles intrastate billing and service complaints, and it can take up a case the federal process does not resolve. Keep the federal route as the primary path for a toll-free port, since numbering is federal.

Common questions