Skip to main content

​
Brazil Anatel Sender-ID Registration Rules

Brazil (BR) is the largest A2P SMS market in Latin America, and Anatel — the Agência Nacional de Telecomunicações — runs a sender-registration regime that every carrier in the country enforces at the edge. An alphanumeric Sender ID reaches a +55 handset only once that Sender ID holds a country-level approved registration; unregistered and unmanaged alphanumeric senders are filtered rather than delivered with a degraded sender. This page expands the BR row of the country-requirements matrix so you can close the Brazil items deliberately instead of re-reading one JSON blob per launch. Brazil is a tenant-owned burden. Orbit never mandates your posture — it keeps the country-rules reference that feeds the send-time gates, and it gives you the consent ledger, quiet-hours, and opt-out surfaces below. The legal posture is yours.
This page is documentation, not legal advice. Anatel blocks unregistered alphanumeric senders at the carrier edge — traffic on a Sender ID with no approved BR entry does not deliver — and the LGPD consent duty is enforced against the sender by the ANPD. Have counsel review your sender-name choice, your consent capture, and your SAIR handling; Orbit supplies the surfaces.

​
How this page differs from the LGPD page

Orbit has two Brazil compliance pages because Brazil’s regime runs on two separate axes: Read both before a Brazil launch: the LGPD page for the consent and data-subject-rights posture, and this page for the sender-readiness and send-gate posture.

​
The Brazil-specific rules

Read the BR row of GET /compliance/country-rules?channel=sms (see Country Compliance Requirements). Consolidated: The registration: required level is the load-bearing one: BR does gate sends on it. An unregistered alphanumeric sender does not gracefully fall back — it disappears at the carrier edge. Treat the registration as a launch prerequisite, not a recommendation.

​
Anatel’s sender-registration regime

Anatel is Brazil’s telecommunications regulator, and the three dominant carriers (Claro, Vivo, TIM) treat A2P SMS as a registered-sender market. The rules as they apply to your traffic:
  • Pre-registration is required. An alphanumeric Sender ID on an SMPP-routed channel into BR delivers only when the BR entry on your registration is approved. Before approval the send-time gate holds the traffic with MESSAGING_BR_SENDER_NOT_REGISTERED (422); see Troubleshooting Compliance Error Codes.
  • Short codes dominate. Dedicated short codes are the dependable A2P sender type in Brazil; long numbers and unmanaged alphanumeric Sender IDs are heavily filtered at the carrier edge. Prefer a short code for production volume; pair it with a registered alphanumeric Sender ID only where your brand needs the name on the from.
  • The 3-character floor is regulatory. Anatel rejects Sender IDs shorter than 3 characters, the same floor enforced by AGCOM, OFCOM, and BTRC — the format rule is 3–11 characters, letters, digits, space, hyphen, and underscore. A two-letter abbreviation is not a viable BR sender.
  • Budget the lead time. Short-code and alphanumeric registration with the carriers is not a same-week operation — budget 4–8 weeks of lead time before a launch date depends on SMS, the same window the LATAM channels onboarding guide and Sender-ID Registration budget for pre-registration markets.
Tenant-owned controls that map to the Anatel rule:

​
LGPD opt-in overlay on the registration

Anatel’s registration is a sender-identity regime, not a consent regime. The LGPD consent duty applies on top of it — registering the sender never substitutes for consent. The full consent posture is on the LGPD page; the send-relevant points:
  • Marketing SMS into BR is opt-in. Consent must exist before dispatch; record it with sms scope per (contact, channel) through Consent Management, with lawful_basis set (consent for promotional traffic).
  • Evidence and withdrawal. The consent ledger is your proof-of-record — exportable through Export Consent & Suppression Records — and withdrawal lands on the suppression list every send reads.
  • Register and posture together. A fully-registered Anatel sender with no consent records is still a non-compliant BR posture; consent with an unregistered sender never delivers. Both surfaces close the BR row.

​
No-send windows vs tenant quiet hours

Orbit’s tenant quiet-hours feature (Quiet-Hours Configuration) and the Brazilian marketing no-send convention are different things: Brazil has no single federal SMS quiet-hours statute comparable to the US TCPA calling window; the practical restraint comes from carrier filtering and LGPD’s purpose-limitation principle — sending marketing at 03:00 São Paulo time is a complaint magnet even where no statute forbids it. If you market into BR, configure tenant quiet hours that cover a conservative window (a common posture is 21:00–08:00 America/Sao_Paulo recipient time) so the opt-in control enforces what the convention asks for. That is a deliberate opt-in — default tenant quiet hours on, BR window set — not a flip Orbit makes for you. Use the local recipient timezone (São Paulo time for the bulk of Brazilian traffic) set deliberately per campaign; the resolver maps the +55 country prefix unless you override it. Validate the window before a campaign with Quiet-Hours Preview.

​
Portuguese opt-out keyword handling

The Opt-Out Keyword Alias Table includes the Portuguese opt-out vocabulary: PARAR, CANCELAR, SAIR, FIM, matched with locale-insensitive case-folding and Unicode normalisation — a recipient replying sair or Sair. matches the same opt-out rule. The Portuguese opt-in counterpart (INICIAR, SIM, COMEÇAR, ASSINAR) re-subscribes after a prior opt-out. When a Brazilian opt-out fires, the suppression entry it writes is channel-scoped to all, not sms — the same propagation behaviour as the English STOP alias. A recipient’s SAIR knocks that contact off SMS, WhatsApp, and RCS simultaneously: the opt-out is a request to stop being contacted, not a request to stop SMS. If you have pruned the seeded Portuguese rules in the dashboard, re-add them under Messages → SMS → Opt-out Rules before launching BR traffic.

​
Where each BR obligation maps in Orbit

​
BR launch checklist

Narrowed from the generic launch checklist in Country Compliance Requirements to the BR row:
1

Look up the BR row

Call GET /compliance/country-rules?channel=sms&country=BR and read the BR row’s sender_types, registration, content_restrictions, and stop_requirement. The BR row reports registration: required — the send-gate holds BR traffic until an approved sender is attached.
2

Pick a sender type

Prefer a dedicated short code for production volume; pair it with a registered alphanumeric Sender ID only where your brand needs the name on the from. If you choose an alphanumeric Sender ID, pick a brand name of at least 3 characters.
3

Pre-flight then file the Sender ID

GET /compliance/check?sender_id=<id>&country=BR to confirm the sender is viable, then POST /compliance/sender-id-registrations with a country: "BR" entry referencing your doc_… KYC documents. Budget 4–8 weeks of Anatel lead time. See Sender-ID Registration.
4

Capture marketing opt-in first

Record a consent entry with sms scope before any BR marketing send; BR is opt-in under LGPD, not opt-out. See Consent Management and the LGPD posture.
5

Cover the no-send window deliberately

If you run BR marketing traffic, turn on tenant quiet hours covering a conservative window (a common posture is 21:00–08:00 America/Sao_Paulo) — Orbit defaults this off. Validate the recipient timezone resolution with Quiet-Hours Preview. See Quiet-Hours Configuration.
6

Wire the Portuguese opt-out family

Confirm PARAR, CANCELAR, SAIR, FIM are mapped into the alias table and write the suppression entry at scope all. See Opt-Out Keyword Alias Table.
7

Verify before first send

GET /compliance/sender-id-registrations shows BR approved; GET /compliance/consent/lookup returns the recipient’s consent row; the quiet-hours preview resolves the recipient timezone correctly. Then send.