Designing Occupancy Target Configuration to Prevent Agent Burnout at High Utilization

How-To-Articles
1

Designing Occupancy Target Configuration to Prevent Agent Burnout at High Utilization

What This Guide Covers

You will configure Genesys Cloud CX Workforce Engagement Management (WEM) to enforce strict occupancy targets that prevent agents from exceeding 85% utilization during scheduled shifts. The result is a forecasting model that automatically inflates staffing requirements when projected occupancy exceeds your defined threshold, ensuring that the WFM schedule generation always includes sufficient shrinkage and buffer time to protect agent well-being while maintaining service levels.

Prerequisites, Roles & Licensing

  • Licensing: Genesys Cloud CX 3 license with the Workforce Engagement Management (WEM) add-on. Basic WEM (included in CX 2/3) does not support advanced occupancy targets or detailed shrinkage modeling.
  • Permissions:
    • Workforce Management > Forecast > View
    • Workforce Management > Forecast > Edit
    • Workforce Management > Schedule > Edit
    • Workforce Management > Target > Edit
  • Data Dependencies:
    • A historical data set of at least 6 months for accurate trend and seasonality analysis.
    • Defined Shrinkage Profiles that accurately reflect paid and unpaid time off, meetings, and coaching.
    • Configured Service Level Targets (e.g., 80/20) that are realistic for your channel volume.

The Implementation Deep-Dive

1. Defining the Occupancy Threshold and Target Profile

Occupancy is the percentage of time an agent is actively handling interactions (talking, typing, or in After-Call Work) relative to their available time. High occupancy correlates directly with agent burnout. If an agent is occupied 95% of the time, they have no buffer for bathroom breaks, mental decompression, or unexpected complex calls. This leads to higher absenteeism and turnover, which ironically increases shrinkage and further strains the remaining workforce.

The first step is to establish the “Hard Stop” for occupancy. Industry best practice dictates an occupancy target between 80% and 85%. Anything above 85% is considered dangerous for long-term retention. Anything below 75% is usually inefficient for the business.

The Trap: Configuring the target in the wrong profile. Many administrators set the occupancy target in the Service Level Target profile. This is incorrect. Service Level Targets dictate how many calls must be answered within a specific time (e.g., 80% in 20 seconds). Occupancy Targets dictate how much work an agent can be assigned. If you mix these, the WEM engine cannot decouple service performance from agent capacity, leading to schedules that hit service levels but crush agents.

The Architectural Reasoning: We separate these concerns because they are controlled by different variables. Service Level is driven by volume and AHT (Average Handle Time). Occupancy is driven by available agent minutes. By isolating Occupancy in its own target profile, we allow the WEM scheduler to add “slack” (idle time) specifically to meet the occupancy goal, even if the Service Level goal is already met.

Configuration Steps:

  1. Navigate to Admin > Workforce Management > Targets > Occupancy Targets.
  2. Click Create Target Profile.
  3. Name the profile: OCUP_85_Max_Burnout_Protection.
  4. Set the Target Occupancy to 85.
    • Note: This means the system will attempt to keep actual occupancy at or below 85%.
  5. Set the Maximum Occupancy to 88.
    • Note: This is the absolute ceiling. The scheduler will prioritize hitting the 85% target, but if volume spikes unexpectedly, it will allow up to 88% before flagging a critical shortage. This provides a tiny buffer for emergency scheduling without breaking the model entirely.
  6. Save the profile.

2. Integrating Occupancy Targets into the Forecasting Model

A forecast in Genesys Cloud predicts the number of interactions expected in a given interval (usually 15-minute blocks). However, a raw forecast does not tell you how many agents you need. That calculation is performed by the Staffing Recommendation engine, which uses the forecast, the AHT, and the Occupancy Target to derive the required headcount.

The formula Genesys Cloud uses is:

$$ \text{Required Agents} = \frac{\text{Forecasted Volume} \times \text{AHT}}{\text{Interval Length} \times (1 - \text{Shrinkage}) \times \text{Occupancy Target}} $$

Notice the Occupancy Target in the denominator. If you set the target to 100%, the system assumes agents never take a breath. If you set it to 85%, the system divides the required work by 0.85, effectively adding 15% more agents (or agent-minutes) to the schedule.

