--- title: "Bulk SMS in Poland: UKE, Consent and Polish Characters Guide" description: "Bulk SMS Poland guide: UKE, consent under the 2024 Electronic Communications Law and GDPR, Orange, T-Mobile, Play and Plus routes, Polish diacritics." canonical: "https://omnichannels.ai/blog/bulk-sms-poland-guide/" language: "en" updated: "2026-11-06" publisher: "BroadNet Technologies" brand: "OmniChannels.ai" category: "sms" primaryQuery: "bulk sms poland" keywords: ["bulk sms poland", "masowe sms polska", "sms marketing polska zgoda", "prawo komunikacji elektronicznej sms", "sms sender id poland", "polish characters sms unicode", "orange play plus t-mobile sms", "uke sms rules"] published: "2026-11-06" author: "OmniChannels.ai Editorial Team" reviewer: "BroadNet Messaging Solutions Team" readingMinutes: 9 answer: "To send bulk SMS in Poland, use a provider with routes to Orange Polska, T-Mobile Polska, Play and Plus, get prior consent for every commercial SMS (Article 398 of the Electronic Communications Law of 2024 and the GDPR), and keep proof of it. Alphanumeric sender IDs of up to 11 characters are listed in our data. Polish diacritics are not in GSM-7, so ordinary Polish text uses Unicode at 70 characters." takeaways: ["The telecom regulator and enforcer of the consent rule is UKE; the Electronic Communications Law of 12 July 2024 (Dz.U. 2024 poz. 1221) bans using automated calling systems and telecommunications terminal equipment to send commercial information, direct marketing included, unless the recipient consented first.", "Consent is channel-specific and sending must not be at the recipient's cost; in an enforcement decision UKE held that the party commissioning a marketing campaign must be able to show it holds the consents.", "Our regulation data lists alphanumeric IDs up to 11 characters, requirements set by the operators and a typical lead time of 5 to 10 business days.", "Four mobile networks appear in our coverage data, all with direct routes: Orange Polska (260-03), T-Mobile Polska (260-02), Play (260-06) and Plus (260-01).", "The Polish letters ą, ć, ę, ł, ń, ó, ś, ź and ż are outside the GSM 7-bit alphabet, so one of them moves a message to Unicode at 70 characters (67 per part); stripping diacritics keeps 160 but reads worse."] faq: - q: "Is bulk SMS legal in Poland?" a: "Yes, for OTPs, service messages and consented marketing. The Electronic Communications Law of 2024 prohibits using automated calling systems and telecommunications terminal equipment to send commercial information without the user's prior consent, and the GDPR applies to the phone numbers. UKE enforces the consent rule, so keep proof and have Polish counsel review your flow." - q: "Do I need consent for promotional SMS in Poland?" a: "Plan on it. Article 398 of the 2024 law requires the user's prior consent for commercial information, direct marketing included. Practitioner and Sejm commentary describes consent as specific to a channel, so agreeing to phone calls does not cover SMS. Our regulation data adds that double opt-in is the operator-preferred standard." - q: "Do I need to register a sender ID in Poland?" a: "Our regulation data says requirements are set by the operators and gives a typical lead time of 5 to 10 business days for alphanumeric IDs of up to 11 characters. BroadNet confirms the current requirements during onboarding. Treat the lead time as typical, not guaranteed, and test on Orange, T-Mobile, Play and Plus handsets." - q: "Do Polish characters work in a standard SMS?" a: "Not in GSM-7. The letters ą, ć, ę, ł, ń, ó, ś, ź and ż are not in the GSM 7-bit alphabet, so a message containing any of them is sent as Unicode and holds 70 characters (67 per part). A message without diacritics fits 160. Check both versions in a character counter and decide which reads better for your brand." - q: "Should I remove Polish diacritics to save money?" a: "Sometimes, but it is a brand and readability decision as much as a cost one. A stripped message can be one part where the accented version is two, yet words lose clarity. Use stripped text for OTPs and short alerts, and consider accented Unicode for offers where the extra part is worth it." - q: "Is there a legal time window for promotional SMS in Poland?" a: "We have not found a regulator-published time-of-day window for promotional SMS in Poland, and our regulation data records none. Agree sending hours with your provider, schedule promotions for local daytime and keep OTPs and alerts on a transactional route that can run at any hour." sources: - title: "Ustawa z dnia 12 lipca 2024 r. Prawo komunikacji elektronicznej (Dz.U. 2024 poz. 1221), ISAP" url: "https://isap.sejm.gov.pl/isap.nsf/DocDetails.xsp?id=WDU20240001221" - title: "General Data Protection Regulation (EU) 2016/679, EUR-Lex" url: "https://eur-lex.europa.eu/eli/reg/2016/679/oj" - title: "UKE: Prezes UKE nałożył kary na Orange Polska S.A. za wysyłanie smsów marketingowych bez posiadania zgód klientów" url: "https://uke.gov.pl/akt/prezes-uke-nalozyl-kary-na-orange-polska-s-a-za-wysylanie-smsow-marketingowych-bez-posiadania-zgod-klientow,139.html" - title: "Urząd Komunikacji Elektronicznej (UKE)" url: "https://www.uke.gov.pl/" - title: "3GPP TS 23.038: Alphabets and language-specific information" url: "https://www.3gpp.org/dynareport/23038.htm" --- # Bulk SMS in Poland: UKE, Consent and Polish Characters Guide Canonical: https://omnichannels.ai/blog/bulk-sms-poland-guide/ Language: en Publisher: OmniChannels.ai by BroadNet Technologies This guide is for marketing, e-commerce, fintech and operations teams that want to send business SMS to Polish mobile numbers: OTPs, delivery alerts, reminders and promotions. It explains who regulates what, how consent works, which operators carry traffic and why Polish letters change message length. It is a practical overview, not legal advice; confirm your set-up with Polish counsel before launch. ## What rules apply to bulk SMS in Poland? Three layers apply: the Electronic Communications Law (Prawo komunikacji elektronicznej, PKE) for commercial messages, the GDPR for personal data, and operator policy for routes and sender names. Poland has no law named after bulk SMS. | Layer | What it covers | Where to check | |---|---|---| | PKE of 12 July 2024, Article 398 | Prior consent for commercial information sent through automated calling systems and telecommunications terminal equipment | [ISAP](https://isap.sejm.gov.pl/isap.nsf/DocDetails.xsp?id=WDU20240001221) | | GDPR | Lawful basis, quality of consent, right to object | [EUR-Lex](https://eur-lex.europa.eu/eli/reg/2016/679/oj) | | UKE and the operators | Telecom regulator, enforcement, routes, sender name handling | [uke.gov.pl](https://www.uke.gov.pl/) | Our regulation data lists UKE, the Urząd Komunikacji Elektronicznej, as the regulator, and records that sender ID requirements are set by the operators. ## Do you need consent to send commercial SMS in Poland? Yes. Plan on prior consent for every commercial SMS. Article 398 PKE prohibits using automated calling systems and telecommunications terminal equipment to send commercial information, including direct marketing, to a subscriber or end user unless they consented beforehand. The GDPR sets the quality of that consent: freely given, specific, informed and unambiguous. Three points from the law and UKE practice shape your sign-up flow: - **Consent is channel-specific.** Agreeing to marketing calls does not cover SMS or email. - **Cost.** Commercial information must not be sent at the end user's expense. - **Burden of proof.** In a decision UKE held that the party commissioning a campaign had to show it held prior consents, and it has fined operators for sending marketing SMS without consents on record, as its announcement on Orange Polska shows. Our regulation data records that GDPR-compliant opt-in is required and that double opt-in is the operator-preferred standard for marketing. A safe routine: 1. **Show clear wording** at sign-up: who is sending, what kind of messages and how often, for example "Oferty Piekarni Kowalski przez SMS". 2. **Ask for SMS consent separately** from phone and email, with an unticked box. 3. **Confirm the number** with a code or reply. 4. **Store the evidence:** wording shown, date and time, channel and number. 5. **Do not buy lists.** Purchased numbers have no consent trail, and contacting someone only to ask for consent is also a risk. Our [opt-in consent generator](/tools/opt-in-consent-generator/) drafts the wording, and [opt-in consent across channels](/blog/opt-in-consent-multichannel-campaigns/) shows how to record it. See [opt-in](/glossary/opt-in/). ## How does opt-out work? Every commercial message should carry a free, simple way to stop, and the request must be honoured at once. Our regulation data records that the STOP keyword is honoured network-wide and that opt-out is one step and holds until the person consents again. Under the GDPR people can object to direct marketing at any time (Article 21). Add a short Polish line to each promotion, such as "Wypisz się: kowalski.example/stop", and feed replies and clicks into a suppression list shared with WhatsApp and email. Keep OTPs on their own sender so a marketing opt-out does not silence a login code. See [opt-out](/glossary/opt-out/). ## How do sender IDs work in Poland? Business SMS to Poland can use an alphanumeric sender ID of up to 11 characters, and our data notes that a numeric long number is also supported. Requirements are set by the operators, and our published lead time for alphanumeric IDs is 5 to 10 business days. Treat that as typical, not guaranteed. | Step | What to do | |---|---| | 1. Classify | Separate transactional and promotional traffic and plan a sender for each | | 2. Choose names | Use your registered business or brand name; avoid names that imitate banks, operators or public bodies | | 3. Prepare documents | Company papers and an authorisation letter naming the sender IDs and your provider | | 4. Submit | Your provider files with the operators; track each result | | 5. Test | Send an OTP and a promotion to Orange, T-Mobile, Play and Plus handsets | Draft the letter with our [sender ID letter generator](/tools/sender-id-letter-generator/), check the position with the [sender ID checker](/tools/sender-id-checker/) or the [Poland sender ID page](/sender-id/poland/), and read [sender ID types explained](/blog/sms-sender-id-types-explained/). To have us prepare and file the registration with you, see [registrations](/services/registrations/); approval stays with the operators. ## Which operators carry SMS in Poland? Four mobile networks appear in our coverage data, each with a direct route: | Operator | MCC-MNC | |---|---| | Orange Polska | 260-03 | | T-Mobile Polska | 260-02 | | Play (P4) | 260-06 | | Plus (Polkomtel) | 260-01 | Our regulation data names Orange Polska and T-Mobile Polska in the sender ID rules, and the coverage data adds Play and Plus. Read delivery reports per operator, not a blended rate; [improving SMS delivery rates](/blog/sms-not-delivered-improve-delivery-rate/) explains how to diagnose gaps. ## How should you separate OTP and promotional traffic? Keep OTPs, order alerts and reminders on their own sender and route, with no offers inside. A mixed message is commercial, which brings the consent rules above, and it puts login codes at risk if marketing traffic is filtered. | Traffic | Example | Practice | |---|---|---| | Transactional | OTP, parcel update, appointment reminder | No offers inside; own sender; any hour | | Promotional | Sale, new product, loyalty offer | Documented consent; opt-out line; daytime schedule | | Mixed | "Paczka w drodze. Rabat 10% na kolejne zakupy!" | Avoid; the offer makes it commercial | For code length and expiry see the [OTP authentication messages guide](/blog/otp-authentication-messages-guide/) and the [OTP service](/solutions/otp-notifications/). ## Do Polish characters work in a standard SMS? Not in GSM-7. The letters ą, ć, ę, ł, ń, ó, ś, ź and ż are outside the GSM 7-bit default alphabet (3GPP TS 23.038), so one of them moves the whole message to Unicode with 70 characters (67 per part). Without diacritics, plain Latin text fits 160 characters (153 per part). Emoji and curly punctuation also force Unicode. See [GSM-7](/glossary/gsm-7/), [Unicode SMS](/glossary/unicode-sms/) and [concatenated SMS](/glossary/concatenated-sms/). | Encoding | Single message | Per part when concatenated | |---|---|---| | GSM 7-bit | 160 characters | 153 | | Unicode (UCS-2) | 70 characters | 67 | These examples were counted against the limits, each in an accented and a stripped version: | Message | Encoding | Characters | Parts | |---|---|---|---| | `Twoj kod: 482913. Wazny 10 minut. Nie udostepniaj go nikomu. Piekarnia Kowalski` | GSM-7 | 79 | 1 | | `Twój kod: 482913. Ważny 10 minut. Nie udostępniaj go nikomu. Piekarnia Kowalski` | Unicode | 79 | 2 | | `Piekarnia Kowalski: 2 bulki w cenie 1 w sobote! Szczegoly: kowalski.example/s. Wypisz sie: kowalski.example/stop` | GSM-7 | 112 | 1 | | `Piekarnia Kowalski: 2 bułki w cenie 1 w sobotę! Szczegóły: kowalski.example/s. Wypisz się: kowalski.example/stop` | Unicode | 112 | 2 | | `Piekarnia Kowalski: zamówienie 1042 jest gotowe. Odbiór do 17:00.` | Unicode | 65 | 1 | The last row stays at one part because it is short enough for Unicode's 70 characters. Strip or keep diacritics deliberately: stripped text saves parts but loses readability. Many teams use stripped text for OTPs and short alerts, and accented text for offers where the second part is worth it. Check final copy in the [SMS character counter](/tools/sms-character-counter/) and read [SMS character limits and Unicode](/blog/sms-character-limits-unicode-arabic/). ## When should you send? We have not found a regulator-published time-of-day window for promotional SMS in Poland, and our regulation data records none. Agree sending hours with your provider, send promotions in local daytime (Central European Time, UTC+1, or UTC+2 in summer) and avoid late evenings. OTPs and alerts can go at any hour. The [send time planner](/tools/send-time-planner/) helps schedule campaigns, and [SMS marketing rules by country](/blog/sms-marketing-rules-by-country/) compares hours across markets. ## A worked example: a bakery chain in Kraków "Piekarnia Kowalski" (synthetic) has 35 shops and wants OTPs for its app, pickup alerts and a weekly offer. - It collects SMS consent separately from phone and email at the till and in the app, with a confirmation step, and stores wording, timestamp and number. - OTPs and pickup alerts use a separate sender and stripped text, so each fits 160 characters. - The weekly offer goes only to confirmed numbers in accented Polish, with a stop line, and the team accepts two parts per message after counting it. - Promotions are scheduled for local daytime and checked against the suppression list. - WhatsApp is offered as a second opt-in channel; see the [Poland WhatsApp pricing page](/whatsapp-pricing/poland/). ## What are the common mistakes? - **Treating phone consent as SMS consent.** Consent is specific to a channel. - **No consent records.** UKE expects the party behind a campaign to show them. - **Not counting accented text.** A one-part draft with stripped text becomes two parts with diacritics. - **Stripping diacritics in brand-sensitive copy** until it reads poorly. - **Offers inside OTPs** or service messages. - **Treating lead times as promises.** Plan buffer beyond 5 to 10 business days. ## How OmniChannels.ai helps OmniChannels.ai is powered by BroadNet, which has direct routes to Orange Polska, T-Mobile Polska, Play and Plus in our coverage data. We support consent-aware campaigns with suppression handling, Polish and Unicode content, per-operator delivery reports and SMPP 3.4 for high volume, and we prepare and file sender registration with you. For indicative list prices see the [Poland SMS pricing page](/sms-pricing/poland/), then [book a demo](/demo/). Starting small? Read our [SMS marketing guide for small businesses](/blog/sms-marketing-small-business-guide/), or the [Germany guide](/blog/bulk-sms-germany-guide/) for a neighbouring market.