> For the complete documentation index, see [llms.txt](https://docs.bird.com/applications/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/applications/channels/channels/supported-channels/sms/concepts/choose-the-right-sender-availability-and-restrictions-by-country/sms-country-information-guide-asia-l-z/malaysia.md).

# Malaysia

### Character Support

In Malaysia the following characters are not supported:

€Δ Φ Γ Λ ΩΠ ΨΣΘ Ξ ¤£ ¥ èé ùìò ÇØø Åå€ Ææß ÉÄÖ Ñ Ü§ ¿ äö ñ üà

### Message Length

Messages to Malaysian networks have a character limit of 153. All non-P2P traffic in Malaysia must begin with 'RM0.00', which takes up the first 7 characters of any message. This reference indicates that the message will be free for the receiver. If your message does not begin with 'RM0.00' operators will add this to your message.

### Concatenated SMS

If you are sending an SMS which is longer than 153 characters, your message must start with 'RM0.00'. If you do not add this, your message might not deliver or deliver with changed content.

### Virtual Mobile Numbers

Virtual Numbers in Malaysia can not be used for sending transactional (OTP) or marketing content. This can incur blocking from the local operators.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bird.com/applications/channels/channels/supported-channels/sms/concepts/choose-the-right-sender-availability-and-restrictions-by-country/sms-country-information-guide-asia-l-z/malaysia.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.