The Trap: Ignoring the impact of AHT volatility on occupancy. If your AHT fluctuates wildly (e.g., standard calls take 3 minutes, but escalated calls take 20 minutes), a static occupancy target can fail. If the AHT spikes, the required agent count spikes. If the scheduler has already locked the schedule, the agents who are on shift will see their occupancy spike above the target because the system cannot add more agents to a live shift. This is known as “Real-Time Occupancy Breach.”

The Architectural Reasoning: To mitigate this, we must ensure the Forecast Profile uses a conservative AHT. We do not use the average AHT. We use the AHT at the 90th percentile. This ensures that when the “bad” calls come in, the staffing model has already accounted for the extra time, keeping the occupancy target intact.

Configuration Steps:

  1. Navigate to Admin > Workforce Management > Forecasts > Forecast Profiles.
  2. Select your primary voice forecast profile (e.g., VOICE_INBOUND_MAIN).
  3. Go to the Parameters tab.
  4. Ensure Use Occupancy Target is checked.
  5. Select the target profile created in Step 1: OCUP_85_Max_Burnout_Protection.
  6. In the AHT section, verify that the AHT value is derived from historical data.
    • Critical Check: Click Analyze on the forecast to view the AHT trend. If the AHT is trending upward, update the AHT manually to reflect the new reality. An outdated AHT is the primary cause of occupancy breaches.
  7. Save the profile.

3. Configuring Shrinkage Profiles to Support Occupancy Goals

Shrinkage is the percentage of paid time that agents are not available to handle calls. This includes breaks, lunches, meetings, training, and absenteeism. Occupancy and Shrinkage are inversely related in the scheduler’s logic. If you have high shrinkage, you need more total agents to fill the available minutes. If you have low shrinkage, you need fewer agents, but the ones you have will be more occupied.

The Trap: Underestimating “Hidden Shrinkage.” Many organizations configure shrinkage for only “Paid Time Off” and “Meetings.” They forget to include “Coaching,” “Wrap-up Time Variance,” and “Agent Absenteeism.” If your shrinkage profile is set to 20% but actual shrinkage is 30%, the scheduler will generate a schedule with 10% fewer agents than needed. Those agents will then be scheduled at 90-95% occupancy to meet the service level, leading to immediate burnout.

The Architectural Reasoning: We must configure a shrinkage profile that is slightly aggressive (higher than historical averages) to create a “shrinkage buffer.” This buffer acts as a safety net. If an agent calls out sick, the buffer absorbs the loss without pushing the remaining agents over the 85% occupancy threshold.

Configuration Steps:

  1. Navigate to Admin > Workforce Management > Shrinkage > Shrinkage Profiles.
  2. Create or edit a profile named SHRINK_Voice_Standard_HighBuffer.
  3. Configure the following components:
    • Vacation: 2.5% (Annual average)
    • Sick Leave: 3.5% (Include seasonal flu spikes)
    • Meetings: 4.0%
    • Coaching/Training: 3.0%
    • Absence/Tardiness: 2.0%
    • Miscellaneous: 1.0%
    • Total Shrinkage: ~16.0%
  4. Recommendation: Increase the total to 18-20% if your industry has high turnover or seasonal volatility. This extra 2-4% is the “Burnout Prevention Tax.” It costs money in labor, but it saves money in turnover and overtime.
  5. Save the profile.
  6. Assign this shrinkage profile to the relevant Skill Groups or Queues in the Workforce Management > Schedules > Schedule Templates configuration.

4. Validating the Schedule Generation Algorithm

The final piece of the architecture is the Schedule Template. This is where the WEM engine combines the Forecast, the Occupancy Target, and the Shrinkage Profile to generate the actual shifts.

The Trap: Using “Fixed Shifts” instead of “Floating Shifts” in high-volume environments. Fixed shifts (e.g., 9-5) do not adapt to intra-day volume spikes. If volume spikes at 11 AM, agents on fixed shifts will see their occupancy spike to 95% for that hour. Floating shifts allow the scheduler to start agents earlier or end them later to smooth out the occupancy curve.

