Since 2 August 2026, Article 50 of the EU AI Act has been the rule that decides how an AI sales or support agent must introduce itself to anyone in the EU. Most of the noise around the Act concerns high-risk systems — but the Digital Omnibus (Regulation (EU) 2026/1744) deferred those obligations, so for teams running AI agents that talk to EU prospects and customers, the live compliance question today is transparency, not high-risk conformity. This checklist covers what Article 50 requires right now, what it does not, and what a sales or support team should actually do about it. It is general information, not legal advice — get counsel for your specific setup.
Quick answer: Article 50 of the EU AI Act applies from 2 August 2026 and requires that people be told they are interacting with an AI system unless that is obvious, that AI-generated content carries machine-readable marking, and that deepfakes — including cloned voices presented as real people — are disclosed. It reaches non-EU companies whose AI output is used in the EU. High-risk (Annex III) obligations were deferred to 2 December 2027 by the Digital Omnibus, so for most AI sales and support agents the current obligation is disclosure and marking, backed by significant administrative fines for non-compliance.
Why this is a transparency question, not a high-risk one (for now)
The EU AI Act (Regulation (EU) 2024/1689) layers obligations by risk. Prohibited practices have applied since 2025. The general application date — including Chapter IV, where Article 50 sits — arrived on 2 August 2026. The heavyweight regime, for high-risk systems listed in Annex III, was originally due the same day.
Then the Digital Omnibus intervened. Regulation (EU) 2026/1744, published in the Official Journal on 24 July 2026, pushed the application of Annex III high-risk obligations to 2 December 2027, and obligations for high-risk AI embedded in Annex I regulated products to 2 August 2028. We covered the deferral in detail in our EU AI Act August 2026 status post — this article is the practical companion: the checklist for the part that did not move.
Article 50 was not deferred. It applies now, with one narrow transition: for the machine-readable marking duty in Article 50(2), systems already placed on the market before 2 August 2026 have until 2 December 2026 to comply, per the European Commission’s Article 50 transparency FAQ. Content generated before 2 August 2026 does not have to be retroactively labelled.
Article 50 obligations at a glance
| Obligation | Who it applies to | Applies from | What a sales/support team actually does |
|---|---|---|---|
| Art 50(1): tell people they are interacting with an AI system, unless obvious | Providers of AI systems that interact directly with natural persons | 2 Aug 2026 | Put the disclosure in the agent’s opening line, chat header and email footer; don’t rely on “obvious” |
| Art 50(2): mark synthetic audio, image, video and text as artificially generated, in machine-readable form | Providers of generative AI systems | 2 Aug 2026 (systems on market before that date: 2 Dec 2026) | Ask your vendor in writing how outputs are marked/watermarked and keep the answer |
| Art 50(3): inform people exposed to emotion recognition or biometric categorisation | Deployers of those systems | 2 Aug 2026 | If you score caller emotion or categorise people biometrically, notify them — and first check the Article 5 prohibitions |
| Art 50(4): disclose deepfakes and AI-generated public-interest text | Deployers | 2 Aug 2026 | Label cloned-voice audio that resembles a real person; label AI-written public-interest content without human editorial review |
| Annex III high-risk obligations (risk management, logging, conformity assessment) | Providers/deployers of listed high-risk systems | Deferred to 2 Dec 2027 | Diarise it; assess whether your use case is even Annex III (most sales/support agents are not) |
The checklist
1. Disclose the AI — Article 50(1)
Article 50(1) requires providers to ensure that AI systems intended to interact directly with natural persons are designed so those people are informed they are dealing with an AI system — “unless this is obvious from the point of view of a natural person who is reasonably well-informed, observant and circumspect”, as Article 50(1) puts it. The Commission’s guidance treats that exception restrictively: on a phone call, nothing about the medium makes AI obvious, so a voice agent that sounds human needs to say so.
Do this now:
- Script it into the greeting. The disclosure belongs at the start of the first interaction, not three turns in. Our disclosure scripts post has wording patterns that announce the AI without killing the conversation.
- Cover every channel. Voice, chat widget, SMS, email, WhatsApp — each needs its own disclosure surface. A chat window labelled “AI assistant” in the header may do the job; a voice call needs the words said out loud.
- Don’t hide it in terms of service. Article 50(5) requires the information to be provided in a clear and distinguishable manner at the latest at the time of the first interaction, and to meet accessibility requirements.
- Bake it into guardrails. Treat “always disclose, never deny being an AI when asked” as a hard rule in the agent’s instructions — see our guide to writing guardrails for autonomous agents.
2. Synthetic content marking and cloned voices — Articles 50(2) and 50(4)
Article 50(2) sits with the provider of the generative system: outputs must be “marked in a machine-readable format and detectable as artificially generated or manipulated”, per the Commission FAQ. If you buy rather than build, your main job is vendor diligence: get a written statement of how the platform marks generated audio and text, and whether it adheres to the Code of Practice discussed below.
Article 50(4) sits with you, the deployer. It covers deepfakes — AI-generated or manipulated content that resembles real persons and would falsely appear authentic. A cloned voice of your founder fronting outbound calls is squarely in this territory: the person hearing it should be told the voice is AI-generated. Consent from the person cloned is a separate, additional issue — see our voice cloning consent and compliance guide. Article 50(4) also requires disclosure of AI-generated text published to inform the public on matters of public interest, unless it has undergone human editorial review with someone holding responsibility.
3. Timing and wording patterns
Article 50(5) fixes the timing rule: clear, distinguishable, and at the latest at the first interaction or exposure. Patterns that work in practice:
- Voice: “Hi, this is Alex, an AI assistant calling on behalf of [company]” — identity, AI status and principal in one breath, before the pitch.
- Chat: persistent label in the widget header plus a first-message statement; don’t rely on a favicon.
- Email/SMS: a plain-language line identifying the sender as an AI assistant of the named company.
- Handoffs: when a human takes over, say so — the boundary between AI and human should stay legible in both directions.
If you already run disclosure scripts for US state laws or Australian expectations, extend them rather than forking: one honest global greeting is easier to audit than per-jurisdiction variants, and jurisdictions are converging — see our breakdown of Colorado’s SB 26-189 for the US side.
4. What records to keep
Article 50 does not impose the formal logging regime that high-risk systems will face — but market surveillance authorities can ask you to show compliance, and Article 99 backs the transparency obligations with significant administrative fines (Article 99(4)(g) lists Article 50 breaches expressly; we deliberately don’t quote amounts). Sensible evidence to keep:
- Versioned disclosure scripts and screenshots of chat/email disclosure surfaces, with deployment dates.
- Call recordings or transcripts sampled to show the disclosure is actually delivered (subject to your recording-consent obligations — see our outreach compliance overview).
- Vendor statements on Article 50(2) marking, and any Code of Practice adherence.
- Guardrail and approval-gate configurations showing disclosure is enforced, not optional — human-in-the-loop controls help here.
- A dated note of your Annex III self-assessment, so the 2 December 2027 deadline doesn’t surprise you.
Guidelines and Code of Practice: current status
Two support instruments are now final — neither is a draft anymore. On 20 July 2026 the European Commission published the final Guidelines on the Article 50 transparency obligations, clarifying (among other things) how the “obvious” exception and the deepfake definition are read. And the Code of Practice on Transparency of AI-generated Content — final version published 10 June 2026 — has been confirmed by the Commission and the AI Board as an adequate voluntary tool for demonstrating compliance, with roughly 190 signatories by late July 2026. Signing is optional; if your vendor has signed, that is useful evidence for your records, though not conclusive proof of compliance.
Does this reach a US or Australian company?
Yes, in most realistic setups. Article 2(1) applies the Act to providers placing AI systems on the market in the Union irrespective of where they are established, and — the clause that catches outbound teams — to “providers and deployers of AI systems that have their place of establishment or are located in a third country, where the output produced by the AI system is used in the Union” (Article 2(1)(c)). An Australian company whose AI agent calls prospects in Berlin is producing output used in the Union. The practical read: if EU numbers or EU inboxes are in your target list, run the checklist.
Where Zian stands
Zian’s agents operate across phone, SMS, email and WhatsApp in 30+ languages, and voice cloning is supported — which is exactly why we treat disclosure as a platform behaviour, not a customer afterthought. Honest disclosure is also the commercially smart move: a prospect who discovers mid-call that “Alex” was a bot is not warming to your demo. If you want AI sales agents built with transparency as a default, Apply For Partnership.
FAQs
Does the EU AI Act ban AI sales calls?
No. The AI Act does not prohibit AI sales or support calls. Its Article 5 prohibitions target practices like subliminal manipulation and exploiting vulnerabilities, not ordinary commercial outreach. For AI agents talking to EU users, the operative duty today is Article 50 transparency: disclose the AI, mark synthetic content, and label deepfakes. Other rules, such as GDPR and national telemarketing laws, still apply separately.
Do I have to disclose the AI if it’s obvious?
Article 50(1) contains an exception where the AI interaction is obvious to a natural person who is reasonably well-informed, observant and circumspect, and the European Commission’s guidance says this exception is interpreted restrictively, per the Commission’s Article 50 transparency FAQ. A human-sounding voice agent on a phone call is not obvious, so disclose. In practice the safest and cheapest policy is to disclose everywhere and skip the argument.
Does Article 50 apply to a US or Australian company calling EU prospects?
Generally yes. Under Article 2(1) the AI Act applies to providers placing AI systems on the EU market irrespective of where they are established, and to providers and deployers located in third countries where the output produced by the AI system is used in the Union. An AI agent calling, emailing or messaging people in the EU produces output used in the Union, which brings the transparency obligations into play.
What was deferred to 2027 — and what wasn’t?
The Digital Omnibus, Regulation (EU) 2026/1744, deferred the Annex III high-risk obligations from 2 August 2026 to 2 December 2027, and obligations for high-risk AI in Annex I products to 2 August 2028. Article 50 transparency was not deferred: it applies from 2 August 2026, with one transition — systems already on the market before that date have until 2 December 2026 to meet the Article 50(2) machine-readable marking duty.
What happens if we ignore Article 50?
Non-compliance with the transparency obligations is expressly listed among the breaches subject to administrative fines under Article 99 of the AI Act, and the fines are significant. Member State authorities set enforcement within the Act’s framework, and factors like the nature, gravity and duration of the infringement affect the amount. Beyond fines, undisclosed AI is a reputational risk with prospects and a contractual risk with partners.
This article is general information for practitioners, current as at 16 August 2026, and is not legal advice. Regulations and guidance change; verify the current state at EUR-Lex and the European Commission, and speak to qualified counsel about your specific deployment.