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.

Number is “rejected” during the porting process

When a phone number is "rejected" during the porting process, it indicates that the current carrier has not approved the transfer request to Twilio. Here are some common reasons for such rejections and steps to address them. You can read more about common reasons for port request rejections here.

  1. Incorrect Account Information: Ensure that the account PIN, address, and zip code match exactly with the current carrier's records. Any discrepancies can lead to rejection.
  2. Unauthorized User: The port request must be made by an authorized user on the account. Verify that the person initiating the port is recognized by the carrier as having the authority to do so.
  3. Obtain a CSR: The surest way to reduce the likelihood of rejection is to obtain a Customer Service Record (CSR) from your current carrier. This document provides the necessary information to ensure that your port request matches the carrier's records. You can read more about obtaining a CSR here.
  4. Carrier-Specific Issues: Sometimes, rejections occur due to carrier-specific issues such as an invalid VAT number or an incomplete range of numbers. In such cases, contacting the carrier directly to resolve these issues is necessary.

Please take a look at this port-in guide attachment; it will help you to answer most of your questions about port in at Twilio and how to avoid rejections.

By addressing these common issues, you can increase the chances of a successful porting process. If a rejection occurs, it's important to reach out to the current carrier to understand the specific reason and take corrective action.

Have more questions? Submit a request
Powered by Zendesk