SOUTH KOREA (KR)

Country Summary

Country name	South Korea
ISO code	KR
Region	Asia
Mobile country code	450
Dialing code	+82
Major carriers	SK Telecom, KT, LG U+

Guidelines

Two-way SMS supported	Yes
Number portability available	Yes
Twilio concatenated message support	Yes
Message length	-----
Twilio MMS support	Converted to SMS with embedded URL
Sending SMS to landline numbers	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	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: Get opt-in consent from each end user before sending any communication to them, particular for marketing or other non-essential communications. Only communicate during an end user's daytime hours unless it is urgent. SMS campaigns should support HELP/STOP messages, and similar messages, in the end user's local language. Do not contact end users on do-not-call or do-not-disturb registries.

Phone Numbers & Sender ID

	Alphanumeric		Long Code		Short Code
	Pre-registration	Dynamic	Domestic	International
Operator network capability	Not Supported	Not Supported	Supported	Supported	Not Supported
Twilio supported	Not Supported	Not Supported	Supported	Supported	Not Supported
Sender ID preserved	---	---	Yes	No	---
Provisioning time	N/A	N/A	N/A	N/A	N/A
UCS-2 support	N/A	N/A	Supported	Supported	N/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 capability	Not Supported
Twilio supported	Not Supported
Sender ID preserved	---
Provisioning time	N/A
UCS-2 support	N/A
Use case restrictions	N/A
Best practices	N/A

	Alphanumeric - Dynamic
Operator network capability	Not Supported
Twilio supported	Not Supported
Sender ID preserved	---
Provisioning time	N/A
UCS-2 support	N/A
Use case restrictions	N/A
Best practices	N/A

	Long Code - Domestic
Operator network capability	Supported
Twilio supported	Supported
Sender ID preserved	Yes
Provisioning time	N/A
UCS-2 support	Supported
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 capability	Supported
Twilio supported	Supported
Sender ID preserved	No
Provisioning time	N/A
UCS-2 support	Supported
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 capability	Not Supported
Twilio supported	Not Supported
Sender ID preserved	---
Provisioning time	N/A
UCS-2 support	N/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.