Designing Performance-Based Automated Scheduling Workflows for Tiered Staffing

How-To-Articles
1

Designing Performance-Based Automated Scheduling Workflows for Tiered Staffing

What This Guide Covers

  • Implementing a tiered workforce scheduling model where shift priority and schedule quality are determined by real-time agent performance metrics (QA scores, adherence, and conversion rates).
  • Automating the shift bidding and assignment process using the Genesys Cloud WFM API and external performance data.
  • The end result is a self-optimizing workforce where high-performing agents are rewarded with preferred shifts, driving overall operational excellence.

Prerequisites, Roles & Licensing

  • Licensing: Genesys Cloud CX 3 or WEM Add-on (required for Workforce Management).
  • Permissions: Workforce Management > Schedule > Edit, Quality Management > Evaluation > View, and Platform API > Client Credential for automation.
  • Data Source: Access to Genesys Cloud Quality Management (QM) evaluations or an external performance database (CRM/BI tool).

The Implementation Deep-Dive

1. Defining the Tiering Logic and Weighting

The core of performance-based scheduling is the “Performance Scorecard.” You must define which metrics matter most and how they translate into a “Schedule Priority” rank.

The Trap:
Weighting metrics too heavily on single-occurrence events (like a one-off low QA score). This creates “performance anxiety” and leads to high turnover.

Architectural Reasoning:
Use a rolling 30-day average for metrics. A typical weighting might look like:

  • Quality Score (QA): 40%
  • Schedule Adherence: 30%
  • Average Handle Time (AHT) vs. Target: 20%
  • Tenure: 10% (as a tie-breaker).

Normalize these scores into a 1-100 scale. Agents in the top 20% (Tier 1) get first-choice bidding, while the bottom 20% (Tier 3) are assigned remaining shifts.

2. Automating the Shift Bidding Priority

Genesys Cloud WFM natively supports shift bidding, but “Performance-Based Bidding” requires an external orchestration layer to adjust the bidding_priority field before the bidding window opens.

Implementation Steps:

  1. Extract Performance Data: Use the Analytics API to pull rolling average QA and Adherence metrics for all agents in a specific Planning Group.
  2. Calculate Rank: Run a Python script (via AWS Lambda or local middleware) to calculate the rank of each agent within the group.
  3. Update Bidding Groups: Since Genesys Cloud handles bidding priority via Bidding Groups, you must dynamically move agents into the appropriate Bidding Group via the WFM API:
    PATCH /api/v2/workforcemanagement/businessunits/{buId}/planninggroups/{pgId}/biddinggroups/{bgId}
  4. Trigger bidding: Once groups are updated, open the bidding window.

The Trap:
Updating Bidding Groups after the bidding window has opened. The bidding priority is locked the moment the window becomes active. Always schedule your update script to run at least 2 hours before the bidding start time.

3. Performance-Based Intraday Adjustments

Redundancy isn’t just about servers; it’s about staffing. If a Tier 1 agent is out sick, the system should automatically look for another Tier 1 or high-Tier 2 agent to offer “Voluntary Overtime” (VTO) via the WFM Mobile app.

Architectural Reasoning:
By using the Workforce Management Webhooks, you can listen for v2.workforcemanagement.businessunits.{id}.schedules events. When an exception occurs (unplanned absence), your middleware checks the performance tier of available agents and sends a targeted push notification to the highest-performing available agent first.

Validation, Edge Cases & Troubleshooting

Edge Case 1: Data Lag in Quality Evaluations

  • The Failure Condition: An agent improves significantly in the last week, but their schedule priority remains low because the monthly evaluation cycle hasn’t closed.
  • The Solution: Implement a “Recent Trend” bonus. If an agent’s last 5 evaluations are 10% higher than their 30-day average, bump their rank by +1 tier for the next bidding cycle.

Edge Case 2: Union/Legal Compliance (Seniority vs. Performance)

  • The Failure Condition: Legal requirements in certain regions mandate that seniority must take precedence over performance.
  • The Solution: Use a “Hybrid Priority” model. Assign 60% weight to Tenure and 40% to Performance. This ensures high-performers still get an edge without violating labor agreements.

Official References