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 length-----
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

You may use a global SMS-capable number to reach mobile phones in Vietnam; however the sender ID will be changed to a numeric string in international format to ensure delivery. Not all Vietnamese carriers support Unicode characters. Delivery reports are SMSC acknowledgment only and is not guaranteed. Customers have reported better results when using only the basic ASCII character set in Vietnam.

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

PreregisteredAlphanumericLong CodeShort Code
Operator network capabilityRequiredSupportedNot SupportedNot Supported
Twilio supportedRequiredSupportedNot SupportedNot Supported
Sender ID preservedYes --- No ---
Provisioning time1 week------
UCS-2 support --------
Use case restrictions --Alphanumeric is only supported through pre-registrationNumeric senderId would be overwritten into generic alphanumeric outside Twilio's platform--
Best practices --------
Preregistered
Operator network capabilityRequired
Twilio supportedRequired
Sender ID preservedYes
Provisioning time1 week
UCS-2 support --
Use case restrictions --
Best practices --
Alphanumeric
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preserved ---
Provisioning time--
UCS-2 support --
Use case restrictions Alphanumeric is only supported through pre-registration
Best practices --
Long Code
Operator network capabilityNot Supported
Twilio supportedNot Supported
Sender ID preservedNo
Provisioning time--
UCS-2 support --
Use case restrictions Numeric senderId would be overwritten into generic alphanumeric outside Twilio's platform
Best practices --
Short Code
Operator network capabilityNot Supported
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.