Is AI Cold Calling Legal in Europe?
A Country-by-Country Guide
AI cold calling is legal in some European countries and needs prior consent in most others. Under the ePrivacy Directive an AI voice counts as an automated calling machine, so whether it is allowed for businesses depends on how each country transposed the rule. Today, disclosed AI-voice B2B cold calls to genuine company landlines are viable in roughly eleven markets on an opt-out basis.
This is the green / amber / red map: which markets allow it, on what legal basis, and how the number path changes at each border. Hear the disclosed AI your prospects would hear.
This is general information, not legal advice - verify current rules for your use case.
The Short Answer
The decisive question is set by the ePrivacy Directive, Article 13: marketing via automated calling machines needs prior opt-in consent. An AI voice with no live human is such a machine. So the answer turns on one thing per country - does that country apply the automated-call consent rule to businesses (legal persons), or only to consumers (natural persons)?
- Where the rule protects consumers only, disclosed AI-voice B2B cold calling to company lines can run on an opt-out basis. That is roughly eleven markets.
- Where the rule also covers businesses, an automated cold call needs prior consent - even to a company landline. That is most of the EU, plus the US and the UK. There, a live human has to open.
- Consumers (B2C) are protected everywhere: cold AI calling and cold text messaging to individuals need consent across the EU, the UK and the US.
On top of that legal basis, the EU AI Act adds a disclosure duty that everyone must meet. For the plain-language version of this, read is AI cold calling legal in the EU.
The One Targeting Rule That Keeps It Clean
Across every viable market, the same discipline keeps a campaign compliant. It is not a loophole - it is who you are allowed to call and how:
- Call genuine company or organisational landlines of limited companies - never sole traders, never personal mobiles. A sole trader or a named person on a personal mobile is a natural person, which flips the basis to opt-in.
- Keep the pitch business or job relevant, and keep the call organisation-directed. In Latvia especially, do not lead with a named individual - address the organisation.
- Disclose that it is an AI, on every call, and honour opt-outs the instant they are given.
Do that, and the campaign is opt-out-clean in the green markets. Dial a sole trader or personalise to a named individual in their consumer capacity, and it becomes cold outreach that needs consent.
Which EU Countries Allow AI Cold Calling?
A country-by-country map of the viable voice markets - the legal basis and the number path for each. Green delivers cleanly via a standard number; amber is legal but needs a special number path; red needs prior consent for an automated call.
| Country | Status | Legal basis | Number path |
|---|---|---|---|
| Lithuania | Green - viable | The automated-call opt-in applies to natural persons only (ERĮ, in force 1 Jul 2026); marketing to legal persons needs no consent. Company lines only, opt-out, disclose the AI. | Home market - a standard Telnyx number, no local lease. |
| Latvia | Green - viable | ISPL s.9(6) limits the automated-calling opt-in to natural persons, so B2B to legal persons is opt-out (the DVI confirms this). Keep it organisation-directed - do not lead with a named person. | A standard Telnyx Latvian number. |
| Luxembourg | Green - viable | The Law of 30 May 2005 confines the automated-call opt-in to natural persons, and there is no national do-not-call register. Legal persons only, disclose the AI. | A standard Telnyx number (local address on file where required). |
| Croatia | Green - viable | The Electronic Communications Act (NN 76/2022) automated-call opt-in expressly does not apply to legal persons. Exclude obrt sole traders, disclose the AI, use a non-spoofed caller ID. | A Telnyx Croatian number with a registered address that matches the number area. |
| Finland | Green - viable | The automated-call opt-in covers natural persons only; B2B to companies is opt-out. Disclose the AI, honour opt-outs, and do not dial sole traders. | A Telnyx national number - your Lithuanian company address works, no local lease. |
| Estonia | Green - viable | The ECA splits by person: natural persons opt-in, legal persons opt-out, and live calling is excluded from the automated-consent rule, so voice rides legitimate interest. Target company / Business-Register lines. | A standard Telnyx Estonian number. |
| Bulgaria | Green - viable | The Electronic Communications Act opt-in binds consumers (natural persons); genuine B2B legal persons need no consent - the most permissive of the group, extending to professionals about their business. Disclose the AI, keep clean B2B lists. | A Telnyx national number - no local lease needed. |
| Slovenia | Green - viable | ZEKom-2 limits the automated-call opt-in to natural-person subscribers; legal-person lines are fine. Exclude s.p. sole traders, use a valid caller ID, rely on legitimate interest. | A standard Telnyx Slovenian number. |
| Portugal | Green - viable | Lei 41/2004 carves legal persons out of the automated-call opt-in (B2B opt-out). Scrub the monthly DGC legal-person opt-out list, disclose the AI. | A Telnyx Portuguese number; provisioning also needs a Portuguese NIF and business registration. |
| Sweden | Green - viable | The Marketing Act automated-call opt-in is natural persons only, and the NIX register does not cover company numbers, so true B2B needs no opt-in. Disclose the AI, present a valid Swedish caller ID. | Legal with no special number, but confirm routing is not caught by the foreign-caller-ID anti-spoofing block - originate through a native Swedish operator. |
| France | Amber - special number path | B2B is legal (the opt-in binds consumers only), but automated marketing campaigns must display a verified ARCEP number range (a VUN). Disclose the AI. | Not a standard DID: a VUN number from a French ARCEP operator, which requires a French SIREN. |
| Ireland | Amber - special number path | Automated calls to business fixed lines are opt-out (scrub the national directory, identify yourself); mobiles and sole traders need consent. | ComReg blocks foreign-originated Irish caller ID, so treat lists as warm / consented and originate through a domestic Irish provider. |
| Germany | Red - consent required | AI voice counts as an automated calling machine (UWG §7); express opt-in is required from everyone, including B2B. The presumed-consent carve-out is live-human only. | Route to reactivation, inbound, or a human opener. |
| Spain | Red - consent required | The General Telecommunications Law (11/2022) extends the automated-call opt-in to legal persons, with no legitimate-interest escape. | Route to reactivation, inbound, or a human opener. |
| Italy | Red - consent required | The Codice Privacy automated-system opt-in extends to legal persons, and spoofed Italian caller ID is separately blocked. | Route to reactivation, inbound, or a human opener. |
| Poland | Red - consent required | The PKE automatic-calling-system opt-in reaches legal persons, and a breach is also an unfair-competition offence. | Route to reactivation, inbound, or a human opener. |
| Netherlands | Red - consent required | The Telecommunications Act automated-system opt-in binds companies too; a live human may cold-call B2B, an AI voice may not. | Route to reactivation, inbound, or a human opener. |
| Austria, Belgium, Czechia, Cyprus, Denmark, Greece, Hungary, Malta, Romania, Slovakia | Red - consent required | Each transposes the automated-call opt-in to cover businesses, so an automated cold call needs prior consent - a live human can sometimes cold-call a company, an AI voice cannot. | Route to reactivation, inbound, or a human opener. |
| United States & United Kingdom | Red - consent required | Separate regimes (TCPA / FCC in the US, PECR in the UK), but an AI voice into cold lists is off the table without consent; in the US, AI voice equals a prerecorded robocall. | Route to reactivation, inbound, or a human opener. |
This is general information, not legal advice - verify current rules for your use case. Each verdict traces to the primary statute and national data-protection authority of that country; the deciding factor is whether the automated-call consent rule covers legal persons or only consumers.
The AI-Act Disclosure Duty Everyone Meets
Separate from the per-country consent question, the EU AI Act sets a baseline that applies in every member state. Article 50 requires that a person be told they are interacting with an AI, and it binds from 2 August 2026. It is not optional and it does not vary by border.
So even in a green market, the opening disclosure is mandatory - and it is also what the whole opt-out model rests on. We open every call by disclosing the AI, which is why the same design works across the map rather than being reworked country by country.
How We Deliver Per Market
A compliant program is not one setting - it is configured country by country. We adapt both the channel and the number path to the market:
- Green markets. A disclosed AI voice cold-calls company landlines on an opt-out basis, from a standard number - with Sweden originated through a native operator and Portugal scrubbed against the DGC list.
- Amber markets. France runs on a verified ARCEP number range via a French operator; Ireland is treated as warm / consented lists on a domestic provider because foreign-originated Irish caller ID is blocked.
- Red markets. Where an automated cold call needs consent, we do not AI-cold-call. We lead with reactivating contacts already in your database, inbound handling, or a human opener instead.
Under the hood it is the same motion as our compliant AI cold calling service, our AI SDR service, and AI lead sourcing from public records - with the number path chosen per country. Where voice is red, we route the same targets into database reactivation.
What to Check Before You Run AI Cold Calling in Europe
The buyer criteria a European program has to meet - and what we build in.
EU data residency
The contact data and call records stay inside the EU, on infrastructure we run, so a European buyer never has to explain a transatlantic data transfer to their DPO.
AI-Act disclosure by default
Every call opens by disclosing that the caller is an AI - the Article 50 duty that binds across the EU from 2 August 2026, built in rather than bolted on.
Instant, honoured opt-out
The moment a prospect says stop, the AI honours it on the spot, logs it, and suppresses that contact across voice and text - no re-dial, with a record of who opted out and when.
Do-not-call scrubbing
Lists are checked against the relevant national opt-out registries before dialling - including the Portuguese DGC legal-person list where it applies - so the campaign starts clean.
Genuine-business targeting
We dial official company / organisational landlines of limited companies, never sole traders or personal mobiles, and keep the pitch business-relevant - the targeting rule that keeps every green market clean.
Done-for-you, per market
You wire up nothing. We adapt the channel and the number path country by country, and where automated voice is red, we lead with reactivation, inbound or a human opener instead.
Powered by industry-leading technology
Hear the Disclosed AI That Opens the Call
Talk to the voice agent right now - this is the natural, disclosed tone your prospects would hear on the opening call.
Click to start a conversation
Frequently Asked Questions
Is AI cold calling legal in the EU?
Which countries allow it?
Do I have to disclose the AI?
Is cold B2C calling ever allowed?
What about Germany, Spain, Italy and Poland?
What is the safest way to target?
Is this legal advice?
Run It in the Markets Where It Is Clean
Tell us the markets you sell into. We configure the channel and the number path country by country, disclose the AI, target genuine business lines, honour every opt-out - and where automated voice is red, we lead with reactivation or a human opener instead.
This is general information, not legal advice - verify current rules for your use case.