Brazil (BR)

Locale name

Brazil

ISO code
The International Organization for Standardization two character representation for the given locale.

BR

Region

South America

Mobile country code
A three digit code associated with the given locale and used in conjunction with a Mobile Network Code to uniquely identify mobile networks.

724

Dialing code
The dialing prefix used to establish a call or send an SMS from one locale to the given locale.

+55

Two-way SMS supported
Whether Twilio supports two-way SMS in the given locale.

Yes

Number portability available
Whether number portability is available in the given locale.

Yes

Twilio concatenated message support
Concatenation refers to the capability of splitting a message that is too long to be sent in one SMS into smaller pieces and then joining the pieces at the receiving end so that the receiver sees the message as one. 

Yes*
For certain sender ID types this may not be supported. Where messages are split and rejoined may vary based on character encoding.

Message length
How many characters can be sent given a particular message encoding before the message will be split into concatenated segments.

140 characters-per-segment for NEXTEL. 160 characters-per-segment for all other carriers.

Twilio MMS support
Multimedia Messaging Service (MMS) provides a standards-based means to send pictures and video to mobile phones.

Converted to SMS with embedded URL

Sending SMS to landline numbers
How Twilio handles an SMS message destined for landline telephone number.

You cannot send SMS to a landline destination number: the Twilio REST API will throw a 400 response with error code 21614, the message will not appear in the logs, and the account will not be charged.

Compliance considerations
Twilio strongly encourages customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws. This table lists some general best practices.

Oi does not support delivery report. Several major carriers in Brazil substitute accented characters for ASCII equivalents. Oi, NEXTEL, and CTBC (Algar) do not support unicode. Sending marketing messages outside the hours of 09:00 and 22:00 local time and all day on Sunday is prohibited. Be aware that Brazil spans three time zones. Messages promoting contests or telecommunication services are prohibited. Sending adult content, controlled substance, and cannabis related content are also strictly prohibited.

Message delivery to M2M numbers is on best effort basis only.

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.

Operator network capability
Whether mobile operators in the given country support the feature.

Supported (Optional)

There is no segregation between International and Domestic Traffic

Not Supported

Twilio supported
Whether Twilio supports the feature for the given country.

Supported (Optional)
Learn more and register via the Console

---

Sender ID preserved
In some countries sender IDs for certain sender types are not preserved and are changed for compliance and/or deliverability reasons. In these countries mobile subscribers will see a different ‘from sender ID’ than the one sent by you.

Yes

---

Provisioning time
Provisioning is the process of getting the sender ID approved and registered with mobile networks (depending on country requirements). Provisioning time is how long this process takes in the given country.

10 weeks

N/A

UCS-2 support

Supported

N/A

Use case restrictions

The Pre-Registration is optional and available only for TIM, CLARO and VIVO networks

N/A

Best practices

We would suggest requesting only an Uppercase Sender ID as VIVO networks only supports Uppercase Sender ID Registration

N/A

Operator network capability
Whether mobile operators in the given country support the feature.

Supported

Not Supported

Supported

Twilio supported
Whether Twilio supports the feature for the given country.

Supported

Supported

Supported

Sender ID preserved
In some countries sender IDs for certain sender types are not preserved and are changed for compliance and/or deliverability reasons. In these countries mobile subscribers will see a different ‘from sender ID’ than the one sent by you.

Yes

No

Yes

Provisioning time
Provisioning is the process of getting the sender ID approved and registered with mobile networks (depending on country requirements). Provisioning time is how long this process takes in the given country.

N/A

N/A

2-4 weeks

UCS-2 support

Supported

Supported

N/A

Use case restrictions

You can only use Brazil long code phone numbers for person-to-person (P2P) messaging.

N/A

Please refer to Brazil Short Code Best Practices for further information.

Best practices

N/A

You may use a global SMS-capable number from another country to send application-to-person (A2P) messaging to mobile phones in Brazil. SenderId is not preserved and may be overwritten with a random shortcode or longcode outside Twilio's platform.

Please refer to Brazil Short Code Best Practices for further information.