Rule settings

Rule Settings includes the name, description, the engines used by the Recorder Analytics Rule, and defines if the rule is activated.

Rule Setting	Description
Name	Mandatory. The name for the Recorder Analytics Rule.
Description	Optional. Meaningful information that describes the Recorder Analytics Rule. For example, its purpose.
Tenant	In a multi-tenant environment, the tenant to whom to assign the Recorder Analytics Rule. If the service provider is also a tenant, and you are creating the rule for the sole use of the provider Reserve for Provider. Once you save the Rule Settings, you cannot change the tenant assigned to the rule. The tenant name is displayed in parentheses next to the rule name. To see tenant definitions, go to Organization Management Module in WFO that allows administrators to set up different hierarchies to manage users from a single, unified, Web interface.. Under Hierarchies, select Tenant Settings.
Enabled	Defines if the Recorder Analytics Rule is activated on interactions. By default, not activated.
Engine Type	The engine or engines that are appropriate for the function you want the Recorder Analytics Rule to perform. Only licensed engines are available. Metadata Detection: To perform Metadata Detection. Real-Time Acoustics: To detect silence time or cross-talk in interactions, and activate real-time assistance. Real-time Linguistics (remote): To detect terms spoken in predefined real-time categories, or custom real-time categories for users with Speech Analytics Product that analyzes ongoing changes in customer behavior through spoken interactions with the customer, and drives effective organizational changes needed to address challenging market conditions., and activate real-time assistance. This engine performs the same functions as the Real-time Speech Analytics engine, except with this engine, the analytics processing is performed in the cloud rather than on the Recorder on which the interaction In Speech Analytics, an interaction represents a single part of the contact between one employee and the same customer. In Text Analytics, an interaction is the communication session between one or more employees and the same customer with a unifying contextual element. is recorded. This approach conserves processing resources on the Recorder on which the interaction is recorded. Real-Time Speech Analytics: To detect terms spoken in predefined categories, and activate real-time assistance. With this engine, analytics processing is performed locally on the Recorder on which an interaction is recorded. Risk Assessment: To implement the Risk Assessment Tactical solution, when voice biometrics is deployed in conjunction with the Victrio Management service. Voice Biometrics: To perform 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. or 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.. Voice Enrollment: To perform 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.. Licensing notes: The appropriate license must be enabled. To see what is enabled, go to System Management Module that allows performing suite-wide system management activities from a single, Web-based application, the Enterprise Manager.. Under Licensing Management, select System Licensing. To see Metadata Detection: Metadata Engine must be enabled. Metadata Engine is under IAFD. To see Voice Biometrics: Identity Authentication, Fraud Detection, or both must be enabled. Both are under IAFD. To see Real-Time Speech Analytics, Real-Time Speech Analytics Recording must be enabled. To see Real-Time Acoustics, RTAA for Acoustic Triggers must be enabled.