Skip to main content

Locale Summary

Locale nameBrazil
ISO codeBR
RegionSouth America
Dialing code+55


Use Cases

Short codes are ideal for high-throughput programmatic messaging.

Short codes are approved for specific use cases, so if you are experiencing carrier filtering on long codes, you may be a good candidate for short codes.

Some of the most common use-cases for short codes in Brazil are: 

  • Two-factor authentication (2FA) or one-time passwords (OTP)
  • Promotional alerts
  • Account alert notifications
  • Reminders (appointments, upcoming payments, etc.)

Short codes can only message users on carriers within the countries in which they are provisioned. Although Twilio can provision short codes in multiple countries, if your customers are not located in Brazil, you should not obtain a short code in Brazil.

Short codes require express consent from end-users before any SMS can be sent. Unless you obtain consent, you shall not use a short code. Twilio and the carriers will not support certain types of campaigns, including but not limited to:

  • Those in which express end-user consent cannot be obtained. This includes friend-to-friend invite-based campaigns, as well as opt-ins obtained through lead generation.
  • Campaigns containing unsupported content, which are prohibited by Twilio’s AUP.

The notice period for returning your Short Code is 35 days.

If a Short Code does not receive any traffic in Brazil for extended amount of time, it may get disconnected due to absence of usage without any prior warning.

Traffic restrictions:

  1. Time. Promotionalmessages can only be sent between 9am - 10pm. User agreement is required, in case messages are to be received outside these hours. 
  2. Frequency. 7 Promotional messages per week, maximum. User agreement is required, in case the promotional messages are to be sent more frequently than the limit set. 
  3. Traffic. Promotional and Transactional traffic can not run on the same short code. Promotional (marketing-related messages) and Transactional (OTP/TFA) messages require separate short codes. Not meeting this requirement, will result in your short code withdrawal without any prior notice.

Kindly refer to Brazil Short Code Best Practices for further details about the Short Codes' restrictions, requirements and best practices in Brazil.

Other Options

Only Standard (random number) Short Codes are available in Brazil. Please note, that all Short Codes in Brazil are Free To End User (FTEU). 

Specific short code number availability can be checked upon request, otherwise you will be automatically assigned a random number.

Brazil Short Codes are 5 digits long. Other format requests are handled on a case-by-case basis and are subject to availability.


To apply for a Short Code in Brazil, the following details need to be forwarded via email:

  • Use case
    • Specification for the main purpose of the Short Code
  • Traffic type
    • Promotional/Transactional
  • Privacy Policy
  • Terms & Conditions
  • Short Code type
    • All short codes in Brazil are FTEU
  • Company
    • Brand name
    • Webpage
  • Monthly Volumes 
    • Expected amount of messages sent monthly
    • Estimated traffic start date
  • Content
    • Sample SMS texts. If applicable, please include URL
  • Billing preference
    • Quarterly/Yearly
  • Your Account Sid
  • 2-4 weeks, once all required information and documentation has been submitted.

Please expect delays on all applications submitted in the end of November through mid-January, as Brazil carriers experience an annual provisioning freeze during this period of time.

Regulatory Bodies

Please refer to How Much Does A Short Code Cost? for further details on the pricing.

Next Steps

To apply for a Short Code in Brazil, please follow these steps:

  • Check all the requirements above and collect the needful information.
  • Send the application including all the requirements to

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.