Jump to: navigation, search

SplitMS

Section: ScheduleService
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Dependencies: SplitMode and SplitCoverage

Specifies whether or not WFM uses multi-skill splitting of schedule coverage.

If this option value is set to true, the coverage split in WFM Web is dynamically adjusted to maximize multi-skill performance gain. It works on top of the obtained coverage, based on either of these option settings: SplitMode = 0 or SplitMode = 2.

If the SplitCoverage option is set to false, then the SplitMS option is ignored.

more...

Multi Forecasting Primer

In this topic, find information about the Workforce Management approach to multi-site forecasting in a networked contact center, where some call types and activities are distributed to agents working across multiple sites. It also describes the Genesys approach to multi-skill forecasting, where agents with multiple skills can increase the center’s efficiency by performing multiple tasks within a single timestep.

Multi-Site Forecasting

A contact center analyst can use Genesys WFM to model a networked contact center, where some call types and activities are distributed to agents working across multiple sites. To model a multi-site environment, follow the steps and guidelines outlined in these sections:

Set Up Multi-Site Activities

These multi-site activities are work activities that are handled at the site (child) level, and in the object tree they appear higher in the hierarchy.

Determine the Total Demand

To configure Multi-Site Forecasting (MSF) properly, you need data to inform your choices. To gather that data, you can configure WFM to collect:

  • Historical Interaction Volume (IV) and Average Handle Times (AHT) for multi-site activities
  • Historical average handle times at the child level

After you build a volume forecast at the multi-site activity level and understand the total demand for this call type across all sites, you can configure MSF for two scenarios:

Option A: Contact centers that do a percentage allocation across their sites

To configure for this scenario, perform these steps:

  1. Split the volume of the multi-site activity to the site level.
  2. Build staffing forecasts at the site level for each child activity.

Option B: Virtual contact centers that do routing based on resource availability, open hours, etc.

To configure for this scenario, perform these steps:

  1. Split the volume of the multi-site activity to the site level.
  2. Build a staffing forecast at the multi-site activity level. (See the figure Comparing Two Multi-Site Scenarios.)
  3. Split the staffing forecast to each child activity.
Tip
The volume split is the required first step, so that the staffing splitting algorithm understands the demand at each site.

WM 812 MSA options.png
Figure: Comparing Two Multi-Site Scenarios

Volume Splitting

In a multi-site enterprise, when you split the volume of multi-site activity interaction to the child sites, you must decide which Average Handling Time (AHT) to use:

  • AHT collected at the multi-site activity level
  • AHT collected at the child activity level

To inform your decision, determine if there is a measurable difference in AHT at the various sites in the enterprise. For example, if one site consists of many less-skilled agents (perhaps they are new to their jobs), you may expect to see a longer AHT at this site for some activities. In this case, you would do well to use the child AHT rather than the multi-site AHT.

After you split the volume to the child sites, decide if you want to:

  • Build staffing forecasts for each activity, at the site level
  • Build staffing forecast at the multi-site activity level and then split that forecast to the site level

Be aware, when WFM splits the interaction volume to the child sites, the forecast splitting algorithm considers:

  • Agent skills
  • Contract availability
  • Activity open hours
  • Time zones
  • Agent hire/termination dates
  • Granted, pre-planned items from the WFM Calendar (days off, time off, shifts, working hours, availability, exceptions, and rotating patterns)

In the figure Model of Contact Center Environment Used by WFM, you can see model of the contact center environment that WFM uses when splitting volumes from the multi-site activity level to the site (child) activity level.

WM 812 Splitting diagram.png
Figure: Model of Contact Center Environment Used by WFM

Key to Figure: Model of the Contact Center Environment

IV—Interaction Volume at the multi-site activity level. There is a separate IV for each of three MSAs (1, 2, 3)

Arrows—The distribution of the activity work from the multi-site activity level to the site level.

1, 2, 3—These numbers represent MSAs.

AHTsubscript—Average Handle Time. When each MSA is split to the site level, there is a separate set of AHT values for each activity/site combination. As described above, this is an option. The user might also choose to use the AHT collected at the multi-site level, in which case, for example, AHT3A and AHT3B would be equivalent.

Circles—The agent pool at each site. At site A, there are two sets of agents. One set of agents has skills that qualify them to work on activities 1 and 2. The other set of agents has skills that qualify them to work on MSAs 1, 2, and 3. At site B, there are also two sets of agents. One set can only work on activity 2, and the other set can work on either MSA 2 or 3.

Model of the Contact Center Environment Explained

As the activity work is distributed from the multi-site level to the site level, WFM must estimate (for each timestep) the percentage of time that an agent will be handling each type of activity for which she is skilled. In some cases, there is only one choice.

For MSA 1: No agents at site B are skilled to handle that activity. Thus, all the workload must be distributed to site A.

