Guidelines

Vietnam (VN)

We've compiled regulatory and compliance information to help ensure you're communicating effectively and compliantly around the world.

Locale Summary

Locale name

Vietnam

ISO code
The International Organization for Standardization two character representation for the given locale.

VN

Region

Asia

Mobile country code
A three digit code associated with the given locale and used in conjunction with a Mobile Network Code to uniquely identify mobile networks.

452

Dialing code
The dialing prefix used to establish a call or send an SMS from one locale to the given locale.

+84

Guidelines

Two-way SMS supported
Whether Twilio supports two-way SMS in the given locale.

No

Number portability available
Whether number portability is available in the given locale.

Yes

Twilio concatenated message support
Concatenation refers to the capability of splitting a message that is too long to be sent in one SMS into smaller pieces and then joining the pieces at the receiving end so that the receiver sees the message as one. 

Yes*
For certain sender ID types this may not be supported. Where messages are split and rejoined may vary based on character encoding.

Message length
How many characters can be sent given a particular message encoding before the message will be split into concatenated segments.

160 characters

Twilio MMS support
Multimedia Messaging Service (MMS) provides a standards-based means to send pictures and video to mobile phones.

Not available

Sending SMS to landline numbers
How Twilio handles an SMS message destined for landline telephone number.

You 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
Twilio strongly encourages customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws. This table lists some general best practices.

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 therefore recommends using pre-registered Alphanumeric Sender IDs and message templates only. Sending promotional traffic (non transactional) is not currently supported.

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 are not guaranteed. Sending firearms, gambling, adult content, money/loan, political, religious, controlled substance, cannabis, and alcohol related content is strictly prohibited. Messages containing URLs, WhatsApp/LINE chat links, and phone numbers in the body are not allowed.

Sending marketing and promotional messages between 8PM to 8AM 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, 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

Alphanumeric
 

International Pre-registration

Domestic Pre-registration

Dynamic

Operator network capability
Whether mobile operators in the given country support the feature.

Required

Required

Not Supported

Twilio supported
Whether Twilio supports the feature for the given country.

Supported
Learn more

Supported
Learn more

Not Supported

Sender ID preserved
In some countries sender IDs for certain sender types are not preserved and are changed for compliance and/or deliverability reasons. In these countries mobile subscribers will see a different ‘from sender ID’ than the one sent by you.

Yes

Yes

N/A

Provisioning time
Provisioning is the process of getting the sender ID approved and registered with mobile networks (depending on country requirements). Provisioning time is how long this process takes in the given country.

5 weeks

5 weeks

N/A

UCS-2 support

Supported

N/A

N/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 a Sender ID.

Delivery reports are not supported by all mobile networks other than VietnaMobile.

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

Sending promotional traffic (non transactional) is not currently supported.

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 a Sender ID.

Delivery reports are not supported by all mobile networks other than VietnaMobile.

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

Sending promotional traffic (non transactional) is not currently supported.

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 from or is not affiliated with the company requesting 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.

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 from or is not affiliated with the company requesting 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

Long codes and short codes
 

Long code domestic

Long code international

Short code

Operator network capability
Whether mobile operators in the given country support the feature.

Not Supported

Not Supported

Not Supported

Twilio supported
Whether Twilio supports the feature for the given country.

Not Supported

Supported

Not Supported

Sender ID preserved
In some countries sender IDs for certain sender types are not preserved and are changed for compliance and/or deliverability reasons. In these countries mobile subscribers will see a different ‘from sender ID’ than the one sent by you.

---

No

---

Provisioning time
Provisioning is the process of getting the sender ID approved and registered with mobile networks (depending on country requirements). Provisioning time is how long this process takes in the given country.

N/A

N/A

N/A

UCS-2 support

N/A

Supported

N/A

Use case restrictions

N/A

Delivery of messages submitted with Numeric Sender IDs is on a best-effort basis and will be overwritten with either a random Numeric or Alphanumeric Sender ID outside the Twilio platform.

Sending with a pre-registered Sender ID is highly recommended.

N/A

Best practices

N/A

Twilio suggests using a pre-registered Alphanumeric Sender ID in Vietnam

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.