Article50.io
Question · Art. 50(1)

Do AI Phone and Voice Agents Need a Disclosure Under Article 50?

· 7 min read

Yes. Article 50(1) of the EU AI Act covers AI systems intended to interact directly with people, and an AI agent that answers or makes phone calls does exactly that. Callers must be told they are talking to an AI, at the latest at the start of their first interaction. On a call, that means a spoken statement at the beginning of the conversation, not a notice on your website.

Key point: An AI phone or voice agent is covered by Article 50(1) in the same way as a text chatbot. The disclosure has to reach the caller in a clear and distinguishable way at the latest at the first interaction (Art. 50(5)), which on a phone line means saying it at the start of the call.

Why voice agents are squarely in scope

The test in Article 50(1) is functional: is the AI system intended to interact directly with natural persons? It doesn't matter whether the interaction happens by text, voice or video, or whether the system is high-risk. AI receptionists, booking lines, support hotlines, outbound sales callers and in-app voice assistants all interact directly with people.

The only way out is the "obvious" exception. Article 50(1) doesn't require a disclosure where it is obvious "from the point of view of a natural person who is reasonably well-informed, observant and circumspect" that they are dealing with an AI. Voice agents are usually built to make that less obvious. They use natural-sounding voices, pause and say "mm-hm", and often introduce themselves with a human name. For most voice agents, rely on the disclosure, not the exception.

What the disclosure should sound like

Law firms reporting on the Commission's Article 50 guidelines, adopted on 20 July 2026, say the guidelines accept a spoken statement as a disclosure in a voice interaction, and expect it at the very first interaction. They also reportedly reject vague references to an "assistant" as a disclosure on their own.

In practice:

  • Say it first. Put the disclosure in the opening line of every call, before you ask for a name, account number or reason for calling.
  • Say "AI" plainly. For example: "Hi, you've reached Acme. I'm an AI assistant and I can help with bookings, or put you through to a person." The words "virtual assistant" alone may not be clear to every caller.
  • Don't bury it after hold music or a long menu. The caller should hear it before they start talking to the AI.
  • Keep it accessible. Article 50(5) requires the information to meet applicable accessibility requirements. Speak at a normal pace, and don't rely on a text message or web page as the only disclosure.

For written disclosure wording you can adapt, see the AI chatbot disclaimer template.

Inbound and outbound calls

  • Inbound (AI receptionists, support lines). The caller chose to ring you, but they may not expect an AI. Disclose in the greeting.
  • Outbound (AI sales or reminder calls). The person didn't start the conversation, so the disclosure matters even more. State that the caller is an AI, and which business it's calling for, at the start.
  • Transfers. If the call moves from the AI to a person, or back, make the switch clear.
  • Voicemail. Whether an AI-generated voicemail counts as an interaction isn't settled. The cautious approach is to include the disclosure in the message anyway.

Who owns the duty: you or the voice platform?

Article 50(1) is a provider duty. Who the provider is depends on how your voice agent was built.

  • You use an off-the-shelf AI phone product (an AI receptionist or call-centre platform). The platform that builds the system and places it on the market under its own name is most likely the provider. You are most likely a deployer. But you usually write the greeting script, pick the voice and name the agent, so in practice you control whether callers hear a disclosure.
  • You or an agency build your own voice agent on speech and language model APIs, and run it under your own name. You are likely the provider of that voice agent, and the Article 50(1) duty is then directly yours.

The same reasoning is set out in more detail, for text chatbots, in do I need Article 50 compliance if I only use a chatbot?

Cloned and synthetic voices

Voice agents raise two further Article 50 questions that a text chatbot doesn't.

Machine-readable marking (Art. 50(2)). Providers of AI systems that generate synthetic audio must mark the output in a machine-readable format so it can be detected as artificially generated. That is the voice platform's duty, not yours, if you use someone else's. For generative systems already on the market before 2 August 2026, Article 111(4), inserted by the Digital Omnibus (Reg. 2026/1744), gives providers until 2 December 2026. See Article 50 deadlines.

Deep fakes (Art. 50(4)). A deep fake is AI-generated or manipulated image, audio or video content that resembles existing persons, objects, places, entities or events and would falsely appear to a person to be authentic (Art. 3(60)). A cloned voice of a real person, such as your founder or a well-known presenter, used in recorded audio can be a deep fake, and deployers must disclose deep fakes under Article 50(4).

Whether a live AI call in a cloned real voice also falls under Article 50(4) is not settled. A practical approach: if your voice agent uses a clone of a real person's voice, say so in the opening disclosure as well, for example "This is an AI assistant using [name]'s voice." For recorded audio, see deepfake disclosure and Article 50 for podcasters.

Other rules still apply

Article 50 sits alongside other laws rather than replacing them (Art. 50(6)). Phone lines often raise separate obligations under data protection, call recording, telemarketing and consumer protection rules, which vary by country. An Article 50 disclosure doesn't satisfy those, and they don't replace it.

Checklist for an AI voice agent

  • The opening line of every inbound call says the caller is speaking to an AI, in plain words.
  • Outbound AI calls say they're from an AI, and on whose behalf, at the start.
  • The disclosure comes before the AI asks for personal details.
  • Transfers between the AI and a person are announced.
  • The agent doesn't use a human name without also saying it's an AI.
  • If the voice is a clone of a real person, that is disclosed too.
  • You've asked your voice platform how it handles Article 50(2) marking of synthetic audio.
  • You've called your own number, as a customer would, and heard the disclosure.

The free Article50.io scan checks website pages, not phone lines. It flags a detectable AI chat widget with no AI-disclosure wording on the page or in the widget as it loads. Use the checklist above for your voice channel.

Frequently asked questions

Does an AI phone receptionist need to say it's an AI?

Yes, unless it is obvious to the caller. Article 50(1) covers AI systems intended to interact directly with people, including by voice. The caller must be told at the latest at the first interaction (Art. 50(5)), which on a call means in the greeting. Law firms report that the Commission's July 2026 guidelines accept a spoken statement as a disclosure in a voice interaction.

When during a call should the AI disclosure be made?

At the start, before the caller is asked for anything. Article 50(5) requires the information at the latest at the time of the first interaction, and in a clear and distinguishable manner. A disclosure after the caller has already given personal details, or only on your website, is unlikely to be enough.

Is a realistic AI voice "obviously" an AI?

Usually not. The exception in Article 50(1) only applies where a reasonably well-informed, observant and circumspect person would already know they are dealing with an AI. Natural-sounding synthetic voices are designed to sound human, so the exception rarely helps voice agents.

Who is responsible if I use an AI receptionist platform?

The platform that builds the AI system and places it on the market under its own name is most likely the provider, which is who Article 50(1) formally addresses. You are most likely a deployer. But you usually control the greeting script, so in practice the disclosure callers hear is in your hands. This is a legal judgement that depends on your setup.

Does using a cloned voice of a real person change anything?

It can. Audio that resembles an existing person and would falsely appear authentic is a deep fake under Article 3(60), and deployers must disclose deep fakes under Article 50(4). Whether a live AI call counts as deep fake content is not settled, so the cautious approach is to disclose the cloned voice in the opening line too.

This article is general information, not legal advice.

Check your site automatically

Article50.io is an automated Article 50 transparency assessment platform that scans websites for potential EU AI Act transparency obligations and provides remediation guidance, implementation instructions, and compliance-ready disclosure language.

The free scan shows your single most severe finding in about 30 seconds — no signup, public pages only.

More from the blog

Automated technical guidance, not legal advice. Citations refer to Regulation (EU) 2024/1689.