> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Sender-ID Decision Tree by Market

> Pick the right sender-identity rules page for your target market — branch by country, then by channel, using the live country-requirements reference. Covers BR (Anatel), IN (DLT), ID (Komdigi), PH, VN (MIC), SA (CST), SG (SGNIC), NZ (UEM), AR (ENACOM), AE (TDRA), MX (NOM-184), FR, UK (PECR), and more.

# Sender-ID Decision Tree by Market

Thirteen country-specific sender rules pages live in this section. When
you are launching into a new market, you need to know which one applies —
not read all thirteen. This page is the branching guide: start from the
country you are targeting, pick the channel, and follow the pointer to
the rules page that governs that market's sender-identity regime.

Every decision here keys off the live
[Country Compliance Requirements](/compliance/country-requirements)
reference. Read that row first for the current `registration` level and
accepted `sender_types`, then use this tree to open the right deep-dive
page.

***

## The per-country top-level checklist

Before you branch, confirm these four items against the live
country-rules row for your destination. The branch guide below assumes a
`yes` on all four — if any one is `no`, stop here and fix it before
reading the detailed page.

1. **Allowed sender type** — the row's `sender_types` array includes the
   "from" identity you plan to use. An alphanumeric sender ID into a
   long-code-only market is the most common silent-failure cause.
2. **Registration required?** — read `registration`. `required` means
   the send-time gate holds traffic until you have an approved Sender ID
   for that country. `recommended` means your traffic flows but may
   degrade. `none` means you can start sending once the country is
   enabled.
3. **Content restrictions** — read `content_restrictions`. A restricted
   industry or missing consent capture blocks the send independently of
   registration. The
   [Restricted & Prohibited Industries](/compliance/restricted-industries)
   page lists the banned and restricted categories across all markets.
4. **Opt-out keyword** — read `stop_requirement`. If the row calls for a
   language-specific keyword (French `STOP au 36111`, Arabic `إلغاء`),
   configure it in the suppression surface before launch.

***

## Branching guide — pick market, pick channel, follow the page

Start with the country code from your target destination. Each branch
names the regulating body, the sender-registration requirement, and the
dedicated page that documents the full regime.

### Brazil (`BR`)

Regulator: **Anatel**. Alphanumeric Sender IDs that reach a `+55` handset
must hold a country-level approved registration — unregistered alphanumeric
senders are filtered at the carrier edge.

* **SMS (A2P)** — short codes and pre-registered alphanumeric senders
  dominate. If your sender type is alphanumeric, registration is required.
  → **[Brazil Anatel Sender-ID Registration Rules](/compliance/brazil-anatel-sender-rules)**
* **WhatsApp** — Meta's WABA rules govern the sender identity; read the
  channel row on the country-rules reference and the
  [WhatsApp Content Policy](/compliance/whatsapp-content-policy).
* **Voice / Email** — LGPD consent duties apply across all channels.
  The [Brazil LGPD](/compliance/lgpd-brazil) page covers the data-protection
  layer above the channel-specific sender rules.

### India (`IN`)

Regulator: **TRAI**. India runs the DLT (Distributed Ledger Technology)
portal regime — every Principal Entity, every Header (sender ID), and
every content template must be registered on a DLT portal before any
A2P SMS delivers.

* **SMS (A2P)** — the DLT portal is the only path. Register a Principal
  Entity, pre-approve Headers, and submit content templates.
  → **[DLT-India Onboarding](/compliance/dlt-india)**
* **WhatsApp** — WABA rules apply separately; the
  [WhatsApp Content Policy](/compliance/whatsapp-content-policy) governs
  the sender identity.
* **Data protection** — the [DPDP India](/compliance/dpdp-india) page
  covers India's privacy law, which applies on top of the TRAI DLT regime.

### Indonesia (`ID`)

Regulator: **KOMDIGI** (formerly Kominfo). Alphanumeric Sender IDs require
pre-registration with KYC-backed brand identity. Marketing SMS is
opt-in-strict under PDP Law No. 27/2022.

* **SMS (A2P)** — pre-register the alphanumeric sender with KYC evidence
  and configure Bahasa Indonesia + English STOP keywords.
  → **[Indonesia KOMDIGI Sender & Marketing Rules](/compliance/indonesia-komdigi-sender-rules)**
