# Porting Options: US In-App vs International Manual Process > Step-by-step to port a non-Twilio number into a GHL Customer Care Location, with cut-over checks plus A2P/Toll-Free and international compliance tips. - Source: https://docs.ghlcustomercare.com/docs/phone-system/phone-numbers/porting-options-us-in-app-vs-international-manual-process - Section: Phone System / Phone numbers - Reading time: 7 min - Images: 5, each explained below - Modified on Thu, 3 Sep at 9:43 AM --- This guide explains how to port a phone number from an external carrier into a GHL Customer Care sub-account. It covers the required documents, how to submit a port request, and what to expect during the transfer process. Please prepare the information mentioned in the article and complete the Porting Form. --- **TABLE OF CONTENTS** - [What is Porting a Phone Number?](#what-is-porting-a-phone-number)  - Prerequisites - Billing Statement Requirement - Decide Your Destination Carrier (Important) - [US Phone Number Porting: In-App Flow](#us-phone-number-porting-in-app-flow) - [US Phone Number Porting: Manuel Port Request](#us-phone-number-porting-manuel-port-request) - [Step 1: Gather documents](#step-1-gather-documents) - [Step 2: Complete the High-Level Porting Form (US numbers)](#step-2-complete-the-high-level-porting-form-us-numbers) - [Step 3: Approval & FOC (Firm Order Commitment)](#step-3-approval-and-foc-firm-order-commitment) - [International Phone Number Porting](#international-phone-number-porting) - [After Your Number is Ported](#after-your-number-is-ported) - [Frequently Asked Questions](#frequently-asked-questions) - [Related Articles](#related-articles) --- # **What is Porting a Phone Number?**  Porting a number is the transfer of a phone number between two telecom service providers. The process involves providing the right documentation to prove ownership of the number as well as the execution of the transfer between the current provider and the new provider.  When you’re ready to port your number, you’ll just need to send us a signed Letter of Authorization (LOA) that matches the service information your current carrier has on file. Once you submit your LOA, we’ll handle coordination with your current carrier to complete the port.  The porting process takes between two and four weeks from when you submit the required documentation for port requests of fewer than 50 numbers and six to eight weeks for larger, more complex ports. During this process, you’ll have full access to your phone number, as there is no downtime associated with porting a phone number. You can find the Porting form here. **IMPORTANT! PLEASE READ** 1\. All Wireless Numbers REQUIRE a Pin for Port Requests. Providing a incorrect or fake pin in this box will cause the port request to be rejected by our carrier. 3\. Please double check with your provider to make sure your wireless number has a pin and the pin is correct to avoid delays in the number porting process 4\. If you are porting multiple numbers. Please check if there are multiple unique pins per number, if your carrier/provider allows a single pin for multiple numbers please note this in the wireless number pin field above. 5\. Landline and Toll Free Port Request may not need a pin **Note:** Name & address must match your carrier records exactly. PO Boxes are not accepted as service addresses. --- ## **US Phone Number Porting: In-App Flow** US phone numbers use GHL Customer Care's dedicated port-in process. Keeping the complete US workflow in one resource ensures you have the latest requirements, submission steps, and request-tracking information without relying on duplicate instructions that may become outdated. For complete instructions, see [](https://docs.ghlcustomercare.com/docs/phone-system/phone-numbers/how-to-submit-and-track-port-in-number-requests)[How to Submit and Track Port-In Number Requests](https://docs.ghlcustomercare.com/docs/phone-system/phone-numbers/how-to-submit-and-track-port-in-number-requests) The dedicated guide covers: - Port-in eligibility and prerequisites - Information and documents required to submit a request - Submitting a port-in request from GHL Customer Care - Letter of Authorization (LOA) requirements - Tracking the status of a port request - Resolving rejected port requests - What to expect while a port is being processed **Important:** Follow the requirements in the dedicated US port-in guide rather than using a manual porting form for the US in-app workflow. We are currently able to port in numbers **from United States** only through this flow. For international numbers, please [reach out to support](https://docs.ghlcustomercare.com/docs/customer-support/general-support-info/24-7-customer-support-options "reach out to support") so we can submit[**Twilio's International Porting Form**](https://twlo.my.salesforce-sites.com/InternationalPorting "Twilio's International Porting Form")for you. ![US Phone Number Porting: In-App Flow (image 1 of 5)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155079848583/original/ktxZ8OYPDOQRjAR0vqmabBdcV4FOHNavzQ.png) **US Phone Number Porting: In-App Flow (image 1 of 5)** This screenshot appears in the "US Phone Number Porting: In-App Flow" section of "Porting Options: US In-App vs International Manual Process". The text alongside this image reads: Important: Follow the requirements in the dedicated US port-in guide rather than using a manual porting form for the US in-app workflow. We are currently able to port in numbers from United States only through this flow. For international numbers, please reach out to support so we can submit…. This part of the guide covers 7 fields, listed below. Immediately after, the guide continues: Manual port request may be required for some US phone numbers or porting scenarios that are not supported by the dedicated in-app workflow. Accurate carrier information is critical when a phone number must go through a manual porting…. - How to confirm: Important: Follow the requirements in the dedicated US port-in guide rather than using a manual porting form for the US in-app workflow. We are currently able to port in numbers from United States only through this flow. For international numbers, please reach out to support so we can submit Twilio's International Porting Form for you. - Fields: Port-in eligibility and prerequisites, Information and documents required to submit a request, Submitting a port-in request from GHL Customer Care, Letter of Authorization (LOA) requirements, Tracking the status of a port request, Resolving rejected port requests, What to expect while a port is being processed - Controls: from United States, Twilio's International Porting Form - Next: Manual port request may be required for some US phone numbers or porting scenarios that are not supported by the dedicated in-app workflow. Accurate carrier information is critical when a phone number must go through a manual porting process. The information submitted for a port request generally needs to match the records maintained by the current carrier to reduce the likelihood of rejection or processing delays. Full procedure: 1. Port-in eligibility and prerequisites 2. Information and documents required to submit a request 3. Submitting a port-in request from GHL Customer Care 4. Letter of Authorization (LOA) requirements 5. Tracking the status of a port request 6. Resolving rejected port requests 7. What to expect while a port is being processed --- ## **US Phone Number Porting: Manuel Port Request** Manual port request may be required for some US phone numbers or porting scenarios that are not supported by the dedicated in-app workflow. Accurate carrier information is critical when a phone number must go through a manual porting process. The information submitted for a port request generally needs to match the records maintained by the current carrier to reduce the likelihood of rejection or processing delays. **IMPORTANT**: We are currently able to port in numbers **from United States only**. For international numbers, please [reach out to support](https://docs.ghlcustomercare.com/docs/customer-support/general-support-info/24-7-customer-support-options "reach out to support") so we can submit[**Twilio's International Porting Form**](https://twlo.my.salesforce-sites.com/InternationalPorting "Twilio's International Porting Form")for you. #### **Step 1:** Gather documents - LOA (Letter of Authorization) — signed by the authorized person. Note that the **company name field** (as shown in the screenshot) on the **LOA** can be **left blank**. ![Step 1 of 5: LOA (Letter of Authorization) — signed by the authorized person. Note…](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155079925262/original/_zRU3E9Y0PI2CVy1AKOZzsI2vJNw9ANuBQ.png) **Step 1 of 5: LOA (Letter of Authorization) — signed by the authorized person. Note…** This screenshot accompanies step 1 of 5 in the "Step 1: Gather documents" section of "Porting Options: US In-App vs International Manual Process". At this point in the walkthrough you LOA (Letter of Authorization) — signed by the authorized person. Note that the company name field (as shown in the screenshot) on the LOA can be left blank. The next step is to latest phone bill — clear/legible PDF, provided by the phone carrier. - What this covers: LOA (Letter of Authorization) — signed by the authorized person. Note that the company name field (as shown in the screenshot) on the LOA can be left blank. - Controls: company name field, LOA, left blank, Latest phone bill, PDF, must not be older than 90 days, Google Voice, Landline or VoIP numbers, no bill is available, List of numbers to port, E.164, Location ID - Next: Latest phone bill — clear/legible PDF, provided by the phone carrier. Full procedure: 1. LOA (Letter of Authorization) — signed by the authorized person. Note that the company name field (as shown in the screenshot) on the LOA can be left blank. <- this image 2. Latest phone bill — clear/legible PDF, provided by the phone carrier. 3. List of numbers to port — in E.164 format (e.g., +15551234567). 4. Location ID — destination sub‑account. (Find it in the Location: Settings → Business Profile.) 5. Carrier account details — account # and PIN/Passcode for any wireless numbers. ![Step 1 of 5: LOA (Letter of Authorization) — signed by the authorized person. Note…](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155058842655/original/V_oYDFgRxSYGkU7SwhxqzMDOuQTepdCtLw.png) **Step 1 of 5: LOA (Letter of Authorization) — signed by the authorized person. Note…** This screenshot accompanies step 1 of 5 in the "Step 1: Gather documents" section of "Porting Options: US In-App vs International Manual Process". At this point in the walkthrough you LOA (Letter of Authorization) — signed by the authorized person. Note that the company name field (as shown in the screenshot) on the LOA can be left blank. The next step is to latest phone bill — clear/legible PDF, provided by the phone carrier. - What this covers: LOA (Letter of Authorization) — signed by the authorized person. Note that the company name field (as shown in the screenshot) on the LOA can be left blank. - Controls: company name field, LOA, left blank, Latest phone bill, PDF, must not be older than 90 days, Google Voice, Landline or VoIP numbers, no bill is available, List of numbers to port, E.164, Location ID - Next: Latest phone bill — clear/legible PDF, provided by the phone carrier. Full procedure: 1. LOA (Letter of Authorization) — signed by the authorized person. Note that the company name field (as shown in the screenshot) on the LOA can be left blank. <- this image 2. Latest phone bill — clear/legible PDF, provided by the phone carrier. 3. List of numbers to port — in E.164 format (e.g., +15551234567). 4. Location ID — destination sub‑account. (Find it in the Location: Settings → Business Profile.) 5. Carrier account details — account # and PIN/Passcode for any wireless numbers. - **Latest phone bill** — clear/legible **PDF**, provided by the phone carrier. - The billing statement **must not be older than 90 days**. - The document must clearly show the phone number(s), account owner name, and provider name. - For **Google Voice** numbers, provide a screenshot showing the phone numbers and associated email assress. - For **Landline or VoIP numbers**, Provide the latest monthly billing statements whenever possoble. - If **no bill is available**, a receipt or account portal screenshot displaying the numbers and owner may be accepted. - **List of numbers to port** — in **E.164** format (e.g., `+15551234567`). - **Location ID** — destination sub‑account. _(Find it in the Location:_ **_Settings → Business Profile_**_.)_ - **Carrier account details** — account # and **PIN/Passcode** for any **wireless** numbers. _ ![Step 5 of 5: Carrier account details — account # and PIN/Passcode for any wireless…](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155054088147/original/x_YH0z1VALLLlkJeQKy9xQErsE4uQaYjwA.png) **Step 5 of 5: Carrier account details — account # and PIN/Passcode for any wireless…** This screenshot accompanies step 5 of 5 in the "Step 1: Gather documents" section of "Porting Options: US In-App vs International Manual Process". At this point in the walkthrough you carrier account details — account # and PIN/Passcode for any wireless numbers. - What this covers: Carrier account details — account # and PIN/Passcode for any wireless numbers. - Controls: Carrier account details, PIN/Passcode, wireless, company name field, LOA, left blank, Latest phone bill, PDF, must not be older than 90 days, Google Voice, Landline or VoIP numbers, no bill is available Full procedure: 1. LOA (Letter of Authorization) — signed by the authorized person. Note that the company name field (as shown in the screenshot) on the LOA can be left blank. 2. Latest phone bill — clear/legible PDF, provided by the phone carrier. 3. List of numbers to port — in E.164 format (e.g., +15551234567). 4. Location ID — destination sub‑account. (Find it in the Location: Settings → Business Profile.) 5. Carrier account details — account # and PIN/Passcode for any wireless numbers. <- this image _ #### **Step 2:** Complete the High-Level Porting Form (US numbers) Complete the manual port request form (Click here to view the form). Provide the following information. - **Agency Relationship Number.** - **Contact name + email** - support updates will go to this email. - **Location ID** (destination). - **Customer/Business legal name** and **service address** — must match the carrier’s records exactly. - **Landline/Toll‑Free numbers** (if any). - **Wireless numbers** (if any) + **Account # + PIN/Last 4 SSN**. - **Upload required PDFs:** LOA and Billing Statements. After filling in the required information, check the consent boxes and submit the porting form. Expect a brief service impact during the port window. Keep the old carrier active until completion. **Please Note:** Your Letter of Authorization and Billing Statement(s) must be **PDF** files and cannot exceed **4MB**. ![Step 2: Complete the High-Level Porting Form (US numbers) (image 5 of 5)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155054088581/original/RaM3J1q1AfqHnQ-1Jd-KLOz6H_vDkdDgDQ.png) **Step 2: Complete the High-Level Porting Form (US numbers) (image 5 of 5)** This screenshot appears in the "Step 2: Complete the High-Level Porting Form (US numbers)" section of "Porting Options: US In-App vs International Manual Process". The text alongside this image reads: Please Note: Your Letter of Authorization and Billing Statement(s) must be PDF files and cannot exceed 4MB. Immediately after, the guide continues: After submission, you’ll receive status updates via email. When approved, the carrier issues a FOC date/time window. Same‑day or date‑specific ports are not guaranteed. - What this covers: Please Note: Your Letter of Authorization and Billing Statement(s) must be PDF files and cannot exceed 4MB. - Controls: Agency Relationship Number., Contact name + email, Location ID, Customer/Business legal name, service address, Landline/Toll‑Free numbers, Wireless numbers, Account # + PIN/Last 4 SSN, PDF, 4MB - Next: After submission, you’ll receive status updates via email. When approved, the carrier issues a FOC date/time window. Same‑day or date‑specific ports are not guaranteed. Full procedure: 1. Agency Relationship Number. 2. Contact name + email - support updates will go to this email. 3. Location ID (destination). 4. Customer/Business legal name and service address — must match the carrier’s records exactly. 5. Landline/Toll‑Free numbers (if any). 6. Wireless numbers (if any) + Account # + PIN/Last 4 SSN. 7. Upload required PDFs: LOA and Billing Statements. #### **Step 3:** Approval & FOC (Firm Order Commitment) - After submission, you’ll receive **status updates via email**. - When approved, the carrier issues a **FOC date/time window**. Same‑day or date‑specific ports are **not guaranteed**. --- ## **International Phone Number Porting** International phone number porting is not currently available through the standard GHL Customer Care port-in workflow. The standard flow currently supports porting in numbers from the United States only. If you need to port an international number, please contact [GHL Customer Care Support.](https://docs.ghlcustomercare.com/docs/customer-support/general-support-info/24-7-customer-support-options) Our support team can submit Twilio's [International Porting Form](https://twlo.my.salesforce-sites.com/InternationalPorting) on your behalf and provide guidance on the required information and documentation. International porting availability and requirements vary by country, number type, and telecommunications provider. Additional documentation or regulatory information may be required before the number can be transferred. --- ## **After Your Number is Ported** Completing a number transfer does not automatically complete every messaging or regulatory requirement associated with the number. Review the requirements for the number type and destination before using the newly ported number for customer communications. For applicable numbers: - **US local numbers:** Review [A2P 10DLC requirements](https://docs.ghlcustomercare.com/docs/phone-system/a2p-registration/what-is-a2p-10-dlc-brand-and-campaign-registration) and ensure applicable numbers are associated with the appropriate approved campaign before sending SMS/MMS. - **US and Canadian toll-free messaging:** Complete [Toll-Free Verification](https://docs.ghlcustomercare.com/docs/phone-system/phone-numbers/toll-free-number-verification-guide-for-lc-phone-us-canada) as required before using the number to send SMS/MMS to US and Canadian recipients. - **International numbers:** Ensure [applicable regulatory requirements](https://docs.ghlcustomercare.com/docs/phone-system/lc-phone-system/regulatory-bundle-and-address-creation-for-sub-accounts), addresses, or other country-specific documentation have been completed. Keep your previous carrier account active until the port is confirmed as complete and you have verified that the number is working as expected. --- ## **Frequently Asked Questions** **Q. What is the difference between the in-app port-in and the manual form?**  The in-app option is available to Agency Owners and Admins with Labs enabled, supports US numbers only, and auto-generates the LOA. The manual form supports both LC Phone and Twilio destinations and requires you to upload a signed LOA yourself. Both options result in the same outcome your number ported into GHL Customer Care. **Q. Where can I find the porting form?** Here is a link to the Porting Form. **Q. Can you port on a specific date/time?** Carriers do not guarantee exact dates/times. We’ll request preferences where available and confirm the port window once the carrier issues FOC. **Q. Will SMS history move with the number?** No. Porting moves the number; it does not migrate historic logs/conversations. Export any critical history from your prior provider. **Q. Can I change destination (LC Phone ↔ Twilio) after I submit?** No, the request once submitted cannot be changed. However, reach out to [GHL Customer Care support](https://docs.ghlcustomercare.com/docs/customer-support/general-support-info/24-7-customer-support-options) for any assistance. **Q. Do I need to cancel my old carrier?** Only after the port completes and you’ve verified calls/messages are working in GHL Customer Care. **Q. My port request was rejected, what do I do?** Check the description shown in the Port-In Numbers tab (in-app) or the email notification for the rejection reason. Common causes include an invalid address, mismatched account number, incorrect PIN, suspended account, or a billing statement older than 90 days. **Important: Rejected requests cannot be edited.** You must **delete the request and create a brand new one** with corrected information. Contact your current carrier to verify the correct details before resubmitting. --- ## **Related Articles** - [](https://docs.ghlcustomercare.com/docs/phone-system/phone-numbers/how-to-submit-and-track-port-in-number-requests)[How to Submit and Track Port-In Number Requests](https://docs.ghlcustomercare.com/docs/phone-system/phone-numbers/how-to-submit-and-track-port-in-number-requests) - [Moving Phone Numbers: Migration Guide](https://docs.ghlcustomercare.com/docs/phone-system/general/moving-phone-numbers-migration-guide)  - [Moving Phone Numbers across accounts (US and International)](https://docs.ghlcustomercare.com/docs/phone-system/phone-numbers/moving-phone-numbers-across-accounts-us-and-international)  - [How to Move Numbers Between Sub-Accounts (Same Agency)](https://docs.ghlcustomercare.com/docs/phone-system/phone-numbers/moving-numbers-between-sub-accounts-same-agency)  - [Toll-Free Number Verification Guide for LC Phone](https://docs.ghlcustomercare.com/docs/phone-system/phone-numbers/toll-free-number-verification-guide-for-lc-phone-us-canada)[](https://docs.ghlcustomercare.com/docs/phone-system/phone-numbers/toll-free-number-verification-guide-for-lc-phone-us-canada) --- Documentation for GHL Customer Care. Support: support@ghlcustomercare.com