With Avaya Experience Platform™ (On-Prem + Connect), supervisors can change an agent state from Ready to Not Ready to prevent agents from receiving further interactions. A supervisor can also forcibly log out an agent from Avaya Workspaces and end the session.
Note:
The Class of Restriction (COR) permission settings in Avaya Aura® Communication Manager do not apply when the supervisor changes the agent work state or forcibly logs out an agent.
If the supervisor changes the state of an agent who is active on an interaction, the agent is moved to a pending state. When the agent closes the interaction, the agent moves to the state the supervisor sets.
When a supervisor logs out an agent with active interactions, the agent state changes to Logout Pending. The agent does not receive any active interactions during this state.
A supervisor can also log out an agent when the agent has a stuck card and cannot close the card in Avaya Workspaces. During a stuck interaction, the agent fails to end an interaction even after the interaction with the customer is complete. Here, the agent must inform the supervisor about the stuck card. When the agent logs in again after the forced logout, Avaya Workspaces does not display the stuck card.
The following table provides different agent state transitions and the workflow for changing the agent state from the supervisor dashboard: