Vietnam
Last updated on 4/30/2026
Mandatory measures exist
Local Operators
| Operator | MNC | Numeric ID | Alpha ID | Short Code | Comments |
|---|---|---|---|---|---|
| Gtel Mobile | 7 | No | Yes | No | - |
| I-Telecom Vietnam | 8 | No | Yes | No | - |
| REDDI | 9 | No | Yes | No | - |
| Mobifone | 1 | No | Yes | No | - |
| VNPT | 2 | Yes | Yes | Yes | All sender types change to generic alpha sender |
| Vietnamobile | 5 | No | Yes | No | - |
| Viettel Telecom | 4 | No | Yes | No | - |
Sender ID Types Availability
Available Registration Templates
Sender ID registration requirements
To register an alpha sender ID for traffic in Vietnam, please reach out to Sales or support for assistance with the registration process. This will involve providing details such as the sender ID, content samples, company information, and necessary documents. Pricing may vary, so please contact Sales for the latest rates on sender ID registration.
The specific requirements for sender ID registration include a business certificate and supporting documents if the sender ID is different from the company name.
All Operators (required)
- Sender ID
- Content samples (please refer to the guidelines below)
- Company name
- Company URL
- Company address
- Type of traffic (for example, OTP, marketing, etc.)
- Company field of activity (for example, insurance, clothing, travel agency, etc.)
- VAT
- Required documents:
- Business certificate. If the sender ID differs from the company name, a supporting document explaining the relationship between the chosen sender ID and the company name is required.
- An Excel file for content
- The sender ID must be included in the content as this is a requirement.
- For local senders, BM02B and BM03B documents are needed (BM03B filled out by Global Routing).
- For international senders, BM04 and BM05 documents are needed (BM05 filled out by Global Routing).
Fees may apply for registration, specifically a monthly fee of 32 USD.
Content samples guideline
Example:
| Full content | Template - all operators |
|--------------|--------------------------|
| Chuc mung quy khach hang Nguyen Hong Hanh nhan ngay sinh nhat 10/02. Than tang quy khach voucher mua hang tri gia 20.000 dong. Truy cap link de nhan voucher http://tiki.vn/abc?234 | Chuc mung quy khach hang {A,20} nhan ngay sinh nhat {A,10}. Than tang quy khach voucher mua hang tri gia {B,10} dong. Truy cap link de nhan voucher http://tiki.vn/{C,20} |
A variable consists of two parameters: a letter indicating the character type and the maximum number of characters. Variables are enclosed in curly braces {} and separated by a comma (,). For example, {B,10} indicates a Type B variable that can contain a maximum of 10 characters, regardless of whether they are Unicode or non-Unicode.
Variable classification includes four types: A, B, C, and D, each with specific character and content requirements.
If the message content contains regex special characters, each must be preceded by a backslash. For example: \(Sự cố\) cắt điện khu phố trong khung giờ.
- Verification codes returned in messages must be in Vietnamese or English only.
- The brand name must be included in both the message content and the template declaration.
- The maximum parameter character length is 10 characters.
- Supplementary documents or screenshots regarding the web/app returning OTP codes are required, showing the entire process from the client entering the phone number to receiving the OTP message.
Additional information for partners and resellers
Partners and resellers must ensure that their customers are aware that the end customer, as the actual sender of the message, is responsible for the use, accuracy, and registration of the Sender ID. This includes ensuring that all required registrations, approvals, and supporting documentation are completed in accordance with applicable local requirements before traffic is sent.
LINK Mobility does not register Sender IDs on behalf of partners’ or resellers’ customers, unless otherwise agreed. LINK Mobility may provide support to partners and end customers throughout the registration process. Responsibility for providing correct information, obtaining any required approvals, and complying with mandatory Sender ID registration processes remains with the end customer. Partners and resellers should inform their customers of these obligations before sending traffic to destinations where Sender ID registration is mandatory.
Need guidance on SMS destination requirements?
SMS rules, documentation, and compliance requirements can vary by country and operator. Our local teams are ready to help you understand what applies to your destinations, including sender ID, routing, registration, and other local requirements. Visit our support section to get in touch.