Skip to content
OmniChannels.ai
Menu

Bulk SMS in Italy: AGCOM Alias, Consent and GDPR Guide

Invio SMS massivo in Italy: the AGCOM alias registry, Privacy Code article 130 and GDPR consent, TIM, Vodafone, WINDTRE and Iliad routes, and accents in GSM-7.

Updated 10 min read

By OmniChannels.ai Editorial Team · Reviewed by BroadNet Messaging Solutions Team

SMS & OTP

Short answer

To send bulk SMS in Italy, use a provider with routes to TIM, Vodafone, WINDTRE and Iliad, collect prior, specific and documented consent before any promotional SMS (GDPR and article 130 of the Italian Privacy Code), and register your alphanumeric sender (alias) in AGCOM's alias registry through an authorised provider. Operators can block unregistered aliases. Italian accents fit GSM-7, so 160 characters per message is realistic.

On this page
  1. What rules apply to bulk SMS in Italy?
  2. What consent do you need to send promotional SMS in Italy?
  3. Does the Registro delle Opposizioni apply to SMS?
  4. How does opt-out work?
  5. How does the AGCOM alias registry work?
  6. Which operators carry SMS in Italy?
  7. How should you separate OTP and promotional traffic?
  8. Do Italian accents fit in GSM-7?
  9. When should you send?
  10. A worked example: a Milan pastry chain
  11. What are the common mistakes?
  12. How OmniChannels.ai helps

Key takeaways

  • Article 130 of the Italian Privacy Code makes automated calls and electronic messages, SMS and MMS included, for advertising or direct sales subject to the recipient's consent; the GDPR sets what valid consent means.
  • AGCOM decision 12/23/CIR set up a registry of SMS aliases (alphanumeric senders) at alias.agcom.it. Aliases are registered through authorised providers, and operators can block alphanumeric SMS whose alias is not registered.
  • Our regulation data lists a typical sender ID lead time of 5 to 7 business days and alphanumeric IDs up to 11 characters; companies without an Italian seat face extra conditions, so a branded alias is never promised in advance.
  • Four mobile networks appear in our coverage data, all with direct routes: TIM (222-01), Vodafone (222-10), WINDTRE (222-99) and Iliad (222-50).
  • The accented vowels a, e, i, o and u with grave accents are in the GSM 7-bit alphabet, but the curly apostrophe is not: it is the most common reason an Italian message jumps to Unicode at 70 characters.

This guide is for marketing, e-commerce, fintech and operations teams that want to send business SMS to Italian mobile numbers (invio SMS massivo): OTPs, delivery alerts, appointment reminders and promotions. It explains who regulates what, how consent and the alias registry work, and how Italian text affects message length. It is a practical overview, not legal advice; confirm your set-up with Italian counsel before launch.

What rules apply to bulk SMS in Italy?

Four layers apply: the Privacy Code and the GDPR for consent, AGCOM for the alias registry, and operator policy for routes and filtering. None is called a "bulk SMS law".

Layer What it covers Where to check
Privacy Code, article 130 Consent for advertising and direct-sales messages by automated calls and electronic means, including SMS Normattiva
GDPR Lawful basis, quality of consent, right to object EUR-Lex
AGCOM Telecom regulator; alias registry under decision 12/23/CIR agcom.it, alias.agcom.it
Garante privacy Data protection authority; guidance and enforcement garanteprivacy.it

Our regulation data lists AGCOM as the regulator. For the market overview, see the Italy market page.

You need prior, specific and documented consent. Article 130 of the Privacy Code makes the use of automated calling systems and of electronic communications, namely email, fax, MMS and SMS, for advertising, direct sales, market research or commercial communication subject to the recipient's consent. The GDPR defines what consent must be: freely given, specific, informed and unambiguous.

Article 130 also contains a narrow exception for a seller's own similar products or services, but it refers to the email address obtained during a sale. Do not build an SMS programme on it. Collect explicit SMS consent instead.

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 "Offerte di Pasticceria Aurora via SMS".
  2. Use an unticked box and a separate consent for SMS; do not bundle it with terms and conditions.
  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.

Our opt-in consent generator drafts the wording, and opt-in consent across channels shows how to record it.

