T-minus … to EU AI Act Article 50 enforcement · 2 Aug 2026
EU AI Act · Article 50(1) · Chat widgets

Drift 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

Drift (now part of Salesloft) built its category on conversational marketing — bots that qualify buyers with a deliberately human, sales-rep tone before routing hot leads to real reps. That design goal sits in direct tension with Article 50(1): the more convincingly your Drift playbook imitates a human SDR, the less "obvious from context" the AI nature becomes, and the more you need an explicit disclosure.

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: Drift 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 Drift

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

Your Drift disclosure checklist

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

Drift's risk is structural, not accidental: the product's persuasive value comes from feeling like a person, and marketing teams tune personas toward exactly that. Every persona review should now ask one extra question — would a reasonable visitor know this is AI at message one? If the honest answer is no, the playbook needs a disclosure line more than it needs another A/B test.

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

Common questions

Won't an 'I'm an AI assistant' line hurt conversion?

Test it — teams that have report smaller effects than feared, and a visible disclosure at first interaction is dramatically cheaper than being the example an authority uses to define 'non-obvious.' You can disclose and still be charming.

Our playbooks route to humans fast — does the bot part still need disclosure?

Yes. The obligation attaches at first interaction with the AI, however brief. Fast routing actually makes clean handover labeling easier to implement.

Check it in one scan.

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

Join the launch list