Country Summary

Country nameVietnam
ISO codeVN
RegionAsia
Mobile country code452
Dialing code+84
Major carriersMobiFone, Gmobile, VinaPhone, Vietnamobile, Viettel

Guidelines

Two-way SMS supported Yes
Number portability availableYes
Twilio concatenated message supportYes
Message length160 Characters
Twilio MMS supportNot available
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

Vietnam mobile operators require pre-registration of alphanumeric sender IDs and message templates. Numeric Sender IDs are overwritten with generic alphanumeric sender IDs outside Twilio's platform. Quality is lower and delivery is on a best effort basis because generic alphanumeric sender IDs are likely to be blocked or filtered by mobile operators. Twilio recommends using pre-registered alphanumeric sender IDs and message templates only.

Mobile operators prohibit sending virtual currency-related content. You must have a license from the State Bank of Vietnam to send finance-related content via Sender ID. Delivery reports are SMSC-acknowledgment only, and delivery is not guaranteed. Sending adult, gambling, charity, and political content is 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 capabilityRequiredNot SupportedSupportedNot SupportedNot Supported
Twilio supported Required
Learn more
Not Supported Not SupportedSupportedNot Supported
Sender ID preservedYes --- --- No---
Provisioning time2 weeksN/AN/AN/AN/A
UCS-2 supportSupportedN/AN/AN/AN/A
Use case restrictions

Mobile operators prohibit sending virtual currency-related content. You must have a license from the State Bank of Vietnam to send finance-related content using Sender ID.

Delivery reports are SMSC-acknowledgment only, and delivery is not guaranteed.

Sending adult, gambling, charity, and political content is prohibited. 

N/A

N/A

N/A

N/A

Best practices

On receiving your registration request, the Sender ID team will ask you to upload a colored copy of your business registration certificate. This is a legal document issued by the government or a government-related body  that legitimizes the formation of a company or corporation.

If the Sender ID you requested is different or is not affiliated with the company requesting for the Sender ID, you will need to submit documentation that proves the company is allowed to use the Sender ID's brand name. 

For example, Twilio owns the brand 'Authy'. When Twilio submits a registration request for Authy, it needs to submit a document that proves Twilio owns the rights to use the Authy brand name.

N/A

N/A

N/A

N/A

Alphanumeric - Pre-registration
Operator network capabilityRequired
Twilio supported Required
Learn more
Sender ID preservedYes
Provisioning time2 weeks
UCS-2 supportSupported
Use case restrictions

Mobile operators prohibit sending virtual currency-related content. You must have a license from the State Bank of Vietnam to send finance-related content using Sender ID.

Delivery reports are SMSC-acknowledgment only, and delivery is not guaranteed.

Sending adult, gambling, charity, and political content is prohibited. 

Best practices

On receiving your registration request, the Sender ID team will ask you to upload a colored copy of your business registration certificate. This is a legal document issued by the government or a government-related body  that legitimizes the formation of a company or corporation.

If the Sender ID you requested is different or is not affiliated with the company requesting for the Sender ID, you will need to submit documentation that proves the company is allowed to use the Sender ID's brand name. 

For example, Twilio owns the brand 'Authy'. When Twilio submits a registration request for Authy, it needs to submit a document that proves Twilio owns the rights to use the Authy brand name.

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

N/A

Best practices

N/A

Long Code - Domestic
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

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

N/A

Best practices

N/A

Short Code
Operator network capabilityNot Supported
Twilio supportedNot Supported
Sender ID preserved---
Provisioning timeN/A
UCS-2 supportN/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.