Dependency on Identification Rules

It is vital to understand that the field names defined in 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., under Configure in the Fields area, share a dependency with the attributes used in Identification Rules.

The property names of the fields you define here must exactly match the CTI attributes used by Identification Rules. To learn how Identification Rules work, see the related topics section that follows.

Identification rules for employees

For an employee Identification Rule, you always use the Employee Name. The Employee Name in the Identification Rules user interface refers to the unique employee ID. The Employee Name field used by Identification Rules is not configurable. The Employee Name maps directly to an employee selected from the organizational hierarchy Hierarchy set up by administrators (via the EM) that is structured according to the managerial and employee hierarchy in the company. during employee creation in Risk Management.

Identification rules 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. of customers

If you use multiple Identification Rules for customers, take care not to use different fields or field combinations for Identification Rules used for automatic enrollment. If you use different fields or field combinations for automatic enrollment of customers, you risk the creation of more than one voiceprint File containing a mathematical summary of the vocal patterns of a person’s voice used in the IAFD product to assist with identity verification and detection. model per customer.

Example: First customer Identification Rule based on ANI and second customer Identification Rule based on a custom attribute with the account number

If the customer uses multiple telephone numbers, and you have automatic enrollment configured, the result is multiple voiceprint models for one customer. Use of a single identification rule for all customers avoids this issue.

Create Identification Rules (Enterprise Manager Configuration and Administration Guide)