Deep-Dive: Reconciling Intraday Monitoring Shrinkage Metrics

How-To-Articles
1

Deep-Dive: Reconciling Intraday Monitoring Shrinkage Metrics

Executive Summary & Architectural Context

In Workforce Management (WFM), Shrinkage is the silent killer of Service Level Agreements (SLAs). Shrinkage is the percentage of paid time that an agent is unavailable to handle customer interactions.

The primary cause of WFM friction in enterprise contact centers is a fundamental misunderstanding between the WFM team and Operations regarding Forecasted Shrinkage versus Actual Intraday Shrinkage. If WFM forecasts 30% shrinkage, but the Intraday Monitor shows 45% actual shrinkage, the queue will inevitably back up. When Operations asks WFM why they are failing, WFM blames unapproved shrinkage (agents sneaking off to the bathroom). Operations blames WFM for poor forecasting.

This masterclass provides an engineering-level breakdown of how Genesys Cloud calculates Intraday Shrinkage, how to reconcile “Planned” vs “Unplanned” buckets, and how to configure Activity Codes to ensure mathematical accuracy in your real-time dashboards.

Prerequisites, Roles & Licensing

  • Licensing: Genesys Cloud CX 2 or 3 (WEM Add-on).
  • Roles & Permissions: Workforce Management > Intraday > View.

The Implementation Deep-Dive

1. The Mathematical Formula for Shrinkage

In Genesys Cloud Intraday Monitoring, Actual Shrinkage is not a guess. It is a strict mathematical calculation:

Actual Shrinkage % = (Total Out of Office Time + Total Scheduled Shrinkage Time + Total Unscheduled Shrinkage Time) / Total Paid Time

To fix shrinkage reporting, you must ensure every minute of the agent’s day falls into the correct bucket.

2. Auditing Activity Codes (The Root Cause of Bad Data)

If an agent is in a “Meeting”, does that count as Shrinkage? Yes. Does it count as Paid Time? Yes.
If an agent is on “Unpaid FMLA Leave”, does that count as Shrinkage? No. It reduces the base headcount, but it does not count against paid shrinkage.

If your Intraday Shrinkage numbers are wildly inaccurate, your Activity Codes are misconfigured.

  1. Navigate to Admin > Workforce Management > Activity Codes.
  2. Review every single code.
  3. Check the Counts as Paid Time toggle. If a 30-minute unpaid lunch is accidentally marked as “Paid Time”, the denominator of the shrinkage equation inflates, throwing off the entire percentage.
  4. Check the Default Category. Is “System Outage” categorized as Unscheduled? If it is categorized as On Queue Work, your shrinkage will read artificially low, and your AHT will read artificially high.

3. Reconciling Planned vs. Unplanned Shrinkage in Intraday

Open the Intraday Monitoring view. You will see two critical columns: Planned Shrinkage and Actual Shrinkage.

Scenario A: Actual Shrinkage > Planned Shrinkage

  • The Cause: This is the classic “Operations Problem.” Agents are taking too much unscheduled time. They are sitting in “Break” for 25 minutes instead of 15. They are using the “Personal” code excessively.
  • The Fix: The WFM team must use the Real-Time Adherence (RTA) view to identify the specific agents in violation and alert supervisors to enforce schedule adherence.

Scenario B: Actual Shrinkage < Planned Shrinkage

  • The Cause: This is the classic “WFM Problem.” The forecaster built the schedule assuming 35% of agents would be out on vacation or sick leave, but everyone showed up to work.
  • The Trap: While this seems like a good thing (you have extra agents), it means you are over-staffed and wasting payroll.
  • The Fix: The WFM analyst must adjust the historical Shrinkage Profiles to lower the expected absenteeism rate for future schedules.

4. The “Off-Queue Work” Anomaly

Does answering an email count as shrinkage if the agent is primarily a voice agent?

  • In Genesys Cloud, if an Activity Code is assigned to the Off-Queue Work category, it does not count as shrinkage. It is considered productive work time.
  • If Operations tells WFM, “Our shrinkage is 50%!” but the agents are spending 2 hours a day doing mandatory data entry, WFM must ensure that data entry time is coded as Off-Queue Work, not Unscheduled Shrinkage.

Validation, Edge Cases & Troubleshooting

Edge Case 1: Time Off Requests (TOR)

If an agent has an approved full-day vacation, does it show up on the Intraday Monitor as Shrinkage?

  • Troubleshooting: Yes. Approved Time Off is the largest component of Planned Shrinkage. If your Planned Shrinkage looks dangerously low on Friday, it means your supervisors haven’t approved the pending PTO requests yet. The system cannot calculate planned shrinkage for unapproved time off.

Edge Case 2: Shrinkage in a Multi-Skill Environment

If an agent is scheduled to take Billing calls from 9-12, and Support calls from 1-5, how is shrinkage calculated if they take a 15-minute break at 11:45?

  • Logic: Shrinkage is calculated at the Management Unit (MU) level, not the individual skill level. If you attempt to slice Intraday Monitoring by a specific Route Group, shrinkage metrics can skew wildly because the break is applied to the agent’s total paid day, not explicitly tied to the “Billing” block. Always review shrinkage at the MU level for true accuracy.

Official References