CZECH REPUBLIC (CZ)

Country Summary

Country nameCzech Republic
ISO codeCZ
RegionEurope
Mobile country code230
Dialing code+420
Major carriersT-Mobile, Vodafone, O2

Guidelines

Two-way SMS supported Yes
Number portability availableYes
Twilio concatenated message supportYes
Message length160 Characters
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

Alphanumeric Sender ID registration comes with a recurring charge of US$6 per month. Please contact your account manager or Twilio customer support for more details.

If your company is in the Financial Services or Banking industry, O2 Czech Republic requires you to complete and sign a Power of Attorney document, which authorizes Twilio to register and send branded messages on your behalf.

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 capabilitySupportedNot SupportedSupportedNot SupportedSupported
Twilio supported Supported --- SupportedSupportedNot Supported
Sender ID preservedYes --- YesNo---
Provisioning time7 weeksN/AN/AN/AN/A
UCS-2 supportSupportedN/ASupportedSupportedN/A
Use case restrictions

If you do not pre-register the Sender ID or if you use a Numeric Sender ID, network operators will override the Sender ID with a generic Alphanumeric Sender ID outside the Twilio platform.

N/A

N/A

N/A

N/A

Best practices

N/A

N/A

N/A

Numeric Sender ID is overwritten into generic Sender ID outside the Twilio platform to facilitate delivery

N/A

Alphanumeric - Pre-registration
Operator network capabilitySupported
Twilio supported Supported
Sender ID preservedYes
Provisioning time7 weeks
UCS-2 supportSupported
Use case restrictions

If you do not pre-register the Sender ID or if you use a Numeric Sender ID, network operators will override the Sender ID with a generic Alphanumeric Sender ID outside the Twilio platform.

Best practices

N/A

Alphanumeric - Dynamic
Operator network capabilityNot Supported
Twilio 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

N/A

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

N/A

Best practices

Numeric Sender ID is overwritten into generic Sender ID outside the Twilio platform to facilitate delivery

Short Code
Operator network capabilitySupported
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.