* **Voice** — recording consent and calling-window rules apply under the
  same page.
* **WhatsApp / Email** — WABA rules or email consent policies apply; read
  the channel-specific row on the country-rules reference.

### Philippines (`PH`)

Regulator: **NTC**. Alphanumeric Sender IDs require pre-registration.
Marketing consent, English or Filipino opt-out keywords, and
tenant-owned quiet hours apply.

* **SMS (A2P)** — pre-register the alphanumeric sender and configure the
  opt-out vocabulary in the suppression surface.
  → **[Philippines NTC Sender Rules](/compliance/philippines-sender-rules)**
* **Voice** — the Data Privacy Act consent duties apply; the page above
  covers the full posture.

### Vietnam (`VN`)

Regulator: **MIC**. Alphanumeric Sender IDs require pre-registration
under Decree 52/2013. Marketing SMS needs opt-in consent and Vietnamese
opt-out keyword handling.

* **SMS (A2P)** — pre-register the sender and configure Vietnamese STOP
  terms.
  → **[Vietnam MIC Sender Registration + Marketing Rules](/compliance/vietnam-mic-sender-rules)**
* **Voice / Email** — the MIC's reach is channel-dependent; read the
  country-rules row for the non-SMS channels.

### Saudi Arabia (`SA`)

Regulator: **CST** (formerly CITC). Alphanumeric Sender IDs are
pre-registered with KYC-backed brand identity. Marketing SMS is opt-in
strict, with an overnight no-send window convention and dual-language
(Arabic + English) STOP handling.

* **SMS (A2P)** — pre-register the alphanumeric sender and configure
  the local no-send window and Arabic STOP keywords.
  → **[Saudi Arabia CST Sender & Marketing Rules](/compliance/saudi-arabia-cst-sender-rules)**
* **Voice** — recording and calling-window rules differ; read the
  country-rules row for the current voice-channel posture.

### Singapore (`SG`)

Regulator: **IMDA / SGNIC**. Every alphanumeric Sender ID must be
registered on the SGNIC registry before a `+65` handset will receive it.
Unregistered alphanumeric traffic is rejected at the carrier edge.

* **SMS (A2P)** — register the alphanumeric sender on the SGNIC registry.
  Marketing SMS follows the PDPA deemed-consent (opt-out) posture.
  → **[Singapore SGNIC Sender-ID Registration Rules](/compliance/singapore-sgnic-sender-rules)**
* **Data protection** — the PDPA posture page covers consent for
  non-SMS channels: see
  [Singapore and Thailand PDPA Posture](/compliance/pdpa-singapore-thailand).

### New Zealand (`NZ`)

Regulator: **DIA**. The Unsolicited Electronic Messages Act 2007 governs
commercial electronic messaging, with a consent footing that is broader
than Australia's. A functional unsubscribe actioned within five working
days is required.

* **SMS / Email** — UEM Act consent and unsubscribe obligations apply;
  the sender must be identifiable in every message.
  → **[New Zealand UEM Act Sender Rules](/compliance/nz-uem-act-sender-rules)**

### Argentina (`AR`)

Regulator: **ENACOM**. The posture is opt-out: provide an identifiable
sender, a Spanish stop path, and scrub the Registro Nacional No Llame
for covered marketing calls. CUIT/AFIP evidence must align with the
sender identity you submit to a carrier.

* **SMS / Voice** — configure the Spanish opt-out pathway and the DNC
  scrub for `country=AR`. Alphanumeric sender rules follow the
  country-rules row's `sender_types` and `registration` values.
  → **[Argentina ENACOM + CCM/AFIP Rules](/compliance/argentina-enacom-rules)**

### United Arab Emirates (`AE`)

Regulator: **TDRA**. Alphanumeric Sender IDs must be pre-registered with
KYC-backed brand identity before delivery. Marketing SMS and voice are
opt-in strict, with a carrier-honored 21:00–07:00 recipient-local
marketing window and Arabic STOP keywords.

* **SMS (A2P)** — pre-register the alphanumeric sender with KYC evidence
  and configure the Arabic STOP keywords and local no-send window.
  → **[UAE TDRA Sender & Marketing Rules](/compliance/uae-tdra-sender-rules)**
