Skip to main content

​
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 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 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
  • WhatsApp — Meta’s WABA rules govern the sender identity; read the channel row on the country-rules reference and the WhatsApp Content Policy.
  • Voice / Email — LGPD consent duties apply across all channels. The Brazil LGPD 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
  • WhatsApp — WABA rules apply separately; the WhatsApp Content Policy governs the sender identity.
  • Data protection — the 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
  • 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
  • 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.

​
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
  • 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.

​
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.

​
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

​
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
  • 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
  • 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
  • Voice / Email — GDPR consent and data-subject rights apply across all channels; the 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
  • 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 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.
  4. For a jurisdiction covered by GDPR-class obligations, start at the GDPR Posture Guide.

​
Condensed per-market matrix

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.

​
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 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 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.