Outbound Campaign Failing to Align with Published WFM Schedules

General Discussion
1

Trying to understand why our outbound campaign in Genesys Cloud is dialing agents marked as ‘Unavailable’ in the published WFM schedule for the Chicago timezone. The campaign uses the standard ‘Available’ filter, but logs show calls routing during lunch breaks.

  • Verified WFM schedule publish success via API /api/v2/wfm/schedule.
  • Confirmed agent status sync delay is under 5 seconds.

Any insights on latency or configuration gaps?

2

This looks like a configuration misalignment between the outbound campaign’s availability filter and the actual WFM schedule state. The standard “Available” filter in outbound campaigns often relies on the agent’s current status rather than the published WFM schedule, leading to calls routing during planned unavailability like lunch breaks. To resolve this, ensure the campaign uses the “Schedule” availability type instead of “Status” in the flow configuration. This forces the system to consult the published WFM schedule directly.

{
 "type": "availability",
 "value": "schedule",
 "timezone": "America/Chicago"
}

Verify that the timezone in the flow matches the WFM schedule’s timezone to prevent any offset issues.

3

Make sure you verify the specific availability type setting within the outbound campaign configuration. The standard “Available” filter often checks real-time agent status rather than the published WFM schedule, which explains the dialing during lunch breaks. Switching to the “Schedule” availability type forces the system to consult the WFM data directly.

In my JMeter load testing for US-East environments, I observed similar mismatches when simulating high concurrent volumes. The API calls for status checks can introduce slight latency or cache issues if the load is too heavy. Using the schedule-based filter reduces the dependency on real-time status APIs, which helps stabilize the routing logic under pressure. It is a more reliable method for capacity planning.

You can validate this change by running a small test campaign with a few agents. Monitor the routing logs to ensure calls only go out during scheduled available hours. This approach aligns better with WFM data and reduces unexpected outbound attempts during breaks.

4 
{
 "availabilityType": "SCHEDULE",
 "filter": {
 "operator": "EQUALS",
 "value": "AVAILABLE"
 }
}

You might want to look at the outbound campaign configuration specifically. In Zendesk, we used to rely on simple toggle states for agent availability, but Genesys Cloud handles this differently. The standard “Available” filter often checks real-time status, which can lead to calls routing during planned unavailability like lunch breaks. Switching to the “Schedule” availability type forces the system to consult the WFM data directly. This ensures that the campaign respects the published schedules and avoids dialing agents marked as unavailable. It’s a small change, but it makes a huge difference in aligning with your workforce management goals. Just update the campaign settings to use the “Schedule” type, and you should see the issue resolve quickly.

5 
{
 "outboundCampaign": {
 "filter": {
 "availabilityType": "SCHEDULE",
 "status": "AVAILABLE"
 }
 }
}

The configuration snippet above explicitly forces the campaign to query the WFM schedule rather than real-time status. This distinction is critical for high-throughput integrations, as relying on STATUS introduces race conditions during schedule transitions. Ensure the payload targets the correct org context.