Porting your telephone number (non-Twilio number) to a location

Modified on: Thu, 12 Jun, 2025 at 9:40 AM

Overview

This guide walks you through the process of porting a non-Twilio number—like one from Verizon or AT&T—into your HighLevel-connected Twilio account. You’ll need to gather a few documents and fill out a porting form.

⚠️ Tip: Porting numbers involves regulations and validation. Missing or incorrect information can cause delays or rejections.

TABLE OF CONTENTS



Please understand that port requests may take 2-4 weeks (4-6 weeks for more requests of more than 50 numbers)



After reviewing the above video, please prepare the following information below and fill out the form: Porting FormIf you have questions, please contact support



What You’ll Need (At a Glance)

Requirement

 Description

Location ID

The ID of your HighLevel sub-account receiving the number

Customer Name

Must exactly match your phone bill

Service Address

No PO Boxes; must be the address on file with your carrier

Phone Numbers

In E.164 format (e.g., +15551234567)

Letter of Authorization (LOA)

Downloaded, completed, and signed within the last 30 days

Recent Phone Bill

Must be a PDF, no larger than 4MB

Carrier Account Info

Account number, PIN or last 4 digits of SSN (for wireless)




Step-by-Step Porting Instructions


Step 1: Locate Your Location ID

You'll need the Location ID for the destination sub-account where the number will be ported.


Step 2: Enter Customer Name

Use the exact name as shown on your current phone bill.

  • First Name

  • Last Name

  • Business Name (if applicable)


Step 3: Enter Service Address

Use the physical address on file with your current carrier.
 PO Boxes are not accepted.

  • Street Address

  • City

  • State/Province

  • Zip/Postal Code


Step 4: List Authorized Phone Numbers

Include the numbers you want to port and relevant account details.

Wireless Numbers

  • Phone Number(s): e.g. +17787787878

  • Wireless Account Number: e.g. 12345678

  • PIN / Last 4 of SSN: e.g. 1234

  • Carrier Name: e.g. Verizon

Landline / Toll-Free Numbers

  • Phone Number(s): e.g. +18881234568

Number type

Phone number(s):

Wireless Account number:

Pin / Last 4 of SSN:

Service Provider

Wireless Numbers

e.g. +17787787878

e.g. 12345678

e.g. 1234

e.g. Verizon

Landline & Toll-Free Phone Numbers

e.g. +18881234568










Step 5: Complete the Letter of Authorization (LOA)

Download and complete the LOA.

  • Must be in PDF format

  • File size cannot exceed 4MB


Step 6: Include Recent Billing Statement

Provide a scanned or electronic copy of your most recent phone bill.

  • Must be in PDF format

  • Max file size: 4MB


Step 7: Submit Your Port Request to Twilio


Porting a Canadian Phone Number?(non-Twilio number) to a location

The process is mostly the same, with a few additional notes:

  • Typical duration: 4–6 weeks
    (varies by losing carrier)

  • One-time porting fee: $7.00 USD per number

What You’ll Need

Before filling out the Twilio Porting Form, make sure you have the following:

  1. Account SID
     (Provided by HighLevel after setup)

  2. Phone number(s) in E.164 format to be ported.
     Example: [+][1][xxx][xxx][xxxx]

  3. Twilio Canadian Letter of Authorization (LOA)

    • Must be signed within the last 15 days

  4. Your most recent billing document

  5. Customer Account Number

    • The one in your current carrier’s records



Frequently Asked Questions

Q: My Twilio number took forever to port. Why?
A: Sometimes it might be that those Twilio numbers are already with another Twilio project. So we just need to move the Twilio number once the client provides the losing Account SID.

   For details, see: Move Twilio Numbers From One Account To Another



Related Articles


 



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article

OSZAR »