AI Meeting Disclosure: What to Tell People

If you deploy an AI Employee into a meeting, the first question most people ask is: do I have to tell anyone?

The short answer is yes. And in many cases, you are legally required to.

But disclosure is not just a legal obligation. It is also the right approach, and for most teams, it helps rather than hurts.

Here is a practical guide to what you need to say, who you need to tell, and when.

Why disclosure matters

AI Employees are visible participants. They join meetings with a name and a role. So in most cases, the people in the meeting already know something is there. The question is whether they understand what it is and why it is in the room.

Clear disclosure does three things. It sets accurate expectations. It prevents the awkward moment when someone notices the participant list and asks who that is. And it builds the kind of trust that makes AI-assisted meetings more productive, not more tense.

Trying to hide an AI participant is also bad strategy. It creates suspicion that disclosure prevents. And in many jurisdictions, recording a conversation without consent is not just uncomfortable. It is illegal.

Who you need to tell

External participants: clients, candidates, prospects

Tell them before the meeting starts. A single sentence in the invite or at the opening of the call is enough. You do not need to write a legal paragraph. Confirm that an AI Employee will be present, explain its role, and make space for questions.

Internal participants: your own team

If the AI Employee is attending an internal sync, a brief note to the team before the first session is sufficient. After that, the AI Employee's presence in the participant list is self-explanatory.

Interview candidates

This is one of the most important disclosure moments. Candidates who discover mid-interview that an AI Employee was present, and were not told, will have a negative experience. In some regions, you may also have a legal problem. Tell candidates upfront, in writing, as part of the interview confirmation.

Clients on regulated calls

If you operate in financial services, legal, healthcare, or any regulated industry, check your obligations before deploying an AI Employee on client calls. Requirements vary by jurisdiction. When in doubt, get explicit written consent before the meeting.

What clients actually notice

Most clients notice the AI Employee once, ask what it does, and move on. A single sentence of context, "that is our operations assistant; it logs decisions and follow-ups", is usually enough for the meeting to continue normally.

Some clients will ask follow-up questions about recording, data handling, or who receives the output. Those questions are reasonable. They are easier to answer when the AI Employee is visible by design than when someone discovers tooling after the fact.

What prospects actually do when they see it

Most prospects acknowledge the AI Employee and move on. A brief explanation from the rep, "that's our AI sales assistant, it helps with follow-up and deal notes", is usually enough. The call continues.

Some prospects ask a follow-up question. "Will this be recorded?" or "What does it do with the information?" Those are reasonable questions. They are easy to answer honestly.

A small number of prospects will have a strong preference against AI participation. That is a legitimate response. And it is far better to know that upfront than to have them discover a hidden tool after the fact and lose the deal on trust grounds.

What to actually say

For an external call:

"I want to let you know that I use an AI Employee to help manage follow-up and structured notes from this call. It will join as [AI Employee name] in the participant list. Is that okay with you?"

For an interview:

"This screening includes an AI assistant called Rx · Recruiting. It asks structured questions and captures your responses so we can evaluate candidates consistently. Do you have any questions before we start?"

For an internal meeting:

"Starting this week, our recurring [meeting name] will include an AI Employee. It handles notes and structured output so we can focus on the discussion. Let me know if you have questions about how it works."

These are short statements. They are not legal documents. They treat the other person like an adult, which is exactly the right tone.

When disclosure is legally required

Two-party and all-party consent laws govern recording in many US states and across the EU. California, Florida, and Illinois all require all-party consent for recorded conversations. The EU's GDPR applies to any personal data captured in a meeting, including voice.

If your AI Employee speaks as well as listens, which is one of its core capabilities, it is a participant in the conversation. Most jurisdictions treat that differently from silent transcription tools. But the underlying recording of the conversation still triggers consent requirements in many places.

This is not legal advice. The practical rule is: when in doubt, disclose. The downside of disclosing too much is minimal. The downside of under-disclosing can be significant.

How DelegateWorker handles this by design

DelegateWorker AI Employees are transparent by default. They join meetings as named AI participants. They do not join covertly, impersonate humans, or hide their presence.

That design choice is intentional. Visible participation builds more trust than invisible recording. Participants know the AI Employee is there. They know its role. That clarity makes the meeting more productive, not less.

For situations where you need to manage disclosure carefully, such as regulated industries, candidate interviews, or sensitive client calls, prepare your disclosure statement before the first session. One paragraph, sent in advance, handles most scenarios cleanly.

The bottom line

Disclose before the meeting. Keep it short. Focus on what the AI Employee does, not on the technology behind it. And in regulated environments, check your legal obligations before deploying.

Transparency is not a liability in AI-assisted meetings. It is a design feature. The teams that approach this openly tend to get better outcomes than the ones that try to minimize the AI Employee's presence.

→ Learn how DelegateWorker handles transparency. Use cases: Zoom meetings