Compliance capture in the contact center

Organizations capture interactions for compliance or regulatory purposes. Reasons for compliance capture include ethical compliance, contractual compliance, corporate liability, consumer protection, and interaction In Speech Analytics, an interaction represents a single part of the contact between one employee and the same customer. In Text Analytics, an interaction is the communication session between one or more employees and the same customer with a unifying contextual element. analysis.

Administrators and compliance officers use Risk Management Component of the Real-Time Analytics (RTA) Framework that provides interaction search and replay functionality, combined with integration of the Real-Time Analytics (RTA) Framework. to review and analyze the captured interactions for compliance, non-compliance, and to service compliance requests.

Example: Compliance review

The organization receives a complaint about non-compliant sales of financial products by a specific team. The administrators or compliance officers search for specific interactions associated with the team. After organizing and grouping the interactions into a case, compliance officers review the captured interactions for evidence of non-compliance.

Other compliance requests

Other types of compliance requests can be handled in Risk Management:

Project Rules Manager Component that allows you to define rules, according to which the system performs specific actions.

Use complementary products within the suite to manage compliance requests. The Project Instance of the Speech and Text Analytics application that supports a different language or Line of Business (LOB). Rules Manager enables you to:

  • Populate cases, legal holdcases, and recycle bins in bulk

  • Export interactions in bulk

  • Delete captured interactions

Immutable storage (Verint® Cloud Capture Configuration Guide)