---
title: "Bulk SMS in Romania: ANCOM, Consent and Romanian Diacritics"
description: "Bulk SMS Romania guide: ANCOM, Law 506/2004 consent, GDPR and ANSPDCP, Orange, Vodafone, Digi and Telekom routes, sender IDs and diacritics in SMS length."
canonical: "https://omnichannels.ai/blog/bulk-sms-romania-guide/"
language: "en"
updated: "2026-11-06"
publisher: "BroadNet Technologies"
brand: "OmniChannels.ai"
category: "sms"
primaryQuery: "bulk sms romania"
keywords: ["bulk sms romania", "sms sender id romania", "sms marketing romania", "legea 506/2004 sms", "romanian diacritics sms", "orange vodafone digi sms", "sms in masa romania"]
published: "2026-11-06"
author: "OmniChannels.ai Editorial Team"
reviewer: "BroadNet Messaging Solutions Team"
readingMinutes: 10
answer: "To send bulk SMS in Romania, use a provider with routes to Orange, Vodafone, Digi and Telekom, send from an alphanumeric sender ID of up to 11 characters, and send marketing only to people who gave prior, express consent under Law 506/2004 and GDPR. Plan on 5 to 10 business days for sender ID set-up, keep OTPs separate from promotions, and note that Romanian diacritics (ă, â, î, ș, ț) force Unicode at 70 characters."
takeaways: ["Our regulation data lists ANCOM as the telecoms regulator, with sender ID requirements set by the operators and a typical lead time of 5 to 10 business days; alphanumeric IDs run up to 11 characters and numeric long codes are also supported.", "Law 506/2004 transposes the ePrivacy Directive and is supervised by the data protection authority, ANSPDCP; its enforcement decisions on commercial messages cite express, prior consent, and GDPR applies to the numbers themselves.", "Four mobile networks appear in our coverage data, all with direct routes: Orange Romania (226-10), Vodafone Romania (226-01), Digi Romania (226-05) and Telekom Romania (226-03).", "The Romanian letters ă, â, î, ș and ț are outside the default GSM 7-bit alphabet, so a message containing one is sent as Unicode with 70 characters (67 per part) instead of 160 (153).", "We have not found a regulator-published time-of-day window for promotional SMS in Romania; schedule promotions for local daytime and keep OTPs and alerts on a transactional route."]
faq: 
  - q: "Is bulk SMS legal in Romania?"
    a: "Yes. Businesses send OTPs, alerts, reminders and marketing by SMS in Romania, provided they use a legitimate route, hold a lawful basis for the numbers and, for marketing, prior express consent. There is no single bulk SMS statute, so the rules come from Law 506/2004, GDPR, ANCOM and the operators."
  - q: "Do I need consent to send marketing SMS in Romania?"
    a: "Treat prior, express consent as required. Law 506/2004, which transposes the ePrivacy Directive, governs unsolicited commercial communications, and ANSPDCP enforcement decisions on commercial messages refer to express prior consent. Our regulation data also calls for GDPR-compliant opt-in. Keep proof of each consent and ask Romanian counsel about exceptions."
  - q: "Do I need to register a sender ID in Romania?"
    a: "Plan on a set-up step. Our regulation data says sender IDs are set up through the operators, BroadNet confirms current requirements during onboarding, and the typical lead time is 5 to 10 business days. That is a typical range, not a promise, so test delivery on every network before launch."
  - q: "Can I use Romanian diacritics in SMS?"
    a: "Yes, but they cost length. The letters ă, â, î, ș and ț are not in the GSM 7-bit alphabet, so a message containing one is sent as Unicode and holds 70 characters instead of 160. Many senders drop the diacritics for short messages, which is readable but less polished. Choose per message type."
  - q: "Which operators carry SMS in Romania?"
    a: "Our coverage data lists Orange Romania, Vodafone Romania, Digi Romania and Telekom Romania, each with a direct route. Review delivery reports per operator, because a healthy overall rate can hide a weak network."
  - q: "What is the difference between cedilla and comma-below letters?"
    a: "Romanian ș and ț are written with a comma below, but older systems used the cedilla forms ş and ţ. Both sets are outside GSM-7, so both force Unicode. For consistent display, use the comma-below forms in modern Unicode text and test on real handsets."
sources: 
  - title: "ANCOM: National Authority for Management and Regulation in Communications"
    url: "https://www.ancom.ro/"
  - title: "ANSPDCP: National Supervisory Authority for Personal Data Processing"
    url: "https://www.dataprotection.ro/"
  - title: "Legea nr. 506/2004 privind prelucrarea datelor cu caracter personal și protecția vieții private în sectorul comunicațiilor electronice"
    url: "https://legislatie.just.ro/"
  - title: "3GPP TS 23.038: Alphabets and language-specific information"
    url: "https://www.3gpp.org/dynareport/23038.htm"
---

# Bulk SMS in Romania: ANCOM, Consent and Romanian Diacritics

