VCT work queue configuration
When creating or editing a VCT work queue Entity that represents demand in WFM. Queues help predict workload by multiplying the volume of customer interactions by their expected handling time., define or update data about the work queue.
Setting |
Description |
---|---|
As of |
Specifies the date from which to view or set the Activity Handling Time (AHT) Inbound scheduling statistic in WFM that measures the amount of time of an average customer interaction in a defined time interval (up until the resolution). for the work queue. |
Use Volume Capture |
Specifies the work queue as a VCT work queue. Once this check box is selected, the system displays the remaining fields for defining the work queue as a VCT work queue. |
Type |
Specifies the type of VCT work queue:
|
Shown on Work Page |
Indicates whether you can distinguish a manual entry VCT queue from an automated queue, without requiring the creation of suborganizations to hide the automated VCT queues. If you select this check box, the queue is displayed on the Work page under My Volumes in the My Home module. |
Activity Handling Time (in seconds) |
Specifies the Activity Handling Time (AHT) in seconds for the work queue. To enter effective dates for the AHT, select the icon to the right of the field. |
Arrival Pattern |
Specifies the type of arrival pattern:
|
LQF Only |
Determines whether the work queue is available for VCT or VCT data imports. If this check box is selected, the work queue is not available for VCT or VCT data imports. |
Complete the following fields if you want the work volume from the work queue to flow to a target queue: |
|
Add |
Allows you to add a target queue to which the work volume from the defined work queue flows into. |
Multi Selection |
Allows you to select multiple target queues. |
Source Event |
Specifies the type of event from the source queue that causes the work item to flow from the source work queue to the target work queue. Typically, the source event is Check-in. |
Target Event |
Specifies the type of event where the target queue receives the work coming from the source queue. This event could be one of the following:
|
Target Work Queue(s) |
Specifies the work queue into which the work volume from the source queue flows into. |
Proportion Type |
Specifies how to calculate the work that flows from one queue to another:
|
Period (Weeks) |
Specifies the number of weeks the system considers when calculating the work flow from one queue to another. |
Proportion (Pct) |
Specifies the proportion of work that flows from the source work queue to the target work queue. |
Bundle Size |
Optional: Specifies the required number of items sent in a bundle from the source queue to the target queue. Items from the source queue are not sent to employees working on the target queue until the required bundle size is reached. |
Lag (Hrs) |
Optional: Specifies the number of hours of lag time between bundles sent from the source queue to the target queue. |
Lag (Mins) |
Optional: Specifies the number of minutes of lag time between bundles sent from the source queue to the target queue. |
Lag times between bundles
The Lag (Hrs) and Lag (Mins) fields allow adding a delay in creating the forecast for target queues in a linked queue forecasting chain. If there is a delay in processing that is not modeled by an activity Core component of both schedules and time records in Workforce Management (WFM). When an employee performs any kind of work, activities specify the scheduled work and capture employee adherence to their schedule., it can be modeled through a bundle lag.
Example: Lag between bundles
Queue A produces 10 units of work at 9:00 AM. It is chained 100% to Queue B. Without a bundle lag time, the 10 units of work would immediately be pushed to Queue B as an arrival. However, with a bundle lag time of two hours, it becomes an arrival for Queue B at 11:00 AM, not 9:00 AM.