For MSA 3: Agents at both site A and site B who can handle this activity. But the diagram shows other factors to consider in distributing activity 3 work:

  • Not every agent at every site can handle activity 3.
  • Some of the agents who can handle activity 3 can also handle other activities.

Therefore, when WFM estimates for each agent how much of each timestep should be allocated to a certain type of work, WFM will consider:

  • The demand for the activity
  • The number of agents who can handle that activity across all sites
  • The work allocation of these other agents

Volume Splitting Using Percentages

You can specify a percentage to allocate volumes from a multi-site activity to each Child (site) activity or apply a template. The interval can be the entire forecast scenario, weekday, or timestep.

For more information about this feature, see the Web for Supervisor Help topic Forecast > Forecast Scenarios > Volume Split Wizard.

Staffing Splitting

As described above in Scenario B, for virtual contact centers, you can build a staffing forecast at the multi-site activity level and then split that staffing forecast across the child activities. This allows the enterprise to more accurately model a virtual routing environment where there is an efficiency gain in the way that calls are handled. WFM recalculates service objectives at this multi-site level and makes these calculations available in the Performance and Schedule views, and in reports.

When building the staffing forecast at the MSA level, you may specify the indirectly occupied time (IOT) and service objectives.

However, you cannot specify the hourly wage or paid hours a day when building the MSA staffing forecast. Instead, you specify those values during the splitting process, when you split the calculated staffing from the MSA level to the child activity level.

Tip
Before you split the staffing forecast from the MSA level to the child activity level, you must first split the volume forecast so that the staffing splitting algorithm knows the resource demand at each site. The staffing splitting wizard gives you the option to consider the AHT values of the child activities. You can use it to better estimate how to distribute staffing requirements across child activities. Although the staffing splitting wizard splits calculated staffing by default, it offers you the option to split required staffing.

After the staffing split is accomplished, you can view results data for calculated staffing (and optionally, required staffing) at the child activity level.

You can examine this data at the MSA level or as the sum or weighted average of the child activities, in these views:

  • Schedule Coverage
  • Intra-Day Schedule
  • Schedule Summary
  • Performance views

You can manipulate the MSA staffing results in the same way that you can manipulate child activity staffing. Forecast graphs are also available for MSA staffing.

Multi-Skill Forecasting

A multi-skilled contact center presents an opportunity for increased productivity.

An agent might be idle in a single-skill environment because she cannot answer calls that are queuing for an activity/skill which she may posses—but a skill that the schedule prevents her from using.

In a multi-skilled environment, she can use her additional skills to answer those calls.

Tip
A high-load environment does not present much opportunity for increased efficiency, because the agents have very little idle time. However, in an overstaffed environment, agents have more idle time and can use their multiple skills to increase efficiency.

How WFM Supports Multi-Skilled Agents

A multi-skilled agent is qualified to work on multiple activities, and therefore may perform different types of work during a shift.

In a multi-skill environment, an agent might be available for multiple activities during any timestep. That agent can be scheduled to work for an activity for only part of a time interval, and only the fraction of the time period during which she or he works is counted.

Because of this, the value for staffing can be expressed as a fraction. Consider the following example of a 15-minute timestep:

Example: An agent is scheduled to work on Activity A for 10 minutes and for 5 minutes on Activity B. She is counted as 2/3 (or .667) of an agent for Activity A, and as 1/3 (or .333) of an agent for Activity B.

Enabling Multi-Skill Support

To enable multi-skill support, follow these steps:

  1. Open Genesys Administrator.
  2. Open the WFM Server Application.
  3. From the Options tab, open the section [ScheduleService].
  4. Create a new option named SplitMS and set the value to true. (See the figure Enable Multi-Skill Support.)

WM 851 SplitMS true.png
Figure: Enable Multi-Skill Support

Calculating Multi-Skill Equivalents

Consider the comparison of Single Skill Equivalents (SSE) to Multi-Skill Equivalents (MSE) in the figure Comparing Multi-Skill and Single-Skill Equivalents.

The Multi-Skilled forecasting algorithm takes into account how many agents (with their various skill sets) could be available to work on each Activity, as well as how the occupancy of an average agent would be divided among this Activity and the other Activities on which the agent could work.

WM 812 multiskill 1.png
Figure: Comparing Multi-Skill and Single-Skill Equivalents

When building a schedule, WFM can optionally use the staffing forecast in Multi-Skilled Equivalents (MSE) while taking into account agents that the schedule is being built for, as well as agents for whom schedules have already been built.

If the Multi-Skilled Equivalents option is set, in the Performance views/reports and Schedule views/reports, coverage for an Activity is based on MSEs, calculated from actual agent schedules. See the figure Multi-Skill Gains, which depicts multi-skill gains.

WM 812 multiskill 2.png
Figure: Multi-Skill Gains

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on April 18, 2018, at 03:42.