Quality Management - System Limitations
QM is only tested for Cisco Voice (UCCE)
The hardcoded agent role is automatically assigned to Cisco sync agents and supervisors.
Users must manually add the agents to the team on unified admin to include them in the conversation list and Create Scheduler view filters.
Conversations will appear in the conversation list only after configuring the DN in the Channel section on Unified Admin. However, any conversations before configuring the DN will not be displayed
For the conversation of a consult call during an outbound call, the consulted leg is not created, and the consulted agent's information is not visible in the created conversation.
If a call is consulted to an agent and that agent transfers the call to another agent, the conversation for that call will not be created.
In an outbound call that is Consult/Directly transferred, the original agent's name is replaced with the agent who becomes the primary agent of the call.
The system does not support Conference calls, so conversations will not appear on the conversations list.
If an agent performs a Consult or Transfer on an inbound or outbound call using a Queue DN, the conversation will not be created in QM.
If the call gets disconnected within the second (like in 0.4s), the conversation of that call is created with 00:00 duration. The conversation manager is not handling milliseconds.
Relogin on the unified admin to get created agents in Reviews and Schedules
Agents deleted in Cisco remain in CX even after the sync job, but those agents are marked as disabled on Keycloak.
If Keycloak server is temporarily unavailable, the sync job fails and only retries in the next scheduled cycle, potentially delaying updates. New data will be shown after the next scheduled sync cycle is successfully executed.
If a team on Cisco is created with the same name as exists on CX, the Cisco team will not be synced to avoid duplication. Ensure unique team names across both systems.
When a team is deleted in Cisco, it remains in CX after the sync job is executed. The system currently does not support team deletion synchronization and this needs to be addressed in future updates.