* **Voice** — recording consent and calling-window rules are covered on
  the same page.

### Mexico (`MX`)

Regulator: **SCT**. NOM-184-SCFI requires explicit, time-stamped opt-in
with prescribed disclosure language for promotional SMS. The sender
must be identifiable in every message.

* **SMS (Promotional / A2P)** — capture explicit, time-stamped opt-in
  backed by the prescribed disclosure text before any promotional SMS.
  → **[Mexico NOM-184 Consent](/compliance/mx-nom-184-consent)**
* **Transactional SMS** — the country-rules row governs sender-type and
  registration requirements separately for non-promotional traffic.

### France (`FR`)

Regulator: **ARCEP / CNIL** (under GDPR). Marketing SMS requires prior
opt-in. No marketing sends are permitted 20:00–08:00 or on Sundays and
public holidays. The STOP keyword must be in French (`STOP au 36111`).

* **SMS (Marketing)** — configure the French no-send windows, the
  marketing opt-in consent surface, and the `STOP au 36111` keyword.
  → **[France Marketing SMS Rules](/compliance/fr-marketing-sms-rules)**
* **Voice / Email** — GDPR consent and data-subject rights apply across
  all channels; the [GDPR Posture Guide](/compliance/gdpr-posture-guide)
  covers the general obligations.

### United Kingdom (`GB`)

Regulator: **ICO / Ofcom**. PECR governs marketing SMS, email, and
automated calling. Marketing SMS is opt-in; automated calling always
requires consent. Scrub TPS/CTPS do-not-call registers before voice
campaigns.

* **SMS / Email / Voice** — capture marketing consent, scrub TPS/CTPS,
  and include an unsubscribe mechanism in every message.
  → **[UK PECR and ePrivacy](/compliance/uk-pecr-eprivacy)**
* **Voice** — automated calling and the TPS scrub are covered on the
  same page; Ofcom sender rules apply separately.

### Other markets

The country-rules reference covers every market Orb delivers to, not
just the thirteen with dedicated pages. If your destination does not
appear in the branches above:

1. Read the live row on
   `GET /api/v1/compliance/country-rules?channel=<channel>` for your
   destination.
