Country Summary

Country nameCanada
ISO codeCA
RegionNorth America
Mobile country code302
Dialing code+1

Guidelines

Two-way SMS supported Yes
Number portability availableYes
Twilio concatenated message supportYes
Message lengthInbound long code: GSM 3.38=136, Unicode=70 Outbound long code: GSM 3.38=136, Unicode=70
Twilio MMS supportSupported
Sending SMS to landline numbersTwilio will not check whether the number is a landline and will attempt to send it to our carrier for delivery. Some carriers will convert the SMS into text-to-speech messages via voice calls.
Compliance considerations

Twilio recommends sending application-to-person (A2P) traffic over short codes for optimal delivery results. Canada mobile carriers enforce strict filtering on Application-To-Person (A2P) messages. The mobile carriers would not lift this filtering but mobile subscribers can reach out to their mobile carrier to petition.  

Twilio strongly encourages customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws. The following are some general best practices:

  1. Get opt-in consent from each end user before sending any communication to them, particular for marketing or other non-essential communications.
  2. Only communicate during an end user's daytime hours unless it is urgent.
  3. SMS campaigns should support HELP/STOP messages, and similar messages, in the end user's local language.
  4. Do not contact end users on do-not-call or do-not-disturb registries.

Phone Numbers & Sender ID

AlphanumericLong CodeShort Code
Pre-registrationDynamicDomesticInternational
Operator network capabilityNot SupportedNot SupportedSupported --- Supported
Twilio supported --- --- Supported --- Supported
Sender ID preserved --- --- Yes --- Yes
Provisioning timeN/AN/AN/AN/A8-12 weeks
UCS-2 support------Supported---Supported
Use case restrictions

N/A

N/A

Application-to-person (A2P) messages sent via long codes may be subject to carrier filtering. Learn more about carrier filtering.

N/A

None specifically, but they follow US policies in certain cases.

Best practices

N/A

N/A

N/A

N/A

The character limit for Canada short code SMS is 160 ASCII characters. Messages with more than 160 characters will not be delivered. Also refer to our FAQ for short code best practices about: + Mobile Marketing Opt-In + Help and Stop Standards + Opt-In S

Alphanumeric - Pre-registration
Operator network capabilityNot Supported
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 support---
Use case restrictions

N/A

Best practices

N/A

Alphanumeric - Dynamic
Operator network capabilityNot Supported
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 support---
Use case restrictions

N/A

Best practices

N/A

Long Code - Domestic
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedYes
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

Application-to-person (A2P) messages sent via long codes may be subject to carrier filtering. Learn more about carrier filtering.

Best practices

N/A

Long Code - International
Operator network capability ---
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 support---
Use case restrictions

N/A

Best practices

N/A

Short Code
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedYes
Provisioning time8-12 weeks
UCS-2 supportSupported
Use case restrictions

None specifically, but they follow US policies in certain cases.

Best practices

The character limit for Canada short code SMS is 160 ASCII characters. Messages with more than 160 characters will not be delivered. Also refer to our FAQ for short code best practices about: + Mobile Marketing Opt-In + Help and Stop Standards + Opt-In S

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.