Resolving Adherence Gaps During Multi-Skill Cross-Training Sessions

How-To-Articles
1

Resolving Adherence Gaps During Multi-Skill Cross-Training Sessions

Executive Summary & Architectural Context

In an agile contact center, upskilling agents is a continuous process. A Tier 1 agent taking Billing calls on Monday might spend Tuesday in a 4-hour cross-training seminar to learn Technical Support, and then take Technical Support calls on Wednesday.

The WFM (Workforce Management) engine must handle this transition gracefully. However, a massive architectural conflict occurs when the WFM scheduling engine (which looks at future agent skills) collides with the Real-Time Adherence (RTA) engine (which looks at present agent skills) during the exact moment of the cross-training. If not sequenced perfectly, the agent will be hit with severe adherence violations or routed calls they do not know how to handle.

This masterclass details the exact sequencing required to schedule cross-training activities, update ACD routing profiles, and utilize specific Activity Codes to prevent adherence gaps.

Prerequisites, Roles & Licensing

  • Licensing: Genesys Cloud CX 2 or 3 (WEM Add-on).
  • Roles & Permissions:
    • Admin > Users (to apply skills).
    • Workforce Management > Schedule > Edit.

The Implementation Deep-Dive

1. The Core Conflict (The “Skill Trap”)

The WFM scheduling engine generates schedules based on the skills the agent possesses at the time the schedule is generated.

If you generate next week’s schedule on Thursday, the engine sees John Doe only has the Billing skill. It schedules him for On Queue work to handle Billing.
On Tuesday morning, John attends the 4-hour Technical Support training. At 1:00 PM, the trainer adds the Tech_Support skill to John’s user profile so he can start taking tech calls.

  • The Trap: The WFM schedule was generated days ago. It still expects John to only take Billing calls. The RTA engine sees him taking Tech Support calls. Depending on strict Route Group mapping, this can flag as an Out of Adherence violation because his actual activity no longer matches the expected Scheduled Route Group.

2. Utilizing “Training” Activity Codes Correctly

To shield the agent from adherence hits during the actual classroom session:

  1. Navigate to Admin > Workforce Management > Activity Codes.
  2. Ensure you have a dedicated Cross-Training activity code.
  3. Category: Unscheduled or Meeting (Do not use On Queue Work).
  4. Counts as Paid Time: True.
  5. When the agent is in the classroom, they must manually select the Cross-Training system presence.
  6. The WFM analyst must have pre-scheduled this 4-hour block using the exact same Cross-Training activity code so the RTA engine maps Scheduled: Training to Actual: Training = 100% Adherence.

3. Sequencing the Skill Update (The Fix)

You must decouple the addition of the new skill from the active schedule generation cycle.

  1. Do not add the new skill to the agent’s profile before generating the schedule for the week of the training. If you do, the AI forecasting engine will mistakenly assume the agent is fully available for Tech Support all week and understaff the floor.
  2. The Go-Live Moment: The skill should be added to the agent’s profile immediately after the classroom session concludes.
  3. The Intraday Reforecast: The moment the skill is added, the WFM analyst must go into the schedule and perform an Intraday Update. They must alter the agent’s scheduled block for the remainder of the week.
  4. Instead of the generic On Queue code, the analyst must update the agent’s scheduled Route Group to explicitly reflect the new blended skill set (Billing + Tech_Support). This forces the RTA engine to accept the new reality and stops adherence violations.

Validation, Edge Cases & Troubleshooting

Edge Case 1: Proficiency Traps (Nesting)

After training, agents usually enter “Nesting” (taking calls with a supervisor listening in). They have the new skill, but they are very slow.

  • Troubleshooting: If you add the Tech_Support skill at a high proficiency (e.g., 5 out of 5), the routing engine will flood the agent with technical calls, destroying their handle time and morale.
  • Solution: Always add newly trained skills at the lowest possible proficiency (e.g., 1 out of 5, or 5 if using 1-is-best numbering). You must also instruct WFM to artificially inflate that specific agent’s expected AHT in the scheduling parameters for the next 2 weeks, ensuring the scheduling engine doesn’t assume the new agent can handle 30 calls an hour.

Edge Case 2: Historical Reporting Skew

When you run a report for “Tech Support Queue Performance” for the month, it will include John Doe’s metrics starting from Wednesday.

  • The Trap: If your BI dashboards analyze agent performance by comparing them to their peer group, John will look like a terrible Tech Support agent because his Handle Time will be 3x the average of the veterans.
  • Solution: You must use Agent Utilization Tags or specific Skill Group filtering in your Analytics Workspace to exclude “Nesting” agents from aggregate performance dashboards until they graduate to full proficiency.

Official References