Country Summary

Country nameMalaysia
ISO codeMY
RegionAsia
Mobile country code502
Dialing code+60
Major carriersCelcom, Maxis, DiGi

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. If you're a local company or based in Malaysia, please note that Malaysian mobile operators has tightened the rules and penalties whereby all domestic traffic must include company name/brand/identity in the SMS content. Due to these rules, please take notice that all messages sent must include company name/brand/identity in message content; otherwise a penalty might be imposed by the operators. Sending of political, religious, and gambling related content is strictly prohibited.

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.

Phone Numbers & Sender ID

AlphanumericLong CodeShort Code
Pre-registrationDynamicDomesticInternational
Operator network capabilityNot RequiredNot SupportedNot Supported --- Supported
Twilio supportedNot RequiredNot SupportedSupported --- Not Supported
Sender ID preserved --- --- No --- ---
Provisioning time------None------
UCS-2 support---------------
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
---
---
Non-Malaysian long code would be overwritten with random operator approved shortcode outside Twilio's platform.
---
---
Alphanumeric - Pre-registration
Operator network capabilityNot Required
Twilio supportedNot Required
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions
---
Best practices
---
Alphanumeric - Dynamic
Operator network capabilityNot Supported
Twilio supportedNot Supported
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions
---
Best practices
---
Long Code - Domestic
Operator network capabilityNot Supported
Twilio supportedSupported
Sender ID preservedNo
Provisioning timeNone
UCS-2 support---
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
Non-Malaysian long code would be overwritten with random operator approved shortcode outside Twilio's platform.
Long Code - International
Operator network capability ---
Twilio supported ---
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions
---
Best practices
---
Short Code
Operator network capabilitySupported
Twilio supportedNot Supported
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions
---
Best practices
---

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.