I evaluated two Genesys Cloud orgs last month - one mid-market (200 agents) and one enterprise (3,000 agents).
The mid-market org had 12 AppFoundry integrations running and spent more time managing integration conflicts than actually using the contact center. The enterprise org had 3 tightly scoped integrations and ran flawlessly. More integrations ≠ better. Be ruthlessly selective.
When you manage 15 BYOC trunks, you want redundancy. But during peak volume with RONA (Redirect on No Answer), the platform keeps trying the same unresponsive agent.
The RONA timeout is 20 seconds by default. If 5 calls in a row hit an agent who stepped away without changing their status, that’s 100 seconds of wasted capacity. Reduce the RONA timeout to 8 seconds for high-volume queues.
I see this as an opportunity for AI-driven workforce optimization.
If the platform detects 3 consecutive RONA events for the same agent, it should automatically change their status to ‘Away’ and notify the supervisor. This is exactly the kind of intelligent automation that Agent Assist should handle - proactive anomaly detection, not just keyword spotting.
In CIC, RONA was configurable per workgroup, and the system automatically logged the agent out after 3 missed calls.
Genesys Cloud does have a ‘Force Off Queue’ after RONA setting, but it is buried in the queue configuration under ‘Alerting’. Many admins don’t even know it exists. Look for the ‘Number of RONA alerts before going off queue’ setting.
As a QM supervisor, RONA events are the #1 reason I fail evaluations.
The agent doesn’t answer, the customer is redirected to another agent, and the second agent has zero context. The customer repeats their entire issue. I score the first agent for non-responsiveness and the second agent gets penalized for asking redundant questions. Nobody wins.
We are rolling out Genesys Cloud in phases, but our existing PureConnect IVR needs to coexist for 6 months.
During the parallel run, some calls land in PureConnect and others in GC depending on the DID. Agents need to be logged into BOTH systems simultaneously. How do you handle dual-login without doubling the license cost?
You cannot avoid dual licensing during a parallel run. Budget for it.
From a project management perspective, the parallel run is the most expensive phase of any migration. We typically negotiate a 90-day overlap discount with Genesys sales. Factor this into your migration budget from day one, or the CFO will kill the project when the dual invoice arrives.
From a WFM perspective, third-party integrations can silently consume agent capacity.
We installed an AppFoundry gamification integration that periodically polls each agent’s status via the API. At 3,000 agents, this created 3,000 API calls every 30 seconds. Our WFM intraday dashboard started showing phantom ‘Not Responding’ events because the polling was competing with the platform’s native presence updates.