Does the Registro delle Opposizioni apply to SMS?

We have not verified that it does, so do not treat it as an SMS suppression list. The Registro pubblico delle opposizioni (RPO) was extended to mobile numbers, and it was described to us in terms of marketing telephone calls. The sources we reviewed do not say whether SMS is covered. For SMS, your obligation is documented consent under article 130 and the GDPR, plus your own suppression list. Ask Italian counsel if your programme also uses calls.

How does opt-out work?

Withdrawing consent must be as easy as giving it, and every marketing message should carry a simple, free way to stop. 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. The GDPR also gives a right to object to direct marketing at any time (article 21).

Add a short Italian line, such as "Non vuoi più messaggi? aurora.example/stop", and feed every opt-out into one suppression list that covers SMS, WhatsApp and email. Keep OTPs on a separate sender so a marketing opt-out never silences a login code. See opt-out.

How does the AGCOM alias registry work?

If you want your brand name as the SMS sender, the alphanumeric sender (alias) has to be registered. AGCOM decision 12/23/CIR set up a registry of SMS aliases at alias.agcom.it. Aliases are registered through authorised providers, and operators can block alphanumeric SMS whose alias is not registered. Our regulation data lists alphanumeric IDs of up to 11 characters, a numeric long number as an alternative, and a typical lead time of 5 to 7 business days. Treat that as typical, not guaranteed.

Step What to do
1. Classify Decide which traffic is transactional and which is promotional, and plan aliases 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 aliases and your provider
4. Submit Your provider files the alias in the registry; track each result
5. Test Send an OTP and a promotion to TIM, Vodafone, WINDTRE and Iliad handsets

Companies without an Italian seat face extra conditions. We confirm the options for your company at onboarding and never promise a branded alias in advance; a numeric sender or WhatsApp is still possible. Draft the letter with our sender ID letter generator, check the position with the sender ID checker or the Italy sender ID page, and read sender ID types explained. To have us prepare and file the registration with you, see registrations; approval stays with the registry and operators.

Which operators carry SMS in Italy?

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

Operator MCC-MNC
TIM 222-01
Vodafone Italy 222-10
WINDTRE 222-99
Iliad Italy 222-50

Our regulation data names TIM and Vodafone Italy as the operators behind the sender ID rules, and the coverage data adds the other two. Vodafone Italia has been part of the Swisscom group with Fastweb since Swisscom completed its purchase at the end of 2024. Read delivery reports per operator rather than a blended rate; improving SMS delivery rates 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 promotional, which brings the consent rules above, and it puts login codes at risk if marketing traffic is filtered.

Traffic Example Practice
Transactional OTP, delivery update, appointment reminder No offers inside; own sender; any hour
Promotional Sale, new product, loyalty offer Documented consent; opt-out line; daytime schedule
Mixed "Ordine spedito. Ecco il 10% di sconto!" Avoid; the offer makes it promotional

For code length and expiry see the OTP authentication messages guide and the OTP service.

Do Italian accents fit in GSM-7?

Yes. The letters à, è, é, ì, ò and ù belong to the GSM 7-bit alphabet (3GPP TS 23.038), so plain Italian fits 160 characters in one message and 153 per part when split. What breaks it is punctuation and symbols: the curly apostrophe (as in "un’offerta") and emoji are outside GSM-7 and move the whole message to Unicode with 70 characters (67 per part). Use the straight apostrophe. See GSM-7 and 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:

Message Encoding Characters Parts
Il tuo codice è 482913. Valido 10 minuti. Non condividerlo con nessuno. Pasticceria Aurora GSM-7 90 1
Pasticceria Aurora: 2 cornetti al prezzo di 1 sabato! Dettagli: aurora.example/s. Non vuoi più messaggi? aurora.example/stop GSM-7 124 1
Pasticceria Aurora: il tuo ordine n. 1042 è pronto. Ritiro entro le 17:00 in via Manzoni 12. GSM-7 92 1
Pasticceria Aurora: ecco un’offerta per te, 2 cornetti al prezzo di 1 sabato! Dettagli: aurora.example/s. Stop: aurora.example/stop Unicode 131 2

The last row shows the cost of one curly apostrophe. Check final copy in the SMS character counter and read SMS character limits and Unicode for other scripts.

