Compliance disclosure made identifies interactions where the agent communicated required regulatory or legal disclosures such as privacy notices, recording notifications, fee explanations, terms acknowledgments, or other mandated statements. This signal captures when required disclosures actually occurred, not whether they were done perfectly.
The signal recognizes various disclosure types across different regulatory contexts: financial services fee disclosures, healthcare privacy notices, debt collection Mini-Miranda warnings, telemarketing compliance statements, or insurance terms explanations. What matters is that legally required information was communicated during the appropriate interaction type.
Missing required disclosures creates legal and regulatory risk that compounds over time. Unlike process violations that affect individual customers, disclosure failures can trigger regulatory investigations, fines, and legal liability that affects the entire organization.
Regulatory compliance cannot rely on sampling-based QA when disclosure requirements apply to every applicable interaction. A 95% compliance rate with required disclosures means 5% of interactions create potential regulatory exposure — and regulators typically evaluate 100% of interactions they review, not representative samples.
Compliance teams need automated disclosure tracking because manual detection is unreliable at scale. Agents may skip disclosures under time pressure, forget them during complex interactions, or assume another team already covered them. Without systematic monitoring, disclosure gaps are invisible until regulators find them.
Compass evaluates whether required disclosure content was communicated during the interaction, recognizing both scripted language and natural paraphrasing that conveys the same regulatory information. The signal accounts for context — disclosures required in collections calls are different from those in sales interactions.
The detection focuses on substance over format. An agent who explains fee structures in their own words may satisfy disclosure requirements even if they did not read the exact scripted language, provided the required information was clearly communicated to the customer.
Compliance officers use disclosure tracking to monitor regulatory adherence across all applicable interactions. They can identify which teams, shifts, or interaction types show disclosure gaps and implement targeted remediation before regulatory issues develop.
Legal teams rely on disclosure data for regulatory reporting and audit preparation. When regulators request evidence of compliance procedures, systematic disclosure tracking provides documentation that goes beyond policies and training records to show actual performance.
Training teams focus coaching efforts on agents and scenarios where disclosures are consistently missed. Rather than general compliance training, they can target specific disclosure types and contexts where gaps appear in the data.
This signal is part of Chordia’s Compliance Monitoring capabilities.
We'll walk you through real interactions and show how each signal traces back to specific conversational evidence — so your team can act on what actually happened.
