Implementing Advanced Shift Bidding and Micro-Scheduling Workflows for Remote Agents

How-To-Articles
1

Implementing Advanced Shift Bidding and Micro-Scheduling Workflows for Remote Agents

What This Guide Covers

  • Transitioning away from rigid, top-down Workforce Management (WFM) scheduling to an agent-empowered “Shift Bidding” model in Genesys Cloud.
  • Architecting “Micro-Schedules” (e.g., 2-hour or 4-hour fragmented shifts) tailored specifically for remote, gig-economy, or part-time work-from-home agents.
  • The end result is a highly flexible WFM environment that improves agent retention, reduces absenteeism, and automatically fills sudden intraday volume spikes without requiring supervisor manual intervention.

Prerequisites, Roles & Licensing

  • Licensing: Genesys Cloud CX 3 (or CX 1/2 with WEM Add-on).
  • Permissions: WFM > Schedule > Edit, WFM > Shift Trade > Manage.
  • Infrastructure: A configured WFM Business Unit, Management Unit, and generated historical forecasts.

The Implementation Deep-Dive

1. The Flaw of the 9-to-5 Call Center Schedule

Historically, contact centers scheduled agents in rigid 8-hour blocks (e.g., 8:00 AM to 5:00 PM).

The Trap:
This model completely fails in a modern remote-work environment. Remote agents often have childcare, university classes, or dual jobs. If you force a rigid 8-hour schedule, agents will simply call out sick when a conflict arises, destroying your Service Level (SL). You must embrace Schedule Flexibility and Micro-Scheduling to optimize coverage and reduce attrition.

2. Architecting Micro-Schedules

Instead of generating generic 8-hour shifts, configure the scheduling engine to generate fragmented shifts based on volume demand.

Implementation Steps:

  1. Navigate to Admin > Workforce Management > Work Plan Rotation.
  2. Create a new Work Plan named Remote_Gig_Agent_Plan.
  3. In the Shifts configuration, do not set the minimum duration to 8 hours.
  4. Set the Minimum Duration to 2 Hours and the Maximum Duration to 4 Hours.
  5. Enable Flexible Start Times. Allow the start time to float anywhere between 6:00 AM and 10:00 PM.
  6. When you generate the schedule based on your forecast, the Genesys Cloud WFM AI will look at your volume spikes (e.g., the 11:00 AM lunch rush and the 4:00 PM closing rush) and create highly optimized 2-hour shifts that perfectly overlap those specific spikes.

3. Implementing Automated Shift Bidding

You have generated 100 optimized micro-shifts. Now, instead of assigning them, you let the agents “bid” on them.

Architectural Reasoning:
Shift bidding gives agents control over their lives. They build a schedule that works for them, which guarantees higher schedule adherence.

Implementation Steps:

  1. In the WFM Scheduling view, generate your schedule but do not publish it directly to the agents.
  2. Navigate to Shift Bidding and create a new Bid Period.
  3. The Ranking Metric: Decide how agents will be ranked for bid priority. You can rank by Hire Date (seniority), but a more advanced approach is ranking by Performance Score (Gamification points). This incentivizes top performers by giving them first pick of shifts.
  4. The Bidding Window: Set a 48-hour window. The agents receive an alert in their Genesys Cloud UI. They log in, view the available micro-shifts, and rank their preferences (e.g., “I want Monday 10am-2pm as my first choice, and Tuesday 6pm-8pm as my second choice”).
  5. The Resolution: When the window closes, the WFM engine automatically assigns the shifts based on the agent rankings and business requirements, publishing the final schedule.

4. Intraday Shift Trades and “Drop” Automation

Even with perfect bidding, life happens. An agent’s internet might drop, or their child might get sick.

Implementation Steps:

  1. Navigate to Admin > Workforce Management > Business Units.
  2. Under the Shift Trades tab, enable Automatic Shift Trade Approval.
  3. Configure the rules: Agents can trade shifts if they have matching Skills, and the trade does not result in overtime (e.g., >40 hours a week).
  4. If Agent A has a 4:00 PM shift but needs to leave early, they can offer it up on the internal Shift Trade board. Agent B (who wants extra hours) accepts it. Because the rules match, the WFM engine instantly updates both schedules without a supervisor ever needing to click “Approve”.

Validation, Edge Cases & Troubleshooting

Edge Case 1: The “Unpopular Shift” Deficit

  • The Failure Condition: You implement Shift Bidding. Every agent bids on the Monday-Friday morning shifts. No one bids on the Saturday evening shifts. The WFM engine assigns the Saturday shifts to the lowest-ranking agents, who immediately call out sick because they didn’t want them.
  • The Root Cause: Shift Bidding exposes the reality of unpopular hours.
  • The Solution: Implement Shift Premiums or split requirements. In your Work Plan, configure rules that state: If an agent bids for >20 hours a week, 4 of those hours MUST be on a weekend. Alternatively, rely on HR to offer financial bounties for the specific micro-shifts that go un-bid, converting them to highly desirable overtime slots.

Edge Case 2: Union Rules and Minimum Hours

  • The Failure Condition: The WFM engine generates twenty 2-hour shifts to perfectly match a volume spike. However, your contact center is governed by a labor union contract that states: “Any agent called in to work must be paid for a minimum of 4 hours.” You are now paying for 40 hours of dead, idle time.
  • The Root Cause: The AI scheduling algorithm is prioritizing mathematical queue efficiency over HR legal contracts.
  • The Solution: In your WFM Work Plan configuration, strictly enforce the Minimum Paid Time constraints. Set it to 4 hours. The AI will then stretch the 2-hour shift into a 4-hour shift. To avoid dead time, use the Activity Codes configuration to schedule the remaining 2 hours as “Offline Coaching”, “E-Learning”, or “Back-Office Case Work”, ensuring the union contract is met while keeping the agent productive.

Official References