When should you send?

We have not found a statutory time-of-day window for promotional SMS in Italy, and our regulation data records none. Agree sending hours with your provider and the operators, 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 helps schedule campaigns, and SMS marketing rules by country compares hours across markets.

A worked example: a Milan pastry chain

"Pasticceria Aurora" (synthetic) has 20 shops and wants pickup alerts, loyalty-app OTPs and a weekly offer.

  • It registers one alias for transactional traffic and one for promotions through its provider, and tests both on all four networks.
  • It collects separate SMS consent at the till and in the app with a confirmation step, storing wording, timestamp and number.
  • OTPs and pickup alerts use plain GSM-7 text with no offers inside.
  • The weekly offer goes only to confirmed numbers, uses a straight apostrophe and no emoji so it stays at one part, and ends with a stop line.
  • A WhatsApp message with an approved template carries richer content for customers who also opted in on WhatsApp; see the Italy WhatsApp pricing page.

What are the common mistakes?

  • Assuming an alias is optional. Operators can block alphanumeric SMS from unregistered aliases.
  • No consent evidence. Without a timestamp and source you cannot answer a complaint.
  • Bundled or pre-ticked consent. It is neither specific nor unambiguous.
  • Curly apostrophes and emoji that double the part count.
  • Offers inside OTPs or service messages.
  • Relying on the email exception in article 130 for SMS.

How OmniChannels.ai helps

OmniChannels.ai is powered by BroadNet, which has direct routes to TIM, Vodafone, WINDTRE and Iliad in our coverage data. We prepare and file your alias registration with you, support consent-aware campaigns with suppression handling, Italian and Unicode content, per-operator delivery reports and SMPP 3.4 for high volume, and offer the WhatsApp Business API as a complement. For indicative list prices see the Italy SMS pricing page, then book a demo. Starting small? Read our SMS marketing guide for small businesses.

Frequently asked questions

Is bulk SMS legal in Italy?

Yes, for OTPs, service messages and consented marketing. Article 130 of the Privacy Code requires consent for advertising and direct-sales messages sent by electronic means, including SMS, and the GDPR applies to the phone numbers. No single law is called an SMS law, so rules come from the Privacy Code, the GDPR, AGCOM measures and operator policy. Have Italian counsel review your flow.

Do I need to register a sender alias in Italy?

If you want your brand name as the sender, yes. AGCOM's alias registry (decision 12/23/CIR) records alphanumeric senders, which are filed through authorised providers, and operators can block alphanumeric SMS from aliases that are not registered. We prepare the registration with you; the decision stays with the registry and operators.

Can a company outside Italy use a branded alias?

Companies without an Italian seat face extra conditions under the alias rules. Depending on your situation there may be options, for example through an Italian entity. We review your case at onboarding and do not promise a branded alias in advance; a numeric sender or WhatsApp remains possible.

What consent do I need for promotional SMS in Italy?

Prior, specific and documented consent. Under the GDPR it must be freely given, specific, informed and unambiguous, so it cannot be pre-ticked or bundled with unrelated terms, and withdrawing it must be as easy as giving it. Our regulation data also records double opt-in as the operator-preferred standard for marketing.

Does the Registro delle Opposizioni cover SMS?

The public opposition register (RPO) was extended to mobile numbers for telephone marketing calls. We have not verified that it covers SMS, so we do not describe it as an SMS suppression list. For SMS, rely on documented consent under article 130 and keep your own suppression list.

Do Italian accents work in GSM-7?

Yes. The letters à, è, é, ì, ò and ù are in the GSM 7-bit alphabet, so plain Italian fits 160 characters in one message and 153 per part when split. Emoji and the curly apostrophe are not, and either one moves the whole message to Unicode with a 70-character limit.

Sources

  1. Decreto legislativo 196/2003 (Codice in materia di protezione dei dati personali), article 130, Normattiva
  2. General Data Protection Regulation (EU) 2016/679, EUR-Lex
  3. AGCOM, Autorità per le Garanzie nelle Comunicazioni
  4. AGCOM alias registry
  5. Garante per la protezione dei dati personali
  6. 3GPP TS 23.038: Alphabets and language-specific information

Keep reading

More guides