Locale Summary |
|
---|---|
Locale name |
Canada |
ISO code |
CA |
Region |
North America |
Dialing code |
+1 |
Guidelines |
|
---|---|
Portable Numbers |
|
Restrictions |
Most numbers are portable. In rare cases, Twilio may not have rate-center (geographic) coverage for particular phone numbers. |
Required Information |
Most mobile operators require account numbers and PINs to port; some providers also require account PINs to port out. Before porting, check with your current provider to see whether a PIN is required and, if so, what it is. Note that your LOA must show your actual Canadian service address for the number(s) to be ported. We will send this document to your current provider to request the numbers' release; the address must match their records. Please reach out to porting@twilio.com with questions or concerns. |
Timeframe |
Once you submit all required documentation/information, up to 4 weeks, depending on the complexity of the port and time required by the current service provider. Please note that you will need to approve the port within a 90-minute timeframe from receiving the port approval SMS text from the losing provider. Unless you respond to the text message within the given timeframe, the port will get rejected. |
Regulatory Bodies |
The Canadian Radio-television and Telecommunications Commission (CRTC) |
Other Details |
|
How To Submit |
For Canadian toll-free numbers, submit your request directly via the Twilio Console. For Geographic (local) and Mobile numbers, submit your port request via the porting form here. You can find all the requirements needed here. |
For the benefit of all our customers, these guidelines are provided to help you comply with applicable requirements and to help ensure Twilio's platform remains compliant with global telecommunications ecosystem requirements. These guidelines represent our current understanding of common compliance requirements generally applicable to Twilio and its customers, and do not constitute legal advice. By posting these guidelines, Twilio makes no assurances regarding the legal compliance of your application built using our APIs. You are expected to understand and abide by all compliance obligations applicable to your specific application. You should check these pages regularly for updates as telecommunications ecosystem requirements continue to evolve and change, and the information below may be updated or changed without notice.