Skip to main content

Locale Summary

Locale nameBrazil
ISO codeBR
RegionSouth America
Mobile country code724
Dialing code+55

Guidelines

Two-way SMS supported Yes
Number portability availableYes
Twilio concatenated message supportYes
Message length140 characters-per-segment for NEXTEL. 160 characters-per-segment for all other carriers.
Twilio MMS supportConverted to SMS with embedded URL
Sending SMS to landline numbersYou 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

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 21:00 local time is prohibited. Be aware that Brazil spans three time zones. Messages promoting politicians, political causes, gambling, contests, or telecommunication services are prohibited.

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 capabilitySupportedNot SupportedSupportedNot SupportedSupported
Twilio supported Supported --- SupportedSupportedSupported
Sender ID preservedYes --- YesNoYes
Provisioning time10 weeksN/AN/AN/A2-4 weeks
UCS-2 supportSupportedN/ASupportedSupportedN/A
Use case restrictions

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

N/A

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

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

N/A

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.

Alphanumeric - Pre-registration
Operator network capabilitySupported
Twilio supported Supported
Sender ID preservedYes
Provisioning time10 weeks
UCS-2 supportSupported
Use case restrictions

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

Best practices

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

Alphanumeric - Dynamic
Operator network capabilityNot Supported
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
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

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

Best practices

N/A

Long Code - International
Operator network capabilityNot Supported
Twilio supportedSupported
Sender ID preservedNo
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

N/A

Best practices

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.

Short Code
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedYes
Provisioning time2-4 weeks
UCS-2 supportN/A
Use case restrictions

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

Best practices

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

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.