|
Locale Summary |
|
|---|---|
|
Locale name |
Brazil |
|
ISO code |
BR |
|
Region |
Latin America |
|
Guidelines |
|
|---|---|
|
Prerequisites |
Upgraded Twilio account: Free trial accounts must upgrade to a paid account. |
|
Restrictions |
RCS messaging in Brazil requires creating an RCS Sender specifically for use in Brazil. Brazil RCS Senders cannot be used to send messages in other countries.
Content Restrictions: The content restrictions for messaging in Brazil are strict and heavily regulated, primarily by the National Telecommunications Agency (ANATEL). Since major carriers like Vivo, Claro, and TIM all adhere to these national guidelines, the restrictions are consistent across the networks. For both Short Code and RCS, the following content is prohibited or highly restricted:
|
|
Requirements |
General Requirements: To get started in Brazil, submit this form
Also, be aware that,
If you plan to use RCS in a region other than Brazil, you can directly submit your RCS sender through Twilio's Console. For more information, please review our documentation.
Carrier Specific Requirements:
|
|
Timeframe |
The RCS onboarding process has two main steps, each with its own timeline. Step 1: Twilio Internal Review After you submit a sender in the Twilio Console, a Twilio RCS onboarding specialist will begin the review process. This initial step is designed to confirm that your submission aligns with all carrier and messaging compliance requirements. The specialist will reach out to you with their findings, highlighting any corrections needed and providing guidance on how to fix them. The overall timeline for this process is variable and depends entirely on the compliance, requirements of your initial submission and your responsiveness to any requested changes. We can only move to the next stage once the submission is fully compliant.
Step 2: Carrier Review Once your sender application passes Twilio's review, we submit it to our carrier partners in Brazil for approval. The final launch timeline can vary and may take longer depending on the use case and specific requirements. The best way to ensure a faster approval is to submit a fully compliant application, as the process can be delayed if carriers require additional information or clarification. Important Note: Please be aware that application timelines may be impacted by carrier network freezes or delays around major holidays. |
|
Pricing |
Learn more here. |
|
Next Steps |
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.