SOUTH KOREA (KR)

Country Summary

Country nameSouth Korea
ISO codeKR
RegionAsia
Mobile country code450
Dialing code+82
Major carriersSK Telecom, KT, LG U+

Guidelines

Two-way SMS supported Yes
Number portability availableYes
Twilio concatenated message supportYes
Message length-----
Twilio MMS supportConverted to SMS with embedded URL
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

SMS messages toward South Korea would be automatically appended with [Web 발신] which means the message is A2P. Only numeric senderId is supported and it would be automatically prefixed with 009. Only EUC-KR characters are supported by the South Korean mobile operators so carefully review your content and only use characters that are on the list 

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 capabilityNot SupportedNot SupportedSupportedSupportedNot Supported
Twilio supportedNot SupportedNot SupportedSupportedSupportedNot Supported
Sender ID preserved --- --- YesNo---
Provisioning timeN/AN/AN/AN/AN/A
UCS-2 supportN/AN/ASupportedSupportedN/A
Use case restrictions

N/A

N/A

N/A

N/A

N/A

Best practices

N/A

N/A

Please take note that local longcode would be delivered in local format (without the country code)

Please take note that international longcode would be appended with 009 as regulation by the mobile operators

N/A

Alphanumeric - Pre-registration
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

Alphanumeric - Dynamic
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

Long Code - Domestic
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedYes
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

N/A

Best practices

Please take note that local longcode would be delivered in local format (without the country code)

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

N/A

Best practices

Please take note that international longcode would be appended with 009 as regulation by the mobile operators

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.