Do we have to tell callers they are talking to AI?
Requirements vary by state and are changing, so confirm your specific obligations with counsel — that goes for AI disclosure and for call recording consent, which is a separate rule set. Practically, disclose anyway. A short, matter-of-fact statement up front costs very little, prevents the worst customer reaction, and removes the ugliest failure mode of all: an agent that denies being AI when a caller asks directly.
Two different legal questions
People conflate them, and they are separate. One is whether you must tell someone they are interacting with an automated system. The other is whether and how you may record the call. Both vary by jurisdiction, both have seen recent legislative activity, and both can apply to the same phone call at once.
Recording consent rules in particular differ on whether one party or all parties must consent, and multi-state operators end up with the strictest applicable rule in practice. None of this is legal advice — have counsel review your specific footprint and greeting language before you deploy.
The practical case for disclosing
Set the law aside for a moment. Undisclosed automation creates a specific, avoidable harm: the caller finds out mid-conversation, feels deceived, and the interaction is over regardless of how well the agent was performing.
Disclosure moves that discovery to the front, where it costs almost nothing. Most callers do not care, some appreciate the honesty, and a small number ask for a person — which they were going to do anyway, just later and angrier.
How to word it without killing the call
- Short and early. One clause in the greeting, not a paragraph of legal text.
- Plain language. An automated assistant that can book appointments. Not virtual agent powered by proprietary conversational intelligence.
- Paired with the exit. Say a person is available in the same breath. That single addition does more for caller sentiment than anything else in the script.
- Never deny it. If a caller asks directly, the answer is yes, immediately, with an offer to transfer. Hard-code that response rather than leaving it to the model.
Where disclosure interacts with your data
If you are recording and analyzing calls — which is the point of call intelligence — your notice needs to cover that too, and your retention policy should be written down rather than inherited from whatever the vendor defaults to. Decide how long transcripts live, who can access them, and what happens on a deletion request.
None of that is exotic. It is the same governance any system holding customer conversations needs, and it is worth settling before launch rather than after a complaint. We treat it as part of the integration design, not an afterthought.
Topics: disclosure · consent · compliance · trust
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.