Is my chatbot covered by EU AI Act Article 50?

Short answer: if EU users can talk to your bot and a reasonable person might not realise it is an AI, yes, Article 50(1) covers you — from 2 August 2026. This guide walks through the actual legal test in Regulation (EU) 2024/1689 so you can make (and document) the call for your own product.

The rule

“Providers shall ensure that AI systems intended to interact directly with natural persons are designed and developed in such a way that the natural persons concerned are informed that they are interacting 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, taking into account the circumstances and the context of use.” — Article 50(1)

Three elements have to be present for the duty to bite:

1. An AI system (Article 3(1) — machine-based, infers from input how to generate output).
2. Intended to interact directly with natural persons — chat, voice, or any conversational interface.
3. The AI nature is not obvious to a reasonably well-informed user in context.

Covered in practice

• Customer-support chat widgets answering with an LLM — even if a human can take over mid-conversation.
• Sales and lead-qualification bots on marketing sites.
• AI voice agents answering phone calls — voice is the highest-risk channel, because callers naturally assume a human.
• In-app AI assistants that converse with end users (as opposed to purely showing generated text in an editor).
• WhatsApp / Messenger / Telegram bots operated by your business for EU users.

Where the “obvious” exemption realistically applies

The exemption is judged from the standpoint of a reasonably well-informed, observant and circumspect person, in the specific context of use. Cases with a decent argument:

• A product literally named and branded as an AI assistant, where every surface says so (e.g. the user opened “ChatGPT”).
• Developer tools where invoking the model is the explicit action (an API playground, a code-completion pane).

Cases that fail the exemption more often than teams expect: a support widget labelled only “Chat with us”, a voice line with a human-sounding greeting, a bot with a human name and avatar. If you rely on the exemption, write down why it is obvious — under Article 99(4)(g) the transparency tier carries fines up to €15M or 3% of worldwide turnover (see our penalties guide).

Provider vs deployer: whose job is it?

Article 50(1) is a provider duty: the disclosure must be designed into the system. If you build a chatbot product for other businesses, you must ship the disclosure capability. If you are a SaaS company that deploys a third-party bot on your site, you still have skin in the game: under Article 2 the Act reaches deployers in the EU and, for third-country actors, situations where the output is used in the EU (see does the AI Act apply to non-EU companies?). Verify your vendor's disclosure actually renders, and cover the gap contractually.

What a compliant disclosure looks like

Article 50(5) sets three tests:

• Clear and distinguishable — not buried in a terms page.
• At the latest at first interaction — shown before or as the conversation starts.
• Accessible — conforming to applicable accessibility requirements.

Concretely, for a chat widget:

• A persistent line in the chat header or the first system message: “You are chatting with an AI assistant.”
• For voice agents: a spoken disclosure in the greeting.
• Don't undo it with design: a human name, photo-realistic avatar and “typing…” indicator can make a written disclosure misleading in context.

Edge cases teams ask about

Human-in-the-loop / hybrid support

If the AI answers first and humans take over, disclose the AI part. Best practice is also to signal the handover (“You are now talking to a human agent”) so the disclosure stays truthful.

Internal-only bots

Article 50(1) protects natural persons interacting with the system — it does not carve out employees. If staff might not know the tool is AI, disclose. In practice this is a one-line banner; the cost of arguing the exemption is higher.

RAG / search bots that only quote documents

Retrieval does not change the analysis: the conversational interface is still an AI system interacting with a person.

Do this before 2 August 2026

1. Inventory every conversational surface (web chat, voice, messaging apps, in-product).
2. For each, decide: disclose, or document a written case for the “obvious” exemption.
3. Add the disclosure at first interaction and check it against Article 50(5)'s three tests.
4. Work through the rest of the Article 50 compliance checklist — chatbots are usually only one of your exposure points.