Locale Summary
Locale name | Malaysia |
---|---|
ISO code | MY |
Region | Asia |
Mobile country code | 502 |
Dialing code | +60 |
Guidelines
Two-way SMS supported | Yes |
---|---|
Number portability available | Yes |
Twilio concatenated message support | Yes |
Message length | ----- |
Twilio MMS support | Converted to SMS with embedded URL |
Sending SMS to landline numbers | 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 | Per local regulations, only Person-to-Person (P2P) messages may be sent via Malaysian domestic long codes. If you can guarantee that you only send legitimate P2P messages, please reach out to Twilio Customer Services to ensure the proper domestic long code connectivity is enabled on your account. For Application-to-Person (A2P) messages, you can use any international long codes. For all messages submitted to Malaysia, you must include your brand name to avoid blocking and filtering by mobile operators. Brand names in message content allow mobile operators to identify which organizations are sending messages to their subscribers. The Sender ID of A2P messages to Malaysia is overwritten with a Shortcode Sender ID. Sending political, religious, and gambling-related content is strictly prohibited. Malaysian mobile operators require the content header 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:
|
Phone Numbers & Sender ID
Alphanumeric | Long Code | Short Code | |||
---|---|---|---|---|---|
Pre-registration | Dynamic | Domestic | International | ||
Operator network capability | Not Supported | Not Supported | Supported | Not Supported | Supported |
Twilio supported | --- | --- | Supported | Supported | Not Supported |
Sender ID preserved | --- | --- | Yes | No | --- |
Provisioning time | N/A | N/A | N/A | N/A | N/A |
UCS-2 support | N/A | N/A | Supported | Supported | N/A |
Use case restrictions | N/A | N/A | Malaysian long codes are limited to 200 messages per day per number and should only be used for Person-to-Person (P2P) messaging. Malaysian long codes will be delivered intact to the target handset. | N/A | N/A |
Best practices | N/A | N/A | N/A | Non-Malaysian long codes will be overwritten with a random operator-approved long code or short code when sent to the Digi network in Malaysia, or with a random approved short code to all other Malaysian mobile networks. | N/A |
Alphanumeric - Pre-registration | |
---|---|
Operator network capability | Not Supported |
Twilio supported | --- |
Sender ID preserved | --- |
Provisioning time | N/A |
UCS-2 support | N/A |
Use case restrictions | N/A |
Best practices | N/A |
Alphanumeric - Dynamic | |
---|---|
Operator network capability | Not Supported |
Twilio supported | --- |
Sender ID preserved | --- |
Provisioning time | N/A |
UCS-2 support | N/A |
Use case restrictions | N/A |
Best practices | N/A |
Long Code - Domestic | |
---|---|
Operator network capability | Supported |
Twilio supported | Supported |
Sender ID preserved | Yes |
Provisioning time | N/A |
UCS-2 support | Supported |
Use case restrictions | Malaysian long codes are limited to 200 messages per day per number and should only be used for Person-to-Person (P2P) messaging. Malaysian long codes will be delivered intact to the target handset. |
Best practices | N/A |
Long Code - International | |
---|---|
Operator network capability | Not Supported |
Twilio supported | Supported |
Sender ID preserved | No |
Provisioning time | N/A |
UCS-2 support | Supported |
Use case restrictions | N/A |
Best practices | Non-Malaysian long codes will be overwritten with a random operator-approved long code or short code when sent to the Digi network in Malaysia, or with a random approved short code to all other Malaysian mobile networks. |
Short Code | |
---|---|
Operator network capability | Supported |
Twilio supported | Not Supported |
Sender ID preserved | --- |
Provisioning time | N/A |
UCS-2 support | N/A |
Use case restrictions | N/A |
Best practices | N/A |
For the benefit of all our customers, these guidelines are provided to help you comply with applicable requirements and to help ensure Twilio's platform remains compliant with global telecommunications ecosystem requirements. These guidelines represent our current understanding of common compliance requirements generally applicable to Twilio and its customers, and do not constitute legal advice. By posting these guidelines, Twilio makes no assurances regarding the legal compliance of your application built using our APIs. You are expected to understand and abide by all compliance obligations applicable to your specific application. You should check these pages regularly for updates as telecommunications ecosystem requirements continue to evolve and change, and the information below may be updated or changed without notice.