call recording consent beep never played - the agent recorded 30 calls in a two-party consent state

TL;DR

Gate every recording on a played consent notice: the agent must play the disclosure beep or announcement and confirm it played before the recorder starts, with the rule varying by the lead's jurisdiction. When in doubt, treat the stricter rule as the default - unconsented recordings are a legal problem, not a data problem.

call recording consent beep never played  -  the agent recorded 30 calls in a two-party consent state

Steps

1. Map the consent rules you operate under: which states and countries require all-party consent, and what disclosure each requires (beep, announcement, or both). Expected: a written jurisdiction map exists, owned by legal, that the dialer configuration references.

2. Make the consent notice a blocking precondition of recording: the dialer plays the beep or announcement first, logs that it played, and only then starts the recorder. Expected: the call log shows the notice event before the recording-start event on every recorded call.

3. Resolve the lead's jurisdiction from the phone number and CRM data before the call, and apply the stricter rule when the jurisdiction is unknown. Expected: unknown-jurisdiction calls get the all-party treatment by default, and the log shows which rule was applied.

4. Audit recent recordings for missing consent notices, quarantine the affected files, and get legal's guidance on retention and deletion. Expected: a list of affected recordings exists, they are access-restricted, and legal has signed off on next steps.

5. Test the notice audibly in staging - place test calls and confirm a human ear actually hears the beep or announcement, not just that a flag was set. Expected: test-call recordings contain the audible notice, verified by listening.

Use this when

• recordings start without a consent beep or announcement
• the agent records in all-party consent states with one-party handling
• consent logic is not tied to the lead's jurisdiction

Not for this skill when

• the consent notice played but transcription is wrong - see the transcription skill
• calls are not being recorded at all - that is a dialer configuration issue
• you need general call-recording best practices - this skill is specifically about consent gating

Variant phrasings

• consent beep never played before recording
• recorded calls in a two-party consent state without disclosure
• all-party consent not handled per jurisdiction
• recording started before the announcement finished

Why it happens

Recording gets wired as a global dialer setting - "record all calls" - while consent is a per-call, per-jurisdiction requirement. The two configurations live in different places, built by different people, and nobody connects them until the audit. The beep is a small feature with large legal weight, which is exactly why it gets skipped.

Edge cases

• This is legal territory: have counsel review the jurisdiction map and the disclosure wording - this skill covers the operational gating, not legal advice.
• Inbound calls to your own numbers have their own consent rules - cover both directions, not just outbound.
• The lead asks "are you recording this" mid-call - the agent should answer honestly and stop recording if asked, regardless of jurisdiction.
• Quarantined recordings must actually be inaccessible - check backups and analytics pipelines, not just the primary store.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_LOHpkfY8ZB96p8nklQdyYQ