Jump to: navigation, search

CalendarOverScheduleData

Section: CalendarService
Default Value: 0
Valid Values: 0, 1, 2, 3
Changes Take Effect: Immediately
Dependencies: None

Specifies whether or not Calendar data overlaps Schedule data when checking agent time-off balances, enabling the resolution of conflicts between Granted or Preferred time-off items and schedule data.

The valid values are described, as follows:

  • 0—Disables the resolution functionality (do not overlap—default value).
  • 1—Enables overlap of only Granted Calendar time-off and Schedule data.
  • 2—Enables overlap of Granted and Preferred time-off.
  • 3—Enables overlap of Granted and non-wait-listed Preferred time-off. These requests are counted against an agent’s time-off balance and limits:
    • All requests with the status Granted/Not Scheduled.
    • Only wait-listed requests with the status Preferred/Not Scheduled.

WaitlistTimeout

Section: CalendarService
Default Value: 30
Valid Values: Any positive integer, -1
Changes Take Effect: Immediately
Dependencies: None
Modified: 8.5.207.09

Specifies the interval (in minutes) between the processes handling time-off bidding and wait-listed items.

Setting this option value to -1 turns this functionality off.

Tip
In WFM Server 8.5.207.09, the default value was changed to 30 (minutes) from 60 (minutes) and the description was changed to include time-off bidding items.

AutoPublishTimeOffToSchedule

Section: CalendarService
Default Value: 0
Valid Values: 0, 1, 2
Changes Take Effect: Immediately
Dependencies: None

Specifies whether or not Granted time off is published to an agent's schedules when he/she requests time off.

The following valid values describe WFM’s response when agents request time off:

  • 0—Feature is off.
  • 1—Feature is on; a part-day time off cannot overlap exceptions.
  • 2—Feature is on; a part-day time off deletes overlapped exceptions.

CalendarOverScheduleData

Section: CalendarService
Default Value: 0
Valid Values: 0, 1, 2, 3
Changes Take Effect: Immediately
Dependencies: None

Specifies whether or not Calendar data overlaps Schedule data when checking agent time-off balances, enabling the resolution of conflicts between Granted or Preferred time-off items and schedule data.

The valid values are described, as follows:

  • 0—Disables the resolution functionality (do not overlap—default value).
  • 1—Enables overlap of only Granted Calendar time-off and Schedule data.
  • 2—Enables overlap of Granted and Preferred time-off.
  • 3—Enables overlap of Granted and non-wait-listed Preferred time-off. These requests are counted against an agent’s time-off balance and limits:
    • All requests with the status Granted/Not Scheduled.
    • Only wait-listed requests with the status Preferred/Not Scheduled.

Enabling and Configuring Wait-Lists

This topic contains lists and descriptions of the conditions and settings that make Workforce Management (WFM) wait-list functionality possible, and offers or refers to instructions for these tasks:

  • Automatic Approval (sometimes called auto-granting)
  • Auto-publishing
  • Wait-listing
  • Handling preferred time-off requests
  • Making ungranted time-off requests count in a build
  • Improved viewing time-off availability

If WFM cannot immediately grant a time-off request, it puts the request on a waiting list (called wait-listing). When all requirements are met, including configuration, WFM can grant the request and insert it into the Master Schedule automatically.

The information in this topic supplements the information found in Workforce Management Web for Supervisors Help and Workforce Management Web for Agents Help.

Overview

WFM considers all wait-listed time-off requests on a First-In, First-Out (FIFO) basis, using the date and time of the request. To determine if there are slots available for the wait-listed time-off request, the process first considers all time-off instances that are Granted/Granted and Scheduled and have intersecting timesteps with the wait-listed request for time off. If the [CalendarService] CalendarOverScheduleData configuration option in the WFM Server Application is set, then Granted/Not Scheduled time-off instances are also taken into account before processing the wait-list.

Next, WFM considers all Preferred time-off requests that were submitted earlier than the wait-listed request that is currently being processed. Only Preferred time-off instances that count against the time-off limit according to their actual status are considered. Also, if an earlier Preferred request is not valid for time off within the various limits, it is ignored.

You can configure the advance threshold for automated time-off wait-lists. You can also configure the minimum number of weeks in advance that a request can be made for each time-off rule; that minimum number is called the automatic approval threshold. If an ungranted time-off request in the wait-list violates the automatic approval threshold, then WFM removes the request from the wait-list. That time-off request remains in the status Preferred, but it cannot remain wait-listed.

See Enabling Automatic Approval and Configuring the Threshold below.

Events that might change the system’s ability to grant time off, such as the agent’s contract availability status, can affect the validity of any time-off request. Thus, wait-listing takes place on a schedule that is specified by a timeout option.

Enabling and Configuring Wait-Lists

