For use in Contact Center Minnesota and IVR applications.
|0||Reason code not entered||Represents an agent
going Not Ready without a reason code.
Appears in a report, if after logging in, waits a few seconds before going ready/active.
As the agent is waiting, the system considers the agent as "Not Ready" with a reason code of "0". This data will show up in the Not Ready Reason Code reports even though the agent did not explicitly "go" not ready.
|33||Supervisor not ready|
|20001||Agent state||Agent's state was changed to Not Ready, and the agent's state was forcibly logged out.|
|20003||If an agent is in Not Ready state, a request is made to place the agent in the Not Ready state and then a logout request is made to request to the agent out.|
|32767||RONA - call to agent was redirected on No Answer and agent was put into not ready state||The agent's state was changes to Not Ready because the agent did not answer and the call was redirected to a different agent or skill group.|
|50002||CTI failure - CTIOS component failed or agent desktop closed||An issued occurred, causing the agent to be logged out. This could be due to closing the desktop application, or other system components.|
|50010||Missed tasks - agent did not receive multiple consecutive calls||The agent did not receive multiple consecutive calls routed to them. The system makes the agent Not Ready automatically so the additional calls are not routed to the agent.|
|20||End of day|
|22||Supervisor log out|
|50001||Agent disconnected from CTIOS server.|
|50002||CTI disconnect log out, missed heartbeats, agent closed desktop, or CTI component failure.|
|50003||Device failure log out: call manager reported that the device is out of service.|
|50004||Inactivity timer log out. Agent timer set in agent desk settings caused agent to transition from not ready to log out.|
|50020||The agent was logged out when the skill group assignment dynamically changed in the AW.|