2. Follow the [launch checklist](/compliance/country-requirements#a-launch-checklist-for-a-new-country)
   on the country-requirements page — the four-step sequence (read the
   row, pick the sender type, register if required, check content and
   keywords) resolves the large majority of country-launch questions
   without a dedicated page.
3. If the row's `registration` field is `required`, submit the Sender ID
   through [Sender-ID Registration](/compliance/sender-id-registration).
4. For a jurisdiction covered by GDPR-class obligations, start at the
   [GDPR Posture Guide](/compliance/gdpr-posture-guide).

***

## Condensed per-market matrix

| Country / code | Regulator | Registration | Page |
| - | - | - | - |
| Brazil (`BR`) | Anatel | Required (alphanumeric) | [BR Anatel Rules](/compliance/brazil-anatel-sender-rules) |
| India (`IN`) | TRAI | Required (DLT portal) | [DLT-India](/compliance/dlt-india) |
| Indonesia (`ID`) | KOMDIGI | Required (alphanumeric + KYC) | [ID KOMDIGI Rules](/compliance/indonesia-komdigi-sender-rules) |
| Philippines (`PH`) | NTC | Required (alphanumeric) | [PH NTC Rules](/compliance/philippines-sender-rules) |
| Vietnam (`VN`) | MIC | Required (alphanumeric) | [VN MIC Rules](/compliance/vietnam-mic-sender-rules) |
| Saudi Arabia (`SA`) | CST | Required (alphanumeric + KYC) | [SA CST Rules](/compliance/saudi-arabia-cst-sender-rules) |
| Singapore (`SG`) | IMDA / SGNIC | Required (SGNIC registry) | [SG SGNIC Rules](/compliance/singapore-sgnic-sender-rules) |
| New Zealand (`NZ`) | DIA | Recommended | [NZ UEM Act](/compliance/nz-uem-act-sender-rules) |
| Argentina (`AR`) | ENACOM | Recommended | [AR ENACOM Rules](/compliance/argentina-enacom-rules) |
| UAE (`AE`) | TDRA | Required (alphanumeric + KYC) | [AE TDRA Rules](/compliance/uae-tdra-sender-rules) |
| Mexico (`MX`) | SCT | Required (NOM-184 disclosure) | [MX NOM-184](/compliance/mx-nom-184-consent) |
| France (`FR`) | ARCEP / CNIL | Recommended | [FR Marketing Rules](/compliance/fr-marketing-sms-rules) |
| United Kingdom (`GB`) | ICO / Ofcom | Opt-in (PECR) | [UK PECR](/compliance/uk-pecr-eprivacy) |

The `registration` column in this table is a snapshot — always verify
against the live `registration` field on the country-rules row before
launch.

***

## Common rejection reasons for the top markets

These are the most frequent reasons a first send to a new market is
held or filtered. Match your configuration against this list before
launch.

| Country | Common rejection | How to fix |
| - | - | - |
| **Brazil** | Alphanumeric Sender ID sent without an approved Anatel registration | Register the Sender ID through [Sender-ID Registration](/compliance/sender-id-registration) with `country=BR`. Wait for `approved` before sending. |
| **India** | Header (sender ID) or content template not registered on the DLT portal | Onboard as a Principal Entity on a DLT portal, register the Header, and submit the content template. The [DLT-India guide](/compliance/dlt-india) walks through each step. |
| **Indonesia** | KYC evidence missing or rejected by KOMDIGI | Submit the brand-ownership and business-registration documents through [Documents & KYC](/compliance/documents-kyc) before the sender registration. |
| **Saudi Arabia** | Arabic STOP keyword missing or incorrect | Configure the Arabic opt-out keyword (`إلغاء` / `إلغاء الاشتراك`) in the suppression surface. The country-rules row lists the exact vocabulary. |
| **Singapore** | Alphanumeric sender not listed on the SGNIC registry | Register the sender name on the SGNIC registry. Unregistered alphanumeric traffic is rejected at the carrier edge — there is no hold-and-review path. |
| **France** | Marketing SMS sent during the no-send window (20:00–08:00, Sundays, holidays) | Configure tenant-owned quiet hours for `country=FR` with the recipient-local timezone. See [France Marketing SMS Rules](/compliance/fr-marketing-sms-rules). |
| **UAE** | Sender ID submitted without KYC that ties to a locally recognized entity | TDRA requires a KYC-verified brand identity. Submit your trade license or equivalent through [Documents & KYC](/compliance/documents-kyc) before the sender registration. |
| **Mexico** | Promotional SMS sent without the NOM-184 prescribed disclosure | The NOM-184 standard requires specific disclosure language in the opt-in capture. See [Mexico NOM-184 Consent](/compliance/mx-nom-184-consent) for the exact required text. |

***

## Pointers into the deeper page per region

Where the branching guide above routes you to a country page, that page
documents the full regime: the statutory obligations, the Orbit surface
that carries each one, the configuration steps, and the enforcement
exposure. Every country page follows the
[template](/compliance/country-rules-directory#template-for-a-new-per-country-page)
defined in the Regional Posture Hub — so once you have read one, the
structure of the others is familiar.

Each page is also listed in the
[Regional Posture Hub](/compliance/country-rules-directory) matrix, which
is the single landing point for referencing every per-country page at
once. Use that page when you need to cross-check multiple markets or
browse the full set.

***

## Related references

* [Country Compliance Requirements](/compliance/country-requirements) —
  the live per-country, per-channel rules reference this tree keys off.
* [Regional Posture Hub — Per-Country Rules Index](/compliance/country-rules-directory) —
  the full matrix of every jurisdiction's dedicated page.
* [Sender-ID Registration](/compliance/sender-id-registration) — file
  and track a sender registration where a market requires it.
* [Restricted & Prohibited Industries](/compliance/restricted-industries) —
  content restrictions that apply on top of every country's sender rules.
* [Send Gates](/compliance/send-gates) — the send-time enforcement
  points the country-rules reference feeds.
* [Troubleshooting Compliance Error Codes](/compliance/troubleshooting-compliance-error-codes) —
  the gate-error surface for send failures per country.
* [GDPR Posture Guide](/compliance/gdpr-posture-guide) — the general
  GDPR obligations for European and GDPR-class jurisdictions.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.