Compliance

Consent and disclosure

The two consent lines an agent speaks before its greeting, and the checks that stop a switched-on disclosure from saying nothing.

Before its normal greeting on a call, the agent can speak two short consent lines in its own voice (see the opener in Voice and speech).

1  "This call is being recorded for quality and coaching purposes."   recording disclosure
2  "You're speaking with an AI assistant."                            AI disclosure
3  the agent's normal greeting

You can audition either line with the Preview button.

Each switch can follow the workspace default or be set on the agent, like the other controls on the Privacy page. The line itself is set on the agent. A new agent starts with both switches set to off on the agent.

Recording disclosure

The recording disclosure tells the caller the call is being recorded. Turn this on whenever you record call audio.

This is the line that matters legally. In two-party-consent jurisdictions (Western Australia, for example) recording a private conversation needs the caller's consent.

When the disclosure resolves to on, it is spoken first, ahead of the AI disclosure and the greeting.

Preset lines

Pick one of the presets or write your own. The presets are plain, one sentence each:

  • "This call is being recorded for quality and coaching purposes."
  • "Just so you know, this call may be recorded for training and quality."
  • "This call is being recorded."

AI disclosure

The AI disclosure tells the caller they are speaking with an AI assistant. This is best-practice rather than a legal requirement in Australia, and it is independent of recording.

It is spoken after the recording disclosure, before the greeting. Presets include lines like "You're speaking with an AI assistant."

Why an enabled-but-blank disclosure is blocked

A switched-on disclosure with no line blocks publishing

If you turn a disclosure on but leave its line empty, the agent would announce nothing: a silent consent failure. The editor rejects a save that switches a disclosure on with an empty line, and the readiness validator blocks publishing an agent whose own disclosure is on with no line.

Add the line the agent should speak, or switch the disclosure back off.

Three layers check this:

  • At save. The settings API rejects a request that switches a disclosure on with a blank line, whatever sent it.
  • At publish. The readiness validator raises a blocking error when the agent's own disclosure is on with no line. When the recording disclosure is on only through the workspace default and the agent has no line, it raises a risk you can acknowledge instead. See the publish gate in Agents.
  • At call time. The runtime speaks a disclosure only when it is both switched on and non-blank, and it never substitutes copy of its own.

An explicit "off" is honoured the same way, as a deliberate choice.

Risks you can acknowledge

On voice agents, the validator also flags three non-blocking risks:

  • recording is on but the recording disclosure is off
  • the disclosure is on but the agent does not store audio, so the spoken claim would be misleading
  • the workspace turns the recording disclosure on but this agent has no line

On this page