Automatic enrollment
Automatic enrollment uses Recorder Analytics Rules to enter many people in voice biometrics.
During automatic enrollment, the Recorder Analytics Rule selects interactions, combined with a unique identifier, to create a record in the database for the person. The interaction is used to create the biometric voiceprint model for later verification of the person.
It is important to understand the following about automatic enrollment:
-
Targets cannot be enrolled automatically. Automatic enrollment applies only to employees and customers.
-
Do not use a single Recorder Analytics Rule to enroll both employees and customers. To use automatic enrollment for both types of people, create a separate Recorder Analytics Rule for each type of enrollment.
-
Always use historical interactions (campaign-based) for automatic enrollment. Do not attempt to use automatic enrollment with real-time interaction selection.
-
For employee and customer interaction selection, use different campaigns. One campaign selects interactions for customers, a separate campaign selects interactions for employees.
Improving accuracy
To improve the quality of the voice biometric analysis and the quality of the voiceprint model, a predefined number of interactions can be required (based on the Recorder Analytics Rule configuration). Enrollment for a person is not complete until:
-
The Recorder Analytics Rule has found the configured number of interactions, the interactions have been approved for use
-
The system updates the interactions to indicate that they are being used by the voiceprint model (Currently In use state).
After the enrollment is complete, the voiceprint model is considered fully trained.
About the unique identifier
A unique identifier is required to reference the voiceprint model.
-
The employee identifier is the employee ID, referred to in some areas of the user interface as Employee Name.
-
A customer identifier could be a reference number used by a business to identify each customer uniquely.
A customer identifier could be an account number. However, if a customer account is used by more than one person, the account does not fully identify a person. In such instances, use multiple fields for identification. For example, the account number combined with the full name of the person. The combined fields function as a unique identifier.