The European Commission's August 2026 transparency explanation says people should be clearly informed when they are interacting with an AI system rather than a real person. For teams building customer experiences, the difficult part is not writing the sentence. It is delivering it at the right moment in every supported channel.
Place the notice in the interaction
Review what a first-time visitor sees before sending a message. A chatbot's name, avatar, and introduction should not imply a human representative if the interaction is automated. For voice experiences, evaluate the opening audio, not only a web page that the caller may never visit.
The legal assessment should account for applicable conditions and exceptions. Do not assume one generic wording satisfies every deployment.
Keep escalation understandable
Explain when a person can take over and whether the system can make decisions or only provide information. If escalation is unavailable outside service hours, say so accurately. A misleading promise of immediate human support can undermine an otherwise clear AI disclosure.
Test more than the default desktop view
Check mobile screens, translated interfaces, returning sessions, embedded installations, and accessibility modes. Ensure dismissing an unrelated cookie banner does not hide the only meaningful AI notice.
Keep dated evidence of the user experience and assign an owner to recheck it when branding or widgets change. Legal text, product behavior, and customer expectations need to remain aligned. A visible disclosure does not solve every governance issue, but it gives users a clearer basis for deciding what to share and how much to rely on the response.
Sources & further reading
Reviewed October 26, 2026. Product availability and regulatory guidance can change. Vendor performance claims are not independent Rovio AI benchmarks.
Found this useful? Share it.