Qualified and the EU AI Act: does your chat widget tell people it's AI?
Qualified's Piper is an AI SDR: it greets website visitors, qualifies them and books meetings, in chat and voice. The product ships a library of human avatars and voices, a configurable human name and title, and its own materials describe AI-signature disclosure in email as 'optional'. That posture was defensible before August 2026. For EU visitors it inverts: an AI agent with a human face, a human name, a voice and a sales quota is the least 'obvious from context' AI on your site, which makes the explicit first-interaction disclosure do all of the Article 50(1) work.
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 open your site and start a chat.
Where the disclosure lives in Qualified
- The messenger frame (#q-messenger-frame), bubble and panel states of the website experience
- Piper's persona: name, title, avatar (or voice 'orb') configured in Agent Studio
- The first message or spoken greeting a visitor gets, chat and voice both count as first interaction
- Outbound email signatures when PiperX sends 'on behalf of' your reps
Your Qualified 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?
- In Agent Studio, review Piper's persona: a human name + human-photo avatar + no AI title means the disclosure must be carried explicitly by the greeting text
- Consider the 'orb' (non-human avatar) option for EU-facing experiences, it keeps the experience on-brand without impersonating a person
- If you use Piper's voice mode, script the AI disclosure into the spoken greeting, voice interactions are squarely inside Art. 50(1)
- Check email sends: 'on behalf of your reps' framing presents AI output as a named human's message, for EU recipients, keep the AI-agent signature on
- Screenshot the first-interaction state (and record a voice greeting) with a date, and export the persona config
Watch out for
By default Qualified ships human avatars, human names, human titles and email that can send as your reps. Their own FAQ frames AI disclosure as optional. For EU traffic after 2 August 2026 the safe reading is the opposite: the more human Piper looks and sounds, the more explicit and early your AI notice has to be.
Common questions
Qualified says disclosure is optional, who's right?
Their FAQ addresses GDPR, and on that narrow point they're broadly correct, GDPR doesn't mandate an AI signature. Article 50(1) of the AI Act is a different law with a different rule: from 2 August 2026, people interacting with an AI system must be informed unless it's obvious from context. An AI SDR presenting as a human rep is the opposite of obvious.
Does the voice experience change our duties?
It raises the bar. A synthetic voice that answers like a person is exactly the interaction pattern Art. 50(1) targets, and 'the visitor could have guessed' is a weak position when the product's pitch is that Piper feels human. Script the disclosure into the first spoken exchange and keep a dated recording as evidence.