Porting Phone Numbers – Revenue.io Support

Porting Phone Numbers

Revenue.io enables you to transfer your existing phone numbers from your current service providers to the Revenue.io platform. This process is known as porting.

Prerequisites

The following items are needed to port your phone number to Revenue.io. Three are required, and the fourth is optional but recommended.

Customer Service Record (CSR): Contact your current service provider, tell them you want to transfer your numbers away, and give them your list of numbers. Request a CSR, and send us a copy.
- Mobile numbers might require a PIN, which is listed in your CSR.
- Your current provider might have placed a port freeze or number lock on your account. If so, contact them to remove it before porting can occur.
Letter of Authorization (LOA): Fill out a letter of authorization that lists the phone numbers you want to port to Revenue.io. Download the Letter of Authorization form.
- Make sure the information matches your CSR exactly, including the business name, the address, and the signature of the authorized representative.
- The signed LOA must be dated within 30 days of your request. Carriers reject older documents.
Recent phone bill: Send a copy of your most recent phone bill that proves you own the numbers. It must be dated within 30 days of your request.
Assignment list (optional): Attach a CSV file with two columns. In the first column, list every phone number you want to port. In the second column, enter the Revenue.io call flow or user you want to assign to that number. This lets us pre-configure routing rules for you. If you haven’t set up call flows yet, see Call Flow Overview.

When you have everything, email your request to our support team. You will typically receive confirmation that your port request was submitted within 24 hours.

If your port is delayed or restarted, we might ask for a new LOA and phone bill so that they stay within the 30-day window.

Porting dates are decided mutually by the carriers, not by Revenue.io. We can’t guarantee a specific port date. We’ll request your preferred date and work to make it happen. Numbers in the same port request can also be scheduled on different dates. See “Will all of my numbers port on the same date?” for details.

What happens after you submit your request

We submit your port request to the carrier and confirm the submission, typically within 24 hours.
Both carriers agree on a porting date for each number. We’ll share the dates we receive and keep you updated if they change.
Before your numbers port, we pre-configure them so that incoming calls route to the right place as soon as porting is complete. Your numbers appear in your Revenue.io account right away, but they aren’t active until they port. Until then, your previous carrier handles the calls.
Each number becomes active for calling on Revenue.io as soon as it ports. SMS might take up to 24 hours longer to start working after a number ports.

Do not cancel service with your current provider until Revenue.io confirms that all of your numbers have ported.

Frequently asked questions

How long does it take to port phone numbers?

Once you submit all required information, the typical timelines are:

Standard ports: 5–15 days. A port can take up to 4 weeks or longer if your current service provider rejects it.
Large ports (more than 50 numbers): Can take up to 4–6 weeks, barring rejections from your current service provider.

The time varies depending on your current provider and how many numbers you’ve requested to port. In general, large national carriers tend to release phone numbers more quickly than small regional carriers. Because carriers set the dates, we can’t guarantee a specific date or time frame. See the next question for how this affects numbers in the same request.

Will all of my numbers port on the same date?

Not necessarily. Carriers do not guarantee a specific porting date, and even numbers that you submit in a single port request might be given different porting dates. This can happen for several reasons:

Different underlying carriers. The numbers in your request might be held by different carriers, and each carrier processes and approves its numbers on its own schedule.
Different number types. Mobile, toll-free, landline, and VoIP numbers can move through different porting processes.
Processing limits. A carrier might only process a certain number of numbers in one window, which pushes some numbers to a later date.
Approvals and rejections. If your current provider rejects some numbers, for example because of a PIN or account information that doesn’t match, or approves them later than the rest, those numbers port after the others. See What are common reasons a port request is rejected?
Large requests. Requests with many numbers are submitted in batches of up to 50 numbers, and each batch moves through the process separately.

What are common reasons a port request is rejected?

A rejection means your current provider hasn’t approved the transfer. It almost always happens because the information on your port request doesn’t match what your provider has on file. A rejection can delay your port or move individual numbers to a later date.

