Configuring CXone MAX Agent Timeout and Auto-Logout Behaviors

How-To-Articles
1

Configuring CXone MAX Agent Timeout and Auto-Logout Behaviors

Executive Summary & Architectural Context

In a contact center, “ghost agents” destroy service levels. A ghost agent is someone who closes their laptop lid or leaves for the day without explicitly clicking “Log Out” or “Available” in the NICE CXone MAX client.

If the CXone platform still believes the agent’s web socket is active, the routing engine will deliver a phone call to their empty desk. The call rings for 30 seconds (Ring No Answer), and then bounces back to the queue (Reroute on No Answer - RON), damaging the customer experience and crushing the queue’s SLA.

The architectural solution is to configure Station Timeout and Refused Call Limits in the CXone Admin portal. These safeguards automatically identify unresponsive agents, force their status to “Unavailable”, and ultimately log them out to protect the routing engine. This masterclass details the specific configuration layers required to enforce agent session hygiene.

Prerequisites, Roles & Licensing

  • Licensing: NICE CXone.
  • Roles & Permissions: ACD > Contact Settings > Skills, ACD > Users > Profiles.

The Implementation Deep-Dive

1. Handling the “Ring No Answer” (RONA)

The first line of defense is detecting when an agent doesn’t answer a ringing call.

  1. Navigate to ACD > Contact Settings > Skills.
  2. Select your Inbound Voice Skill.
  3. Go to the Post Contact or Parameters tab.
  4. Locate the Agent No Answer Timeout.
    • Best Practice: Set this to 15 or 20 seconds. Do not let a call ring for 45 seconds at an empty desk.
  5. The Critical Setting: Locate the setting State After No Answer or Refusal State.
    • You must configure this to shift the agent into an unavailable state (e.g., System_Refused or Unavailable).
    • If you leave this blank, CXone will bounce the call back to the queue, but leave the agent in Available. The next call in queue will instantly hit the same empty desk, creating an infinite loop of routing failures.

2. The Station Timeout (The Auto-Logout)

If an agent walks away in the Unavailable state, they aren’t hurting routing, but they are consuming a concurrent license port. You must force a logout.

  1. Navigate to Admin > Users > Login Authenticator (or Station Profiles, depending on your UI version).
  2. Look for the Station Timeout setting.
  3. This timer dictates how long an agent can remain connected to the CXone voice servers without any active media stream or UI interaction.
  4. Set this to 120 minutes (or whatever your maximum acceptable idle time is).
  5. How it works: If the agent is in Break for 121 minutes, the CXone platform violently severs the web socket and SIP registration, forcing the MAX client back to the login screen.

3. Maximum Refusals (The Three-Strike Rule)

Some contact centers use progressive dialers where agents might accidentally miss a connection beep. You might want to give them a second chance before forcing them offline.

  1. Navigate to Admin > Users > Profiles.
  2. Edit the profile assigned to the agents.
  3. Locate the Maximum Refused Contacts setting.
  4. Set this to 3.
  5. Logic: If the agent misses Call 1, they are put in Refused. If they click “Available” again, but miss Call 2, they go back to Refused. If they hit Available and miss Call 3, the MAX client forcibly logs them out of the platform entirely.

Validation, Edge Cases & Troubleshooting

Edge Case 1: The “Auto-Answer” Conflict

To prevent RONA entirely, many operations teams demand that WFM/IT enable Auto-Answer for the agents.

  • The Trap: If Auto-Answer is enabled, a call delivered to an empty desk is instantly answered. You now have a customer talking to a silent room for 5 minutes before hanging up. A RONA (Ring No Answer) is bad, but a silent connect is worse-it ruins CSAT and inflates Handle Time.
  • Solution: Never enable Auto-Answer unless the agents are using physical headsets with strict supervisor enforcement of desk presence, or if you are running an Outbound Predictive campaign where the “zip tone” is mandatory.

Edge Case 2: Integrated Softphone (WebRTC) Sleeping

If an agent is using the CXone Integrated Softphone (WebRTC inside the browser), modern browsers (Chrome/Edge) have an aggressive “Tab Sleeping” or “Memory Saver” feature.

  • Troubleshooting: If the agent puts the MAX client in a background tab and reads a PDF for 10 minutes, Chrome might “put the tab to sleep” to save RAM. This kills the WebRTC web socket. CXone registers this as a station drop. When a call arrives, it fails to deliver.
  • Solution: IT must deploy a GPO to whitelist the CXone domain (*.niceincontact.com) from Chrome’s “Memory Saver” feature, ensuring the tab receives persistent CPU priority even when minimized.

Official References