Workflow: Configure a Recorder Analytics Rule

Create a Recorder Analytics Rule for automatic enrollment Process in the IAFD product where an employee, customer, or target is registered and the system is then able to assist with identity verification and watch list detection when that speaker is on a call., identity verification Feature in voice biometrics where the speaker’s voice is compared to a collection of employee or customer voiceprints that should match the call. If a match occurs, the speaker is said to be verified., target detection Function of the IAFD product that compares a caller’s voice to one or more voiceprints in a watch list to detect if a target is participating in a call. for voice biometrics, real-time acoustic and linguistic events. As part of the Recorder Analytics Rule, configure Rule Settings, Call Selection, Engine Settings, Conditions, and Actions.

Required privileges

You must have these security privileges to view and configure Recorder Analytics Rules:

• Biometrics > View Biometrics - A user with this privilege Permissions associated with each role that define the features of the application a user is able to view and the functionality in the application the user can access. can view the Recorder Analytics Rules configuration screens, but cannot change them.

• Biometrics > View Biometrics > Configure Biometrics - A user with this privilege can create, edit, and delete Recorder Analytics Rules.

Workflow

Follow the workflow to configure a Recorder Analytics Rule.

1. Configure Rule Settings

   Define the name, engine type or types to associate with the Recorder Analytics Rule, and enable the rule to activate it.

2. Configure Call Selection

   Define if the Recorder Analytics Rule analyzes real-time interactions or historical interactions.

3. Configure Engine Settings

   Configure settings for each of the engine types selected for the Recorder Analytics Rule. Engine settings are not required for the Metadata Detection engine.

4. Configure Conditions

   Configure the conditions that must match for the Recorder Analytics Rule to trigger the actions configured for the rule. If you have selected more than one engine type for the rule, you must configure conditions for each engine type.

5. Configure Actions

   Configure the actions to trigger for the Recorder Analytics Rule when the conditions configured for the rule are met, and the action frequency. You can configure single or multiple actions for the same rule. To assign the interactions to a folder, to tag attributes, or send notifications, you must predefine folders, custom data attributes, and the notification settings