Rejection reason	What it means	What to do
Account number or PIN mismatch	The account number or port-out PIN doesn’t match the provider’s records. Some providers use it to verify the request.	Find the account number on your phone bill or CSR. Ask your provider for the correct PIN.
Address or ZIP code mismatch	The address on your request doesn’t match the address on the CSR. Providers usually require the service address for the numbers, not the billing address.	Use the service address exactly as it appears on your CSR.
Company name mismatch	The business name doesn’t match what your provider has on file.	Use the business name exactly as it appears on your CSR.
Data mismatch	The company name, authorized name, and address on the request are all incorrect. This is more common with toll-free numbers.	Request a CSR from your provider, and update the request with the correct information.
Incorrect billing telephone number (BTN)	The BTN, which is the main number on your account, doesn’t match your provider’s records.	Confirm the BTN with your provider and correct the request.
Numbers on different accounts	The numbers in the request are tied to more than one address or account number.	Request a CSR, and split the request by address or account.
Remaining services on the account	Other services, such as additional numbers or data services, are still on the account.	Work with your provider to decide which services to port and which to disconnect, or to reconfigure the account so the numbers can move.
Port freeze or number lock	Your provider has locked the number against transfer.	Contact your provider to remove the freeze. They might give you an identification code to remove it.
Inactive or disconnected number	The number has been disconnected, is unassigned, or can’t be found in your provider’s billing records.	Confirm that the number is active with your provider. Numbers must stay active until the port completes.
Pending order on the account	The account has an open order, such as a recent feature change, disconnect, address change, or authorized name change.	Wait for your provider to complete the pending order, then resubmit.
Unauthorized user	The person who signed the request isn’t an authorized user on the account.	Have an authorized user on the account sign the LOA.
Incomplete or outdated LOA	The LOA is missing the authorized name, address, account number or PIN, signature, or date. It might also be more than 30 days old.	Complete every field, and sign and date it within 30 days of your request.
Carrier-specific issues	For some providers, especially for international numbers, the request has an invalid VAT number or an incomplete range of numbers.	Contact your provider to resolve the issue.

To avoid rejections:

Request a CSR from your current provider before you submit, and use it to fill out your LOA.
Submit a separate request for each service address if the numbers you’re porting are registered to more than one.
Get your account number and port-out PIN from your provider, and include them in your request.
Keep your numbers active until the port completes. A disconnected number causes the port to fail.
If you’re porting only some of the numbers on an account, don’t include the billing telephone number. It can cause a rejection.

If your port request is rejected, contact our support team. We’ll work with you and the carrier to identify the reason and the fix.

What can I do to expedite the porting process?

Here are some tips to help expedite the process.

Before you submit your request, call your current provider to confirm the billing name and address they have on file, and use exactly that information in your LOA. They can also provide your CSR.
Ask your current provider to approve the port request for your numbers. This has sped up the process in select cases. Make sure you ask to speak to the porting department or a porting specialist.
Keep each port request to 50 numbers or fewer. Smaller batches are generally quicker and easier to port, but they might land on different dates, so group numbers by team or function to help the people who work together go live together.

Can I port phone numbers from any U.S. state?

At the moment, Revenue.io is able to port most phone numbers from every state except Hawaii or Alaska.

Can I port international phone numbers?

Yes. Revenue.io offers standard porting services for numbers in the following countries.

Australia

Austria

Belgium

Brazil

Canada

Czech Republic

Denmark

Finland

France

Germany

Ireland

Italy

Japan

Luxembourg

Mexico

Netherlands

New Zealand

Norway

Portugal

Puerto Rico

Romania

Slovenia

South Africa

Spain

Sweden

Switzerland

United Kingdom

If your country isn’t on this list, we might still be able to port your numbers. Contact our support team to ask.

Toll-free numbers are designed to be used for inbound voice calls and are reachable only in the country they are designated for. The exception is US toll-free numbers, which can be reached from Canada and include SMS capabilities.

Can I port non-traditional numbers, such as Google Voice?

There is a good chance that Revenue.io can port non-traditional numbers such as Google Voice, Skype, or other VoIP numbers. In some circumstances, numbers that otherwise meet the porting criteria could be rejected. A Revenue.io team member will advise you on possible next steps if this issue occurs.

How much does it cost to port phone numbers to Revenue.io?

Revenue.io does not charge a fee to port-in standard U.S. or Canadian phone numbers (though regular monthly number-hosting/usage fees still apply). There may be an additional service charge for international number ports.

Who owns the phone numbers once they are ported to Revenue.io?

You do. They will appear in your Revenue.io account, but you can port them to another carrier at any time while your account is active. If you choose not to port your phone numbers after your account is deactivated, those numbers will be released.

Porting to another provider

Transferring your phone numbers away from Revenue.io to another provider is a simple process which your new service provider should be able to guide you through.

Requesting a Customer Service Record (CSR)

Your new provider may require you to provide a Customer Service Record (CSR) for the numbers you want to port. Mobile numbers may also require a PIN to port successfully. Requesting a CSR may take several business days, depending on the volume of numbers requested.

To expedite this, contact our Support team early with the list of numbers you wish to port away and we will provide you with the CSR and PIN for each number requested.

My port request was rejected

If you are receiving a rejection for any reason, it may be coming from one of our Carrier Partners instead of us directly. If this is the case, please let us know and we will investigate the reason for rejection. Often it is caused by an element of your port request not matching the CSR record exactly.