Brazil
Name

Brazil

ISO Code

BR

Region

South America

Mobile Country Code

724

Dialing code

+55

Major carriers

Oi, NEXTEL, CTBC, TIM, Vivo, Claro

Guidelines for Brazil
Two-way SMS supported

No

Number portability available

Yes

Twilio concatenated message support

Yes

Message length

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

Twilio MMS support

Converted to SMS with embedded URL

Sending SMS to landline numbers

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.

Best practices

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 ensure 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 and Sender ID
Preregistered
Operator network capability

Not Available

Twilio supported

--

Sender ID format

--

Sender ID preserved

--

Two-way support

--

Provisioning time

--

Cost
--
Throughput (messages per second)
--
Use case restrictions
--
Best practices
--
Alphanumeric
Operator network capability

Not Available

Twilio supported

--

Sender ID format

--

Sender ID preserved

--

Two-way support

--

Provisioning time

--

Cost

--

Throughput (messages per second)

--

Use case restrictions

--

Best practices

--

Long Code
Operator network capability

Available

Twilio supported

Supported

Sender ID format

Mobile

Sender ID preserved

No

Two-way support

No

Provisioning time

--

Cost

Refer to our pricing page

Throughput (messages per second)

--

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 capability

Available

Twilio supported

Not Supported

Sender ID format
--
Sender ID preserved
--
Two-way support
--
Provisioning time
--
Cost
--
Throughput (messages per second)
--
Use case restrictions
--
Best practices
--
The Twilio advantage
  • Communicate reliably

    Experience a 99.95% uptime SLA made possible with automated failover and zero maintenance windows.

  • Operate at scale

    Extend the same app you write once to new markets with configurable features for localization and compliance.

  • Many channels

    Use the same platform you know for voice, SMS, video, chat, two-factor authentication, and more.

  • No shenanigans

    Get to market faster with pay-as-you-go pricing, free support, and the freedom to scale up or down without contracts.