Skip to main content

Country Summary

Country nameMalaysia
ISO codeMY
RegionAsia
Mobile country code502
Dialing code+60

Guidelines

Two-way SMS supported Yes
Number portability availableYes
Twilio concatenated message supportYes
Message length-----
Twilio MMS supportConverted to SMS with embedded URL
Sending SMS to landline numbersYou 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 long numbers. Please use other global SMS-capable numbers such as US and Canadian numbers to send application-to-person (A2P) messages.

For all messages submitted to Malaysia, it is required to include the brand name to avoid blocking and filtering by mobile operators. The brand name in the content would allow mobile operators to identify which brands are sending messages to their subscribers. Note that the Sender ID of Application-To-Person 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 'RM 0.00 ' to be added in every message sent to Malaysia. This header tells the receiving subscriber that they were not charged for receiving the SMS message. Sending your messages without this header would result in the content being truncated or the message failing entirely. Concatenated message is supported by all mobile operators except Digi Malaysia where it is delivered as multiple separate messages.

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, particularly 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.

Phone Numbers & Sender ID

Toll FreeLong CodeShort Code
DomesticInternationalDomesticInternational
Operator network capability --- --- SupportedNot SupportedSupported
Twilio supported --- --- SupportedSupportedNot Supported
Sender ID preserved --- --- YesNo---
Provisioning time------N/AN/AN/A
UCS-2 support------SupportedSupportedN/A
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. Malaysia long codes would be delivered intact to the target handset.

N/A

N/A

Best practices------

N/A

Non-Malaysian long code would be overwritten with random operator approved longcode or shortcode to the Digi network in Malaysia and with a random approved shortcode to the rest of the Malaysian mobile networks. 

N/A

Toll Free - Domestic
Operator network capability ---
Twilio supported ---
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions---
Best practices---
Toll Free - International
Operator network capability ---
Twilio supported ---
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions---
Best practices---
Long Code - Domestic
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedYes
Provisioning timeN/A
UCS-2 supportSupported
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. Malaysia long codes would be delivered intact to the target handset.

Best practices

N/A

Long Code - International
Operator network capabilityNot Supported
Twilio supportedSupported
Sender ID preservedNo
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

N/A

Best practices

Non-Malaysian long code would be overwritten with random operator approved longcode or shortcode to the Digi network in Malaysia and with a random approved shortcode to the rest of the Malaysian mobile networks. 

Short Code
Operator network capabilitySupported
Twilio supportedNot Supported
Sender ID preserved---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Alphanumeric - Pre-registration
Operator network capabilityNot Supported
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Alphanumeric - Dynamic
Operator network capabilityNot Supported
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Phone Numbers & Sender ID (continued)

Alphanumeric
Pre-registrationDynamic
Operator network capabilityNot SupportedNot Supported
Twilio supported --- ---
Sender ID preserved --- ---
Provisioning timeN/AN/A
UCS-2 supportN/AN/A
Use case restrictions

N/A

N/A

Best practices

N/A

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.