Monitoring Workforce Performance and Adherence
Workforce Management (WFM) provides the tools, described in this topic, to help you can monitor the performance and adherence in your workforce environment. You can generate Performance and Adherence data, enabling you to analyze it and spot trends that might be developing over time.
See the following sections:
The Performance modules compare the forecast and schedule to what is actually happening in the contact center. WFM shows intra-day statistics, such as interaction volume, average handling time (AHT), agents logged in, service level, average speed of answer (ASA), and abandons, and compares them to the planned values.
Intra-day contact-center performance data is displayed in an informative and easy-to-read format, enabling efficient performance monitoring and quick response to unanticipated interaction flow or agent-staffing situations.
WFM also provides a “what-if” calculator as an aid to decision making. You can enter new values for staffing, interaction volume, and/or other performance statistics into the What-If window. The what-if calculator then supplies the results to be expected if the values change as you project.
See also, Contact Center Performance Report Metrics.
Workforce Management provides real-time agent-adherence data, which compares the current agent status to the scheduled status. WFM can track agent adherence per time interval on a single channel or across multiple channels simultaneously.
Agents who are not adhering to their schedules (within user-defined thresholds) are highlighted in yellow if they are nonadherent or in red if they are severely nonadherent. WFM also displays the amount of time, in minutes, that the agent’s current status has differed from the scheduled status. This running total is continually updated.
To enable tracking of multi-channel adherence in WFM Web, assign a media channel to a Schedule State Group; WFM then calculates adherence by comparing real-time states to the scheduled states for that channel. See the example in Use Case 1: Multi-Channel Adherence.
Use Case 1: Multi-Channel Adherence
A site in the contact center has voice and e-mail related activities, and agents can make outbound calls, which are scheduled as exceptions. The schedule state groups can be configured as follows:
|Schedule state group||Channel||Schedule state||Real-time state|
|Inbound calls||Voice/unspecified||All (immediate) voice-related activities||WaitForNextCall, CallRinging, AfterCallWork, CallInbound|
|Outbound calls||Voice/unspecified||Exception types that represent outbound call work||WaitForNextCall, CallRinging, AfterCallWork, CallOutbound|
|<channel_name> (for example, email)||Deferred, e-mail related activities||WaitForNextCall, CallRinging, AfterCallWork, CallInbound|
|Overhead||None (no channel)||Breaks, meals, time off, exceptions, etc.||NotReadyForTheNextCall, LoggedOut|
If WFM is tracking multi-channel adherence (new in WFM 8.5), and there are no Schedule State Groups with a channel name under the Site, WFM calculates adherence as it would for a single agent real-time state, and Stat Server aggregates the statistics as it did prior to 8.5. However, if there is at least one Schedule State Group with a configured channel name, WFM tracks multiple channels. For each Site, WFM tracks as many different channels as there are distinct channel names for all Schedule State Groups under the Site.
For information about how to configure multi-channel adherence, see Configuring Media Channels for Schedule State Groups.
For information about WFM adherence calculations, see How WFM Calculates Adherence.
- For any given set of criteria (site/timezone/agent/date), the data in the 8.5 report is different than the data in the 8.1.3 report, because the adherence rules change when you add multi-channel settings to Schedule State Groups, which means the adherence percentages also changes.
- The Schedule State, Agent State, Start Time, End Time columns are in reverse order. In 8.5, the report displays the columns in this order: Start Time, End Time, Schedule State, Agent State.
Using Reason Codes
WFM enables you to enter reason (aux) codes when you configure agent-adherence rules. The reason codes are linked to Genesys Agent States and add additional details to the state information. The Genesys state + reason code combination is mapped to WFM Scheduled State Groups and is displayed in Adherence views.
For example, an agent might signal that she is in a NotReady state. By adding a reason code, she can specify that she is doing after-call work or answering email. This detailed information then appears in the WFM Web Adherence Details view and agent-adherence reports.
To use reason codes, your switch must support them. See your T-Server documentation to find out whether your switch can include reason codes when it sends Genesys TEvents.