SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Why should I provide a CSR with my port request?

 

Providing a Customer Service Record (CSR) with your port request is highly beneficial for several reasons:

  1. Proof of Ownership: A CSR serves as a document of proof for a given phone number. It confirms your right to port the number by detailing the authorized parties and the service address.
  2. Accuracy: The CSR contains the exact information that your current carrier has on file. By ensuring that the information on your Letter of Authorization (LOA) matches the CSR, you significantly reduce the chances of discrepancies that could lead to port request rejections.
  3. Reduced Rejections: One of the most common reasons for port request rejections is mismatched information. By providing a CSR, you align your request with the carrier's records, thereby minimizing the likelihood of rejection.
  4. Efficiency: While obtaining a CSR may require some effort initially, it can save time in the long run by preventing delays and rejections. This ensures a smoother and faster porting process.
  5. Clarity in Reseller Situations: If your carrier is reselling services from another provider, the CSR will reflect the underlying carrier's records, which may differ from your billing information. This clarity is crucial for successful porting.

In summary, providing a CSR with your port request enhances the accuracy and efficiency of the process, reducing the risk of rejections and ensuring a smoother transition.

Have more questions? Submit a request
Powered by Zendesk