Porting your U.S. phone number to CloudTalk is a straightforward process, but it requires some important steps to ensure a smooth transition. Here's everything you need to know.
Supported Number Types
Local numbers
Toll-free numbers
Mobile (wireless) numbers - with restrictions (PIN required)
Required Documents
Before we can begin, please prepare the following:
Signed Letter of Authorization (LOA) - signed by an account owner or admin on the current account
Recent invoice or proof of ownership – shows ownership of the number or contract with the service provider
CSR– (optional, but highly recommended) - confirms all the official details associated with your phone number. Your current service provider can give you this.
How to Obtain a CSR (Customer Service Record)
A Customer Service Record (CSR) is a document from your current carrier that lists all the official details associated with your phone number(s). This information helps ensure your porting request matches the records on file and reduces the risk of rejection.
To obtain a CSR, follow these steps:
Contact Your Current Carrier
Reach out to your current telecommunications provider. You may need to ask for their Porting Team specifically.
Request the CSR
Clearly specify that you need the Customer Service Record on file, not just your billing records. While billing records may contain similar info, they are not always identical.
Verify the Information
Ensure that the information on your LOA matches what is on the the CSR. This step will prevent rejections due to company name or address mismatches.
Special Requirements
Mobile or Wireless numbers: Require a PIN code from your current provider in order to port the number away
After porting
SMS on fixed and mobile numbers: A2P 10DLC registration must be completed before SMS can be sent through CloudTalk.
SMS on toll-free numbers numbers: A2P Toll-Free Verification must be completed before SMS can be sent through CloudTalk.
Estimated Timelines
1–2 days: Internal checks & LOA submission
5–20 days: Processing with the losing carrier
(timeline may vary based on the carrier and number type)
Step-by-Step Porting Process
Submit a porting request to the CloudTalk Porting Team
We check the portability and confirm details with you
You fill out and sign the LOA
You send us the LOA + invoice
We submit the request to our partner carrier
Our partner carrier forwards the request to your current provider
If accepted, we’ll notify you of the port date (usually 2–4 days in advance)
If rejected, we’ll share the reason and help you correct the info to resubmit
Common Rejection Reasons (and How to Avoid Them)
Incorrect address or company name – Verify with your current provider before submitting
Missing or incorrect PIN – Required for mobile numbers
Unsigned or incorrectly signed LOA – Must be signed by someone authorized
Outdated invoice or mismatched number info – Make sure it shows the number you’re porting.
What Happens on Port 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.