Canonical: https://omnichannels.ai/blog/bulk-sms-romania-guide/
Language: en
Publisher: OmniChannels.ai by BroadNet Technologies

This guide is for marketing, e-commerce, banking and operations teams that want to send business SMS to mobile numbers in Romania: OTPs, delivery alerts, appointment reminders and promotions. It explains who regulates what, how sender IDs work, what consent you need, and how Romanian diacritics affect message length. It is a practical overview, not legal advice; confirm requirements with Romanian counsel and your provider before launch.

## What rules apply to bulk SMS in Romania?

Three layers apply: telecoms regulation and operator policy, Law 506/2004 on electronic communications privacy, and GDPR. None is a single "bulk SMS law", so you assemble the picture from each.

| Layer | What it covers | Where to check |
|---|---|---|
| ANCOM and the operators (Orange, Vodafone, Digi, Telekom) | Telecoms regulation, routes, sender ID handling, filtering | [ancom.ro](https://www.ancom.ro/) |
| Law 506/2004 | Unsolicited commercial communications, privacy in electronic communications | [legislatie.just.ro](https://legislatie.just.ro/) |
| GDPR and ANSPDCP | Lawful basis, transparency and rights for personal data; supervision and fines | [dataprotection.ro](https://www.dataprotection.ro/) |

Our regulation data lists the National Authority for Management and Regulation in Communications (ANCOM) as the regulator. It records that sender ID requirements are set by the operators, so the rule that matters on launch day is the one your operator route enforces.

## Do you need consent to send marketing SMS in Romania?

Yes, treat prior, express consent as required. Law 506/2004 transposes the ePrivacy Directive, and its rules on unsolicited commercial communications are enforced by the data protection authority ANSPDCP. Published ANSPDCP sanctions against commercial messages refer to the lack of prior express consent, including a fine on a mobile operator over unsolicited commercial SMS and fines on retailers who could not show consent. We list no amounts here because they date from earlier years; see the authority's site for current decisions.

Separately, GDPR applies to the phone numbers as personal data. Our regulation data records that GDPR-compliant opt-in is required, that double opt-in is the operator-preferred standard for marketing, and that a STOP keyword is honoured network-wide. A safe routine is:

1. **Record consent:** the exact wording shown, date and time, channel and number.
2. **Say who is sending and why** at sign-up, for example "Offers from Dacia Cafe by SMS".
3. **Include an opt-out in every promotion** and honour it at once.
4. **Keep one suppression list** across SMS, WhatsApp and email.
5. **Keep proof.** The burden of showing consent is on the sender in practice, as the fines on retailers show.
6. **Never buy lists.** Bought numbers carry no consent trail.

For wording, use our [opt-in consent generator](/tools/opt-in-consent-generator/) and read [opt-in consent across channels](/blog/opt-in-consent-multichannel-campaigns/) for how to record it.

## How do sender IDs work in Romania?

Business SMS to Romania normally uses an alphanumeric sender ID of up to 11 characters, which shows your brand instead of a number. Numeric long codes are also supported, according to our regulation data. See [alphanumeric sender ID](/glossary/alphanumeric-sender-id/).

Our published lead time is 5 to 10 business days. Treat it as typical, not guaranteed.

| Step | What to do |
|---|---|
| 1. Classify | Decide which traffic is transactional (OTP, alerts) and which is promotional, and plan one sender ID for each |
| 2. Choose names | Use your brand name; avoid names that imitate banks, authorities or operators |
| 3. Prepare documents | Company registration details and an authorisation letter naming the sender IDs and your provider |
| 4. Submit | Your provider files with the operators that need it; track each approval |
| 5. Test | Send an OTP and a promotion to Orange, Vodafone, Digi and Telekom handsets and check how the sender displays |

Our [sender ID letter generator](/tools/sender-id-letter-generator/) drafts the letter, the [sender ID checker](/tools/sender-id-checker/) shows the current position, and the [Romania sender ID page](/sender-id/romania/) summarises it. If you want us to prepare and file the registration with you, see [registrations](/services/registrations/); approval decisions stay with the operators and regulators. Background on formats is in our guide to [sender ID types](/blog/sms-sender-id-types-explained/).

## Which operators carry SMS in Romania?

Four mobile networks appear in our coverage data, each with a direct route:

| Operator | MCC-MNC |
|---|---|
| Orange Romania | 226-10 |
| Vodafone Romania | 226-01 |
| Digi Romania | 226-05 |
| Telekom Romania | 226-03 |

Read delivery reports per operator instead of a blended rate. Our guide to [improving SMS delivery rates](/blog/sms-not-delivered-improve-delivery-rate/) explains how to diagnose gaps, and an [HLR lookup](/glossary/hlr-lookup/) removes dead numbers before you send.

## How should you separate OTP and promotional traffic?

Keep OTPs, order alerts and other service messages on their own sender ID and route, and put promotions on another. A promotion inside an OTP puts your login codes at risk if the sender is filtered or reported.

| Traffic | Example | Practice |
|---|---|---|
| Transactional | OTP, payment confirmation, delivery alert | No promotion inside; own sender ID; any hour |
| Promotional | Sale, new product, loyalty offer | Consented numbers only; opt-out in the message; daytime schedule |
| Mixed | "Your parcel has shipped. Get 10% off next time" | Avoid; the offer makes it promotional |

For OTP content and security, read our [OTP authentication messages guide](/blog/otp-authentication-messages-guide/).

## How do Romanian diacritics affect SMS length?

Romanian diacritics push a message to Unicode. The letters ă, â, î, ș and ț are not in the default GSM 7-bit alphabet, so one of them switches the whole message to Unicode with 70 characters (67 per part) instead of 160 (153). The same applies to emoji and curly quotation marks. See [GSM-7](/glossary/gsm-7/) 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. The pairs show the same text with and without diacritics:

| Message | Encoding | Characters | Parts |
|---|---|---|---|
| `Codul tau Dacia Cafe este 482913. Nu il da nimanui.` | GSM-7 | 51 | 1 |
| `Codul tău Dacia Cafe este 482913. Nu îl da nimănui.` | Unicode | 51 | 1 |
| `Dacia Cafe: Un croissant gratuit la orice cafea in weekend! Arata acest SMS la casa. Dezabonare: daciacafe.example/stop` | GSM-7 | 119 | 1 |
| `Dacia Cafe: Un croissant gratuit la orice cafea în weekend! Arată acest SMS la casă. Dezabonare: daciacafe.example/stop` | Unicode | 119 | 2 |

The last pair shows the trade-off: the correctly spelled promotion needs two parts, the unaccented one needs one. Short OTPs fit either way, so keep correct spelling there. For long promotions, decide whether the extra part is worth it. Use the comma-below forms ș and ț in modern text, since the older cedilla forms are also outside GSM-7. 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/) for other scripts.

## When should you send?

We have not found a regulator-published time-of-day window for promotional SMS in Romania, and our regulation data records none. Agree sending hours with your provider, schedule promotions for local daytime (Romanian time, EET or EEST) and avoid late evenings. OTPs and alerts can go at any hour. The [send time planner](/tools/send-time-planner/) helps, and [SMS marketing rules by country](/blog/sms-marketing-rules-by-country/) compares hours across markets.

## What is a launch checklist for Romania?

1. **Purpose split:** OTP, service and promotional messages each have their own sender ID and copy.
2. **Consent store:** every marketing number has wording, date, time and channel recorded.
3. **Opt-out path:** a STOP keyword or link works, is tested and feeds the suppression list the same day.
4. **Sender display:** each ID is tested on Orange, Vodafone, Digi and Telekom handsets, with the 5 to 10 business day lead time built into the plan.
5. **Encoding decision:** each template is marked as diacritics or plain, counted in the character counter, and its number of parts is known.
6. **Delivery monitoring:** reports are read per operator, with a named owner for failures.
7. **Fallback plan:** decide what happens when an SMS fails, for example a retry or a message on a channel the customer has opted in to, such as WhatsApp. Our [Romania WhatsApp pricing page](/whatsapp-pricing/romania/) shows the rate card context.

## A worked example: a Cluj café chain

"Dacia Cafe" (synthetic) has fifteen cafés and wants OTPs for its app, order-ready alerts and a weekly offer.

- It uses two alphanumeric sender IDs, one for transactional and one for promotional traffic, built into a plan with the 5 to 10 business day lead time, and tests both on all four networks.
- It collects consent in the app and at the till, storing wording, timestamp and number, and shows "Oferte prin SMS" with a clear opt-out.
- OTPs use correct Romanian spelling, since they are short and stay at one part.
- The weekly offer is written without diacritics to stay at one part, checked against the suppression list and scheduled for local daytime.
- Opt-outs feed one suppression list that also covers email and WhatsApp.

## What are the common mistakes?

- **No consent evidence.** Without a timestamp and source you cannot answer an ANSPDCP complaint.
- **Assuming a past purchase is consent for promotions.**
- **Mixed diacritics and plain text without checking length.** A single ă can double the cost of a long message.
- **Cedilla letters in copied text.** They look right but still force Unicode.
- **Look-alike sender names.** Names imitating banks or authorities risk blocking.
- **Mixing OTP and promotion on one sender ID.**

## How OmniChannels.ai helps

OmniChannels.ai is powered by BroadNet, which has direct routes to Orange, Vodafone, Digi and Telekom in our coverage data. We prepare and file sender ID registration with you, support Romanian and English content, and give you per-operator delivery reports, with SMPP 3.4 for high volume. For indicative list prices, see the [Romania SMS pricing page](/sms-pricing/romania/), then [book a demo](/demo/). Small team? Our [SMS marketing guide for small businesses](/blog/sms-marketing-small-business-guide/) covers the basics.