Quick answer: Singapore does not filter unregistered alphanumeric senders; it rejects them. The Infocomm Media Development Authority (IMDA) administers the SMS Sender ID Registry, operated by SGNIC, and an alphanumeric sender name reaches a +65 handset only once that exact name holds an approved registry entry. Traffic on an unregistered name is refused at the carrier edge, with no hold-and-review path. On top of the sender-identity regime, marketing SMS follows the PDPA's deemed-consent (opt-out) posture plus the national Do Not Call register, with an English STOP opt-out vocabulary. Register the brand before the campaign, scrub the list, record the consent basis, and Singapore is one of the more predictable A2P markets to operate. This post walks the registry, the spoofing stance behind it, the tenant-owned controls Orbit carries, and the cost planning for the launch.
Everything below is a tenant-owned launch playbook, not legal advice and not a delivery guarantee. Orbit carries the controls — sender-ID registration, consent records, DNC scrubbing, suppression, and quiet hours — and the Singapore posture on each is yours to set; the final reading of the IMDA rules and the PDPA sits with you and your counsel.
What the registry requires of businesses sending A2P SMS into Singapore
The registry is an allowlist of sender names, not a filter applied after the fact. An alphanumeric sender ID appears on the "from" line of an SMS only when the name is on file with the SGNIC registry and approved; the carriers pass registered names and refuse everything else. The rules that matter operationally:
- Pre-registration is required. The sender name must be approved before the first message, not after. Singapore rejects the traffic itself when the name is unregistered, which makes the registry a launch-path item rather than a launch-day item.
- The name must tie back to your entity. Generic strings that no registered organization can own —
INFO,SMS,ALERT— are refused. The registry exists to bind sender names to accountable entities. - The format has a regulatory floor. Sender IDs run 3–11 characters: letters, digits, space, hyphen, and underscore. A two-letter abbreviation is not a viable Singapore sender.
- Numeric senders bypass the alphanumeric gate, not the privacy layer. Carriers provision numeric long codes at purchase time, so a numeric sender does not wait on the registry — but the PDPA consent and DNC obligations still apply to its traffic.
Budget the approval lead time, measured in days to weeks, into the launch plan: the registry clock starts when you file, and the send gate holds SG traffic until the entry reads approved.
Why the registry exists: spoofing, scams, and the IMDA and PDPC stance
The registry is Singapore's answer to sender-name spoofing, the technique behind most SMS scam traffic: a message that arrives wearing a bank's name, a courier's name, or a government agency's name. When only registered entities may wear a sender name, a spoofed name has nowhere to land — the carriers refuse every alphanumeric name that is not on file. IMDA rolled the registry out in stages, beginning with the most-spoofed sector, financial institutions, before widening it to every organization that sends alphanumeric IDs; the regime you register under today is that widened one.
The privacy half of the picture sits with the PDPC. Marketing SMS to +65 numbers runs under the PDPA's deemed-consent posture and the DNC register (PDPA Part 9): you may send on a disclosed, recorded basis until the recipient opts out, and numbers listed on the DNC register are blocked at any hour, not just overnight. The two regimes are separate obligations with separate failure modes — a fully registered sender with no consent records is still a non-compliant posture, and PDPA consent on an unregistered sender never delivers. Both surfaces close the SG row.
Tenant-owned controls in Orbit: register before you launch
Orbit's posture on Singapore is the same as on every required market: the registration obligation is the tenant's, and the platform carries the workspace to discharge it.
- Register the sender ID in the Sender ID workspace before the campaign runs. The workspace takes a Singapore entry beside your other markets, with the KYC documents the registry expects; the send-time gate holds A2P SMS to SG on an alphanumeric sender until the entry is
approved. File at the start of the launch plan, not at the start of the campaign — the difference between a scheduled launch and a held queue is lead time. - Pre-register brand names, not campaigns. The registry approves names, not traffic bursts. Pick the registrable brand (three characters minimum, tied to your entity documents) once and reuse it across programs.
- Pre-flight the name before filing. The compliance pre-flight check answers "can this sender ID work in SG?" before you spend registry lead time on a name that will not survive the format and brand-ownership rules.
- Layer the privacy controls. Consent records per contact and channel, the DNC scrub wired into campaign rollout, the English
STOP/UNSUBSCRIBE/CANCEL/END/QUITaliases writing suppression entries, and a tenant quiet-hours window covering Singapore overnight hours (a fixed UTC+8 zone with no daylight saving). The full overlay is walked on the Singapore SGNIC sender-ID registration rules page, and the consent layer on the Singapore and Thailand PDPA posture page.
The country-by-country launch loop lives in the sender-ID registration country playbook; the Singapore lane appends these rows to its five steps: read the SG row live, pre-flight the name, file with KYC and wait for approved, record the PDPA basis and scrub the DNC register, then set quiet hours and the English opt-out aliases. The SG row of the per-country checklist also sits in sender ID required vs recommended: which market to launch first, where Singapore occupies the required column that hard-holds at send time, beside India and Saudi Arabia.
Planning the launch cost: Singapore on the pricing surface
Registration decides whether Singapore traffic flows; per-network rates decide what it costs. The SMS lane of the pricing page lists Singapore beside every market Orbit delivers to, so the SG leg of a launch plan is costed from the same surface as the rest of the rollout: read the per-message rate for Singapore, multiply by the projected volume including the registration lead-time window (a held queue that releases on approval is still billed volume), and compare it against the markets you already run. Because the registry holds unapproved senders at the gate, the honest cost model prices SG volume from the approval date, not from campaign day one.
Compliance posture: tenant-owned obligation, platform tooling
The SG gate row reading required is a posture the platform documents and enforces, not a compliance guarantee it assumes. Registering with SGNIC, holding a PDPA consent basis, scrubbing the DNC register, and keeping the content you send within the rules are the sender's legal obligations; Orbit supplies the workspace — registration tracking, the send gate, the consent ledger, the suppression layer — and not the legal posture. IMDA and the PDPC enforce against senders, not platforms. Have counsel review your sender-name choice, your consent capture, and your DNC handling before you flip SG live.
Frequently asked questions
Is sender-ID registration required for Singapore?
Yes. An alphanumeric sender ID must hold an approved SGNIC registry entry before A2P SMS delivers to +65 handsets; unregistered alphanumeric traffic is rejected at the carrier edge. Orbit's country-rules reference carries the SG row as required, and the send-time gate enforces it.
Can I send with a numeric sender instead?
A numeric long code bypasses the alphanumeric registry gate because carriers provision it at purchase time. The PDPA consent duty, the DNC register, and the opt-out rules still apply to its traffic.
Which sender names does SGNIC refuse?
Names shorter than three characters, and generic strings that no registered entity can own, such as INFO, SMS, or ALERT. The name must match the brand your KYC documents support.
Is marketing SMS to Singapore opt-in or opt-out?
Opt-out. The PDPA operates a deemed-consent posture: send on a disclosed, recorded basis until the recipient withdraws, subject to the DNC register, which blocks listed numbers at any hour.
Does Devotel Orbit guarantee Singapore compliance?
No. Orbit carries the controls — the sender-ID registration workspace, the send gate, the consent ledger, DNC scrubbing, suppression, and quiet hours — and the compliance posture is tenant-owned. Statutory interpretation stays with you and your counsel.
Source and further reading
- IMDA public guidance on the SMS Sender ID Registry (imda.gov.sg) — the regime this post summarizes; verify the live rules before launch.
- Singapore SGNIC sender-ID registration rules — the Orbit mechanics page for the SG row.
- Singapore and Thailand PDPA posture — the consent, DNC, and DSAR layer.
- Sender-ID registration country playbook — the series' launch loop.
- Sender ID required vs recommended — where the SG row sits in the launch-order ranking.
Published 27 October 2026.