In Avaya Workspaces, the Work Assignment component stops if an agent closes the browser without logging out or if the client session is disconnected. Hence, no new work is routed to that agent. The client session can be disconnected for various reasons, such as browser refresh, browser crash, network change, system shutdown or sleep, and Avaya Breeze® platform load balancer failure.
Avaya Workspaces does the following once the configured timeout value expires:
Changes the agent to Not Ready when the agent is not active on an interaction.
Changes the agent state to Not Ready Pending when the agent is active on an interaction and then changes to Not Ready when the active interaction ends.
Sends a pop-up toast message to the supervisor. Avaya Workspaces also sends the message when the agent browser disconnects.
Avaya Workspaces also sets the Not Ready reason code when changing the state to Not Ready. The administrator must configure this Reason code in Avaya Control Manager. The agent cannot select this Not Ready Reason code when logged into Avaya Workspaces.
The administrator must also configure the timeout setting to a value from 0 to 300 seconds.
