Customer-Support Chatbots and the EU AI Act: What You Actually Need to Do
Most customer-support chatbots are limited-risk under the EU AI Act. Your core duty is Article 50(1) AI disclosure — applies from 2 August 2026.
A customer-support chatbot is, in most cases, a limited-risk AI system under Regulation (EU) 2024/1689. Its primary obligation is transparency: under Article 50(1), the provider must ensure that users know they are interacting with an AI system, unless that is obvious to a reasonably well-informed person. There is no conformity assessment, no Annex IV technical documentation file, and no CE marking for a standard support bot. These limited-risk transparency duties apply from 2 August 2026.
That is the short answer. The longer answer depends on what the chatbot actually does — and a chatbot that starts making or influencing consequential decisions about people can cross into high-risk territory entirely by virtue of its function, not its form.
Is a customer-support chatbot high-risk under the EU AI Act?
No — not by default. The EU AI Act classifies AI systems by what they do and the context in which they do it, not by the technology stack. A bot that handles FAQs, routes tickets, and helps users reset passwords is a limited-risk system under Article 50. It does not appear on the Annex III list of high-risk use cases, so the full high-risk obligation stack — the risk management system (Article 9), technical documentation (Article 11), human oversight requirements (Article 14), and the Article 43 conformity assessment — does not apply.
The classification follows Article 6(3): even a system that sits within an Annex III category is not high-risk if it does not pose a significant risk of harm to health, safety, or fundamental rights. A narrow procedural task — answering questions, escalating tickets, surfacing help articles — typically clears that filter.
But classification is always a function-first analysis. The question is not "Is this a chatbot?" but "What does this chatbot decide or influence?" If the answer extends into areas listed in Annex III, the system needs to be reassessed. For a more detailed walkthrough of how to classify a chatbot against the risk tiers, see our guide to chatbot AI Act classification.
Your core obligation: Article 50 transparency
Article 50(1) of Regulation (EU) 2024/1689 requires the provider of a chatbot — any AI system designed to interact with natural persons — to ensure that those persons are informed they are interacting with an AI system. The disclosure must be made at the latest at the start of the interaction.
The regulation carves out a sensible exception: disclosure is not required where it is obvious to a reasonably well-informed, observant, and circumspect natural person that they are interacting with an AI system. A bot with a name like "AutoBot" that opens every session with a scripted greeting and cannot carry context between sessions might fall within this exception — but if there is any realistic chance a user could believe they are talking to a human, the exception does not apply. In practice, the safest approach is to disclose.
These obligations apply from 2 August 2026. That date was not touched by the Digital Omnibus (the Commission proposal of November 2025, agreed politically in May 2026, which deferred the high-risk Annex III deadline to 2 December 2027). Article 50 limited-risk transparency remains on its original timeline.
Non-compliance with Article 50 falls within the €15,000,000 or 3% of total worldwide annual turnover tier (Article 99(4)), whichever is higher. For companies that qualify as SMEs or start-ups, Article 99(6) caps the fine at the lower of the percentage or the fixed amount.
For a full analysis of the Article 50 obligations, see EU AI Act Article 50: transparency and disclosure.
When a chatbot tips into high-risk
The limited-risk default holds only as long as the chatbot stays in an informational or conversational role. A chatbot that moves from answering questions to shaping consequential outcomes for individuals crosses into different territory.
Consider a few scenarios. A chatbot that determines whether a customer qualifies for a financial product — or materially influences that determination — is operating in the creditworthiness and credit-scoring space covered by Annex III, point 5(b). A chatbot that filters which job applicants advance to a human reviewer, or screens candidates based on their answers, touches the employment and worker-management area in Annex III, point 4. A chatbot that controls access to essential services — healthcare triage, public-benefit eligibility, emergency routing — sits in Annex III, point 5 more broadly.
In any of these cases, the system is not "a chatbot" for classification purposes. It is an AI system that performs a high-risk function, and the full Article 6 and Annex III framework applies: risk management (Article 9), data governance (Article 10), technical documentation (Article 11 and Annex IV), logging (Article 12), transparency to deployers (Article 13), human oversight (Article 14), accuracy and robustness requirements (Article 15), and conformity assessment (Article 43) before the system goes to market. The applicable deadline for stand-alone Annex III systems under the Digital Omnibus agreement is 2 December 2027.
One addition worth noting: any AI system that profiles natural persons is always high-risk under Article 6(3), regardless of how narrow the surrounding task appears. A chatbot that builds or uses a behavioural profile of the user it is speaking to does not qualify for the limited-risk default.
For a structured checklist of what triggers the high-risk stack, see Is my AI system high-risk? and Annex III: the high-risk use-case list.
If it runs on a foundation model
Many customer-support chatbots are built on or via a general-purpose AI (GPAI) model — a large language model accessed through an API. The EU AI Act addresses this layered architecture explicitly.
The GPAI model itself is subject to Chapter V of the regulation (Articles 51–55). Those obligations — technical documentation, downstream information, copyright policy, training-data summary — stay with the model provider: the company that developed and made the model available. If the model is classified as systemic-risk under Article 51 (based on training compute or Commission designation), the model provider carries the additional obligations in Article 55: model evaluations, adversarial testing, incident reporting, and cybersecurity measures.
Your position is different. You are deploying a system built on top of that model. Your obligations are determined by what your deployed system does — its function, its users, its effects — under Articles 5, 6, and 50. The GPAI obligations at the model layer do not transfer to you. What does transfer is the Article 25 logic: if you substantially modify the model or put your name on a high-risk system built from it, you take on provider obligations (Article 16) for that system.
For most customer-support chatbot deployments using a third-party API, the classification analysis is clean: you are the provider (or the deployer, depending on the contractual structure) of the chatbot system, not the GPAI model underneath it. Classify your system by its function and apply the appropriate tier accordingly.
What to do
The practical steps for a typical customer-support chatbot are short. None of them require months of preparation.
Add an Article 50 AI disclosure. The disclosure should be visible and unambiguous at the start of the interaction. A sentence — "You're chatting with an automated assistant, not a human agent" — satisfies the requirement for most deployments. Build this into your chatbot flow before 2 August 2026.
Screen for Article 5 prohibitions. Article 5 prohibitions have applied since 2 February 2025. A support chatbot should not use manipulative techniques that exploit psychological vulnerabilities, should not deceive users in ways that cause or are likely to cause harm, and should not engage in prohibited social scoring. Review your bot's conversational design against these prohibitions — this is not a theoretical exercise if your bot is incentivised to up-sell or retain customers under pressure.
Train your staff under Article 4. AI literacy obligations under Article 4 have applied since 2 February 2025 and cover all organisations using AI, not just those with high-risk systems. Staff who configure, monitor, or make decisions alongside the chatbot should understand how it works, what it can and cannot do, and when to escalate to a human.
Document your classification. Even for a limited-risk system, keeping a record of your classification analysis — why you concluded the system falls under Article 50 rather than Article 6 — is good practice. It demonstrates due diligence if a regulator or auditor asks.
Reassess if the scope changes. If the chatbot starts handling loan applications, filtering candidates, or deciding access to services, run the classification again. The limited-risk conclusion is conditional on the function staying conversational.
How Confir helps
Confir is a rule-based EU AI Act compliance tool for companies that need to classify AI systems, document that classification, and generate the supporting compliance materials — without hiring a consultant or spending months on a framework.
For a customer-support chatbot, the workflow is straightforward: enter the system in the Confir registry, answer the plain-English classification questions, and Confir's deterministic logic maps the answers to the correct risk tier and role under the regulation. If the bot is limited-risk, Confir surfaces the Article 50 transparency obligations, flags the 2 August 2026 deadline, and supports the documentation of your Article 4 staff-training status. If a future scope change tips the system into an Annex III area, the classification updates and the full high-risk checklist becomes available.
The classification engine is rule-based and deterministic — same inputs produce the same output, the rule that fired is human-readable, and there is no inference to second-guess. That matters for a compliance artefact. Confir starts at €600 per year. Details at confir.eu.
Frequently Asked Questions
Does every chatbot need to comply with the EU AI Act?
Only chatbots that meet the definition of an AI system in Article 3 of Regulation (EU) 2024/1689 — a machine-based system that infers from inputs to generate outputs such as content, predictions, or decisions — are in scope. A simple rule-based scripted bot with no machine-learning or inference component may not qualify. Most modern chatbots built on large language models or intent-classification models do qualify. The Article 50 transparency duty for in-scope chatbots applies from 2 August 2026.
What exactly does the Article 50(1) disclosure require?
The provider must ensure that natural persons interacting with the AI system are informed that they are doing so. The disclosure must be made at the start of the interaction, at the latest. It does not require a specific format — a clear sentence at the top of the chat window is sufficient for most deployments. The exception is where it is already obvious to a reasonably well-informed person that they are talking to an AI system.
Can we use a cookie banner or terms of service to satisfy Article 50?
No. Article 50(1) requires disclosure at or before the interaction begins, in a way that is clear to the person engaging with the system. A reference buried in terms of service or shown only on a separate settings page does not satisfy the timing and clarity requirement. The disclosure needs to be present in the chatbot interface itself.
Our chatbot sometimes escalates to a human agent mid-session. Does that affect anything?
Not directly under Article 50, which governs AI-interaction disclosure. But the transition back to AI — if the session returns to the chatbot after a human step — should be equally clear. More significantly, if the chatbot is deciding which users escalate to a human and which do not, and that triage decision has meaningful consequences (e.g. for access to a service), that function needs to be assessed separately against Annex III. Triage that determines access to essential services can be high-risk.
We deploy a chatbot from a SaaS vendor. Who is the provider for Article 50 purposes?
The provider under the EU AI Act is the party that places the AI system on the market or puts it into service under its own name or trademark (Article 3(3)). If the vendor provides the underlying technology and you white-label or customise it for your customers, the analysis turns on who is presenting the system to end users and on whose authority it operates. Under Article 25, if you substantially modify the system or deploy it as your own product, you take on provider obligations. If you are simply running the vendor's system through their interface, you may be a deployer — but deployers still carry obligations under Article 26, including monitoring and ensuring that use aligns with the intended purpose.
What happens if we miss the 2 August 2026 Article 50 deadline?
Breaches of Article 50 fall under the €15,000,000 or 3% of total worldwide annual turnover tier under Article 99(4), whichever is higher. For SMEs and start-ups, the fine is the lower of the percentage or the fixed amount (Article 99(6)). Enforcement authority rests with the national market-surveillance authorities in the member states where the system is used.
Related guides
- Chatbot AI Act classification: how risk tier is determined
- EU AI Act Article 50: transparency and disclosure for limited-risk systems
- Limited-risk AI systems: what Article 50 requires
- How to classify any AI system under the EU AI Act
- Annex III: the eight high-risk use-case areas
- Is my AI system high-risk?
Manage your EU AI Act compliance in one place
Confir automates risk classification, technical documentation, and audit trails for any company. No consultants. No 6-month projects. 7-day free trial.
Start free trial →