Stuck on the capacity formula for inbound messaging queues. We are publishing schedules via the WFM API (v2) for a team handling 5 concurrent chats per agent. The system seems to ignore the ‘handle time’ weight when calculating available capacity for digital channels, defaulting to voice metrics instead. This causes overstaffing alerts during peak chat hours despite adherence being 100%. Is there a specific configuration flag in the Workforce Management settings that forces the scheduler to respect the digital channel service level objectives?
Make sure you verify the channel-specific service level goals in the WFM optimization settings. The scheduler does not automatically apply voice handle time to digital queues unless the channel configuration is explicitly mapped to a digital service level target.
In the Genesys Cloud admin console, navigate to WFM → Optimization → Service Level Goals. Check if the chat queue is assigned a distinct SLG with a longer handle time estimate than the default voice metric. If the system defaults to voice metrics, it is often because the digital channel shares the same skill group without a separate SLG override.
Additionally, review the “Digital Channel” settings under Organization Settings. Ensure that the concurrent session limits are correctly defined for the agents’ skills. If the API payload for publishing schedules lacks the specific channel_type identifier, the engine may fall back to generic voice calculations. Explicitly defining the handle time distribution for chat in the schedule API request can resolve this discrepancy.
2 Likes
Check the channelType field in the WFM schedule payload. If it defaults to voice, the capacity engine ignores chat handle times. Switch it to digital_chat and ensure the shrinkage and handleTime metrics align with your actual digital SLA. The API documentation for v22.12 specifies this mapping is required for accurate digital capacity planning.
1 Like
it depends, but generally… the channeltype fix works for the api side. in our appfoundry integrations, we also sync the digital slg directly. if the wfm engine still pulls voice metrics, check the optimization config. sometimes the handle time override gets lost in the sync. verify the payload matches the admin console settings exactly.
switching the channel type to digital_chat did the trick. the capacity engine started respecting the handle time immediately after that change. we also had to tweak the service level goal in the optimization tab to match our 5 concurrent chat target. it was defaulting to a 20 second handle time which threw off the whole calculation. just be careful with the shrinkage values. if you leave them at the voice default, the scheduler will still overstaff because digital wrap-up times are usually longer. make sure the handle time in the schedule payload matches the actual average handle time from your queue analytics, or you’ll see false alerts. the api response now shows the correct available capacity. thanks for the pointer on the channel type field, that was the missing piece.
2 Likes