---
title: "Brazil SMS Guideline"
slug: "brazil-sms-guideline"
description: "Follow Brazil SMS guidelines in Insider One to comply with local SMS regulations, sender requirements, and messaging best practices for campaigns."
updated: 2026-05-14T12:23:40Z
published: 2026-05-14T12:23:40Z
canonical: "academy.insiderone.com/brazil-sms-guideline"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://academy.insiderone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Brazil SMS Guideline

You can refer to the SMS guidelines for Brazil, which will assist you during onboarding.

| Locale Name | ISO Code | Region | Dialing Code | Available Routes |
| --- | --- | --- | --- | --- |
| Brazil | BR | South America | +55 | Promotional Transactional |

## Promotional Routes

Below, you can see the guidelines for promotional routes:

| Available Sender IDs | Dedicated Short Code (e.g., 33058) | Shared Short Code (e.g., 26640) |
| --- | --- | --- |
| Comparison of Sender IDs | - 100 MPS is the default. - Registration takes 4-6 weeks. - Two different short codes are required to send Promotional and Transactional SMS. | 100 MPS is the default. |
| Opt-out Options for Sender IDs | - Unsubscribe with External/Internal Link - Unsubscribe with Keyword | Unsubscribe with External/Internal Link |

## Required Information for Shortcodes

| Information | Additional Information and Necessary Documents |
| --- | --- |
| Use Case | The primary purpose of the shortcode |
| Traffic type | Promotional or Transactional |
| Privacy Policy URL | URL Needed |
| Terms & Conditions URL | URL Needed |
| Short Code type | All shortcodes in Brazil are FTEU |
| Company | Brand name Webpage |
| Monthly Volumes | Expected number of messages sent monthly Estimated traffic start date |
| Content | Sample SMS texts If applicable, you can include a URL. |
| Billing preference | Quarterly or Yearly |

## Transactional Routes

SenderID approval processes are the same for transactional routes to use the [SMS transactional API](/v1/docs/send-transactional-sms).