Designing Automated Shift Bidding Workflows based on Performance Metrics

How-To-Articles
1

Designing Automated Shift Bidding Workflows based on Performance Metrics

What This Guide Covers

  • Implementing a merit-based shift bidding system that rewards high-performing agents with priority schedule selection.
  • Configuring “Ranking Rules” in Genesys Cloud WFM using Quality Scores, Adherence, and CSAT metrics.
  • Automating the bidding window execution and schedule assignment to reduce administrative overhead.

Prerequisites, Roles & Licensing

  • Licensing Tier: Genesys Cloud CX 3 or CX 1/2 with the WEM Add-on.
  • Permissions: Wfm > ShiftBidding > Add, Wfm > Schedule > Edit, Gamification > Scorecard > View.
  • Requirements: An active Gamification profile or Performance Scorecard integration for the target agent group.

The Implementation Deep-Dive

1. Defining the Ranking Criteria (The Meritocracy Engine)

A shift bid is only as fair as its ranking logic. Genesys Cloud allows you to rank agents based on a variety of data points.

  • The Process: In WFM > Management Units > Ranking Rules, create a new rule.
  • Metric Weighting: A “Principal Architect” typically recommends a 3-tier weighting:
    1. Quality Evaluation Score (40%): Ensures the best technical agents get the best shifts.
    2. Schedule Adherence (30%): Rewards reliability.
    3. Tenure/Seniority (30%): Balances performance with loyalty.
  • The Trap: “The Recency Bias.” If you only use last month’s performance for a 6-month shift bid, you punish a great agent who had one bad week. Always use a Rolling 90-Day Average for ranking metrics to ensure a representative sample of performance.

2. Configuring the Shift Bid Window

The bid window is the period during which agents can view available “Shift Blocks” and rank them in order of preference.

  • Implementation: Create a Shift Bid in the WFM menu. Select the Schedule Period (e.g., Q3 2026) and the Agent Groups.
  • Assignment Logic: Select your custom Ranking Rule. The system will process agents in order (Rank 1 gets their 1st choice, Rank 2 gets their highest available choice, etc.).
  • The Trap: “The Duplicate Shift Block.” If you create ten identical 8 AM - 5 PM shifts, you must group them into a “Shift Count.” If you list them individually, agents will waste their top 10 choices on the same shift time. Always use Shift Groups to simplify the agent’s ranking interface.

3. Automating the Post-Bid Schedule Generation

Once the bidding window closes, the “WFM Admin” should not have to manually move agents.

  • Automation: Use the Assign and Publish feature. This takes the results of the bid and automatically populates the master schedule.
  • The Trap: “The Vacation Conflict.” If an agent bids for and wins a shift, but they have pre-approved Time Off (PTO) during that period, the WFM engine may throw an error or leave the shift vacant. You must ensure the Conflict Handling mode is set to “Keep PTO” so the agent doesn’t lose their approved leave when the new shift pattern is applied.

Validation, Edge Cases & Troubleshooting

Edge Case 1: The “Tie-Breaker” Paradox

  • The Failure Condition: Two agents have identical performance scores and identical tenure; the system hangs or assigns randomly.
  • The Root Cause: No “Tie-Breaker” rule was defined in the Ranking Rule.
  • The Solution: Always add a Random Seed or a Hired Date (to the second) as the final, absolute tie-breaker in your ranking configuration.

Edge Case 2: Multi-Skill Coverage Gaps

  • The Failure Condition: All high-performing agents bid for the same popular shift (e.g., 9 AM - 5 PM), leaving the 5 PM - 12 AM shift staffed only by low-performing or new agents.
  • The Root Cause: Shift blocks were not limited by Planning Group requirements.
  • The Solution: Use Target Staffing Levels within the Shift Bid. This limits the number of people with a specific skill (e.g., “Spanish Support”) who can win a specific shift block, ensuring service level parity across all hours of operation.

Official References