Drift and the EU AI Act: does your chat widget tell people it's AI?
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.
Where the disclosure lives in Drift
In a typical Drift setup, the surfaces that can carry (or fail to carry) the AI disclosure are:
- The chat bubble and proactive greeting messages fired by playbooks on key pages
- The bot participant's name and avatar inside the conversation
- Playbook opening scripts — the qualifying questions a visitor answers before routing
- The routing moment where a live sales rep takes over from the bot
Your Drift disclosure checklist
- Run through your highest-traffic playbook as a visitor: is the AI/bot nature stated before qualification questions begin?
- Audit bot personas across playbooks — human first names with headshot-style avatars need an explicit AI label
- Add the disclosure to the proactive greeting itself, since many visitors read it before engaging
- Check meeting-booking flows where the bot negotiates calendars on a rep's behalf
- Make the human-takeover moment explicit in the thread when a rep joins
- Archive playbook configurations and greeting screenshots whenever marketing edits them
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.
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