Singapore's commercial SMS rules are now an operational concern, not a filing footnote. The Infocomm Media Development Authority (IMDA) launched the Singapore SMS Sender ID Registry (SSIR), administered through SGNIC, to make approved sender identity part of the delivery path. By Q4 2026, businesses sending application-to-person (A2P) SMS to +65 numbers should treat sender registration and send-time readiness as one launch workstream.
This is a news explainer, not legal advice. IMDA's SSIR announcement and SSIR FAQ are the primary sources for the programme and its dates. Your organisation remains responsible for its consent, Do Not Call (DNC), content, and quiet-hours decisions.
What changed: SSIR made sender identity a delivery control
The SSIR gives businesses a registry for the alphanumeric sender names recipients see in commercial SMS. SGNIC manages the sender-ID registration process, while IMDA sets the regulatory direction. The practical change is simple: a brand name that has not completed the relevant registration should not be treated as ready for commercial A2P traffic to Singapore.
The registry is separate from privacy permission. Registration answers, “Is this sender name authorised for this business?” It does not answer, “May this business contact this person?” A sender can satisfy one question and fail the other.
As of Q4 2026, plan for the registry to be part of launch readiness rather than a post-send reconciliation. Confirm the current IMDA and SGNIC treatment before each launch because regulatory programmes and carrier handling can change.
How Devotel Orbit's SG gate works
Devotel Orbit documents the SGNIC rules in the Singapore SGNIC Sender-ID reference. For an alphanumeric sender, an approved SGNIC registration is required before the send can proceed when the tenant has opted into the Singapore regional gate.
That opt-in matters. Compliance controls other than the platform's narrow statutory voice guard are tenant-configured. To enforce the SG sender-registration check for your organisation, enable regional_send_gates.SG.enabled in your organisation settings. With that tenant setting enabled, an unregistered alphanumeric sender is rejected at send time with MESSAGING_SG_SENDER_NOT_REGISTERED, rather than being silently treated as approved. Configure the setting deliberately, verify it in a non-production workflow, and keep the registration status aligned with the sender on each campaign.
A numeric long code is a different sender class. The Singapore sender-types table documents numeric long codes as bypassing the SGNIC alphanumeric gate. That does not bypass the rest of your tenant's obligations: consent, DNC scrubbing, suppression, content review, and any quiet-hours posture still apply.
The format floor: 3–11 characters
An alphanumeric Sender ID for Singapore must be between 3 and 11 characters. Treat the exact approved string as the contract: spelling, punctuation, spacing, and case should match the sender configured on the route. A short internal abbreviation may be memorable to your team but still fail the format floor or make brand ownership difficult to establish.
Before filing, choose a name your business can support with its registration and brand evidence. After approval, compare that exact name with every campaign and route that can reach Singapore. Registration in another market does not make the Singapore sender ready.
PDPA sits beside registration, not inside it
The Personal Data Protection Act (PDPA) overlay addresses the recipient and the use of personal data; SGNIC registration addresses the sender identity. Keep the controls separate in your launch review:
- Consent and deemed consent: document the basis on which you contact each person and the purpose of the message. Singapore's deemed-consent posture is not a blanket permission to message anyone.
- DNC scrubbing: scrub Singapore numbers against the applicable Do Not Call register and your tenant suppression list before a marketing send. A registered sender does not override a DNC result.
- English STOP opt-out: publish a clear English opt-out instruction, such as
STOP, and make sure the reply writes the contact to your suppression list. Confirm the vocabulary your tenant has configured rather than assuming a default. - No-send convention and quiet hours: registration is not a timing rule. Map the Singapore no-send convention to tenant-configurable quiet hours, using the recipient's Asia/Singapore timezone and a window your counsel accepts. Record that choice separately from the sender filing.
The useful distinction is operational: the registry protects sender identity at the message boundary; privacy controls govern whether and when your tenant should contact a person.
A tenant-owned Singapore launch checklist
Run this checklist for each organisation and each sender identity:
- Register the brand. File the exact alphanumeric Sender ID through the SGNIC process and retain the approval record.
- Choose the sender class. Decide whether the programme uses a registered alphanumeric Sender ID or a numeric long code. Do not assume the two classes have the same registry treatment.
- Enable the SG gate if you want send-time enforcement. Set
regional_send_gates.SG.enabledfor the tenant, then verify that an unregistered alphanumeric test is rejected withMESSAGING_SG_SENDER_NOT_REGISTEREDbefore production traffic. - Match the wire value. Check that the Sender ID attached to each Singapore campaign is the approved 3–11 character value, with no silent substitution.
- Set quiet hours. Configure a tenant window for Singapore recipients and preview the resolved timezone before launch. This is your tenant posture, not an assertion that SGNIC performs the timing check.
- Scrub and record. Run your DNC check, retain the consent basis and purpose, and confirm that suppression is applied before the first send.
- Publish the opt-out vocabulary. Tell recipients how to stop messages and test the English
STOPpath.
| Worked example | Tenant decision | Verification before launch |
|---|---|---|
A retailer sends order updates and promotions from ACMEStore to +65 customers | Register ACMEStore; enable regional_send_gates.SG.enabled; configure Singapore quiet hours; record the consent basis; publish STOP | Registration is approved, the live sender is exactly ACMEStore, DNC and suppression checks pass, and an unregistered test returns MESSAGING_SG_SENDER_NOT_REGISTERED |
For a registration walkthrough and the wider country matrix, see the Sender-ID Registration Country Playbook 2026. Singapore appears there as one row; this explainer owns the SSIR and SGNIC launch context. For the broader Gulf sender-ID comparison, see GCC and MENA sender-ID registration. Keep the implementation details beside the Singapore SGNIC Sender-ID rules page.
Frequently asked questions
Does registering a Sender ID make a marketing send compliant?
No. Registration covers the sender identity. You still own consent, DNC scrubbing, suppression, content, and timing decisions for your tenant.
Does Orbit reject every unregistered Singapore sender automatically?
No. The SG regional gate is tenant-configured. Enable regional_send_gates.SG.enabled when you want Orbit to reject unregistered alphanumeric senders at send time, and verify the MESSAGING_SG_SENDER_NOT_REGISTERED response in your rollout checks.
Does a numeric long code need SGNIC alphanumeric registration?
The SGNIC sender-types table documents numeric long codes as bypassing the alphanumeric SGNIC gate. The other tenant-owned messaging controls still apply.
Where should I verify dates and programme changes?
Use IMDA's SSIR announcement and current SGNIC/IMDA programme materials as the primary sources, then reconcile your tenant configuration and sender records before sending.