Skip to main content

๐Ÿ‡บ๐Ÿ‡ธ USA Number Porting Guide

A step-by-step guide to porting your U.S. phone number to CloudTalk

V
Written by Valeriia Volobrinskaia
Updated this week

This guide outlines the supported number types, required documents, hosting rules, and porting timelines for U.S. numbers.

Initial Overview

1. Supported Number Types

Number Type

Example Prefixes

Geographic (Local)

All U.S. area codes are portable

Mobile (Wireless)

Portable with a valid 4-digit PIN from the current provider

Toll-Free

+1800, +1833, +1844, +1855, +1866, +1877, +1888

โš ๏ธ SMS Requirements

2. Submit Your Request

You can request number porting using the USA Porting Form.

Looking to port numbers from other countries? Use the International Porting Form or check Global Porting coverage for details.

3. Download LOA Template

Youโ€™ll need to submit a Signed Letter of Authorization (LOA)

(Other document requirements listed below.)

4. Timelines & Pricing

Number Type

Estimated Duration

Pricing

Local

3โ€“10 business days

โ‚ฌ30.00 per request, โ‚ฌ2.00 per number

Mobile

3โ€“10 business days

โ‚ฌ30.00 per request, โ‚ฌ2.00 per number

Toll-Free

3โ€“10 business days

โ‚ฌ30.00 per request, โ‚ฌ4.00 per number

โš ๏ธ Timelines may vary if submitted details do not match your current providerโ€™s records.


Required Documents for Number Porting

โœ… Local Numbers

โœ… Mobile Numbers

  • Signed LOA

  • Latest invoice or proof of ownership

  • PIN Code

    • Typically required by mobile carriers (e.g. Verizon, T-Mobile) and some VoIP platforms

    • Must be requested from your current provider

  • (Optional but recommended) CSR

โœ… Toll-Free Numbers

  • Signed LOA

  • Latest invoice or letter from current provider confirming ownership

How to Obtain a CSR (Customer Service Record)

A Customer Service Record (CSR) is an official document from your current carrier that lists all service-related details tied to your phone number(s). Submitting a CSR can help minimize porting delays and reduce the risk of rejections due to mismatched information.

To obtain your CSR:

  • Contact your current service provider (ask for the Porting Department, if applicable)

  • Request the full Customer Service Record โ€” not just billing records

  • Cross-check the CSR against your LOA to ensure all key details match:

    • Company name

    • Billing address

    • Phone number(s) being ported


Porting Process Overview

  1. Submit Your Porting Request
    Send your request to the CloudTalk Porting Team to begin the process.
    โ€‹

  2. Initial Review
    Cloudtalk team'll verify number portability and confirm the next steps.
    โ€‹

  3. Documentation Collection
    Complete and sign the LOA (Letter of Authorization), and provide a recent invoice from your current telecom provider.
    โ€‹

  4. Submission to Carrier
    CloudTalk submits your request to our partner carrier, who then forwards it to your current provider.
    โ€‹

  5. Approval or Rejection

    • If approved, Cloudtalk team will confirm the porting date (typically 2โ€“4 business days in advance).

    • If rejected, Cloudtalk team will share the reason and guide you on how to correct and resubmit the request.


Common Rejection Reasons

Issue

How to Fix It

Incorrect address or company name

Confirm the correct details with your current provider before submitting the LOA

Missing or incorrect PIN

Request the valid PIN from your mobile or VoIP provider

Unsigned or incorrectly signed LOA

Ensure the LOA is signed by an authorized account holder (no typed signatures)

Outdated invoice or mismatched info

Provide a recent invoice showing the exact number(s) being ported


On Porting Day

  • Your number will switch over to CloudTalk on the scheduled date

  • Your old provider will deactivate the number

  • CloudTalk billing starts the same day

  • We recommend contacting your old provider to make sure the number is removed from your billing


SMS Functionality Note

  • SMS routing is a secondary porting process, and SMS activation can be delayed by up to 1โ€“3 days after the port is complete

  • A2P 10DLC registration must be finished in advance to enable messaging - this can be done simultaneously or in advance of the porting process


Need Help?

Check out our detailed porting articles:

Or reach out to our Porting Team - weโ€™re here to guide you every step of the way.

Did this answer your question?