Dependency on Identification Rules
It is vital to understand that the field names defined in Risk Management, under Configure in the Fields area, share a dependency with the attributes used in Identification Rules.
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 during employee creation in Risk Management.
Identification rules for automatic enrollment 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 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.