The Architectural Reasoning: To protect occupancy, we must use Intraday Flexibility. This allows the scheduler to adjust break times and shift starts/ends within a defined window. This flexibility is crucial for smoothing out occupancy peaks.

Configuration Steps:

  1. Navigate to Admin > Workforce Management > Schedules > Schedule Templates.
  2. Create a new template: SCHED_Voice_Occupancy_Protected.
  3. In the Shift Patterns tab:
    • Add a Floating Shift pattern.
    • Set Minimum Duration to 7 hours.
    • Set Maximum Duration to 8 hours.
    • Set Start Time Window to 6:00 AM – 2:00 PM.
    • Set End Time Window to 2:00 PM – 10:00 PM.
  4. In the Breaks tab:
    • Configure two 15-minute breaks and one 30-minute lunch.
    • Check Flexible Breaks.
    • Set Break Window to +/- 15 minutes from the scheduled time.
    • Why this matters: Flexible breaks allow agents to take their break when the queue is empty, preventing them from being pulled back in during a lull (which increases occupancy) or missing a break during a surge (which increases stress).
  5. In the Constraints tab:
    • Set Maximum Consecutive Hours to 6.
    • Set Minimum Time Between Shifts to 11 hours (to ensure rest).
  6. Save the template.

Validation, Edge Cases & Troubleshooting

Edge Case 1: The “Green Shirt” Effect (Over-Staffing vs. Occupancy)

The Failure Condition: The scheduler generates a schedule that meets the 85% occupancy target, but the Service Level (80/20) drops to 60%. Agents are sitting idle (low occupancy), but customers are waiting.
The Root Cause: The Occupancy Target is too low for the Service Level Target. You are demanding too much idle time from agents. The math simply does not support both goals simultaneously with the current headcount.
The Solution:

  1. Analyze the Schedule Analysis report in WEM.
  2. Look at the Occupancy vs. Service Level correlation chart.
  3. If you cannot increase headcount, you must relax the Occupancy Target to 90% or tighten the Service Level Target to 70/20. You cannot have both high efficiency (low occupancy) and high responsiveness (high service level) without more resources.
  4. Recommendation: Keep Occupancy at 85% and accept a slightly lower Service Level, or invest in more agents. Burnout is a higher risk than a slight SLA miss.

Edge Case 2: Real-Time Occupancy Breach During Volume Spikes

The Failure Condition: The schedule is perfect on paper, but during a live event (e.g., a marketing campaign launch), volume spikes by 50%. Agents’ real-time occupancy hits 95%.
The Root Cause: The Forecast did not account for the campaign, or the AHT increased due to campaign-specific questions. The static schedule cannot adapt to real-time reality.
The Solution:

  1. Enable Genesys Cloud Real-Time Management (RTM) rules.
  2. Create a rule: IF Queue.Occupancy > 90% FOR 10 MINUTES THEN Alert Supervisor.
  3. Configure Skill-Based Overflow to route calls to a secondary, less utilized queue (if available).
  4. Use Agent Desktop notifications to prompt agents to wrap up calls slightly faster (if appropriate) or to take micro-breaks if the queue clears suddenly.
  5. Proactive Fix: Update the Forecast manually for the affected period if a campaign is known in advance. WEM allows manual forecast adjustments that immediately recalculate staffing needs.

Edge Case 3: Shrinkage Mismatch in New Hires

The Failure Condition: A cohort of new hires starts. Their AHT is 30% higher than veterans. Their occupancy immediately exceeds 85%, even with the protected schedule.
The Root Cause: The Shrinkage Profile and AHT used in the schedule were based on veteran performance. New hires require more coaching time (shrinkage) and have longer AHTs.
The Solution:

  1. Create a separate Shrinkage Profile for new hires (e.g., SHRINK_NewHire_HighCoaching) with an additional 5-10% for coaching.
  2. Create a separate Forecast Profile or adjust the AHT for the skill group associated with new hires.
  3. Assign new hires to a specific Skill Group that uses these adjusted profiles.
  4. This ensures the scheduler assigns fewer calls to new hires, keeping their occupancy within the safe 85% limit while they ramp up.

Official References