Jump to: navigation, search

Schedule Build Parameters

This content may not be the latest Genesys Engage cloud content. To find the latest content, go to Workforce Management in Genesys Engage cloud.

Use the Schedule Build Wizard's Parameters screen to select parameters for the selected sites from the previous screen. Each site is a node in a tree on the left-hand side of the screen. Click the node to open the tree and display that site's build parameters. Select a parameter in the tree (on the left,) and you can select, specify, or disable all of its options on the right side of the screen.

The parameters are:

Team Synchronicity

Specify these parameters:

Synchronize Days Off Select this check box to specify that days off should be synchronized for all teams.
Synchronize By Use the radio buttons to specify the synchronization combinations to apply when building the schedule:
  • No additional synchronization
  • Shift Start Time—If checked, use the duration control Maximum Start Time Difference to specify the maximum difference between shift start times inside the team. Use the format HH:MM; where 02:59 is two hours and fifty-nine minutes.
  • Paid Duration
  • Shift Start Time and Paid Duration
  • Shift Start Time, Paid Duration, and Meals
  • Shift Start Time, Paid Duration, Meals and Breaks
  • Paid Duration and Meals
  • Paid Duration, Meals and Breaks
Maximum Start Time Difference Specify in hh:mm format. Range is from 0 (zero) to 23:59.
Apply constraints only to the same contracts inside team Select this check box to specify that while synchronizing teams, WFM must take configured contract information into account while creating the schedule. By default, this check box is cleared.
Synchronization applies to all teams under the selected site.

Shared Transport Constraints

Shared Transport is known by many different names worldwide—bus, carpool, ride share, lift share, and paratransit, for example. See Wikipedia for details.

If you selected Shared Transport Constraints in the Select Sites (and Build Options) dialog box, this selection is enabled and Team Synchronicity is disabled (team and shared transport group restraints are mutually exclusive). Type, or use the spinner controls, to specify the maximum deviation between starts and ends of shifts. You can specify any value between 1 minute and 23 hours, 59 minutes; most practical values will be less than 30 minutes.

The participants in a shared transport group can work in shifts that begin and end at different times; however, they should not deviate greatly, or the shared transport group becomes impractical. You are specifying the maximum allowable deviation in the schedule of each participant in the same shared transport group.

Preference Fulfillment Options

The Force Maximum Preference Fulfillment parameter optimizes the number of profiles for the selected site. See How the Preference Fulfillment Ratio Works for more information.

Select this parameter to:

  • Treat all preferences with preferred status as granted.
  • Resolve all granted and would-be granted preferences.
  • Use the result to build the schedule.
  • Disable all other options on the page.

Clear this parameter (default) to disable the options listed above, and enable the options listed below.

Prioritization Specifies how WFM Builder favors agent requests when building the schedule. Select one item from the drop-down list:
  • None specifies no prioritization during schedule building.
  • Seniority favors agents by their hire dates (which are indicated in the table on the lower part of the Preference Fulfillment screen).
  • Rank favors agents by their rank, as defined by a supervisor in the Agent Properties (and also indicated in the table on the lower part of the Preference Fulfillment screen).
  • Seniority + Rank favors agents by Seniority first, and if that results in a tie, then uses Rank as the criterion.
Emphasis Controls how closely the build process considers skill coverage when it assigns priorities to preferences. Select one item from the drop-down list:
  • None specifies that agents' preferences are assigned on the basis of seniority and/or rank alone, using the percentages assigned to the agents (as shown in the % column). This option tends to favor multiskilled optimization over preference fulfillment.
  • Low specifies that schedule building places more emphasis on preference fulfillment, without sacrificing multiskilled optimization.
  • Medium specifies that schedule building accommodates preferences if a loss in any skill coverage is caused only by an exception.
  • Strong specifies that schedule building does not consider multiskilled optimization when it allocates preferences.
Emphasis is disabled when you select Team Constraints in the Select Sites (and Build Options) wizard page.
Fulfillment Sets the minimum and maximum percentage of preferences that schedule building fulfills. For example, if you set Min to 10% and Max to 80%, every agent has at least 10% of his or her preferences fulfilled, while the highest-ranking or most senior agent has at least 80% of his or her preferences fulfilled. Agents with intermediate standing receive a percentage between the two extremes (their exact percentage depends on their place in the hierarchy).

Enter or select the Min(imum) and Max(imum) values. The range is 0—100 and Min. must be lower than Max.


Schedule building applies these percentage values separately to each preference type and satisfies all preferences, when possible. For example, if an agent has a 50% fulfillment ratio, and makes 20 shift preferences and 8 day-off preferences over a 4-week period, the agent is guaranteed to receive at least 10 preferred shifts and 4 preferred days off, unless this preference fulfillment is prohibited by other working rules.

In cases where the preference fulfillment ratio cannot be achieved due to working-rule violations, WFM Web displays a warning indicating that the schedule results may not be desirable. WFM Web attempts to satisfy more than the minimum level of preference fulfillment, as long as the results do not cause understaffing.

