Skills Compliance
Call recording governance
Recordings are the highest-risk data a support operation holds and the least governed, because they usually live in the telephony system rather than the helpdesk — owned by a different team, with its own retention, its own access model, and frequently outside every review that covers "support data".
npx rulebase-skills install cx-call-recording-governanceWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “review our call recording practices”
- “do we need to tell customers we're recording”
- “who can listen to our calls”
How it works
The method, in the order the skill runs it. The full procedure — tables, worked examples and the edge cases — is in the skill itself.
What is on the recording that should not be
Callers say things nobody intended to capture: Health information and vulnerability disclosures, volunteered, Third parties in the background, Other customers, where an agent is on a shared floor, The agent's own personal information, in an aside.
Access
Recordings get listened to by more people than anyone expects: Enumerate who can access them, Vendor access, including from other countries.
Customer requests for their own recording
A recurring, awkward request.
Related skills
Free and open source, and vendor-neutral — it reads the conversations from whichever helpdesk you already run. Browse all 149 skills · connect your helpdesk over MCP · source on GitHub
