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. 

Optional rule conditions

Defining Recorder Analytics Rule conditions is optional. Without conditions, rule actions trigger according to the action frequency for every recording that matches the Call Selection criteria. For example, to track how many interactions the Real-time Linguistics (remote) Engine processes, you could define a rule with no conditions but with an action to track processing.

Required role privileges

  • Enterprise Manager > Analytics Rules > View Analytics Rules - Users can view a Recorder Analytics Rule but cannot make changes.

  • Enterprise Manager > Analytics Rules > View Analytics Rules > Edit Analytics Rules - Users can create, edit, and delete a Recorder Analytics Rule.

Security privileges are assigned to users from the User Management Module that an administrator uses to create a profile for each employee in their organization. options of the enterprise portal Home page or main UI access point for all WFO applications..

Workflow 

To configure a Recorder Analytics Rule, follow the workflow .

  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. Optional: Configure Conditions

    Configure the optional conditions to match for the Recorder Analytics Rule. If you define conditions, the conditions must match before any rule actions trigger. If you omit conditions and define actions, the rule triggers for every recording that matches the Call Selection criteria selected for the rule. If you have selected more than one engine type for the rule, configure conditions for each engine type.

  5. Configure Actions

    Configure the actions to trigger for the Recorder Analytics Rule and the action frequency. If you omit conditions for the rule, the actions trigger for every recording that matches the Call Selection criteria. 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.