Skip to main content

KYRGYZSTAN (KG)

Locale Summary

Locale nameKyrgyzstan
ISO codeKG
RegionEurope
Mobile country code437
Dialing code+996

Guidelines

Two-way SMS supported No
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

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

AlphanumericLong CodeShort Code
Pre-registrationDynamicDomesticInternational
Operator network capabilityNot RequiredSupported --- Not Supported---
Twilio supported --- Supported
Learn more
Not SupportedSupported---
Sender ID preserved --- Yes --- No---
Provisioning time---N/A---N/A---
UCS-2 support---Supported---Supported---
Use case restrictions---------

The network Megacom does not support Numeric Sender IDs. Use Alphanumeric Sender IDs to ensure message delivery. Messages submitted with a Numeric Sender ID will be delivered on a best effort basis and the Numeric Sender ID will be replaced with a generic Alphanumeric one outside Twilio's platform

---
Best practices---------------
Alphanumeric - Pre-registration
Operator network capabilityNot Required
Twilio supported ---
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions---
Best practices---
Alphanumeric - Dynamic
Operator network capabilitySupported
Twilio supported Supported
Learn more
Sender ID preservedYes
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions---
Best practices---
Long Code - Domestic
Operator network capability ---
Twilio supportedNot Supported
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions---
Best practices---
Long Code - International
Operator network capabilityNot Supported
Twilio supportedSupported
Sender ID preservedNo
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

The network Megacom does not support Numeric Sender IDs. Use Alphanumeric Sender IDs to ensure message delivery. Messages submitted with a Numeric Sender ID will be delivered on a best effort basis and the Numeric Sender ID will be replaced with a generic Alphanumeric one outside Twilio's platform

Best practices---
Short Code
Operator network capability---
Twilio 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.