Country Summary

Country namePoland
ISO codePL
RegionEurope
Mobile country code260
Dialing code+48

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

Dynamic Alphanumeric Sender IDs are supported. However, non-Polish Numeric Sender IDs to some networks in Poland will be overwritten to an Alphanumeric Sender ID to ensure delivery.

The use of URL shorteners such as bit.ly or tiny.url is strictly prohibited in Poland. Use the full form of the URL instead. Moreover, if you need to include a full URL in the content of a Long SMS (more than 160 characters), we advise you to test it before submitting a large number of messages as the local networks tend to block this type of message. Contact Twilio support with the exact text you would like to send, if you would like us to perform this check for you.

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 RequiredSupportedSupportedNot SupportedNot Supported
Twilio supported --- Supported
Learn more
SupportedSupported---
Sender ID preserved --- YesYesNo---
Provisioning timeN/AN/AN/AN/AN/A
UCS-2 supportN/ASupportedSupportedSupportedN/A
Use case restrictions

N/A

N/A

N/A

N/A

N/A

Best practices

N/A

N/A

N/A

Polish mobile operators do not support Numeric Sender IDs; these will be overwritten with a generic Alphanumeric Sender ID outside the Twilio platform to facilitate delivery. It is highly recommended that you send from a Alphanumeric Sender ID to avoid blocking and filtering.

N/A

Alphanumeric - Pre-registration
Operator network capabilityNot Required
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Alphanumeric - Dynamic
Operator network capabilitySupported
Twilio supported Supported
Learn more
Sender ID preservedYes
Provisioning timeN/A
UCS-2 supportSupported
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

Polish mobile operators do not support Numeric Sender IDs; these will be overwritten with a generic Alphanumeric Sender ID outside the Twilio platform to facilitate delivery. It is highly recommended that you send from a Alphanumeric Sender ID to avoid blocking and filtering.

Short Code
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

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.