EU AI Act · Article 50(1) · Chat widgets

Intercom and the EU AI Act: does your chat widget tell people it's AI?

Applies from 2 Aug 2026Fines up to €15M / 3% turnoverLast reviewed July 2026

Intercom's Fin is one of the most widely deployed AI agents in customer support, and it usually answers first — before any human teammate is involved. That makes the very first message in your Messenger the moment Article 50(1) cares about: if a visitor in the EU can start chatting without being told they're talking to AI, the gap is on your site, in production, visible to anyone who opens the widget.

The rule itself is short. Article 50(1) of the EU AI Act requires AI systems that interact directly with people to be designed so users know they're dealing with AI — no later than the first interaction, in a clear and distinguishable way. The exception for cases where it's "obvious" is narrow: a natural-language customer-service bot doesn't qualify just because it has a robot icon. A line in your terms of service doesn't satisfy it either. And it's easy to enforce, because a regulator can simply open your site and start a chat.

Who's on the hook? Responsibility is split: Intercom carries provider-side duties for the system itself, but how the widget is configured and presented on your site is your deployment. If the disclosure setting exists and isn't enabled — or the notice is hidden — that gap is yours.

Where the disclosure lives in Intercom

In a typical Intercom setup, the surfaces that can carry (or fail to carry) the AI disclosure are:

The Messenger launcher and home screen — the entry point a visitor sees before any conversation starts
Fin's identity block: its name, avatar, and the "AI Agent" descriptor shown in the conversation header
Fin's opening message — the first thing sent when a conversation begins
Handover moments — where Fin passes the thread to a human teammate and the participant changes

Your Intercom disclosure checklist

Open your site in a private window as an EU visitor and start a chat: is it explicit you're talking to AI before or in the very first exchange?
Check Fin's identity settings — keep the AI descriptor visible and don't rename Fin to a human-sounding persona without an AI label
Put an explicit line in the opening message (e.g. "I'm Fin, an AI agent — I can bring in a human anytime") rather than relying on an icon
Verify the disclosure survives on mobile and in the compact Messenger view, not just desktop
Check the human-handover message makes the participant change clear in both directions
Screenshot the first-interaction state and save your Messenger/Fin settings export with a date

Keep proof. On a complaint, an authority will want to see that the disclosure was there and how it was designed. Keep timestamped screenshots of the first-interaction state, your widget configuration, and a record of when each was last changed — that evidence file is the difference between "we comply" and "we can show we complied."

Watch out for

The classic Intercom failure mode is cosmetic humanization: Fin renamed to a teammate-style persona with a human avatar, answering instantly with natural language. Each choice is individually reasonable; together they make the AI nature non-obvious, which is exactly what strips you of the 'obvious from context' exception. The second one is drift — Fin ships new capabilities and settings frequently, and a Messenger update or workspace migration can quietly change what visitors see first.

Note: vendor interfaces and setting names change. This page describes where disclosure surfaces typically live in Intercom as of July 2026 — verify the exact toggles in your own Intercom workspace and against Intercom's current documentation.

Common questions

Fin already has an AI label in the header — is that enough?

A persistent label helps, but the safer pattern is layered: keep the header descriptor and add an explicit statement in the first message. Regulators have signaled that disclosure must be clear and distinguishable at first interaction, and a small header tag alone is a judgment call you don't need to gamble on.

We only use Fin for some conversations — do we still need disclosure?

Yes, wherever AI is the one interacting. Mixed routing raises the bar: if visitors can't tell which conversations are AI-led, disclose at the start of any thread Fin participates in and mark handovers clearly.

Check it in one scan.

DisclosureProof opens your site the way a regulator would, triggers your Intercom widget, and records whether the AI disclosure actually appears — with timestamped evidence either way. Free scan at launch.

Join the launch list