Checking Assignment Failure Logs
Updated
There might be some scenarios where a case arrives in a work queue but the algorithm cannot find the suitable agent for assignment. In such scenarios, Assignment wait reasons are generated, which show why a case is still waiting in the work queue for agent assignment.
The Assignment Wait Reasons feature enables administrators to view and understand the specific reasons for which a case remains unassigned in the work queue along with the various case attributes. Admins can also search for the case number to view the associated wait reasons for that case.
Enablement Note: The feature is DP enabled, and to enable this you need to contact your Success Manager.
To view assignment wait reasons in a particular work queue, click on three dots beside any work queue name and click View Details. This will open a third pane on the right with different tabs. Users can switch between these tabs by simply clicking on it.
Click on Assignment Wait Reasons tab in the navigation pane on the right. Here, whenever the routing engine fails to assign a case to the agent, the reason is captured here with the time when it was occured.
Click the down arrow on the case screen, the details of the case for which assignment wait reason occured is displayed. By double clicking on the case card, the case opens in the third pane. The case card has the Channel, Skills, Priority Rank and Work Queue Assignment Time as its field details.
Also you can select the case for which you want to see the details by clicking on the Case#. You can also refresh the screen with the help of the refresh button.
The reasons which are responsible for assignment wait reasons are as follows:
Work should be assigned soon: This wait reason appears when at least one agent satisfies all the requirements for case assignment and has free capacity to handle the case. However, when there is a high backlog of cases in the queue or the partner, the case might sometimes take a few seconds for agent assignment. During this brief waiting period, this reason is displayed.
No agent available: This wait reason appears when no agent is in the availability status, as configured in the work queue, to handle the case.
No agent with required skills: This wait reason appears when there are available agents in the queue, but none of them have the specific skills required to handle the case.
No eligible agent with free capacity: This wait reason is displayed when agents with the required skills and availability status, as configured in the work queue, are present but don't have the required free capacity to handle this case.
Whenever a case is waiting for stickiness agent, the following are the stickiness wait reasons that are assigned:
No agent available (Stickiness): This wait reason is displayed when the stickiness agent is in the "agent status for stickiness," as defined in the work queue, but is not in the availability status to handle the case.
No agent with required skill (Stickiness): This wait reason is displayed when the stickiness agent is in the availability status for case assignment, but lacks the required skills to handle the case.
No eligible agent with free capacity (Stickiness): This wait reason is displayed when the stickiness agent is in the availability status for case assignment, possesses the required skills, but does not have the free capacity to handle the case.
Whenever there is stickiness wait reason, there is an additional field, Stickiness Agent that appears on the same case card screen.