Calculate Re-sorts the table below by the % column, which will then display each agent's calculated chance of preference fulfillment. (Use the table's vertical scroll bar to display more agents.)
  • Click Calculate.
Adjust Fulfillment Ratio Adjusts the preference fulfillment ratio using the controls below the table.
  1. In the Adjust Fulfillment Ratio text box, enter a value or use the up or down arrows to modify the displayed value. Range is -100 to +100.
  2. Click Adjust.
In the % column, WFM Web adds your adjustment to, or subtracts it from, all agents' chances of preference fulfillment. However, it does not increase any agent's fulfillment ratio above 100% or reduce it below 0%.

How the Preference Fulfillment Ratio Works

The preference fulfillment ratio modifies the impact of the agent prioritization settings.

  • The preference fulfillment functionality applies only to calendar items that an agent can request (Shift, Day Off, and Availability). Also these items may be inserted into the calendar by a supervisor. Any other preferred calendar items (such as Exceptions, Times Off, Working Hours) are not fulfilled; they remain in Preferred status even if 100% fulfillment is defined.
  • If you set the ratio to a value greater than 0, then each agent's chances of having his or her preferences fulfilled is increased by whatever value you entered, up to the maximum percentage that you set for the Max option.
  • If you set the ratio to a value less than 0, then every agent's preference fulfillment ratio is reduced by whatever value you entered, down to the minimum percentage that you set for the Min option.
The preference fulfillment ratio cannot surpass the Min and Max percentage values set under Preference Fulfillment Options. For example, if Max is set to 80%, and the preference fulfillment ratio is set to 100 (maximum preference fulfillment), all agents will top out at 80%. If Max is set to 80% and Min is set to 10%, and the preference fulfillment ratio is set to -30 (favoring optimization), then agents who would be at 80% are dropped to 50%; agents at 40% are dropped to 10%; and all agents with prioritizations lower than 40% also drop to 10%.

Optimize Profiles

The grid displays all profiles for the selected site. These are the profiles that are based on configured profiles, not profiles that are based on agents. The columns in this grid are:

Profile Profile names.
Min The minimum number of profiles that WFM can use when building the schedule. Range: Empty (default) or any number from 0 to 9999. This value is editable, and must be less than the value of Max.
Max The maximum number of profiles that WFM can use when building the schedule. Range: Empty (default) or any number from 1 to 9999. This value is editable, and must be greater than the value of Min.
Existing The number of actual profiles already present in the selected schedule scenario.
Growth Ratio The current growth ratio value that WFM can use for a particular profile when building the schedule. Range: Empty (default) or any number from 1 to 9999. This value is editable.

To archive specific goals for profiles optimization, the following valid parameters must also be considered:

  1. Profiles are excluded from optimization when none of the following are specified: minimum profiles, maximum profiles, or growth ratio. Profiles must be empty.
  2. Profiles with a fixed number of agents must have the minimum profiles = maximum profiles, with both values greater than 0. They do not require optimization, growth ratio is not applicable, and growth ratio fields must be empty.
  3. Profiles participate in optimization when both minimum and maximum values are specified by following these rules: minimum profiles must be > or = 0, maximum profiles must be > 0, and minimum profiles must be < maximum profiles.
    1. Growth ratio is specified—All profiles that participate in profile optimization must have a specified growth ratio > 0 (0 is not a valid value for growth ratio).
    2. Growth ratio not specified—Must be empty for all profiles.
  • You cannot have profiles with growth ratio and without growth ratio in the same schedule. Growth ratio must be specified for all profiles being optimized (see 3a) or none (see 3b). The only exception is in line 1 (above), where profiles are excluded from optimization completely.
  • If minimum profiles = 0, it does not mean that a value is not specified. 0 is a valid value for minimum profiles.


These controls appear at the bottom of the Optimize Profiles pane:

Total Growth Ratio Total of all rows from the grid column Growth Ratio (%). Not editable.
Show configured profiles check box Check to limit filter the grid to show only profiles that have Min and Max parameters specified.

Default: cleared

Show existing profiles check box Check to limit filter the grid to show only profiles that are already present in the selected schedule scenario. Grid column Existing cannot contain 0 (zero).

Default: cleared

Understaff threshold (%) field Enter the understaff threshold that WFM must use when building the schedule.

Range: 0 (no understaffing) to 100 (total understaffing).

Default: 20.

Assign Profiles to Teams

  • Select Use Backfilling of Existing Teams to enable this parameter.
  • Enter a number in the Team Size field.

The schedule scenario that you are building contains profiles and not actual agents in the selected site. You can assign profiles to be used to backfill teams that require it.

The grid displays all non-profile teams in the selected scenario. For each team, you can select the profile should be used to backfill that team. The grid has these columns:

Team The team name.
Profile A drop-down list of possible profile choices:
  • None (default)
  • A list of profiles that corresponds the value of Max on the Optimize Profiles page.

Click Finish to apply your choices and begin the build.

This page was last edited on October 2, 2020, at 12:35.
Comments or questions about this documentation? Contact us for support!