Country Summary

Country nameBrazil
ISO codeBR
RegionSouth America
Mobile country code724
Dialing code+55
Major carriersOi, NEXTEL, CTBC, TIM, Vivo, Claro

Guidelines

Two-way SMS supported No
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 statuses. Several major carriers in Brazil substitute accented characters for ASCII equivalents. Oi, NEXTEL, and CTBC (Algar) do not support Unicode. Sending marketing messages between 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

PreregisteredAlphanumericLong CodeShort Code
Operator network capability --- Not SupportedSupportedSupported
Twilio supported --- --- SupportedNot Supported
Sender ID preserved --- --- No ---
Provisioning time--------
UCS-2 support --------
Use case restrictions ----You can only use Brazil long code phone numbers for person-to-person (P2P) messaging, but outbound sender IDs will not be preserved.--
Best practices ----Include a reply number in the text message for person-to-person (P2P) messaging. You may use a global SMS-capable number from another country to send application-to-person (A2P) messaging to mobile phones in Brazil.--
Preregistered
Operator network capability ---
Twilio supported ---
Sender ID preserved ---
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices --
Alphanumeric
Operator network capabilityNot Supported
Twilio supported ---
Sender ID preserved ---
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices --
Long Code
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedNo
Provisioning time--
UCS-2 support --
Use case restrictions You can only use Brazil long code phone numbers for person-to-person (P2P) messaging, but outbound sender IDs will not be preserved.
Best practices Include a reply number in the text message for person-to-person (P2P) messaging. You may use a global SMS-capable number from another country to send application-to-person (A2P) messaging to mobile phones in Brazil.
Short Code
Operator network capabilitySupported
Twilio supportedNot Supported
Sender ID preserved ---
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices --

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.