AI sales and lead-capture chatbots: disclosure, consent and handing leads to sales
What applies, in one table
| Part of the chat | Rule | What to do |
|---|---|---|
| The bot itself | AI Act Article 50(1) and (5) | Say it is an AI, at the latest at the first message |
| Asking for name, email, company | GDPR Articles 6 and 13 | Short notice in the chat, link to the privacy policy |
| "Can we email you about offers?" | ePrivacy Directive Article 13 | Separate opt-in, not pre-ticked |
| Chat widget cookies and identifiers | ePrivacy Directive Article 5(3) | Covered by the cookie banner unless strictly necessary |
| Claims about price, stock, discounts | Unfair Commercial Practices Directive | Answers from approved content only |
| Handing over to a sales rep | Article 50(1), GDPR | Tell the visitor a person is taking over |
The AI disclosure
A lead-capture bot interacts directly with visitors, so Article 50(1) applies to it like any support bot. The duty sits with the provider of the system (often the chatbot vendor, sometimes the agency that built or branded it; see does Article 50 apply to client chatbots). In practice the business running the landing page should check the wording itself.
Sales bots raise two specific risks:
- Human personas. "Hi, I'm Sarah from the sales team" with a stock photo is the set-up Article 50 is aimed at. A named persona is fine if the first message also says it is an AI assistant.
- The "obvious" exception. Article 50(1) does not apply where it is obvious from the context that the visitor is talking to an AI. Sales bots are built to sound like a person, so don't rely on it.
Opening line that works on a landing page:
"Hi, I'm the AI assistant for Northgate. I can answer questions about plans and pricing, or book a call with someone from our team."
More wording options are in the disclosure wording guide.
Collecting the lead's details
A name, work email and phone number are personal data, including for B2B leads. The GDPR points that matter for a chat:
- Notice at the point of collection. Article 13 requires the information to be given when the data is obtained. A line before the bot asks for an email does this: "We'll use your details to reply to this request. Privacy policy: [link]." The full notice sits in the policy.
- Lawful basis. Replying to the visitor's own request (a demo, a quote) can usually rest on steps taken at the person's request before a contract (Article 6(1)(b)) or legitimate interests (Article 6(1)(f)). Adding them to marketing lists is a different purpose and needs its own basis.
- Transcripts. Chat logs often hold more than the form fields. Set a retention period and say in the policy that conversations are stored and who processes them (the chatbot vendor is usually a processor).
- Lead scoring. Scoring leads to decide who sales calls first is unlikely to be a decision with legal or similarly significant effects under Article 22. Scoring that decides who gets a credit offer or a price is a different matter; ask a lawyer.
The Article 50 and GDPR guide covers the general chatbot GDPR points.
Follow-up email: ask in the chat
Under Article 13 of the ePrivacy Directive, email for direct marketing to individuals needs their prior consent. The "soft opt-in" exception covers a business's own customers whose details were obtained in the context of a sale, for similar products. A lead who asked a bot a question has not bought anything, so in most cases the exception does not fit.
Rules for business addresses differ by country: Article 13(5) leaves member states to protect legal persons, and national laws went different ways. If leads come from several EU countries, the simple route is to ask everyone.
What that looks like in the chat:
"Would you like occasional emails about new features? [Yes, email me] [No thanks]"
Keep the answer to the visitor's request separate from the marketing yes or no, store the answer with a timestamp, and don't make the demo depend on saying yes.
What the bot is allowed to promise
Statements a chatbot makes on a business's site are treated as the business's statements. In Moffatt v. Air Canada (2024 BCCRT 149), a Canadian tribunal held the airline responsible for a refund policy its website chatbot had described wrongly (reported widely; not EU law, but the reasoning travels). In the EU, a bot that invents a discount, misstates a price or claims "only 2 left" without basis can be a misleading practice under the Unfair Commercial Practices Directive.
Practical limits:
- Price, plan and contract answers come from an approved source the bot quotes, not from the model's general knowledge.
- The bot does not offer discounts, trials or terms that sales has not approved.
- No false urgency or scarcity. Article 5(1)(a) of the AI Act also bans AI systems that use manipulative techniques to distort behaviour in a way that causes significant harm. Ordinary sales chat is far from that bar, but pressure tactics built into a bot move towards it.
Handing over to a sales rep
When a person takes over the chat, say so: "You're now chatting with Tom from our sales team." Visitors who were told they were talking to an AI should not have to guess when that stops being true. The reverse matters too: if the rep leaves and the bot comes back, the AI line goes back in.
If the chat is passed to a rep by email or CRM, the lead's details go only to the people who need them, and the transcript goes with the consent answer so sales knows whether marketing email is allowed.
Checklist for a lead-capture bot
- [ ] First message says it is an AI assistant, persona or not.
- [ ] One-line privacy notice before the bot asks for contact details.
- [ ] Marketing opt-in is a separate, unticked choice, stored with a timestamp.
- [ ] Price and terms answers come from approved content.
- [ ] No invented discounts, urgency or scarcity.
- [ ] Handover to a person, and back, is announced in the chat.
- [ ] Transcript retention period set and named in the privacy policy.
- [ ] Chat widget cookies covered by the consent banner where needed.
Sources
- Regulation (EU) 2024/1689 (AI Act) on EUR-Lex: Article 5(1)(a) and Article 50(1) and (5).
- Article 50 text and Article 5 text at artificialintelligenceact.eu.
- Regulation (EU) 2016/679 (GDPR) on EUR-Lex: Articles 6, 13 and 22.
- Directive 2002/58/EC (ePrivacy Directive) on EUR-Lex, as amended: Articles 5(3) and 13.
- Directive 2005/29/EC (Unfair Commercial Practices Directive) on EUR-Lex.
- Moffatt v. Air Canada, 2024 BCCRT 149, Civil Resolution Tribunal of British Columbia, reported.