Many enterprises have treated the EU AI Act as a problem for another day. But their procrastination could be about to become costly.
On August 2, the EU AI Act’s transparency requirements under Article 50 begin to apply. While the most complex requirements for certain high-risk AI systems have been pushed back, customer-facing AI cannot be filed away under 'later.'
In a CX context, if a customer is talking to a chatbot, being assessed through emotion-recognition technology, or having their behavior analyzed by AI, organizations must be completely transparent about the process.
Indeed, in an exclusive interview with CX Today, Kristina Holt, Managing Associate at law firm Foot Anstey, explained this issue:
“You need to clearly identify that you're talking to an AI, and anything that sort of makes people think they're talking to a human being needs to be avoided.”
This ruling opens up difficult questions around chatbot design, speech analytics, third-party technology, agent assist, escalation routes, and the increasingly blurry line between a helpful automation and an intrusive one.
The EU AI Act Has Not Been Delayed, It Has Split
The recent EU AI Act changes have created a confusing picture for enterprises.
Yes, the deadline for standalone high-risk AI systems listed in Annex III has moved to December 2, 2027. These are systems used in areas such as recruitment, education, creditworthiness, access to essential services, and employment management.
Meanwhile, requirements for high-risk AI embedded in regulated products, including certain medical devices, vehicles, machinery, and toys, will apply from August 2, 2028.
But those postponements do not erase the August 2026 milestone.
According to the European Commission, Article 50 applies from August 2, bringing transparency obligations for providers and deployers of certain AI systems. These include interactive AI systems, generative AI, deepfakes, emotion recognition, and biometric categorization tools.
For direct customer interactions, providers must design AI systems so people are informed that they are interacting with AI, unless that is already obvious.
The notification should arrive at the first interaction and be clear and distinguishable. That puts customer service AI firmly in view, as Holt detailed:
“The thing around that is transparency. It's really important. So you need to clearly identify that you're talking to an AI.”
For many contact centers, this is not a new principle. Plenty of chatbots already announce themselves, while virtual assistants are often given names that make their non-human status reasonably clear.
Yet there is a large gap between “reasonably clear” and a consistent, auditable approach across every customer channel.
That gap is where trouble starts.
Why This Matters for Contact Centers
Most enterprise CX teams will be AI deployers rather than AI providers.
They are not training foundation models or building large language models from scratch. They are putting AI into the customer journey through contact-center platforms, chatbot vendors, CRM systems, speech-analytics tools, and agent-assist applications.
That distinction matters legally. But operationally, it should not become a loophole.
A third-party provider may carry obligations for how its system is built, but the enterprise using the tool still owns the relationship with the customer, the service design, and the consequences when something goes wrong.
Holt argues that “you can't get rid of your responsibility," and should only point to your third-party provider if "you are confident that they are in fact handling it.”
That means a contact center cannot simply assume that a vendor’s 'AI Act-ready' badge settles the issue.
Take a customer chatbot, for example. The enterprise needs to know whether the AI disclosure appears where the customer actually encounters the tool. It needs to know who controls the wording, how the system behaves after an escalation, and what happens if the chatbot gives an inaccurate, discriminatory, or nonsensical response.
As Holt said: “Who do they [the customer] think they're interacting with, and who has control over that conversation?”
Those are the questions that matter. Not the marketing claims in a vendor slide deck.
The Chatbot is the Easy Part
The obvious use case is a chatbot.
A customer lands on a support page, starts a conversation, and sees an introductory message telling them they are interacting with an AI assistant. That is the sort of transparency design many companies will now be reviewing ahead of the deadline.
But chatbots are only one part of the modern CX AI stack.
Contact centers are also using AI to summarize calls, recommend next-best actions, guide agents during live conversations, predict customer intent, classify contacts, and analyze voice and text for sentiment.
Some of those tools sit in the background. They do not always respond directly to the customer. That is where the legal and ethical lines become more complicated.
For example, a customer may not know that a system is analyzing their language, tone, or behavior to determine whether they are frustrated, vulnerable, likely to churn, or “in the mood to spend money,” as Holt described it.
“The more you're interfering and the more you're doing something that's intrusive, I guess, in that way of interacting, probably the more notice you need to give.”
That does not mean every use of AI behind the scenes automatically triggers the same Article 50 obligation as a customer-facing chatbot. The Commission’s guidance is specific about the systems and circumstances in scope.
However, organizations should not interpret that distinction as permission to be vague.