The following sections provides information about enabling and configuring wait-lists, and describes how auto-approvals, thresholds, and auto-publishing affect wait-lists.

Automatic Approval of Time-Off Requests

Wait-list automation is related to automatic approval functionality. The common workflow of wait-list automation is:

  1. An agent’s time-off request is automatically approved, but there are no time-off slots within the limits of the request.
  2. The request is wait-listed until an appropriate time-off slot becomes available, and then it is automatically approved, if possible.
  3. If automatic approval is enabled but the time-off request is beyond the automatic approval threshold, then the request cannot be wait-listed. It is instead saved with the status Preferred.

When do Time-Off Slots Become Available?

Time-off slots become available when:

  • A supervisor declines a time-off request
  • An agent recalls a time-off request
  • An agent or supervisor deletes a time-off request.

Time-off slots are taken (or unavailable) when a Granted or Preferred or Scheduled time-off request is entered.

Tip
Automatic approval must be enabled for wait-lists to work. If automatic approval is not enabled, then the supervisor must manually grant time-off requests and a request cannot be wait-listed, even if requested by the agent.

Viewing Available Time-Off Slots

Now agents can see if the time off that they want is available before they request it. At the Time Off screen, just hover the cursor over any time slot, and you will see time-off limits and wait-list data about the time slot in a popup.

Enabling Automatic Approval and Configuring the Threshold

Automatic Approval must be enabled for wait-lists to work.

To learn about automatic approval, see Rules for Requests in the Workforce Management Web for Supervisors Help.

To enable and configure automatic approval, see the options Automatically approve time-off request if: Request is made by the following number of weeks in advance <number> and Minimum requested time off is <number> (hours and minutes).

Configuring Auto-Publishing

When WFM automatically approves a time-off request, it can also insert it into the Master Schedule automatically, if auto-publishing is enabled.

To enable and configure auto-publishing, use Genesys Administrator to set the WFM Server Application [CalendarService] AutoPublishTimeOffToSchedule configuration option value to 1 or 2.

Configuring Wait-Lists

Wait-listing is a background function that is enabled by circumstances and configuration. The circumstances are: automatic approval must be enabled and an agent’s time-off request must be valid (time-off slots and agent credit must be available).

To configure wait-listing, use Genesys Administrator to set the WFM Server Application [CalendarService]] WaitlistTimeout configuration option.

When are Time-Off Requests Wait-Listed?

  • When the time-off request is valid (for example, not for time in the past).
  • When the time-off request is not for more time than the agent’s time-off balance contains.
  • When the automatic approval option is enabled.

WFM will only wait-list those time-off requests that would have been automatically approved, if not for time-off limits. Also:

  • If automatic approval is not set up in the accrual rule or the threshold has been passed, then that particular time-off item cannot be wait-listed.
  • The requesting agent should have sufficient time-off balance and there can be no other restrictions.
  • If limits allow, the request will be granted and not wait-listed.

Treatment of Preferred Time-Off Requests

Preferred time-off requests (having the status Preferred) are not considered during schedule building. When a master schedule is published, Preferred time off does not count against limits and agent balance anymore, because they are usually not scheduled.

To override this functionality, use Configuration Manager or Genesys Administrator to set the WFM Server Application [CalendarService] CalendarOverScheduleData configuration option, which makes unscheduled time off count against the agent balance and time-off limits.

See Requesting Time Off in the Workforce Management Web for Agents Help.

Use Cases and Notes

The following use cases discuss scenarios to compare availability and seniority, and provide some additional important rules to keep in mind.

When Availability Overrides Seniority

  1. Request A asks for time slots that are not available (8AM-6PM). The time 8-9AM is not available, and so Request A is wait-listed.
  2. Request B comes in later, but asks for time slots that are available (10AM-6PM).

The Result:
Request B is granted and Request A remains wait-listed, even though Request B came in later.

When Seniority Overrides Availability

  1. Request A is wait-listed. The time slots for automatic approval of this request become available, but the wait-list timeout has not yet expired.So this request remains wait-listed.
  2. Request B comes in later and asks for the same time slots as Request A.

The Result:

  • If the time slots are available for both requests, Request B is honored immediately and Request A is honored after the wait-list timeout expires.
  • If the time slots are available for only one request, Request B is wait-listed and after the wait-list timeout expires, Request A is granted first.

Rules to Remember

  • When the wait-list process can grant a request, it changes the saved status of that request to granted (and removes the internal wait-list flag).
  • If the auto-publish and wait-list functions are set up together, then granted requests are published to the master schedule.
  • A wait-listed request can be granted only if: automatic approval is enabled, the time-off request is valid, there are no other restrictions.

WFM removes from the wait-list any time-off request that has expired (the timesteps that it specifies are in the past) or belongs to an agent with no time-off balance.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on September 27, 2017, at 09:15.