SINGAPORE (SG)

Locale name

Singapore

ISO code
The International Organization for Standardization two character representation for the given locale.

SG

Region

Asia

Mobile country code
A three digit code associated with the given locale and used in conjunction with a Mobile Network Code to uniquely identify mobile networks.

525

Dialing code
The dialing prefix used to establish a call or send an SMS from one locale to the given locale.

+65

Two-way SMS supported
Whether Twilio supports two-way SMS in the given locale.

No

Number portability available
Whether number portability is available in the given locale.

Yes

Twilio concatenated message support
Concatenation refers to the capability of splitting a message that is too long to be sent in one SMS into smaller pieces and then joining the pieces at the receiving end so that the receiver sees the message as one. 

Yes*
For certain sender ID types this may not be supported. Where messages are split and rejoined may vary based on character encoding.

Message length
How many characters can be sent given a particular message encoding before the message will be split into concatenated segments.

160 ASCII characters per message

Twilio MMS support
Multimedia Messaging Service (MMS) provides a standards-based means to send pictures and video to mobile phones.

Converted to SMS with embedded URL

Sending SMS to landline numbers
How Twilio handles an SMS message destined for landline telephone number.

You cannot send SMS to a landline destination number: the Twilio REST API will throw a 400 response with error code 21614, the message will not appear in the logs, and the account will not be charged.

Compliance considerations
Twilio strongly encourages customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws. This table lists some general best practices.

Alphanumeric, Shortcode, Twilio Domestic Longcode must be registered with SGNIC (https://sgnic.sg/smsregistry/overview). International Longcode Sender IDs cannot be registered with SGNIC. Participating Aggregators like Twilio are required to ensure Registered Sender IDs are only received from the same organization who has registered with SGNIC, a Participating Aggregator, or a third party representative. In line with this regulatory requirement, customers must complete the registration with Twilio (https://twiliodoer.secure.force.com/SenderId) to provide proof of registration with SGNIC and all other necessary details before they start sending SMS.

From 30 January 2023, all non-registered Sender IDs will be overwritten with Alphanumeric Sender ID ‘Likely-SCAM’. 

Sending firearms, gambling, adult content, money/loan, political, religious, controlled substance, cannabis, and alcohol related content is strictly prohibited. Messages containing WhatsApp/LINE chat links are not allowed.

Message delivery to M2M numbers is on best effort basis only.

Twilio strongly encourages customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws. The following are some general best practices:

1. Get opt-in consent from each end user before sending any communication to them, particular for marketing or other non-essential communications.
2. Only communicate during an end user's daytime hours unless it is urgent.
3. SMS campaigns should support HELP/STOP messages, and similar messages, in the end user's local language.
4. Do not contact end users on do-not-call or do-not-disturb registries.

Operator network capability
Whether mobile operators in the given country support the feature.

Required

There is no segregation between International and Domestic Traffic

Not Supported

Twilio supported
Whether Twilio supports the feature for the given country.

Required
Learn more and register via the Console

Supported

Sender ID preserved
In some countries sender IDs for certain sender types are not preserved and are changed for compliance and/or deliverability reasons. In these countries mobile subscribers will see a different ‘from sender ID’ than the one sent by you.

Yes

No

Provisioning time
Provisioning is the process of getting the sender ID approved and registered with mobile networks (depending on country requirements). Provisioning time is how long this process takes in the given country.

5 business days

N/A

UCS-2 support

Supported

Supported

Use case restrictions

N/A

Only Alphanumeric Sender ID registered with SGNIC and Twilio will be preserved. From 30 January 2023 all non-registered Alphanumeric Sender IDs.

Best practices

All customers must pre-register Alphanumeric Sender ID in the SGNIC portal.

After registration, customers must reach out to Twilio by heading over https://twiliodoer.secure.force.com/SenderId to provide the necessary proof of registration and other details. 

Only send from pre-registered Sender IDs.

Please review the Compliance Considerations for more details. 

Operator network capability
Whether mobile operators in the given country support the feature.

Supported

Not Supported

Supported

Twilio supported
Whether Twilio supports the feature for the given country.

Not Supported

Supported

Not Supported

Sender ID preserved
In some countries sender IDs for certain sender types are not preserved and are changed for compliance and/or deliverability reasons. In these countries mobile subscribers will see a different ‘from sender ID’ than the one sent by you.

Yes

No

---

Provisioning time
Provisioning is the process of getting the sender ID approved and registered with mobile networks (depending on country requirements). Provisioning time is how long this process takes in the given country.

N/A

N/A

N/A

UCS-2 support

Supported

Supported

N/A

Use case restrictions

Only Domestic Longcodes registered with SGNIC and Twilio will be preserved. From 30 January 2023 all non-registered Domestic Longcodes are overwritten with 'Likely-SCAM'.

From 30 January 2023 all International Longcodes are overwritten with 'Likely-SCAM'. Take note that International Longcodes can't be registered with SGNIC and Twilio.

N/A

Best practices

Avoid sending Person-To-Person messages over SGNIC and Twilio registered Domestic Longcodes as this is not allowed. 

Please review the Compliance Considerations for more details. 

It is recommended to send one-way messages through a pre-registered Alphanumeric Sender ID.

Please review the Compliance Considerations for more details. 

N/A