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
If you would like to send SMS from your ported numbers you will need to complete A2P Registration.
When you submit your porting request in the Dashboard, the Verification step lets you tell us your A2P 10DLC status: register during porting, already registered with CloudTalk, or voice only.
Local or Mobile numbers - A2P 10DLC registration must be completed to send SMS
- A2P registration can be done prior to porting since it typically takes 1.5-2 weeks.
Toll-Free numbers - A2P Toll-Free Verification must be completed before SMS can be sent through CloudTalk
- Toll-free Verification can only be done after the number has ported in to CloudTalk
2. Submit Your Request
Request porting directly in the CloudTalk Dashboard: open Numbers > Port existing number and follow the guided steps. All supported number types for this country use the same flow, and you can track your request anytime under Numbers > Porting requests.
Looking to port numbers from other countries? See Global Porting Coverage.
3. Letter of Authorization
Where an LOA is required, the correct template for this country downloads inside the Documents step of your porting request: download it, sign it, and upload it right there. You no longer need a separate template from this guide.
(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
Signed Letter of Authorization (LOA)
Latest invoice or proof of ownership
(Optional but recommended) Customer Service Record (CSR)
✅ 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) Customer Service Record (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
Documentation Collection
Complete and sign the LOA (Letter of Authorization), and provide a recent invoice from your current telecom provider.
Submit Your Porting Request
Submit your request in the CloudTalk Dashboard under Numbers > Port existing number to begin the process.
Initial Review
Cloudtalk team'll verify number portability and confirm the next steps.
Submission to Carrier
CloudTalk submits your request to our partner carrier, who then forwards it to your current provider.
CloudTalk will set up placeholder versions of your numbers on your account so you can start configuring the call flow designer and assigning the numbers to your agents so you will be ready for porting day.
Approval or Rejection
If approved, Cloudtalk team will confirm the porting date (typically 1–4 business days in advance).
If rejected, Cloudtalk team will share the reason and guide you on how to correct and resubmit the request.
On the Porting Day
Your calls 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
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 |
Need Help?
Check out our detailed porting articles:
Questions about a request you've already submitted? Open it under Numbers > Porting requests and click Open conversation. Our Porting Team is here to guide you every step of the way.
