Bot disclosure
Bot disclosure is a clear notice that tells a caller they are interacting with an automated or AI system rather than a human.
A disclosure helps the person understand who—or what—is participating before they share information or make decisions. Depending on the jurisdiction, industry, call direction, and purpose, disclosure may be required by law, contract, or organizational policy. Even when the exact wording is not prescribed, it should be understandable when spoken once at normal speed.
The notice should appear early enough to inform the interaction, typically near the beginning of the call and before the agent requests sensitive information. Plain wording such as “I’m an automated phone agent” is more direct than a brand name or a vague reference to an “assistant.” The script should not imply that a bot is human through a fabricated job title, biography, or personal experience.
How it works in a call flow
Disclosure is a conversation requirement, not just a line added to a prompt. The call flow should define when the notice plays, whether it must be repeated after a transfer or when a new participant joins, and what the agent does if the person asks whether it is automated. Responses should remain consistent throughout the call.
Teams should test the disclosure against interruptions and barge-in. If a caller speaks over the opening, the agent may need to finish or repeat the material part rather than assuming it was heard. Multilingual agents need an equivalent disclosure in the language being used; a translated phrase should remain direct and should not soften the meaning.
Separate notices serve separate purposes
Bot disclosure does not by itself authorize call recording, establish consent to receive marketing calls, or explain how personal data will be used. Those obligations can overlap in one call but should not be collapsed into an unclear sentence. A caller may agree to speak with an automated agent while declining recording, or accept a recorded support call without agreeing to future outreach.
The required content can change with the calling program, so organizations should document the jurisdictions and use cases they serve and obtain appropriate legal review. The operating policy should also provide a path for questions or a human handoff when the workflow promises one. A clear disclosure sets an accurate expectation; it should not claim capabilities the agent does not have.