WFO V15.1 Reports Guide
WFO V15.1 Reports Guide
Workforce Optimization
Reports Guide
Version 15.1
All materials (regardless of form and including, without limitation, software applications,
documentation, and any other information relating to Verint Systems, its products or services) are
the exclusive property of Verint Systems Inc. Only expressly authorized individuals under
obligations of confidentiality are permitted to review materials in this document. By reviewing
these materials, you agree to not disclose these materials to any third party unless expressly
authorized by Verint Systems, and to protect the materials as confidential and trade secret
information. Any unauthorized review, retransmission, dissemination or other use of these
materials is strictly prohibited. If you are not authorized to review these materials, please return
these materials (and any copies) from where they were obtained. All materials found herein are
provided “AS IS” and without warranty of any kind.
Verint Systems Inc. does not warrant, guarantee or make any representation regarding the use or
the results of the use of the information, links, tools, and materials in terms of the accuracy,
reliability, quality, validity, stability, completeness, currentness, or otherwise of its content or
products. The entire risk as to the use, results and performance of information, links, tools and
materials provided or referenced herein is assumed by the user. Verint Systems Inc. shall not be
liable for damages resulting from the use, misuse or unlawful use of the information, links, tools,
and materials contained or referenced herein.
Any third party technology that may be appropriate or necessary for use with the Verint Product is
licensed to you only for use with the Verint Product under the terms of the third party license
agreement specified in the Documentation, the Software or as provided online at
http://verint.com/thirdpartylicense. You may not take any action that would separate the third
party technology from the Verint Product. Unless otherwise permitted under the terms of the third
party license agreement, you agree to only use the third party technology in conjunction with the
Verint Product.
The Verint Systems Inc. products are protected by one or more U.S., European or International
Patents and other U.S. and International Patents and Patents Pending.
All marks referenced herein with the ® or ™ symbol are registered trademarks or trademarks of
Verint Systems Inc. or its subsidiaries. All rights reserved. All other marks are trademarks of their
respective owners.
2 Framework Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Workforce Optimization Reports Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Activity Manager Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Activity Cost (Unburdened) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Activity Roll Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Daily Activity Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Daily Time Record Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Detailed Time Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Employee Activity Roll Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Employee Activity Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Organization Activity Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Adherence Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Adherence Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Adherence Minutes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Adherence Numbers by Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Adherence Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Contents
Coaching Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Coaching Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Coaching Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Management Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Active Employees . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Employee Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Tenant Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Tenant Usage Summary View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Tenant Usage Detailed View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Tenant Usage Reporting Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Privileges tracked for usage report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
user Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Operations Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Capacity Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Daily Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Intraday Productivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Drill down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Productivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Drill down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Productivity & Effectiveness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
VCT Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
WIT Aging Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
WIT Aging vs. Deadline Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
WIT Drilldown Chart Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
WIT Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Outbound Performance Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Outbound Daily Forecast Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Outbound Daily Performance Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Outbound Forecast Lists Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Outbound Monthly Performance Assessment Summary . . . . . . . . . . . . . . . . . . . 122
Performance Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Daily Comprehensive Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Daily Forecast Assessment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Daily Service Goals and Backlog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Monthly Forecast Assessment Summary . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Monthly Service Goals Assessment Summary . . . . . . . . . . . . . . . . . . . . . . . . 134
Service Goals Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Retail Service Level Heat Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Staffing Number Assessment By Interval . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Recording Compliance Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Data Integrity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Scorecard Dashboard Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Single KPI Trend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
Single KPI Trend vs. Peer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Team Aggregate Multi KPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Team Detail Dual KPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Switch Call ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Recorders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Channel number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Recorder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Speech Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Emotions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Distribution options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
None . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Conditional custom data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Distribute by time intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Distribute by time periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Speech Analytics categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Display selected distribution for all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Display options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371
Display name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371
Sort options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371
Display format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Productivity Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373
Enable drill down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373
Evaluations/Assessments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Evaluated/Assessed by . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Form Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Reason . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Score . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Display Evaluation Data Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
This document details the various reports available within the Report module.
This document is intended primarily for viewing online. However, the format of the
document is based on that of a printed manual, to support customers who print all or
portions of the document. For similar reasons, entries in the Table of Contents, cross
references, and index entries refer to page numbers. Those same entries function as
hyperlinks for ease of use when the document is viewed electronically.
NOTE Colors may not print legibly on black and white printers. If you are using a
non-color printer, select the option to print colors as black.
In addition, please note that the screen shots used in this guide are for illustrative
purposes only. There may be some differences between what you see in the product
and these screenshots, but those differences should not be significant or affect the
accuracy of the information contained in this guide.
Intended audience
This guide is designed to be used by managers, supervisors, schedulers, and
administrators. They are expected to be experienced in working with contact center
equipment and software applications and computer workstation hardware and software.
Preface About this guide
Documentation feedback
We strive to produce the highest-quality documentation products and welcome your
feedback. If you have comments or suggestions about our guides or help, you can email
us. With your feedback, include the following information:
Document name and revision number or title of help topic and product version
Your suggestion for correcting or improving the documentation
Send your messages to [email protected].
The email address is only for documentation feedback. If you have a technical question,
contact Technical Support.
Technical support
Our goal at Verint Systems is to provide you with the best products backed by a high-
quality support network with various resource options. Verint Systems Technical Support
services include email and telephone support.
To learn more about the support options that best suit your needs, visit us at
verint.com/EISsupport.
Verint University
In addition to documentation, help, and support services, Verint Systems also offers
both classroom-based and online learning alternatives to suit your specific needs.
To learn more about available training options from Verint Systems, visit us at
verint.com/training.
Topics
Reports overview, page 12
Ad Hoc Reports, page 13
Report roles and privileges, page 14
Requests & Results - reporting workspace, page 15
Reporting workflow, page 18
Report instance configuration, page 19
Report instance management, page 22
Chapter 1 - Working with Reports Reports overview
Reports overview
Enterprises typically generate huge amounts of data on a daily basis. The key to
effective management and optimization is to connect to the right data at the right time.
The suite’s reporting application, based on Microsoft’s SQL Server Reporting Services
(SSRS), provides an easy and scalable mechanism to monitor and analyze the
performance and effectiveness of call center operations.
Review the key features and functionality of the reporting application:
Reporting workspace
The Requests & Results reporting workspace separates report setup and configuration
from report management through the Parameters and Instances tabs respectively.
Create new reports in the Parameters tab, and manage existing reports through the
Instances tab.
Related topics
Report roles and privileges, page 14
Ad Hoc Reports, page 13
Requests & Results - reporting workspace, page 15
Reporting workflow, page 18
Report instance configuration, page 19
Report instance management, page 22
Ad Hoc Reports
Ad Hoc Reports allow users to create reports using the SQL Server Report Builder.
Related information
Roles and privileges Reference
Related topics
Report Selection pane, page 15
Instances page, page 15
Parameters, page 16
Related topics
Instances page, page 15
Parameters, page 16
Framework Reports, page 25
Interactions and Analytics reports overview, page 262
Instances page
The Instances page shows a tabular grid of all instances for a selected report type and
action buttons to manage the instances.
The term instance refers to a saved report that is scheduled to be generated with or
without recurrence, or an unmanaged report generated on demand.
Status: the status of the report instance, and can be one of the following:
Success: the report has successfully completed its run.
Failed: the report failed to be generated.
Owner: the name of the logged-in user who generated the report.
Report management
The buttons at the bottom grid allow you to manage all or specific report instances.
View: open the report in a new browser window for viewing online. Optionally,
export the data to the required format.
Delete: delete one or more report instances.
Related topics
Parameters, page 16
Reporting workflow, page 18
View unmanaged and saved instances, page 22
Delete a report instance, page 24
Framework Reports, page 25
Interactions and Analytics reports overview, page 262
Parameters
The Parameters page shows the parameter, scheduling, and distribution settings for the
selected report type.
You can create a new report instance, modify the settings of an existing instance, or
delete an existing instance
Parameters
The parameters determine the data that is included in the report. The report type you
select determines the parameters you need to configure. Each report type is associated
with a default set of parameters which are used when no specific parameters are
defined.
Generation
Save and generate the report instance at the scheduled date and time, or generate it
on-demand for immediate viewing.
Related topics
Instances page, page 15
Reporting workflow, page 18
Create and save a new report instance, page 19
Delete a report instance, page 24
Generate on-demand report instances, page 20
Framework Reports Parameters, page 253
Interactions and Analytics report parameters, page 347
Reporting workflow
The workflow describes the steps to create, generate, and manage report instances
include:
1 Access the reporting application and select report type (Reports > Requests &
Results > Report Selection).
2 Configure the report settings (Parameters), including:
a. Parameters
b. Report schedule
c. Distribution
3 Save instance to generate as scheduled or generate an instance on-demand
(Parameters).
4 View report instance (Instances).
5 Modify report parameters (Parameters).
Related information
Create and save a new report instance, page 19
Generate on-demand report instances, page 20
View unmanaged and saved instances, page 22
Modify a report instance, page 23
Export a report instance, page 23
Delete a report instance, page 24
Related topics
Create and save a new report instance, page 19
Generate on-demand report instances, page 20
TIP At any point, to undo the most recent change to any report setting, click
Revert.
Procedure
1 Select Reports > Requests & Results.
2 From the Report Selection pane on the left, select the report type with the instance
you want to create.
3 Click the Parameters tab.
4 In the Parameters section, do one of the following:
For Framework reports, define the parameters.
For Interactions and Analysis reports, click the filter icon, and define the
parameters.
5 In the Schedule section, define the report name, schedule and output format:
a. In the Name field, type a name for the report. This is the name assigned to the
report instance.
b. Optional. In the Note field, type any comment
c. Define the schedule for the report:
To generate the report once on a specific date, select Run Once and then
select the date and time.
To generate the report according to the scheduled frequency, select
Recurring and then select the date and time, and the frequency at which to
generate the report.
d. From the Output Format dropdown, select the format for the report as either
HTML4, PDF or Excel.
b. In the Email List field, define the email addresses to which to send the reports.
You can send the report to any valid email address.
NOTE Separate multiple email addresses with semi colons.
7 Click Save.
The report instance is added to the Instances tab with the date and time
Related topics
Framework Reports Parameters, page 253
Interactions and Analytics report parameters, page 347
Generate on-demand report instances, page 20
Report instance management, page 22
Procedure
1 To generate an on-demand instance, do one of the following:
To generate and save the instance for later viewing, click Run Now. The report
opens in a new browser window. The Instances tab displays options to either
save or delete the report instance.
Continue with Step 2.
To generate without saving the instance, click Run Interactively.
Related topics
Report instance management, page 22
Related topics
View unmanaged and saved instances, page 22
Modify a report instance, page 23
Export a report instance, page 23
Delete a report instance, page 24
TIP For Interactions and Analysis reports, unmanaged instances are shown
only at the report group level.
Procedure
1 Select Reports > Requests & Results.
2 Click the Instances tab.
3 From the Report Selection pane on the left, do one of the following:
To see all instances for a report group, select the title of the report group. For
example, to see instances for all productivity reports, select Productivity
Reports.
To see all instances for a specific report type, expand the report group and then
select the report type. For example, to see all instances of the Employee
Productivity vs. Quality report type, select it.
To see an instance, select that instance.
The Report Instances grid displays all instances for the report group or report type.
4 To view the instance online, double-click or select the instance, and then click View.
The report opens in a new browser window. Use the paging controls and Find
options to navigate through the report.
5 Optionally, export the report to the required format, or as an XML data feed for
offline analysis, as described in Export a report instance, page 23.
Related topics
Delete a report instance, page 24
Procedure
1 Select Reports > Requests & Results, and then click the Parameters tab.
2 From the Report Selection pane on the left, select the report instance you want to
edit.
3 Change the parameters, output format and distributions settings as needed.
4 Click Save.
Related topics
Report instance configuration, page 19
Delete a report instance, page 24
Related topics
View unmanaged and saved instances, page 22
Delete a report instance, page 24
Procedure
1 Select Reports > Requests & Results.
2 Click the Instances or the Parameters tab.
3 From the Report Selection pane on the left, select the report instance you want to
delete.
4 Click Delete, and then click Yes to confirm.
The report instance is deleted from the Instances tab.
Related topics
Report instance management, page 22
Framework Reports
Topics
Workforce Optimization Reports Overview, page 26
Activity Manager Reports, page 27
Adherence Reports, page 43
Coaching Reports, page 54
Management Reports, page 61
Operations Reports, page 70
Outbound Performance Reports, page 114
Performance Reports, page 125
Recording Compliance Reports, page 142
Scorecard Dashboard Reports, page 145
Scorecards Reports, page 153
Shift Bidding Reports, page 155
Staffing Reports, page 171
Time Banking Reports, page 202
Time Off Reports, page 206
Work Force Planning Reports, page 243
Other Reports, page 251
Obsolete Reports, page 252
Chapter 2 - Framework Reports Workforce Optimization Reports Overview
Topics
Activity Cost (Unburdened), page 27
Activity Roll Up, page 29
Daily Activity Summary, page 31
Daily Time Record Summary, page 33
Detailed Time Record, page 35
Employee Activity Roll Up, page 37
Employee Activity Summary, page 38
Organization Activity Summary, page 41
Management can use this report to review the amount of time that specific employees
spend in each activity, including paid, unpaid, and total time, summarized over the
selected period of time. Managers can run this report for a week or a month to see how
each employee is being utilized over that time period, and determine whether particular
employees are spending too much time in breaks, after-call work, or other activities, or
if they are not spending enough time on the phones. If employee wage information is
entered, the activity subtotals on the report can also be used to estimate the cost of
specific activities.
Inputs
Employee Filter: Indicates the set of employees to report on.
Time Frame (reports that are in view time zone): These reports generally return a
single aggregation for the specified time period or a set of records corresponding to
all events that start in or intersect the time period.
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from the current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Time Zone: Indicates the time zone used for display.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For example,
2 hours 30 minutes would be shown as 2.5 hours.
Activity Roll Up
Default Access Rights
This report can be run by the following roles: Manager
Overview
This report provides information on the time spent on each given activity for the
selected time period and/or organization. This report looks at each activity for the
selected time period. It does not give information on a per employee basis.
This report is very similar to Activity Cost (Unburdened), except that it aggregates
over all activities and does not include the Estimated Cost and Wage columns.
Management can use this report to review the amount of time that an organization
spends in each activity, including paid, unpaid, and total time, summarized over the
selected period of time. Managers can run this report for a week or a month to see how
the organization is being utilized over that time period.
Inputs
Employee Filter: Indicates the set of employees to report on. (This report is in the
organization’s time zone.)
Time Frame (reports that are by day and in the organization’s time zone):
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Time Zone: Indicates the time zone used for display.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s From
field shows the value of that parameter, such as From: Last 30 days. This is in contrast to
previous releases, where the From field showed a date.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For example, 2
hours 30 minutes would be shown as 2.5 hours.
This report is similar to the Activity Roll-up report, but for each activity, this report
gives a summary of the time spent in the activity for each day within the selected time
period. This report can also be run for a week or a month and analyzed to identify any
trends in how much time is spent in particular activities day after day. If the typical
selections for reporting are entire organizations and full days, this report can be used as
an alternative to the Activity Roll-up report, without the need to create filters for each
organization.
Inputs
Employee Filter: Indicates the set of employees to report on. (This report is in
organization time zone)
Time Frame (reports that are by day and in organization time zone):
- Last <X> days: This field specifies which days to report on. This mode should
return the last X completed workdays for an organization, however, as
implemented, it sets the From-date to the current day in the time zone of the
SQL Server computer minus X days and the To-date to the current day in the
time zone of the SQL Server computer. Depending on the difference between
the SQL Server computer’s time zone and the organization's time zone and day/
week boundary, this may not be the last X completed workdays.
- From/To date (reports that are in organization time zone): These reports are
generally by day or by week. Here, by day/week means the organization's
workday or workweek, considering day and week boundaries. So, let’s say you
want to report on the workdays 1/10/04 - 1/15/04. The workday named, 1/
10/04, is actually 1/10/04 8:00am - 1/11/04 8:00 a.m. (in the organization's
time zone). It will map differently in GMT. Now, let’s also assume that you are
reporting on multiple organizations, each with different time zones and day/
week boundaries. You are requesting data on 1/10/04 - 1/15/04, but this could
map to different absolute times for each organization. For example:
Org A: 1/10/04 3:00 a.m. - 1/11/04 3:00 a.m., 1/11/04 3:00 a.m. - 1/12/04
3:00 a.m....
Org B: 1/10/04 8:00 a.m. - 1/11/04 8:00 a.m., 1/11/04 8:00 a.m. - 1/12/04
8:00 a.m....
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s From
field shows the value of that parameter, such as From: Last 30 days. This is in contrast to
previous releases, where the From field showed a date.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For example, 2
hours 30 minutes would be shown as 2.5 hours.
NOTE For the Group by Employee option, there is an entry for each time record (normally one per
day). All time record entries that belong to a time record that begins on same workday are
counted on that workday. The time entry itself does not actually have to begin on that workday.
When grouped by employee, supervisors or managers can use this report to verify the
amount of time worked by individual employees during a specific period, including
verifying hours worked on specific days and/or totals for a pay period. Managers can
compare this data with submitted timesheets or other work records to find
discrepancies.
Inputs
Employee Filter: Indicates the set of employees to report on. (This report is in
organization time zone.)
Time Frame (reports that are by day and in organization time zone):
- Last <X> days: This field specifies which days to report on. This mode should
return the last X completed workdays for an organization, however, as
implemented, it sets the From-date to the current day in the time zone of the
SQL Server computer minus X days and the To-date to the current day in the
time zone of the SQL Server computer. Depending on the difference between
the SQL Server computer's time zone and the organization's time zone and day/
week boundary, this may not be the last X completed workdays.
- From/To date (reports that are in organization time zone): These reports are
generally by day or by week. Here, by day/week means the organization's
workday or workweek, considering day and week boundaries. So, let’s say we
want to report on the workdays 1/10/04 - 1/15/04. The workday named, 1/
10/04, is actually 1/10/04 8:00am - 1/11/04 8:00am (in the organization's time
zone). It will map differently in GMT. Now let’s also assume that we are
reporting on multiple organizations, each with different time zones and day/
week boundaries. We are requesting data on 1/10/04 - 1/15/04, but this could
map to different absolute times for each organization. For example:
Org A: 1/10/04 3:00 a.m. - 1/11/04 3:00 a.m., 1/11/04 3:00 a.m. - 1/12/04
3:00 a.m....
Org B: 1/10/04 8:00 a.m. - 1/11/04 8:00 a.m., 1/11/04 8:00 a.m. - 1/12/04
8:00 a.m....
Group by:
- Employee: Aggregates time entries per employee.
- Organization: Aggregates time entries per organization.
- Supervisor: Aggregates time entries per supervisor.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s From
field shows the value of that parameter, such as From: Last 30 days. This is in contrast to
previous releases, where the From field showed a date.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For example, 2
hours 30 minutes would be shown as 2.5 hours.
Related topics
Activity Cost (Unburdened), page 27
You can use this report to see the details of what an employee did throughout the day. It
is particularly useful when investigating issues with employee activity discovered in
summary reports, such as the Daily Time Record Summary report.
Inputs
Employee Filter: Indicates the set of employees to report on. (This report is in the
organization’s time zone.)
Time Frame (reports that are by day and in organization time zone):
- Last <X> days: This field specifies which days to report on. This mode should
return the last X completed workdays for an organization; however, as
implemented, it sets the From-date to the current day in the time zone of the
SQL Server computer minus X days and the To-date to the current day in the
time zone of the SQL Server computer. Depending on the difference between
the SQL Server computer's time zone and the organization's time zone and day/
week boundary, this may not be the last X completed workdays.
- From/To date (reports that are in organization time zone): These reports are
generally by day or by week. Here, by day/week means the organization's
workday or workweek, considering day and week boundaries. So, let’s say you
want to report on the workdays 1/10/04 through 1/15/04. The workday
named 1/10/04 is actually 1/10/04 8:00 a.m. through 1/11/04 8:00 a.m. (in the
organization's time zone). It will map differently in GMT. Now, let’s also
assume that you are reporting on multiple organizations, each with different
time zones and day/week boundaries. You are requesting data on 1/10/04
through 1/15/04, but this could map to different absolute times for each
organization. For example:
Org A: 1/10/04 3:00 a.m. - 1/11/04 3:00 a.m., 1/11/04 3:00 a.m. - 1/12/04
3:00 a.m....
Org B: 1/10/04 8:00 a.m. - 1/11/04 8:00 a.m., 1/11/04 8:00 a.m. - 1/12/04
8:00 a.m....
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s From
field shows the value of that parameter, such as From: Last 30 days. This is in contrast to
previous releases, where the From field showed a date.
NOTE A time entry belongs to the day in which its time record begins.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For example, 2
hours 30 minutes would be shown as 2.5 hours.
Supervisors or managers can use this report to review the amount of time that each
agent spends in each activity, including paid, unpaid, and total time, summarized over
the selected period of time. Managers can run this report for a week or a month to see
how each agent is being utilized over that time period, and determine whether particular
agents are spending too much time in breaks, after-call work, or other activities, or if
they are not spending enough time on the phones.
Inputs
Employee Filter: Indicates the set of employees to report on.
Time Frame (reports that are in view time zone): These reports generally return a
single aggregation for the specified time period or a set of records corresponding to
all events that start in or intersect the time period.
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, then
all events that start in the specified time window are returned.
Time Zone: Indicates the time zone used for display.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For example,
2 hours 30 minutes would be shown as 2.5 hours.
This report is similar to the Employee Activity Roll-up report, but for each activity, this
report gives a summary of the time spent in the activity for each day within the selected
time period. You can also run this report for a week or a month and analyze it to identify
any trends in how much time is spent in particular activities day after day.
Inputs
Employee Filter: Lists the organization on which to report.
Time Frame (reports that are by day and in organization time zone):
- Last <X> days: This field specifies which days to report on. This mode should
return the last X completed workdays for an organization, however, as
implemented, it sets the From-date to the current day in the time zone of the
SQL Server computer minus X days and the To-date to the current day in the
time zone of the SQL Server computer. Depending on the difference between
the SQL Server computer's time zone and the organization's time zone and day/
week boundary, this may not be the last X completed workdays.
- From/To date (reports that are in organization time zone): These reports are
generally by day or by week. Here, by day/week means the organization's
workday or workweek, considering day and week boundaries. So, let’s say you
want to report on the workdays 1/10/04 through 1/15/04. The workday n
a.m.ed 1/10/04 is actually 1/10/04 8:00 a.m. through 1/11/04 8:00 a.m. (in the
organization's time zone). It will map differently in GMT. Now let’s also
assume that you are reporting on multiple organizations, each with different
time zones and day/week boundaries. We are requesting data on 1/10/04
through 1/15/04, but this could map to different absolute times for each
organization. For example:
Org A: 1/10/04 3:00 a.m. - 1/11/04 3:00 a.m., 1/11/04 3:00 a.m. - 1/12/04
3:00 a.m....
Org B: 1/10/04 8:00 a.m. - 1/11/04 8:00 a.m., 1/11/04 8:00 a.m. - 1/12/04
8:00 a.m....
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
NOTE A time entry belongs to the day in which its time record begins.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For example,
2 hours 30 minutes would be shown as 2.5 hours.
Related topics
Detailed Time Record, page 35
This report is similar to the Activity Roll-up report, but the breakdown of time spent in
each activity is summarized for each day within the selected time period. This report can
also be run for a week or a month, and analyzed to identify any trends in organization
utilization that are changing daily.
Inputs
Organization: Indicates the organizations to report on.
Time Frame (reports that are in view time zone): These reports generally return a
single aggregation for the specified time period or a set of records corresponding to
all events that start in or intersect the time period.
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, then
all events that start in the specified time window are returned.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For example,
2 hours 30 minutes would be shown as 2.5 hours.
Related topics
Daily Activity Summary, page 31
Adherence Reports
These reports deal with employees’ adherence to their schedules.
Topics
Adherence Exceptions, page 43
Adherence Minutes, page 46
Adherence Numbers by Interval, page 48
Adherence Summary, page 51
Adherence Exceptions
Default Access Rights
This report can be run by the following roles: Branch Administrator, Branch Manager,
Manager.
Overview
This report consists of a list of exceptions for each employee for the selected employee
filter and time period.
There can be more than one record returned for a single exception. An exception is
defined per planned activity; a new exception is not counted as beginning until the
planned activity has changed. Also, it is necessary to return a new record whenever
any information changes, such as the actual activity or approval status.
Managers can use this report to investigate the details of employee non-adherence to
schedule. Managers can look for employees with unusual numbers of exceptions, or for
patterns of exceptions related to particular times or activities. The information in the
Approved By column is helpful for determining who authorized a particular instance of
non-adherence, and also for discovering whether any approvers have an unusual
number or pattern of such authorizations. If employees are held to adherence goals, it is
particularly useful to review authorization patterns to verify that some managers are not
authorizing more exceptions than others, thus making it easier for their employees to
achieve the goals.
Inputs
Employee Filter: Indicates the set of employees to report on.
Time Frame (reports that are in view time zone): These reports generally return a
single aggregation for the specified time period or a set of records corresponding to
all events that start in or intersect the time period.
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Time Zone: Indicates the time zone used for display.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
Adherence Minutes
Default Access Rights
This report can be run by the following roles: Branch Administrator, Branch Manager,
Manager.
Overall
This report summarizes adherence to schedule information (in minutes) per employee
per workday.
This report does not return adherence exceptions when an employee is not scheduled
for an activity or if the employee is scheduled for an activity that is mapped to No
Activity.
NOTE Adherence to activities of a non-work type (for example, vacations, lunch, break, or no
activity) should not count the same as adhering to work activities. It would skew the
percentages. For this reason, there will be exceptions that show up in the Adherence view,
but do not show up in this report. Also, the following rules govern which day exceptions will
be counted:
If an exception is contained within a shift assignment (that is, the planned event for that
exception is contained within a shift assignment), it is counted on the workday that the
shift assignment begins.
If an exception is not contained within a shift assignment (that is, the planned event for
that exception is not contained in a shift assignment), it is counted on the day that the
planned event begins. Normally this is only the case for calendar events that do not
have to overlap shift assignments.
This report (or the very similar Adherence Summary report) is key for evaluating
employee's overall adherence to schedule. Typically, the focus is on the results for Time
Adhering To Schedule (%). Supervisors can review this report daily for use in
coaching agents towards better adherence. Information from reports run over a longer
period, such as a quarter, is often used in performance evaluations.
Inputs
NOTE For customers who are licensed for Scorecards, the use of adherence KPIs might replace the
use of this report.
Time Frame (reports that are in view time zone): These reports generally return a
single aggregation for the specified time period or a set of records corresponding to
all events that start in or intersect the time period.
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
Employee Name: The name of employee for whom adherence data is being
summarized.
Manager Name: The manager of the employee for whom adherence data is being
summarized.
Start Date: The workday being summarizing. (The following field applies to this
workday).
Time Adhering To Schedule (Minutes): The amount of time the employee is
adhering to the schedule for that day.
Time Not Adhering To Schedule (Minutes): The amount of time the employee is
not adhering to the schedule for that day.
Total Time Scheduled (Minutes): Only includes activities that are not mapped to
activity No Activity.
Time Adhering To Schedule (%): Percentage of scheduled “work” time in which
the employee is adhering.
Time Not Adhering To Schedule (%): Percentage of scheduled “work” time in
which the employee is not adhering.
Adherence Violations: The number of adherence violations where the planned
activity is not mapped to activity No Activity.
This report is helpful for investigating the root causes of service level problems. For
example, if scheduled staffing was adequate during an interval with low service level
results, but adherence to schedule was poor, then the poor adherence might be partially
or entirely responsible for the bad service results.
Inputs
Employee Filter: Indicates the set of employees to report on.
Time Frame (reports that are in view time zone): These reports generally return a
single aggregation for the specified time period or a set of records corresponding to
all events that start in or intersect the time period.
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Time Zone: Indicates the time zone used for display.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
Organization Name: The name of the organization that is being reported on.
Date: Date/time of the interval.
Total No. Scheduled: Total number of full agents that are scheduled during the
interval. For example, if there are two agents whose schedules intersect the
interval by only 15 minutes each, they would be combined to equal one agent.
No. Adhering To Schedule: The number of agents adhering to their scheduled
activities during this interval.
No. Not Adhering To Schedule: The number of agents not adhering to their
scheduled activities during this interval.
Adhering To Schedule (%): Percentage of employees adhering to their schedule.
Adhering to Schedule (%) - (No. Adhering to Schedule / Total No.
Scheduled) * 100
Not Adhering To Schedule (%): Percentage of employees not adhering to their
schedule. Not Adhering to Schedule (%) - (No. Not Adhering to Schedule /
Total No. Scheduled) * 100
NOTE All values only apply to the periods of time containing scheduled activities that are not linked
to the No Activity activity. Approved exceptions count as adhering time.
Adherence Summary
Default Access Rights
This report can be run by the following roles: Administrator, Branch Administrator,
Branch Manager, Manager.
Overview
This report summarizes adherence to schedule information (in hours and minutes) per
employee per workday. This report does not return adherence exceptions when an
employee is not scheduled for an activity or if the employee is scheduled for an activity
that is mapped to No Activity.
NOTE Adherence to activities of a non-work type (for example, vacations, lunch, break, or no
activity) should not count the same as adhering to work activities. It would skew the
percentages. For this reason, there are exceptions that show up in the Adherence view, but do
not show up in this report. Also, the following rules govern which day exceptions will be
counted:
If an exception is contained within a shift assignment (that is, the planned event for that
exception is contained within a shift assignment), it is counted on the workday that the
shift assignment begins.
If an exception is not contained within a shift assignment (that is, the planned event for
that exception is not contained in a shift assignment), it is counted on the day that the
planned event begins. Normally, this is only the case for calendar events that do not
have to overlap shift assignments.
This report (or the very similar Adherence Minutes report) is key for evaluating
employees’ overall adherence to schedule. Typically, the focus is on the results for Time
Adhering To Schedule (%). Supervisors can review this report daily for use in
coaching agents towards better adherence. Information from reports run over a longer
period, such as a quarter, is often used in performance evaluations.
NOTE For customers who are licensed for Scorecards, the use of adherence KPIs might replace the
use of this report.
Inputs
Employee Filter: Indicates the set of employees to report on.
Group By
- Employee: Aggregates time entries per employee.
- Organization: Aggregates time entries per organization.
- Supervisor: Aggregates time entries per supervisor.
Time Frame (reports that are in view time zone): These reports generally return a
single aggregation for the specified time period or a set of records corresponding to
all events that start in or intersect the time period.
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
Employee Name: The name of employee for whom adherence data is being
summarized.
Manager Name: The name of the employee’s manager.
Start Date: The workday being summarizing. (The following field applies to this
workday).
Time Adhering To Schedule (Hours): The amount of time the employee is
adhering to the schedule for that day.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For example,
2 hours 30 minutes would be shown as 2.5 hours.
Time Not Adhering To Schedule (Hours): The amount of time the employee is
not adhering to the schedule for that day.
Total Time Scheduled (Hours): Only includes activities that are not mapped to
activity No Activity.
Time Adhering To Schedule (%): Percentage of scheduled “work” time in which
the employee is adhering.
Time Not Adhering To Schedule (%): Percentage of scheduled “work” time in
which the employee is not adhering.
Adherence Violations: The number of adherence violations where the planned
activity is not mapped to activity No Activity.
Coaching Reports
These reports deal with employees coaching sessions.
Topics
Coaching Impact, page 54
Coaching Summary, page 58
Coaching Impact
This report shows the impact of coaching sessions on the associated KPIs. It shows the
value of the KPI before the session, after the session, and the change between the two
expressed as a percentage. An improvement is expressed as a positive percentage; a
worsening is expressed as a negative percentage.
The report groups sessions in the following order:
1 Coach
2 KPI
3 Employee.
NOTE For each of the above groupings, the report averages the coaching impact.
Inputs
Employee Filter: Indicates the set of employees to report on.
Coach Filter: Indicates the set of coaches to report on.
Time Frame:
- Last <X> days: This mode uses the previous <X> number of days for the
report.
Outputs
IMPORTANT Sessions which do not have KPI information for before or after the session will be
reported but will show no improvement.
Session data reported is only as recent as the last Report Dump. Sessions created after
the last Report Dump will not be reported.
Employee filter information is a snapshot the last Report Dump. New filters will not be
usable until the Report Dump next runs.
Organizational membership changes over time are not shown on the report, so the
context option is not recommended.
Coach: The name of the coach for whom the coaching impact is being reported.
KPI: The metric being reported before and after the coaching session.
NOTE When viewing KPI statistics, it is helpful for you to know how the report determines the KPI
figure to use relative to the time frame for which you are running the report. For example,
assume you run the report for 7 days prior to the session and for 7 says after the session, and
the session occurred on a Wednesday.
If you are looking at a weekly KPI, you may think the KPI figure is calculated based on the 7
days before/after the session. However, the report does not recalculate KPI figures. If the
week begins on a Sunday and ends on a Saturday, a weekly KPI is always calculated based on
that date range — not your report time frame. Therefore, it is possible (and likely for daily
KPIs) that the KPI statistic includes data outside the time frame for your report. The same
logic holds true for monthly, quarterly, and yearly KPI statistics.
Employee: The employee for whom the coaching impact is being reported.
Session Date: The date of the coaching session, based on the date selection
described above for the input parameters.
Periodicity: The period associated with the KPI.
Compare From: The KPI value prior to the coaching session.
Compare To: The KPI value after the coaching session.
Improvement: Ratio of the Compare From value to the Compare To value,
expressed as a percentage. An upward trend is a positive percentage; a downward
trend is a negative percentage.
NOTE The improvement figures are averaged for the following groupings:
Agent
KPI
Coach
Coaching Summary
This report provides a summary for selected employees and coaches of all coaching
sessions scheduled during a selected time frame.
The format for report is similar to the Manage Coaching page, found in the Coaching
module.
You can group sessions by Employee or Coach.
Inputs
Employee Filter: Indicates the set of employees to report on.
Coach Filter: Indicates the set of coaches to report on.
Time Frame:
- Last <X> days: This mode uses the previous <X> number of days for the
report.
- From/To date: Aggregates data for inclusive date range.
Group By: Determines how the data on the report are sorted. Group results by:
- Coach
- Employee
Status: Select one or more session statuses to include. Select from:
- All
- Pending
- Meeting Scheduled
- Coached
- Await Employee Feedback
- Await Coach Feedback
- Completed.
Result: Select one or more session results to include. Although you can add
additional results, the default session results are:
- All
- Below Expectations
- Exceeds Expectations
- Meets Expectations
- None (no session result)
Session Type: Select one or more session types to include. The session types to
which you have access depend on your organizational privileges.
Coaching Topic: Select one or more coaching topics to include. The coaching
topics to which you have access depend on your organization privileges.
Outputs
Coach: The name of the coach for whom the summary is being reported.
Employee: The name of the employee for whom the summary is being reported.
Scheduled Date: The date on which the session is scheduled.
Due Date: The date on which the session is scheduled for completion.
Completion Date: The date on which the session was completed.
Assigned By: The employee who assigned the session.
Session Type: The type of session scheduled.
Management Reports
These reports deal with general employee information, such as IDs, manager names,
job titles, etc.
Topics
Active Employees, page 61
Employee Information, page 63
Tenant Usage, page 64
user Roles, page 68
Active Employees
This report provides a list of the number of active employees per organization or per role
for the selected date. This also reports the total number of employees and total number
of active employees.
You can use this report to get the number of active employees in each organization or to
view active employees based on the role.
Grouped by Organization
Grouped by Role
Inputs
Date: As of date. That is, active employees as of this Date.
Group by: Organization or Role
Outputs
Organization: Name of the organization for which the report is being generated.
Role: Name of the role for which the report is being generated.
Active employees: Active employees per organization or per role.
Total Employees: Total number of employees.
Total Active Employees: Number of active employees as of the input date.
Employee Information
This report provides a list of employees and their information for the selected employee
filter and time period. It includes their manager, job title, and start and end dates.
You can use this report to verify supervisor assignments, job titles, and start/end dates
for employees. You can also use this report to generate a printable list of names
matching a specific employee filter defined in the Workforce Optimization Suite.
Inputs
Date: The date for which the information is relevant (some columns may have ).
Employee Filter: Indicates the set of employees on whom to report.
Time Zone: Indicates the time zone used for display.
Outputs
Organization: Name of the organization for which the report is being generated.
Employee Name: The name of the employee being reported on.
Manager Name: The name of the employee’s manager.
Employee ID: The ID of the employee being reported on.
Tenant Usage
This report provides accurate and consistent reporting to track individual product usage
across the whole enterprise suite. The report also provides tracking per tenant where
there can be multiple tenants in a service provider environment.
The Tenant Usage Report tracks product license usage within the Workforce Optimization
(WFO) suite of products. It provides a detailed count of the usage for each individual
product, with a summary at both the enterprise level and the organization hierarchy
level. Service providers can then easily report on individual tenant along with sub-
organization utilization.
When the Tenant Usage Report is launched, it opens to a summary view which
aggregates total product usage per product and organization. The report also provides a
drill-through feature that allows users to expand into sub-organization usage summary.
It also provides a detailed view that identifies which privileges and consumption records
were tracked by user.
Tenant Specific Reports -Allows the report to be run by the entire enterprise suite
or by a specific organization. This feature allows the service provider to generate
individual tenant usage reports that can be distributed to each tenant for review.
Scheduled Reports - This report can be scheduled so they are automatically
generated on a monthly basis. The report distribution can be configured to send it to
either the service provider or tenants for review.
Report Data Export - The Product Usage report can be exported as a PDF, HTML or
Excel file.
WFM - Time Off Mgr Create / Edit / Counts the time off
Withdraw Time off requests per employee
Requests for
Employee
View Personal Time off
Request
user Roles
This report provides a list of employees showing their organization and the user role and
scope they are assigned.
Administrators can use this report to generate a record of what user roles and scopes
have been assigned to each employee, and to confirm whether the assigned role/scope
is appropriate for each employee's job title. By running filtered instances of the report,
administrators can provide managers with information about what roles have been
assigned to their employees.
Inputs
Date: The date for which the information is relevant (some columns may have ).
Employee Filter: Indicates the set of employees on whom to report.
Time Zone: Indicates the time zone used for display.
Outputs
Organization: Name of the organization for which the report is being generated.
Employee Name: The name of the employee being reported on.
Employee ID: The ID of the employee being reported on.
Manager: The manager on the given input date.
Job Title: The job title on the given input date.
User Role: This field is as defined in the Assigned Roles field of the User
Management module’s User Access Rights.
Scope: This field is as defined in the Organization Scope field of the User
Management module’s User Access Rights.
Operations Reports
The reports under this topic are only displayed if you have an Operations license. They
cover such things as workload, productivity, VCT events, Work Item Tracking (WIT), etc.
Work Item Tracking (WIT) is a real-time generic business intelligence framework
specifically designed to provide productivity and service level metrics from one or more
Customer Relationship Management (CRM) data systems.
The primary benefit of WIT is that it can seamlessly integrate with multiple CRM systems
to identify process bottlenecks and validate service level agreement (SLA) adherence.
By reviewing interactive aging charts that allow you to drill down to the details of an
individual work item in an age category you can do root cause analysis if service goals
are not met. Additionally, employee productivity data can be generated from the same
CRM feed(s) and correlated with the work item aging information to identify proficiency
gaps in specific tasks.
Topics
Capacity Plan, page 70
Daily Production, page 74
Intraday Productivity, page 75
Productivity, page 78
Productivity & Effectiveness, page 90
Utilization, page 94
VCT Events, page 97
WIT Aging Chart, page 105
WIT Aging vs. Deadline Goal, page 108
WIT Drilldown Chart Report, page 110
WIT Item, page 112
Capacity Plan
The Capacity Plan report lets you view the workload for all work queues and unpublished
calendar activities for all employees belonging to the selected organization(s). The
report computes the gross required hours, net required hours, and required FTEs, based
on actual or forecasted volumes for each work queue and activity for the duration of the
report period.
Queue Types:
VCT Queues: The report uses the time standard defined for the queue.
Non-VCT Queues: The report uses volumes and AHT from the Pulse section for
the selected organization and computes the gross required hours and net required
hours for the queue. AHT is a weighted average based on volumes.
The report output consists of four graphs, such as the following:
Inputs
Date Range: The beginning and ending dates of the report period.
Organizations: The organization(s) for which you want to run the report.
Volume Data Source: Select one of:
- WFM Actual Volume = Historical actual volumes.
Outputs
As mentioned previously, the report output consists of three tables:
Work queue information
Analysis of Overall Capacity Requirements
Analysis of Capacity Opportunity
Work Queue Information
The information for all work queues of each parent organization together with its child
sub-organizations are presented in the top table.
Sub Org Name: If one or more work queues belong to a suborganization, this
column is populated with the names of work queues belonging to the
suborganization. This indicates that the work queues are assigned to the
suborganization and not to its parent organization.
Work Queues: The name of the work queue belonging to the parent organization
listed at the top of the table or its child organization(s).
Volumes: Depends on the mode selected (WFM Actual Volume, WFM
Forecasted Volume, VCT Completions).
- WFM Actual Volume: The total actual volume within the report period for
every work queue is displayed.
- WFM Forecasted Volume: The total forecasted volume within the report
period for every work queue is displayed.
- VCT Completions: The total number of VCT completions within the report
period for every work queue is displayed.
Activity Handling Time (Seconds): The activity handling time in seconds for
each work queue configured on the Work Queue Configuration page.
Gross Required Hours: The volume for the work queue * Activity Handling
Time for the work queue / 3600.
Net Required Hours: Gross Required Hours/ Efficiency
Net FTE Required: (Weekly FTE Hours * No of Weeks)
Percentage FTE Allocated to Work (%): FTE / Organization Total FTE * 100.
Analysis of Overall Capacity Requirements
Requirements: The gross requirements, reduced by the specified factors, to
produce the net requirement.
Hours: The hours for each of the items in the Requirements column.
Percent (%): The percent of the Net Requirements for each of the items in the
Requirements column.
Analysis of Capacity Opportunity
Requirement: List categories for actual vs. required FTE and Potential Capacity
Opportunity (understaffed vs. overstaffed).
FTE: Shows actual vs. required FTE.
Daily Production
This report is an expanded version of the Capacity Plan report, and consists of one graph
which represents FTE actual and Forecasted.
Inputs
Time Frame: The time frame can be entered as the last N days, or as an explicit
date range set using a date range selector.
Organizations: Use the Organization selector to choose the organization(s) for
which to run the report.
Daily FTE Hours: Specify the number of FTE Hours to use in the FTE calculation.
Outputs
The reports shows the following metrics in both Forecast and Actual modes
simultaneously:
Hours
Workload (volume)
AHT
Beginning Backlog
Ending Backlog
FTE
Related topics
Capacity Plan, page 70
Intraday Productivity
This report returns information on the productivity of employees (total work assigned
(hours) vs. remaining scheduled hours) grouped by a queue or a team.
For the charts produced by this report, you have the ability to drill down.
The report can be run for details or for summaries, and has two modes:
Schedules: Considers the employees' operations media type activities in their
schedules as generated by Forecasting and Scheduling. The data is shown in the
Scheduled Time column.
Time Records: Considers the employees' operations media type activities, entered
in their time records through the Time Record page of the My Time section of the
My Home module. The data is shown in the Total Actual Time column.
Inputs
Time Frame: The report can be run for the last N days.
Time: Specify the time for which to run the report, using the time selector.
End date: User the drop-down selector to specify the end date of the report.
Choices are: Last VCT Import Date Time or the current date.
Employee Filter: Select the employee filter to use, create a new filter, or edit an
existing filter.
Mode: Select the mode to use when running the report: Time Records or
Schedules.
Group By: Select the entity by which to group the report: Organization,
Supervisor, or Campaign.
Display Mode: Select the display mode for the report: Detailed or Summary.
View: Select the view to be used in the report: Tree View or Matrix View. The
tree view shows tables of both the employee productivity details and the queue
productivity details, with an interactive collapsible tree to drilldown an employee to
the queue level.
The matrix view, on the other hand, has a single table (organization details) which
displays employees as rows and work queues as columns in a static table or matrix
form (with no interactive nodes). Each employee or work queue cell contains the
productivity of that employee for that queue, that is, the employee-queue
productivity (assuming queue hopping). If queue-hopping is not used or the queue
is not mapped to an activity, the cell is blank. The last column of the matrix shows
the total employee productivity across all the queues. The bottom right corner final
row or column shows the total organizational productivity.
Show Work Queue Productivity: Use the drop-down selector to specify whether
to show the work queue productivity or not.
Outputs:
Graphs: One for the group by entity, and a second one for the intraday productivity
distribution.
Bar charts: One for % Intraday Productivity by Employee, a second for % Intraday
Productivity by Work Queue.
Organization Summary: Shows for each employee in the organization:
- Employee
- Completed
- Proficiency (%)
- Expected Time (Minutes)
- Scheduled Time or Actual Time (Minutes)
- Intraday Productivity (%)
- Daily Productivity (%)
- Expected Productivity (%)
Employee Productivity Details: Shows either a tree view or a matrix view for each
employee in the organization:
- Employee
- Work Queues
- Completed
- Expected Completions
- Proficiency (%)
- Activity Handling Time (Seconds)
- Expected Time (Minutes)
- Scheduled Time or Actual Time (Minutes)
- Intraday Productivity (%)
- Activities
Work Queue Productivity Details: Shows for each work queue:
- Work Queue Name
- Employee
- Completed
- Expected Completions
- Proficiency (%)
- Activity Handling Time (Seconds)
- Expected Time (Minutes)
- Work Queue Time (Minutes)
- Intraday Productivity (%)
- Activities
Drill down
1 Click an item on the chart.
2 You then see additional details for the next, lower level of data represented by the
chart element, for example, a bar on the chart.
If you cannot drill further down, you have reached the lowest level of data available.
NOTE The report drill-down feature provides access to the following information, in the order
indicated:
1 Overall organization productivity
2 Productivity distribution count for different percentage ranges
3 Productivity percentages for employees
4 Queue Productivity percentage for an employee
Productivity
The Productivity report reports on the productivity of employees grouped by
organization, supervisor, or campaign.
Productivity is calculated based on the individual VCT Events of type CHECKIN per
queue per employee, and the deferred (email) type activities recorded or scheduled for
each employee. The report only lists the employees in the selected group who are doing
some work within the report period. Nonproductive employees (those with zero
checkins) are not listed on the report.
For the charts produced by this report, you have the ability to drill down.
The report can be run for details or for summaries, and has two modes:
Time Records: Considers the employees' operations media type activities, entered
in their time records through the Time Record page of the My Time section of the
My Home module. The data is shown in the Total Actual Time column.
Schedules: Considers the employees' Assigned Work Activity activity type in their
schedules as generated by Forecasting and Scheduling. The data is shown in the
Scheduled Time column.
The following graphics show detailed and summary for each of the above mentioned
modes, group by campaign, organization, and supervisor:
Detailed Report for Schedules, Grouped by Campaign:
In addition to the detailed and summary views shown previously, there is also a matrix
view, two examples of which are shown below:
Inputs
Time Frame: Time span of the report.
Employee Filter: Allows you to select or edit existing employee filters at the
organization level, or create new ones.
Mode:
- Schedules: Considers the employees' operations media type activities in their
schedules as generated by Forecasting and Scheduling. The data is shown in the
Scheduled Time column.
- Time Records: Considers the employees' operations media type activities,
entered in their time records through the Time Record page of the My Time
section of the My Home module. The data is shown in the Total Actual Time
column.
Group By: Information can be grouped by organization, supervisor, or campaign.
Display:
- Detailed: Shows employee data in detail.
- Summary: Shows each employee's summary information.
View: In detailed mode, an additional parameter, View, has two options: a tree
view or a matrix view. The tree view shows tables of both the employee productivity
details and the queue productivity details, with an interactive collapsible tree to
drilldown an employee to the queue level.
The matrix view, on the other hand, has a single table (organization details) which
displays employees as rows and work queues as columns in a static table or matrix
form (with no interactive nodes). Each employee or work queue cell contains the
productivity of that employee for that queue, that is, the employee-queue
productivity (assuming queue hopping). If queue-hopping is not used or the queue
is not mapped to an activity, the cell is blank. The last column of the matrix shows
the total employee productivity across all the queues. The bottom right corner final
row or column shows the total organizational productivity.
Show Work Queue Productivity: Check this box to include in the report the %
Productivity by Work Queues graph.
Output
The report consists of two tables:
Summary information
Detailed information
Summary Information
Employee: Employee name
Completed: The total value of all CHECKIN events done by the specific employee
for the corresponding Volume work queue or sub-work queue.
Proficiency (%): The average proficiency for each employee computed from the
proficiency levels set in Forecasting and Scheduling. If an employee has no skills,
Proficiency = 100 * 1/proficiency in Forecasting and Scheduling for the employee. If
the employee has skills, Proficiency = 100 * 1/skill proficiency.
Expected Time (Minutes): Completed * Activity Handling Time for the work
queue / 60
Scheduled Time or Actual Time (Minutes)
- Scheduled Time: The sum total in minutes of all activities with an activity type
of Assigned Work Activity that are part of the employee's schedule.
- Actual Time: The sum total of all operations media type activities in minutes
that are part of the employee's time record.
Productivity (%): (Expected time (minutes)*100)/ Scheduled or Actual Time)
Detailed Information
The detailed information table displays essentially the same information as the
summary table, except that it breaks down completed work by work queue and shows
the activity handling time of each work queue. Expected Time (Minutes) is displayed
at the work queue level. Productivity (%) is computed at the employee level using the
same formula as for the summary.
Drill down
1 Right click an item on the chart.
2 Select Drill Down to view additional details for the next, lower level of data
represented by the chart element, for example, a bar on the chart.
If Drill Down is disabled, you have reached the lowest level of data available.
NOTE The report drill-down feature provides access to the following information, in the order
indicated:
1 Overall organization productivity
2 Productivity distribution count for different percentage ranges
3 Productivity percentages for employees
4 Queue Productivity percentage for an employee
NOTE Some data in this report relies on the Scorecards data to populate it. The Productivity &
Effectiveness report adapter is also required to run this report asynchronously with real time
data.
You can also choose to produce a summary report, rather than report the details.
Inputs
Employee Filter: Allows you to select or edit existing employee filters at the
organization level, or create new ones.
Report Type: Allows you to produce a report on the actual numbers or the
scheduled numbers.
Time Frame: Time span of the report, expressed as one of the following two
choices:
- Last <X> days
- Date range
Time Zone: Shows the information based on the time zone you select.
Group By: Information can be grouped by supervisor or organization.
Time: You can show the information expressed in Hours:Minutes, or
Minutes:Seconds.
Activity Type: You can choose to display information for Production Activities, Non-
Production Activities, or both.
Detailed/Summary: You can choose to generate a detailed or a summary report,
as shown previously.
Show Shift Events: This checkbox allows you to show shift event information on
the report.
Output
Queue / Activity Name: For each employee, displays in the top rows VCT Queues.
In the bottom rows, it displays My Time Activities (Production Activities first, then
Non-Production Activities).
Completed: Displays integer values for VCT volumes by employee.
AHT (HH:MM): Shows the Average Handle Time for the VCT queues.
Earned Time (HH:MM): This field is calculated, and shows the completed volume
X AHT / 60 (rounded to a minute).
Production Activity Time (HH:MM): Displays the time clocked by Production
Activity (sums the total minutes clocked).
Non-Production Activity Time (HH:MM): Displays the time clocked by Non-
Production Activity (sums the total minutes clocked).
Production DPA Time (HH:MM): Taken from Scorecards. Shows
DPA#ProductiveTime as SourceMeasureSystemCode, displayed in Minutes.
Utilization (%): This field is calculated, and shows Earned Time / My Time Total
Minutes.
Productivity (%): This field is calculated, and shows Earned Time / Clocked
Production Time.
Production Effectiveness (%): This field is calculated, and shows Earned Time /
DPA Production Time.
Production Time Compliance (%): This field is calculated, and shows
Productivity / Production Effectiveness.
Utilization
This report compares an organization’s productivity against its utilization, or its
productivity against its non-productivity. It allows you to measure employees’
performance and to see the work that employees are scheduled to do, as well as out-of-
office and overtime hours.
Inputs
Time Frame: Time span of the report.
Employee Filter: Allows you to select or edit existing employee filters at the
organization level, or create new ones.
Type: Whether to report on VCT events or schedules.
Show Graph: You have a choice of displaying no graphs with the report (No
Graph), or of displaying a graph for Productivity Vs Utilization (see the previous
graphic) or Productivity Vs Non-Production (see the following graphic).
Goal: Allows you to set a goal line in the graphs.
Outputs
The columns output in the report vary, depending on whether you selected to report on
VCT events or schedules.
VCT Event
Employee Name: The names of the employees selected through the employee
filter.
Total VCT Production Hours: The work completed (CHECKINS) for the VCT
queues of any media other than projects.
Total VCT Non-Production Hours: The work completed (CHECKINS) for VCT
queues of project media.
Overtime: Hours scheduled for overtime activity.
Out of Office Hours: The number of hours an employee is scheduled for an out-of-
office activity based on their work day, not based on a 24 hour day.
Total Hours Assigned: Scheduled activities with the activity type Assigned Work
activity type (excluding Unavailability and Time Off).
VCT Production (%):Total Production Hours/Total Hours Worked.
VCT Non-Production (%): Total Non-Production Hours/Total Hours Worked.
Productivity (%): Total Production + Non-Production Hours/Total Hours Worked.
Utilization (%): Total Production + Non-Production Hours/Total Scheduled Time
(all paid activities).
Organization Total: Totals for the columns Total VCT Production Hours, Total
VCT Non-Production Hours, Overtime, Out of Office Hours, and Total Hours
Assigned.
Schedules
Employee Name: The names of the employees selected through the employee
filter.
Total Scheduled Production Hours: Activities that are of any media other than
projects.
Total Scheduled Non-Production Hours: Activities that are "calendar events,"
excluding Unavailability and Time Off. This assumes project activities are always
non-production work.
Overtime: Hours scheduled for overtime activity.
Out of Office Hours: The number of hours an employee is scheduled for an out-of-
office activity based on their work day, not based on a 24 hour day.
Total Hours Assigned: Scheduled activities with the activity type Assigned Work
activity type (excluding Unavailability and Time Off).
Scheduled Production (%):Total Production Hours/Total Hours Worked.
Scheduled Non-Production (%): Total Non-Production Hours/Total Hours
Worked.
Productivity (%): Total Production + Non-Production Hours/Total Hours Worked.
Utilization (%): Total Production + Non-Production Hours/Total Scheduled Time
(all paid activities).
Organization Total: Totals for the columns Total Scheduled Production Hours,
Total Scheduled Non-Production Hours, Overtime, Out of Office Hours, and
Total Hours Assigned.
VCT Events
This report is an audit report used by managers and supervisors to validate VCT Events
data by employee or work queue at their respective organization.
This VCT data, which is used to measure employee productivity and volume generation,
is entered into the system either through the Volumes page of the Tasks section of the
Tracking module, or through the Operations - Event File Import and Transform adapter.
The report tallies the four VCT Event types for all work queues in an organization within
a given time period:
Check-in
The report displays only the Check-ins done, based on the employee filter and the
date range.
Check-out
The report displays only the Check-outs done, based on the employee filter and the
date range.
Work-in-Progress
The report displays all the Work-in-Progress, based on the date filter and employee
filter.
Arrivals
The report displays all the arrivals based on the date filter, but excludes the
employee filter, even if the employee filter is selected.
You can also show tallies for all four event types:
All
The report displays all the VCT event types for the employee filter and for the
selected date range. It is recommended to select Event Type in the Group by
filter, when Event Type is All.
The data can be viewed at a summary or detail level, and grouped by:
Employee
The report displays all the details based on all the other filters, but grouping is
based on employees. Employee Name is the first column in the summary table.
The event details table is broken down by employee name, that is, individual events
data is displayed in subsections by Employee Name.
Work Queue
The report displays all the details based on all the other filters, but grouping is
based on work queue. Work Queue Name is the first column in the summary
table. The event details table is broken down by work queue name, that is,
individual VCT Events data are displayed in subsections by Work Queue Name.
Event Type
The report displays all the details based on all the other filters, but grouping is
based on event type. Event Type is the first column in the summary table. The
event details table is broken down by event type name, that is, individual events
data is displayed in subsections by Event Type.
The following graphics show highlights from the detailed and summary reports, grouped
by employee, work queue, and event type:
Inputs
Time Frame: Time span of the report.
Employee Filter: Allows you to select or edit existing employee filters at the
organization level, or create new ones.
Display Mode:
- Detailed: Shows employee data in detail.
- Summary: Shows each employee's summary information.
Event Type: Information can be displayed for the following event types:
- All
- Arrival
- Check-Out
- Work In Progress
- Check-In
Group By: Information can be grouped by employee, work queue, or event type.
Output
The report consists of two tables:
Summary information
Detailed information
Summary Information
Employee Name/Work Queue Name/ Event Type: The Employee name, Work
Queue name, or Event Type name, depending on the setting of the Group By
parameter.
Event Type: One of the following events:
- Check-in
- Check-out
- Work-in-Progress
- Arrivals
Value: Shows the VCT Event Type total at the aggregate level.
Detailed Information
The detailed information table has the same columns as the Summary Table, but
displays each and every VCT event for a specific work queue within the range of the
report period. This table has an additional column called Date Time, which shows the
timestamp of the individual VCT event.
Inputs
WIT Named Filter: The filter used to focus on subsets of data in the WIT Aging
Chart report that are relevant to you.
WIT View: A saved set of attributes (such as employee ID, work queue, status of
the item, etc.) you want to see in the report.
Show Graph: The graphs you want included in the report:
- Employee Vs Work Queue By Age Bucket
- Work Queue By Age Bucket
- Employee By Age Bucket
Outputs
Graphs: The graphs shown differ depending on the setting of the Show Graphs
parameter:
- Employee Vs Work Queue By Age Bucket: Volume Vs Work Queue &
Employee, Hours Vs Work Queue & Employee
- Work Queue By Age Bucket: Volume Vs Work Queue, Hours Vs Work Queue
- Employee By Age Bucket: Volume Vs Work Queue, Hours Vs Work Queue
WIT Summary table: Includes such items as Work Queue Name, Employee Name,
Age Bucket, Volume, Hours, Organization.
Inputs
WIT Named Filter: Allows you to select an active WIT filter, create such a filter, or
edit an existing filter.
Group By: Allows you to select whether the report should be grouped by one of the
following: WIT Status; Deadline Goal Status; Employee; or Work Queue.
Display Mode: Specifies whether the report should be shown in detail or summary.
Outputs
Pie chart: A color-coded pie chart that depicts the distribution of the number of WIT
items in the following Deadline Goal Status categories:
Inputs
WIT Named Filter: The filter used to focus on subsets of data in the WIT Aging
Chart report that are relevant to you.
WIT View: A saved set of attributes (such as employee ID, work queue, status of
the item, etc.) you want to see in the report.
Outputs
Attributes: The attributes selected in the WIT view.
Aging buckets: The Aging buckets defined on the WIT Configuration page of the
Data Sources section of the System module.
NOTE To use the drill down feature, click one of the numbers representing the work items for an
aging bracket. The drill down feature displays the details for the aging bracket number
selected in a new window. The new window displays the WIT Item report for the selected
aging bracket and attribute combination. See WIT Item on page 112 to learn more about the
drill down report displayed in the new window.
WIT Item
This report shows all details (attributes) of the WIT Items imported, comparable to a
raw data dump.
Inputs
WIT Named Filter: The filter used to focus on subsets of data in the WIT Item
report that are relevant to you.
Outputs
The attributes associated with the WIT items, including:
Organization Name
External ID
Datasource Group Name
Employee Name
Work Queue Name
Status
Age
Is Workable
Type
Created By
Creation Date
Closed By
Description
CallBackDate
CustomerName
ContactNumber
Datasource Name
NOTE Outbound Performance reports require that the schedule information be current. You may
have to recalculate statistics (such as service level, average speed to answer, and number
scheduled) prior to generating these reports, in order for the reports to use the most current
data. In particular, this recalculation is necessary if the forecast has changed, or the
schedule has been changed.
Topics
Outbound Daily Forecast Assessment, page 114
Outbound Daily Performance Assessment, page 117
Outbound Forecast Lists Assessment, page 120
Outbound Monthly Performance Assessment Summary, page 122
Forecasters can review this report to gauge how accurate their daily connect rate, right-
party connect rate, connect AHT, and right-party connect AHT forecasts are for
individual queues, multiple queues, or the combined queue for a campaign. They can
also see the highest and lowest values in the time period selected, as well as the highest
and lowest deviations. After identifying periods where deviation was high, forecasters
should review what actually happened during that day, so they can improve their
forecasting technique for the future. Management can review this report to assess
forecasters' performance.
Inputs
Date Frame: Specifies the date period for which the report is generated. This can
be set in one of two ways:
- Last <n> days: The last specified number of days, starting backwards from the
current date and time. A value of 0 returns data for today only.
NOTE The daily time range time selections still apply, so the report only shows the times of the day
that fall within this range. For example, if it is currently 3:00PM and Last <n> Days is 0,
and the Daily Time Range is 10:00 AM to 2:00 PM, the report output will only include data
for 10:00 AM to 2:00 PM today.
If the daily time range were 12:00 AM to 11:59 PM, the current time were 3:00 PM, and
Last <n> Days were 0, the Daily Time Range would not be a factor in this case, because
the daily time range includes the whole day. However, the report will only show data for
12:00 AM to 2:45 PM, since data for the 3:00 PM interval would not be known until 3:15 PM.
In other words, the data in the report is always 15 minutes behind the current time when
Last <n> Days is used.
Outputs
Connect Rate Forecasted: The forecasted connect rate.
Connect Rate Actual: The actual connect rate.
Connect Rate % Deviation: The percentage deviation of the actual connect rate
from the forecasted connect rate.
AHT Forecasted: The forecasted connect average handling time.
AHT Actual: The actual connect average handling time.
Forecasters can review this report to gauge how accurate the connects, right-party
connects, dials, and backlog predictions are for individual queues, multiple queues, or
the combined queue for a campaign. They can also see the highest and lowest values in
the time period selected, as well as the highest and lowest deviations. After identifying
periods where deviation was high, forecasters should review what actually happened
during that day, so they can improve their forecasting technique for the future.
Inputs
Date Frame: Specifies the date period for which the report is generated. This can
be set in one of two ways:
- Last <n> days: The last specified number of days, starting backwards from the
current date and time. A value of 0 returns data for today only.
NOTE The daily time range time selections still apply, so the report only shows the times of the day
that fall within this range. For example, if it is currently 3:00PM and Last <n> Days is 0,
and the Daily Time Range is 10:00 AM to 2:00 PM, the report output will only include data
for 10:00 AM to 2:00 PM today.
If the daily time range were 12:00 AM to 11:59 PM, the current time were 3:00 PM, and
Last <n> Days were 0, the Daily Time Range would not be a factor in this case, because
the daily time range includes the whole day. However, the report will only show data for
12:00 AM to 2:45 PM, since data for the 3:00 PM interval would not be known until 3:15 PM.
In other words, the data in the report is always 15 minutes behind the current time when
Last <n> Days is used.
From Time: Specifies the start time of the day. The From Time and To Time
parameters specify the time range within each day of the specified date range for
which the report is generated.
To Time: Specifies the end time of the day. The From Time and To Time
parameters specify the time range within each day of the specified date range for
which the report is generated.
Queue: Indicates the queue on which to report. Can be a single, multiple, or a
combined queue. The queue selector only shows queues of the Phone Outbound
media type.
Time Zone: Indicates the time zone used for display.
Outputs
Connects Forecasted: The forecasted connects.
Connects Actual: The actual connects.
Connects % Deviation: The percentage deviation of the actual connects from the
forecasted connects.
RPC Forecasted: The forecasted right-party connects.
RPC Actual: The actual right-party connects.
RPC % Deviation: The percentage deviation of the actual right-party connects
from the forecasted right-party connects.
Dials Forecasted: The forecasted dials.
A call list doesn't contain the actual phone numbers to dial, but rather the number of phone numbers to
dial (known as the length).
This report displays each call list's forecasted and actual start/end dates, queue, length,
and number of retries for the selected queue(s) linked to the given scheduling period. In
order for a call list to be included in the report output, its start/end dates must intersect
the specified date range. The report summary displays the total forecasted and actual
call list lengths for each queue over the entire period, as well as the percentage
deviation of the actual data from forecasted.
Forecasters can review this report to gauge how accurate their call list forecasts are for
individual queues in a campaign. After identifying queues where deviation was high,
forecasters should review what actually happened during that period, so they can
improve their forecasting technique for the future. Management can review this report
to assess forecasters' performance.
Inputs
Queue: Indicates the queue on which to report. Can be a single, multiple, or a
combined queue. If a combined queue is selected, the report will display the call
lists of each individual queue underneath it. The queue selector will only show
queues of the "Phone Outbound" media type.
Time Zone: Indicates the time zone used for display.
Schedule Period:
- Campaign: The campaign on which to report.
- Schedule Period: The date range defining the schedule period on which to
report for the selected campaign.
- Date Range: Specifies the date period for which the report is generated. You
can choose to report on the entire schedule period, or on any sub-range of days
within the schedule period.
Outputs
Start Date: The date when agents are to begin working on the call list.
End Date: The date when agents are to stop working on the call list.
Queue: The Queue through which calls are made.
Length: The number of phone numbers to dial for the call list.
Retries: The maximum number of retries per phone number.
Length % Deviation: The percentage deviation of the total actual call list length
from the total forecasted call list length for the entire period.
Forecasters can review this report to gauge how accurate the daily connect and right-
party connect predictions are for individual queues or the combined queue for a
campaign. They can also see the highest and lowest values in the time period selected,
as well as the highest and lowest deviations. After identifying periods where deviation
was high, forecasters should review what actually happened during that day, so they can
improve their forecasting technique for the future. Also, the % Change from Previous
Month and % Change from Previous Year columns can be used to detect trends in
the statistics over time.
Inputs
Date Frame: Specifies the date period for which the report is generated. This can
be set in one of two ways:
- Last <n> days: The last specified number of days, starting backwards from the
current date and time. A value of 0 returns data for today only.
NOTE The daily time range time selections still apply, so the report only shows the times of the day
that fall within this range. For example, if it is currently 3:00PM and Last <n> Days is 0,
and the Daily Time Range is 10:00 AM to 2:00 PM, the report output will only include data
for 10:00 AM to 2:00 PM today.
If the daily time range were 12:00 AM to 11:59 PM, the current time were 3:00 PM, and
Last <n> Days were 0, the Daily Time Range would not be a factor in this case, because
the daily time range includes the whole day. However, the report will only show data for
12:00 AM to 2:45 PM, since data for the 3:00 PM interval would not be known until 3:15 PM.
In other words, the data in the report is always 15 minutes behind the current time when
Last <n> Days is used.
Outputs
Connects Forecasted: The forecasted connects.
Connects Actual: The actual connects.
Connects % Deviation: The percentage deviation of the actual connects from the
forecasted connects.
RPC Forecasted: The forecasted right-party connects.
RPC Actual: The actual right-party connects.
RPC % Deviation: The percentage deviation of the actual right-party connects
from the forecasted right-party connects.
Connects % Change from previous month: The percentage deviation of the
current month's actual connects from the prior month's actual connects.
Connects % Change from previous Year: The percentage deviation of the
current month's actual connects from the actual connects of the same month of the
prior year.
RPC % Change from previous month: The percentage deviation of the current
month's actual right-party connects from the prior month's actual right-party
connects.
RPC % Change from previous Year: The percentage deviation of the current
month's actual right-party connects from the actual right-party connects of the
same month of the prior year.
Performance Reports
These reports provide information on the forecasted, actual, and required statistics that
are displayed in Pulse.
Topics
Daily Comprehensive Performance, page 125
Daily Forecast Assessment, page 128
Daily Service Goals and Backlog, page 130
Monthly Forecast Assessment Summary, page 132
Monthly Service Goals Assessment Summary, page 134
Service Goals Assessment, page 135
Staffing Number Assessment By Interval, page 139
NOTE Performance reports require that the schedule information be current. You may have to
recalculate statistics (such as service level, average speed to answer, and number
scheduled) prior to generating these reports, in order for the reports to use the most current
data. In particular, this recalculation is necessary if the forecast has changed, or the
schedule has been changed.
For all performance reports, a value of "—" (two minus signs) means empty/unknown. For
example, you would see this when looking at future actual data, or past actual data where
the ACD was down. Unlike Pulse, the Performance Reports do not show trends. Missing data
is not the same as 0. 0 Means that the value is known, and it just happens to be 0.
All Performance Reports show data aggregated to particular intervals. For example, the Daily
Comprehensive Performance report shows hourly and daily aggregations. These
aggregations can be simple sums (such as for Contact Volume), or they can require more
complex aggregation formulas (such as for Service Level, which uses a weighted average).
Furthermore, if you selected more than one queue in the report parameters page, the
queues are first combined (using combination formulas, which can be different than the
aggregation formulas), and the resulting combined queue is the one displayed in the report.
report to understand if deviations from the contact volume or AHT forecasts are causing
the problems or if there are other causes, such as adherence problems.
Inputs
Date Frame: Specifies the date period for which the report is generated. This can
be set in one of two ways:
- Last <n> days: The last specified number of days, starting backwards from the
current date and time. A value of 0 returns data for today only.
NOTE The daily time range time selections still apply, so the report only shows the times of the day
that fall within this range. For example, if it is currently 3:00PM and Last <n> Days is 0,
and the Daily Time Range is 10:00 AM to 2:00 PM, the report output will only include data
for 10:00 AM to 2:00 PM today.
If the daily time range were 12:00 AM to 11:59 PM, the current time were 3:00 PM, and
Last <n> Days were 0, the Daily Time Range would not be a factor in this case, because
the daily time range includes the whole day. However, the report will only show data for
12:00 AM to 2:45 PM, since data for the 3:00 PM interval would not be known until 3:15 PM.
In other words, the data in the report is always 15 minutes behind the current time when
Last <n> Days is used.
From Time: Specifies the start time of the day. The From Time and To Time
parameters specify the time range within each day of the specified date range for
which the report is generated.
To Time: Specifies the end time of the day. The From Time and To Time
parameters specify the time range within each day of the specified date range for
which the report is generated.
Queue: Indicates the queue on which to report. Can be a single, multiple, or a
combined queue.
Time Zone: Indicates the time zone used for display.
Outputs
Day: The day of the week and date being reported.
Contact Volume Forecasted: The forecasted contact volume for that hour.
Contact Volume Actual: The actual contact volume for that hour.
Contact Volume % Deviation: The percentage deviation of the actual contact
volume from the forecasted contact volume.
AHT Forecasted: The forecasted average handling time.
AHT Actual: The actual average handling time.
AHT % Deviation: The percentage deviation of the actual average handling time
from the forecasted average handling time.
Service Level Required: The required service level for that hour.
Service Level Actual: The actual service level for that hour.
Service Level % Deviation: The percentage deviation of the actual service level
from the forecasted service level.
Daily Total: The total value of the corresponding statistic for the day.
Summary Information
The summary information reports the value, day of the week and date, and time for:
Contact Volume
- Highest: The highest single hourly Contact Volume value in the entire report.
- Lowest: The lowest single hourly Contact Volume value in the entire report.
- Highest % Deviation (Absolute): The Contact Volume % Deviation hourly
value with the greatest absolute value.
- Lowest % Deviation (Absolute): The Contact Volume % Deviation hourly
value with the least absolute value.
NOTE The above two rows compare absolute values. So, a value of -95 is considered greater than
a value of 94 because the absolute value of -95 is 95.
NOTE The above two rows compare absolute values. So, a value of -95 is considered greater than
a value of 94 because the absolute value of -95 is 95.
Service Level
- Highest: The highest single hourly Service Level value in the entire report.
- Lowest: The lowest single hourly Service Level value in the entire report.
- Highest % Deviation (Absolute): The Service Level % Deviation hourly value
with the greatest absolute value.
- Lowest % Deviation (Absolute): The Service Level % Deviation hourly value
with the least absolute value.
NOTE The above two rows compare absolute values. So, a value of -95 is considered greater than
a value of 94 because the absolute value of -95 is 95.
Forecasters can review this report to gauge how accurate their daily contact volume and
AHT forecasts are for individual queues or the combined queue for a campaign. They can
also see the highest and lowest contact volumes in the time period selected, as well as
the highest and lowest deviation. After identifying periods where deviation was high,
forecasters should review what actually happened during that day so they can improve
their forecasting technique for the future. Management can review this report to assess
forecasters’ performance.
Inputs
Date Frame: Specifies the date period for which the report is generated. This can
be set in one of two ways:
- Last <n> days: The last specified number of days, starting backwards from the
current date and time. A value of 0 returns data for today only.
NOTE The daily time range time selections still apply, so the report only shows the times of the day
that fall within this range. For example, if it is currently 3:00PM and Last <n> Days is 0,
and the Daily Time Range is 10:00 AM to 2:00 PM, the report output will only include data for
10:00 AM to 2:00 PM today.
If the daily time range were 12:00 AM to 11:59 PM, the current time were 3:00 PM, and Last
<n> Days were 0, the Daily Time Range would not be a factor in this case, because the
daily time range includes the whole day. However, the report will only show data for 12:00
AM to 2:45 PM, since data for the 3:00 PM interval would not be known until 3:15 PM. In
other words, the data in the report is always 15 minutes behind the current time when Last
<n> Days is used.
From Time: Specifies the start time of the day. The From Time and To Time
parameters specify the time range within each day of the specified date range for
which the report is generated.
To Time: Specifies the end time of the day. The From Time and To Time
parameters specify the time range within each day of the specified date range for
which the report is generated.
Queue: Indicates the queue on which to report. Can be a single, multiple, or a
combined queue.
Time Zone: Indicates the time zone used for display.
Outputs
Contact Volume Forecasted: The forecasted contact volume for that day.
Contact Volume Actual: The actual contact volume for that day.
Contact Volume % Deviation: The percentage deviation of the actual contact
volume from the forecasted contact volume.
AHT Forecasted (Seconds): The forecasted average handling time.
AHT Actual (Seconds): The actual average handling time.
AHT % Deviation: The percentage deviation of the actual average handling time
from the forecasted average handling time.
Summary Information
The summary information reports the value and day of the week and date for:
Contact Volume
- Highest: The highest single hourly Contact Volume value in the entire report.
- Lowest: The lowest single hourly Contact Volume value in the entire report.
- Highest % Deviation (Absolute): The Contact Volume % Deviation hourly
value with the greatest absolute value.
- Lowest % Deviation (Absolute): The Contact Volume % Deviation hourly
value with the least absolute value.
NOTE The above two rows compare absolute values. So, a value of -95 is considered greater than
a value of 94 because the absolute value of -95 is 95.
Inputs
Date Frame: Specifies the date period for which the report is generated. This can
be set in one of two ways:
- Last <n> days: The last specified number of days, starting backwards from the
current date and time. A value of 0 returns data for today only.
NOTE The daily time range time selections still apply, so the report only shows the times of the day
that fall within this range. For example, if it is currently 3:00PM and Last <n> Days is 0,
and the Daily Time Range is 10:00 AM to 2:00 PM, the report output will only include data
for 10:00 AM to 2:00 PM today.
If the daily time range were 12:00 AM to 11:59 PM, the current time were 3:00 PM, and
Last <n> Days were 0, the Daily Time Range would not be a factor in this case, because
the daily time range includes the whole day. However, the report will only show data for
12:00 AM to 2:45 PM, since data for the 3:00 PM interval would not be known until 3:15 PM.
In other words, the data in the report is always 15 minutes behind the current time when
Last <n> Days is used.
From Time: Specifies the start time of the day. The From Time and To Time
parameters specify the time range within each day of the specified date range for
which the report is generated.
To Time: Specifies the end time of the day. The From Time and To Time
parameters specify the time range within each day of the specified date range for
which the report is generated.
Queue: Indicates the queue on which to report. It can be a single, multiple, or a
combined queue.
Outputs
Service Level Required: The required service level for that day.
Service Level Forecasted: The forecasted service level for that day.
Service Level Actual: The actual service level for that day.
Service Level % Deviation from Required: The percentage deviation of the
actual service level from the required service level.
Backlog Forecasted: The forecasted backlog for that day.
Backlog Actual: The actual backlog for that day.
Backlog % Deviation from Forecasted: The percentage deviation of the actual
backlog from the required backlog.
NOTE For monthly reports, only the portions of the months that fall within the selected date range
and time range are included. For example, if you run the report from 5/15/08 to 7/15/08,
the output will show May 2008, June 2008, and July 2008, but only the “June 2008 row will
contain the data for the entire month. Non-monthly reports are a little different because the
specified time range applies to each day in the date range, so each daily aggregation only
includes the entire day’s data if the time range is 12:00 AM – 11:59 PM.
Forecasters can review this report to gauge how accurate their contact volume and AHT
forecasts are when aggregated to the monthly level. Management can review this report
to assess the forecaster's performance. Also, the % Change from Previous Month
and % Change from Previous Year columns can be used to detect trends in the
contact volume over time.
Inputs
Date Frame: Specifies the date period for which the report is generated. This can
be set in one of two ways:
- Last <n> days: The last specified number of days, starting backwards from the
current date and time. A value of 0 returns data for today only.
NOTE The daily time range time selections still apply, so the report only shows the times of the day
that fall within this range. For example, if it is currently 3:00PM and Last <n> Days is 0,
and the Daily Time Range is 10:00 AM to 2:00 PM, the report output will only include data
for 10:00 AM to 2:00 PM today.
If the daily time range were 12:00 AM to 11:59 PM, the current time were 3:00 PM, and
Last <n> Days were 0, the Daily Time Range would not be a factor in this case, because
the daily time range includes the whole day. However, the report will only show data for
12:00 AM to 2:45 PM, since data for the 3:00 PM interval would not be known until 3:15 PM.
In other words, the data in the report is always 15 minutes behind the current time when
Last <n> Days is used.
Outputs
Contact Volume Forecasted: The forecasted contact volume for that month.
Contact Volume Actual: The actual contact volume for that month.
Contact Volume % Deviation: The percentage deviation of the actual contact
volume from the forecasted contact volume.
AHT Forecasted (Seconds): The forecasted average handling time.
AHT Actual (Seconds): The actual average handling time.
AHT % Deviation: The percentage deviation of the actual average handling time
from the forecasted average handling time.
CV % Change from previous month: The percentage change of the contact
volume from the previous month.
CV % Change from previous year: The percentage change of the contact volume
from the same month of the previous year.
NOTE For monthly reports, only the portions of the months that fall within the selected date
range and time range are included. For example, if you run the report from 5/15/08 to 7/
15/08, the output will show May 2008, June 2008, and July 2008, but only the “June 2008
row will contain the data for the entire month. Non-monthly reports are a little different
because the specified time range applies to each day in the date range, so each daily
aggregation only includes the entire day’s data if the time range is 12:00 AM – 11:59 PM.
Inputs
Date Frame: Specifies the date period for which the report is generated. This can
be set in one of two ways:
- Last <n> days: The last specified number of days, starting backwards from the
current date and time. A value of 0 returns data for today only.
NOTE The daily time range time selections still apply, so the report only shows the times of the day
that fall within this range. For example, if it is currently 3:00PM and Last <n> Days is 0,
and the Daily Time Range is 10:00 AM to 2:00 PM, the report output will only include data
for 10:00 AM to 2:00 PM today.
If the daily time range were 12:00 AM to 11:59 PM, the current time were 3:00 PM, and
Last <n> Days were 0, the Daily Time Range would not be a factor in this case, because
the daily time range includes the whole day. However, the report will only show data for
12:00 AM to 2:45 PM, since data for the 3:00 PM interval would not be known until 3:15 PM.
In other words, the data in the report is always 15 minutes behind the current time when
Last <n> Days is used.
Outputs
Service Level Required: The required Service Level for that month.
ASA Required (Seconds): The required average speed to answer.
Service Level Forecasted: The forecasted Service Level for that month.
ASA Forecasted (Seconds): The forecasted average speed to answer.
Service Level Actual: The actual Service Level for that month.
ASA Actual (Seconds): The actual average speed to answer.
% Deviation from Required: The percentage deviation of the actual Service Level
or ASA from required.
% Change from previous month: The percentage change of the Service Level or
ASA from the previous month.
% Change from previous year: The percentage change of the Service Level or
ASA from the same month of the previous year.
Summary: The total value of the corresponding statistic for the entire date range.
Forecasters, schedulers, and management can review this report to quickly identify days
when the actual service levels (or ASA) deviated greatly from required or forecasted.
After identifying these days, they can investigate further to determine the cause of the
deviation (adherence problems, forecasted CV or AHT inaccuracies, over or
understaffing, or other causes).
Inputs
Date Frame: Specifies the date period for which the report is generated. This can
be set in one of two ways:
- Last <n> days: The last specified number of days, starting backwards from the
current date and time. A value of 0 returns data for today only.
NOTE The daily time range time selections still apply, so the report only shows the times of the day
that fall within this range. For example, if it is currently 3:00PM and Last <n> Days is 0,
and the Daily Time Range is 10:00 AM to 2:00 PM, the report output will only include data
for 10:00 AM to 2:00 PM today.
If the daily time range were 12:00 AM to 11:59 PM, the current time were 3:00 PM, and
Last <n> Days were 0, the Daily Time Range would not be a factor in this case, because
the daily time range includes the whole day. However, the report will only show data for
12:00 AM to 2:45 PM, since data for the 3:00 PM interval would not be known until 3:15 PM.
In other words, the data in the report is always 15 minutes behind the current time when
Last <n> Days is used.
From Time: Specifies the start time of the day. The From Time and To Time
parameters specify the time range within each day of the specified date range for
which the report is generated.
To Time: Specifies the end time of the day. The From Time and To Time
parameters specify the time range within each day of the specified date range for
which the report is generated.
Outputs
Day of the Week and Date: The day of the week and date being reported.
Service Level Required: The required service level for that day.
ASA Required (Seconds): The required average speed to answer.
Service Level Forecasted: The forecasted service level for that day.
ASA Forecasted (Seconds): The forecasted average speed to answer.
Service Level Actual: The actual service level for that day.
ASA Actual (Seconds): The actual average speed to answer.
ASA % Deviation from Required: The percentage deviation of the actual ASA
from the required ASA.
ASA % Deviation from Forecasted: The percentage deviation of the actual ASA
from the forecasted ASA.
Service Level % Deviation from Required: The percentage deviation of the
actual service level from the required service level.
Service Level % Deviation from Forecasted: The percentage deviation of the
actual service level from the forecasted service level.
Total: The total value of the corresponding statistic for the entire date range.
Value Color
Inputs
Organizations: Allows you to select one or more organizations for which you want
to run the report. If you select a parent organization, all of its child organizations
are also selected, but you can deselect individual child organizations.
Date Range: Specifies the date period for which the report is generated. This can
be set in one of two ways:
- Next <n> days: The specified number of days, starting from the current date
and time. A value of 0 returns data for today only.
- A specific date range, set using the date range selector.
Tolerance: The permissible % of deviation between service level and service goal.
Based on this setting, cells in the report are color-coded in green, yellow, or red,
depending on the deviation between the service level and the goal and tolerance.
Outputs
From: The starting date of the report’s date range.
To: The ending date of the report’s date range.
Organization: The organization(s) for which the report was run.
Tolerance: The permissible % of deviation between the service level and service
goal.
Work Queues: The list of work queues, one per row,
Data columns: Each column displays a date in the report’s date range. The values in
the cells are colored as described previously, depending on the deviation between
the service level and the goal and tolerance. Non-green-colored cells show the
service level and service goal percentages, separated by a slash character, unless
the work queue is a project queue, where the service level and service goal are
expressed in hours and minutes. Green-colored cells do not show the service level
and goal.
Schedulers and managers can use this report to evaluate whether appropriate staffing is
being provided for specific queues or for the campaign as a whole, in regard to both
planned staffing and actual staffing.
Inputs
Date Frame: Specifies the date period for which the report is generated. This can
be set in one of two ways:
- Last <n> days: The last specified number of days, starting backwards from the
current date and time. A value of 0 returns data for today only.
NOTE The daily time range time selections still apply, so the report only shows the times of the day
that fall within this range. For example, if it is currently 3:00PM and Last <n> Days is 0,
and the Daily Time Range is 10:00 AM to 2:00 PM, the report output will only include data
for 10:00 AM to 2:00 PM today.
If the daily time range were 12:00 AM to 11:59 PM, the current time were 3:00 PM, and
Last <n> Days were 0, the Daily Time Range would not be a factor in this case, because
the daily time range includes the whole day. However, the report will only show data for
12:00 AM to 2:45 PM, since data for the 3:00 PM interval would not be known until 3:15 PM.
In other words, the data in the report is always 15 minutes behind the current time when
Last <n> Days is used.
From Time: Specifies the start time of the day. The From Time and To Time
parameters specify the time range within each day of the specified date range for
which the report is generated.
To Time: Specifies the end time of the day. The From Time and To Time
parameters specify the time range within each day of the specified date range for
which the report is generated.
Queue: Indicates the queue on which to report. It can be a single, multiple, or a
combined queue.
Time Zone: Indicates the time zone used for display.
Outputs
Day of the Week and Date: The day of the week and date being reported.
FTE Required: The required Full Time Equivalents for that 15-minute interval.
FTE Forecasted: The forecasted Full Time Equivalents for that 15-minute interval.
FTE Over/Under: The difference between the forecasted and required FTEs.
FTE Actual: The actual Full Time Equivalents for that 15-minute interval.
FTE % Deviation from Required: The percentage deviation of the actual FTEs
from the required FTEs.
FTE % Deviation from Forecasted: The percentage deviation of the actual FTEs
from the forecasted FTEs.
Staffing Forecasted: The forecasted staffing for that 15-minute interval.
Staffing Actual: The actual staffing for that 15-minute interval.
Staffing % Deviation from Forecasted: The percentage deviation of the actual
staffing from forecasted staffing.
Report Total: The total value of the corresponding statistic for the entire date
range.
Related topics
Data Integrity Report, page 142
Input Parameters
Time Frame: Specifies the last defined number of days, starting backwards from
the current date. A value of zero (0) is invalid and generates an error message.
You can also specify a date range from the calendar fields.
Group By: Aggregates report data by CCD (Conditional Custom Data), CD (Custom
Data), Data Source, Employee, Employee ID, Extension, Organization, or
Recorder.
When grouping by Organization, only leaf organizations display in the reports.
If an employee is moved out of a leaf-organization and the report is run for the time
range when the employee was still in the leaf-organization, the report excludes data
for this employee for that organization.
The report excludes this data because the system does not retain history of the
user’s organizational change.
CD/CCD Field Selection: If you selected CD or CCD in the Group By field, select
the relevant CD or CCD field from this list.
If you selected a value other than CD or CCD in the Group By field, this parameter
is not relevant and unavailable.
Output Parameters
Group By value (CCD, CD, Data Source, Employee, Employee ID, Extension,
Organization, or Recorder): Displays the Group By value selected for the report
input parameter.
Recorded: Displays the number of call segments (Inums) that were recorded.
Not Archived: Displays the number of segments that were recorded but not
archived during the specified time period.
Campaign Name: Displays the campaigns under which the call segments were
archived. The campaign displayed in the report is the historical campaign that was
used originally to archive the recording. This does not reflect any recent changes to
the campaign rules.
The campaign name, Local Compliance Archive, represents call segments
archived by the Local Archive for 100% archiving.
If the Display Campaign Details parameter was selected, a line is shown for each
campaign under which calls were archived. If this parameter was not selected, a
single line displays the total value for all campaigns.
Archived: Displays the number of call segments that were archived at least once.
This count excludes any duplicates.
Total Archived (include duplicates): Displays the number of call segments that
were archived, including duplicates.
Storage (MB): Displays the total storage amount in MB. This value includes
records which may have been archived more than one time under the campaign.
Calculation
If the Input Storage Computation input parameter is selected, the system’s total
storage is calculated for the report. This calculation includes records that have been
archived more than one time under the campaign.
Topics
Single KPI Trend, page 145
Single KPI Trend vs. Peer, page 146
Team Aggregate Multi KPI, page 148
Team Detail Dual KPI, page 149
Team Detail Single KPI, page 151
Inputs
KPI: Allows you to select the desired organization and KPI by means of a pop-up
selector window.
Clicking the icon at the end of the Organization field opens the Organization
Selector pop-up window.
Once you have selected an organization, the KPI Selector window refreshes to
show additional fields.
Use the drop-down selectors to set the desired values for the KPI, Roll up Type,
and Person fields, and click Set.
Date: Allows you to specify the date for the data you want retrieved. Dates can be
specified in one of two ways:
- Last <number> <unit>
where:
<number> is the number of time units
<unit> is one of Completed Day(s), Completed Week(s), Completed
Month(s), Completed Quarter(s), or Completed Year(s)
Outputs
From: The date at which to start displaying scores.
To: The date for which to stop displaying scores.
Organization/Employee: The organization or employee for whom scores are to
be displayed.
KPI: The KPI to display.
Periodicity: The periodicity of the KPI.
A graph showing the KPI Actual Value, KPI Goal Value, and KPI Trend scores
for the selected employee for the specified dates.
Inputs
KPI: Allows you to select the desired organization and KPI by means of a pop-up
selector window.
Clicking the icon at the end of the Organization field opens the Organization
Selector pop-up window.
Once you have selected an organization, the KPI Selector window refreshes to
show additional fields.
Use the drop-down selectors to set the desired values for the KPI, Roll up Type,
and Person fields, and click Set.
Date: Allows you to specify the date for the data you want retrieved. Dates can be
specified in one of two ways:
- Last <number> <unit>
where:
<number> is the number of time units
<unit> is one of Completed Day(s), Completed Week(s), Completed
Month(s), Completed Quarter(s), or Completed Year(s)
- <periodicity> <start_date> <end_date>
where:
Outputs
From: The date at which to start displaying scores.
To: The date for which to stop displaying scores.
Organization/Employee: The organization or employee for whom scores are to
be displayed.
KPI: The KPI to display.
Periodicity: The periodicity of the KPI.
Roll-up Type: The roll-up type of the KPI: No Roll up, Person Roll up to
Supervisor, or Person Roll up to Organization.
A graph showing the KPI Actual Value, KPI Goal Value, and KPI Trend scores
for the selected employee for the specified dates.
Inputs
Organization: Allows you to select the desired organization by means of the pop-
up selector.
Period: Allows you to specify the date for the data you want retrieved. Dates can
be specified in one of two ways:
- Last completed <periodicity>
where:
<periodicity> is one of Day, Week, Month, Quarter, or Year
- <periodicity> <start_date> <end_date>
where:
<periodicity> is selected through a drop-down menu, and can be one of Daily,
Weekly, Monthly, Quarterly, or Annually.
<period> allows you to select the period for that periodicity using a date
selector.
You select the start date of the period; the end date of the period is
automatically filled in by the system.
Outputs
From: The starting date of the period being displayed.
To: The ending date of the period being displayed.
Organization: The organization for whom scores are displayed.
Periodicity: The periodicity of the KPI values being displayed.
Bar charts, each bar having its own scale, normalized so that the goals are at the
same x-coordinate. The Goal for each KPI is indicated as 100.
Inputs
KPI: Allows you to select the desired organization and KPI by means of a pop-up
selector window.
Clicking the icon at the end of the Organization / Employee Filter field opens the
Organization Selector pop-up window.
Clicking the radio button below it, and using the arrows to expand the drop-down
field allows you to select an existing employee filter.
Once you have selected an organization or employee filter, the KPI Selector
window refreshes to show additional fields.
Use the drop-down selectors to set the desired values for KPI 1, KPI 2, and the
Roll up Type, and click Set.
Period: Allows you to specify the date for the data you want retrieved. Dates can
be specified in one of two ways:
- Last completed <periodicity>
where:
<periodicity> is one of Day, Week, Month, Quarter, or Year
- <periodicity> <start_date> <end_date>
where:
Outputs
From: The date at which to start displaying scores.
To: The date for which to stop displaying scores.
Organization: The organization for which scores are to be displayed.
KPI 1: The first KPI to display.
KPI 2: The second KPI to display.
Periodicity: The periodicity of the KPI.
Roll-up Type: The roll-up type of the KPI: No Roll up, Person Roll up to
Supervisor, or Person Roll up to Organization.
A graph showing the actual and goal values for the two KPIs for the organization’s
or filter’s employees for the specified dates.
Inputs
KPI: Allows you to select the desired organization and KPI by means of a pop-up
selector window.
Clicking the icon at the end of the Organization field opens the Organization
Selector pop-up window.
Use the drop-down selector to set the desired values for the KPI, and click Set.
Date: Allows you to specify the date for the data you want retrieved. Dates can be
specified in one of two ways:
- Last <number> <unit>
where:
<number> is the number of time units
<unit> is one of Completed Day(s), Completed Week(s), Completed
Month(s), Completed Quarter(s), or Completed Year(s)
Outputs
From: The date at which to start displaying scores.
To: The date for which to stop displaying scores.
Organization: The organization for which scores are to be displayed.
KPI: The KPI to display.
Periodicity: The periodicity of the KPI.
Scorecards Reports
This report deals with Scorecards.
Inputs
Organization: Which organizations should be reported on. (The report will include
all sub-organizations of the selected organization as well.)
Outputs
Organization Name: The name of the organization that is reported on.
Objective Name: The name of the objective that is reported on.
KPI Name: The name of the KPI that is reported on, that belongs to a specific
objective in a specific organization.
Rule Syntax: The rule syntax is the KPI formula used to calculate the actual value
in the scorecard. The KPI belongs to a specific objective in a specific organization.
Topics
Assigned Schedules, page 155
Preference Achievement, page 160
Unassigned Agents, page 164
Unassigned Schedules, page 166
Assigned Schedules
This report lists all assigned schedules. It lists shifts for each agent that belongs to one
of the organizations, and who is scheduled for the given scheduling period.
The shifts are detailed for each working day of the week (scheduled period), and for
each shift there is a drill down of the activities for that shift. There is also a drill down for
each agent with his skills and proficiencies.
Inputs
Organization: Which organization should be reported on.
Schedule Period: Which schedule period should be reported on.
Group by: Which resolution should appear in the report for grouping. Select Name
or Day.
The following graphic shows the report with Group By set to Name:
The following graphic shows the report with Group By set to Day:
Outputs
Campaign: <name>: The campaign by which the schedules are grouped.
Week <start_date end_date>: The week that is being reported on.
Organization Name: <name>: The name of the organization by which the
schedules are grouped.
Organization Timezone: <timezone>: The timezone of the organization by
which the schedules are grouped.
Total Paid Hours: The amount of paid (scheduled) hours for the organization.
Total Assigned Shifts: The amount of assigned shifts for the organization.
Employee Name/Week Day: The value listed here is Employee Name if the
Group and Sort input parameter selected was Name or Week Day if the Group
and Sort input parameter selected was Day.
Week Day/Employee Name: The value listed here is Week Day if the Group
and Sort input parameter selected was Name or Employee Name if the Group
and Sort input parameter selected was Day.
Employee name by which the shifts are grouped: This value appears as the header
if the Group and Sort setting is Name. This header is a link to the Skill
Schedules Report subreport (see detailed description below). If the Group and
Sort setting is Day, the employee name does not appear as a header, but is still a
link to the Skill Schedules Report subreport.
Weekday by which the shifts are grouped: This value appears if the Group and
Sort setting is Day.
Shift: Details about the shift scheduled. The value of the column is a range of hours
of the shift. For example, 8:15:00 AM - 4:15:00 PM, and is also a link to the Shift
Schedules Report subreport (see detailed description below).
As mentioned previously, this report has two subreports:
Skill Schedules Report: Lists the skills of an agent, and the proficiency level for
each skill.
Outputs
- Employee Name: <name>: The agent that is reported on.
- SkillName: The name of the skill.
- Proficiency: The proficiency level for the skill.
- Shift Schedules Report: Displays start and end times for each activity in a
shift.
Outputs
- Shift: Range of hours for the shift. It has the same format that appeared in the
link that led to the subreport.
- Activities: The activities that occurred during the shift. It includes activity event
start time, activity event end time, and the activity name.
Preference Achievement
This report enables supervisors to evaluate which agents received their preferences. It
also shows the percentage of auctions with approved bids, and the average preferences
achieved by the agent and by the group.
Inputs
Group and Sort: Which resolution should appear for grouping and sorting: Name
or Average.
Organization: Which organization should be reported on.
Time Frame: This specifies the time range for which the report is generated.
Outputs
Period <start_date - end_date>: The period that is being reported on.
Organization Name: <name>: The name of the organization by which the
schedules are grouped.
The data contained on the report varies according to the setting of Group and Sort.
If Group and Sort is set to Name, the output is as shown previously:
The name of the employee being reported on.
Number of Bids: The number of bids this employee submitted.
Approved Bid Preference: The agent’s preference corresponding to those bids
which were approved.
Total: Total number of bids.
Number of bids: The number of bids placed by all the employees in the
organization in the given period.
% Approved: The percentage of bids approved out of all bids, for all the
employees in the organization.
Average Preference: The ratio between the number of approved bids, and the
number of auctions that contain at least one approved bid.
If Group and Sort is set to Average, the output is as follows:
Unassigned Agents
This report lists agents currently unassigned to a schedule, or not currently meeting
their minimum hours rule. You can also confirm with this report if agents have entered
their bids.
Inputs
Group and Sort: Which resolution should appear in the report for grouping and
sorting. Select Name, Min Hours, or Scheduled Hours.
Organization: Which organizations are being reported on.
Schedule Period: Which schedule period is being reported on.
Outputs
Campaign: <campaign_name>: The campaign by which the schedules are
grouped.
Week: <start_date - end_date>: The week that is reported on.
Organization Name: <organization_name>: The name of the organization by
which the schedules are grouped.
Employee Name: The agent that is reported on.
The name of the employee. It serves as a link to the Skill Schedules Report
subreport (see detailed description below).
Min/Max hours HH:MM: The ratio between the minimum amount of time that the
agent can be scheduled in the scheduled period, and the maximum amount of time
that the agent can be scheduled in the scheduled period. For example 30.00/
40.00.
In reports that show hours, minutes are shown as decimal portions of an hour. For example, 2 hours 30
minutes would be shown as 2.5 hours.
Hours Scheduled HH:MM: The number of hours scheduled for the agent, for the
scheduled period.
Bids: The number of bids placed by the agent, for the scheduled period.
As mentioned previously, this report has a subreport:
Skill Schedules Report: Lists the skills of an agent, and the proficiency level for
each skill.
Outputs
- Employee Name: <name>: The agent that is being reported on.
- SkillName: The name of the skill.
- Proficiency: The proficiency level of the skill.
Unassigned Schedules
This report lists all currently unassigned schedules. For each day in the campaign week,
it shows schedules assigned to phantom employees. The results are grouped for each
campaign, then for each organization, and then by the specified grouping.
Inputs
Organization: Which organization should be reported on.
Schedule Period: Which schedule period should be reported on.
Group By: Which resolution should appear in the report for grouping. Select Name
or Day.
Outputs
Campaign: <campaign_name>: The name of the campaign by which the
schedules are grouped.
Week: <start_date - end_date>: The week that is being reported on.
Organization Name: <organization_name>: The name of the organization by
which the schedules are grouped.
Organization Timezone: The time zone of the organization by which the
schedules are grouped.
Total Paid Hours: The number of paid (scheduled) hours for the organization.
Total Unassigned Shifts: The number of unassigned shifts for the organization.
The data contained on the remainder of the report varies according to the setting of
Group By.
If Group By is set to Name, the output is as follows:
Template Name: The name of the phantom employee that is being reported on.
Week Day: The weekday that is being reported on.
Shift: Details about the shift scheduled. The value of the column is a range of hours
of the shift. For example, 7:30 AM - 6:00 PM, and is also a link to the Shift
Schedules Report subreport (see detailed description below).
<template_name>: The name of the phantom agent by which the shifts are
grouped. It is also a link to the Skill Schedules Template subreport (see detailed
description below).
<weekday>: The weekday by which the shifts are grouped. It is also a link to the
Skill Schedules Template subreport (see detailed description below).
As mentioned previously, this report has two subreports:
Skill Schedules Report: Lists the skills of an agent, and the proficiency level for
each skill.
Outputs
- Template Name: <name>: The phantom employee that is reported on.
- Skill: The name of the skill.
- Proficiency: The proficiency level for the skill.
Shift Schedules Report: Displays start and end times for each activity in a shift.
Outputs
- Shift: Range of hours for the shift. It has the same format that appeared in the
link that led to the subreport.
- Activities: The activities that occurred during the shift. It includes activity event
start time, activity event end time, and the activity name.
Staffing Reports
These reports deal with employee schedules.
Staffing reports can be run against both published and unpublished schedules.
Topics
Daily Planned Time Assessment by Employee, page 171
Employee Calendar Events, page 174
Employee Schedule by AgentID, page 175
Employee Schedule by Date, page 176
Employee Schedule by Employee, page 179
Employee Shift Assignments, page 184
Net Staffing Report, page 187
Planned Activity Cost (Unburdened), page 190
Planned Media Cost (Unburdened), page 193
Planned Staffing Numbers By Interval, page 194
Planned Time Assessment, page 197
Weekly Planned Time Assessment by Employee, page 200
NOTE Activity data is counted on the workday (or campaign day) on which the parent shift
assignment begins. Scheduled activities that are not inside a shift assignment are not
included in this report.
Schedulers can use this report to verify the amount of paid time and/or contact time for
each employee. When used in conjunction with an appropriate filter, this report can be
especially helpful in situations where the schedulers are required to provide a specific
number of hours (for example, part-timers cannot exceed 30 paid hours) or distribute
hours “fairly” across a particular group (for example, all technical support
representatives should receive a similar number of hours handling customer contacts).
Inputs
Employee Filter: Indicates the set of employees to report on.
Schedule Period (reports that are in view time zone): These reports generally
return a single aggregation for the specified time period or a set of records
corresponding to all events that start in or intersect the time period.
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
- Schedule Period: Applies an additional constraint, that employees must be in
the selected week of the campaign or scheduling period.
NOTE When this mode is selected, aggregation is no longer per organization workday but per
campaign day.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
NOTE Only calendar events that are “topmost” are returned. For example, if a calendar event is
dominated by a vacation, it is not returned in this report.
Schedulers can use this report to review what calendar events have been assigned.
Filtered instances of this report can be provided to supervisors or managers as a
reference for those meetings, training periods, and so on, assigned to their employees.
This report can be especially helpful if these supervisors/managers are not given any
access to view employee schedules online.
Inputs
Employee Filter: Indicates the set of employees to report on.
Schedule Period (reports that are in view time zone): These reports generally
return a single aggregation for the specified time period or a set of records
corresponding to all events that start in or intersect the time period.
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
- Schedule Period: Applies an additional constraint, that employees must be in
the selected week of the campaign or scheduling period.
NOTE When this mode is selected, aggregation is no longer per organization workday but per
campaign day.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
Related topics
Employee Schedule by Date, page 176
Schedulers can use this report to review employee shift assignments prior to publishing
the final schedule. This report can also be used to distribute information about basic
employee schedules (days and start/end times, but not activity details) to individuals
who do not have access to view schedules online.
Inputs
Employee Filter: Indicates the set of employees to report on.
NOTE When the filtered set of employees is large, this report might time out. In such cases, ask
your administrator to increase the setting of the General Setup parameter Request
Timeout (minutes). The default setting is 10; increasing the value to 30 or 60 should allow
the report to run without timing out.
Schedule Period (reports that are in view time zone): These reports generally
return a single aggregation for the specified time period or a set of records
corresponding to all events that start in or intersect the time period.
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
- Schedule Period: Applies an additional constraint, that employees must be in
the selected week of the campaign or scheduling period.
NOTE When this mode is selected, aggregation is no longer per organization workday but per
campaign day.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
Retail Managers and Retail Regional Managers can use this report to view employee shift
assignments in one week intervals per table. It provides the schedules of employees by
week at different levels of detail, including Shift, Shift and Lunch, or Shift and All Shift
Events. This report can also be used to distribute information about basic employee
schedules (days and start/end times, but not activity details) to individuals who do not
have access to view schedules online.
Inputs
Employee Filter: Indicates the set of employees to report on.
Schedule Period (reports that are in view time zone): These reports generally
return a single aggregation for the specified time period or a set of records
corresponding to all events that start in or intersect the time period.
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
- Schedule Period: Applies an additional constraint, that employees must be in
the selected week of the campaign or scheduling period.
NOTE When this mode is selected, aggregation is no longer per organization workday but per
campaign day.
Outputs
Employee schedules by day by employee for each week in the selected period.
From: The selected scheduling period from date. The first table displayed will start
with this date. A maximum of one week is displayed per table.
To: The selected scheduling period to date. This is the last date to display in the
table(s).
Filter By: The selected employee filter.
Source: The selected published or unpublished schedules.
Organization: The selected organization for reporting.
Columns
Employee: The name of the employee(s) being reported on.
Date(s): A column for each day included in the selected scheduling period. A
maximum of one week is displayed per table.
If schedules are created well in advance of the schedule week, and schedulers want to
give employees a preview of the schedules without publishing, they can run this report
and distribute it so that employees can see expected start and stop times, and what
shifts they are working. If there are rules that require certain employees to work specific
shifts each week (for instance, Employee must work two to four shifts named 8 1/2
hour shift -2 each week), schedulers might also review this report to see how those
scheduling goals were achieved.
Inputs
Employee Filter: Indicates the set of employees to report on.
Schedule Period (reports that are in view time zone): These reports generally
return a single aggregation for the specified time period or a set of records
corresponding to all events that start in or intersect the time period.
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
- Schedule Period: Applies an additional constraint, that employees must be in
the selected week of the campaign or scheduling period.
NOTE When this mode is selected, aggregation is no longer per organization workday but per
campaign day.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
Inputs
Employee Filter: Choose the employees to include on the report
Schedule Period (reports that are in view time zone): These reports generally
return a single aggregation for the specified time period or a set of records
corresponding to all events that start in or intersect the time period.
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
- Schedule Period: Applies an additional constraint, that employees must be in
the selected campaign or scheduling period.
Use Published Schedules: Indicates whether to use published or unpublished
schedules.
Outputs
Employee: Name of the employee and their related time off information. This
column also lists the employee’s organization and month of the report.
Total Time (Hours): Total hours for the employee in the month of the report
Paid Time (Hours): Paid hours for the employee during the month
Work Time (Hours): Actual work hours for the employee during the month
Contact Time (Hours): Amount of time scheduled activity is linked to a media
such as email or phone.
Overtime: Amount of overtime for the employee during the month
Voluntary Time Off (Hours): Amount of time off taken by the employee
Work (%): Percentage of time the employee was working during the month
Contact (%): Percentage of time the employee spent on media such as email or
phone.
Paid (%): Percentage of paid time for the employee during the month
Overtime (%): Percentage of overtime for the employee during the month
Voluntary Time Off (%): Percentage of time off taken by the employee during the
month
Inputs
The parameters for this report are the same as the Daily Forecast Assessment
report.
NOTE If you select two or more queues, the report shows statistics for each queue individually
and then shows statistics for the combined queues.
If you select one or more queues belonging to a non-skilled scheduling period, the
report will produce data only for Combined - Phone. For non-skilled periods, some data
are only stored for the combined queues. Although you can select individual queues for
non-skilled scheduling periods, Net Staffing cannot be calculated in these instances.
Outputs
Queue Name: The name of the queue from the Pulse section.
Date: The date of the net staffing statistics.
Interval: The report provides net staffing calculations at 15 minute intervals. Each
row on the report represents a fifteen minute interval for the date indicated. All
fields in the row apply to the time interval displayed here.
CV Forecasted: Volume of forecasted calls from the Pulse section.
CV Actual: Volume of actual calls from the Pulse section.
CV Absolute Deviation: Absolute value of forecasted volume less actual volume.
CV % Deviation: Ratio of forecasted volume to actual volume, expressed as a
percentage
[(forecasted calls) / (actual calls) - 1].
AHT Forecasted: Forecasted average handle time (AHT) in seconds.
AHT Actual: Actual AHT in seconds.
AHT Absolute Deviation: Absolute value of forecasted AHT less actual AHT.
[|(forecasted AHT) - (actual AHT)|]
AHT % Deviation: Ratio of forecasted AHT to actual AHT, expressed as a
percentage.
[(forecasted AHT) / (actual AHT) - 1]
Staffing Required: Ratio of staffing forecasted to forecasted full-time equivalent
(FTE) multiplied by the required FTE.
[((staffing forecasted) / (forecasted FTE)) * required FTE]
NOTE Required FTE: Calculated for each queue and represents the staff needed to meet
service levels for the queue if staffed with a single skill (dedicated environment). For a
combined queue, as represented for a skill-based campaign, the required FTE is the
sum of the requirements for each queue. Note that for a non-skills campaign, there is
only a single requirement generated for the combined forecast.
Forecasted FTE: Calculated for each queue by aggregating the expected contribution
of each employee with the corresponding skill. Because skill-based routing introduces
leveraging of employee time across multiple queues, the total expected contribution for
a particular employee can be more than 1 FTE for a skill-based campaign. When the
combined queue results are totaled for a skill-based campaign, you could have more
FTEs forecasted than there are staffing forecasted. The forecasted FTE should match the
FTEs Forecasted from the Pulse section.
Staffing forecasted: Number of employees scheduled to handle volume. For each
queue, this is the number of employees scheduled for activity who have the appropriate
skill assigned. For the combined queue, this is the total number of employees scheduled
for activities. This value should match the Staffing Forecasted as displayed in the Pulse
section.
NOTE The staff required calculation is based on the ratio of Staffing Forecasted to Forecasted FTE
(Staffing Forecasted / Forecasted FTE). Then, the ration is multiplied times the Required FTE.
NOTE The actual staff depends on how the staffing value is being collected. It is either the number
provided by the ACD integration, or the number calculated by the Staffing Calculator
adapter. This value should match the Staffing Actual as displayed in the Pulse section.
Net Staffing (Forecasted - Actual): Number of staff scheduled less the number
of actual staff. This is not the same net staffing calculation used by the suite (staff
scheduled - staff required).
Actual Service Level: Actual service level from the Pulse section.
Forecasted Service Level: Forecasted service level from the Pulse section.
Related topics
Daily Forecast Assessment, page 128
Schedulers can view this report to see how much time is scheduled to be in each activity
over the selected period of time, and how that time is allocated among the employees.
They can also see the cost implications of scheduling each activity. For instance, a
scheduler can run the report for a month to see how much time certain employees are
scheduled in meetings, and the cost for those meetings (based on employee wages).
Inputs
Employee Filter: Indicates the set of employees to report on.
Time Frame (reports that are in view time zone): These reports generally return a
single aggregation for the specified time period or a set of records corresponding to
all events that start in or intersect the time period.
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
- Schedule Period: Applies an additional constraint, that employees must be in
the selected week of the campaign or scheduling period.
NOTE When this mode is selected, aggregation is no longer per organization workday but per
campaign day.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For example,
2 hours 30 minutes would be shown as 2.5 hours.
Combined Total: The totals for all organizations being reported on of the Paid
Time, Unpaid Time, Total Time, and Estimated Cost.
Schedulers or managers can view this report to see how much time is scheduled for
handling of each media type over the selected period of time, and how that time is
allocated among the employees. They can also see the cost of serving each media type
(based on employee wages).
Inputs
Employee Filter: Indicates the set of employees to report on.
Time Frame (reports that are in view time zone): These reports generally return a
single aggregation for the specified time period or a set of records corresponding to
all events that start in or intersect the time period.
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For example,
2 hours 30 minutes would be shown as 2.5 hours.
Schedulers can use this report to review the number of agents scheduled in different
periods of the day, and to identify periods in which non-contact activities, such as
calendar events, time off and unavailability, have an impact on staffing levels.
Inputs
Employee Filter: Indicates the set of employees to report on.
Time Frame (reports that are in view time zone): These reports generally return a
single aggregation for the specified time period or a set of records corresponding to
all events that start in or intersect the time period.
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Time Zone: Indicates the time zone used for display.
Use Published Schedules: Indicates whether to use published or unpublished
schedules.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
NOTE If the employee filter does not include all employees in the organization, the aggregation will
be incomplete.
Schedulers can view this report to see quickly for the group how many employees are
scheduled each day, and how much work (on media) versus non-work and paid versus
unpaid time is scheduled, as well as the total cost of the schedules. It may be
particularly useful to review how much work time versus non-work time is scheduled to
understand planned utilization for the group.
Inputs
Employee Filter: Lists the organization on which to report.
Schedule Period (reports that are by day and in organization time zone):
- Last <X> days: This field specifies which days to report on. This mode should
return the last X completed workdays for an organization, however, as
implemented, it sets the From-date to the current day in the time zone of the
SQL Server computer minus X days and the To-date to the current day in the
time zone of the SQL Server computer. Depending on the difference between
the SQL Server computer's time zone and the organization's time zone and day/
week boundary, this may not be the last X completed workdays.
- From/To date (reports that are in organization time zone): These reports are
generally by day or by week. Here, by day/week means the organization's
workday or workweek, considering day and week boundaries. So, let’s say you
want to report on the workdays 1/10/04 through 1/15/04. The workday
named 1/10/04 is actually 1/10/04 8:00 a.m. through 1/11/04 8:00 a.m. (in the
organization's time zone). It will map differently in GMT. Now let’s also
assume that you are reporting on multiple organizations, each with different
time zones and day/week boundaries. You are requesting data on 1/10/04
through 1/15/04, but this could map to different absolute times for each
organization. For example:
Org A: 1/10/04 3:00 a.m. - 1/11/04 3:00 a.m., 1/11/04 3:00 a.m. - 1/12/04
3:00 a.m....
Org B: 1/10/04 8:00 a.m. - 1/11/04 8:00 a.m., 1/11/04 8:00 a.m. - 1/12/04
8:00 a.m....
- Use Published Schedules: Indicates whether to use published or unpublished
schedules.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For example,
2 hours 30 minutes would be shown as 2.5 hours.
Contact Time (Hours): Time is considered contact time if the scheduled activity is
linked to a media.
Paid Time (Hours): Total Paid time for workday. See Is Paid on page 45.
Total Time (Hours)
Cost: The value of Paid Time multiplied by the employee's hourly wage.
Overtime: The number of overtime hours, excluding overtime gaps.
Voluntary Time Off: The number of voluntary time off hours.
Organization Total: The totals for that organization of the Work Time, Contact
Time, Paid Time, and Total Time.
Combined Total: The totals for all organizations being reported on of the Work
Time, Contact Time, Paid Time, and Total Time.
Related topics
Daily Planned Time Assessment by Employee, page 171
NOTE All work weeks that start within the Time Frame input boundaries are aggregated in full.
Schedulers can view this report to see how much time employees are scheduled each
week. This can be particularly useful in identifying if some employees must be paid
overtime (if overtime is determined by weekly hours), or if hours were distributed fairly
(if that is a concern). It also provides a quick view of how much scheduled time is paid
versus unpaid, and work (on media) versus non-work. The uses for this report are
similar to those of the Daily Planned Time Assessment report.
NOTE To access this report you must be licensed for the Time Banking feature.
Topics
Weekly Time Bank Balances By Employee, page 202
Inputs
The parameters for this report are the same as the Weekly Planned Time
Assessment by Employee report.
NOTE The report locates all time banks for the employee that intersect the date range you select for
the Schedule Period parameter.
For example, assume the report date range is 1/1/2012 through 6/30/2012, and an employee’s
time bank assignments are:
Time Bank A (3/1/11 - 2/28/12)
Time Bank B (3/1/12 - 2/28/13)
The report will include both Time Bank A and Time Bank B. If you select a schedule period for
the Schedule Period parameter (the third radio button option), it will only be used for choosing
the date range.
The Schedule Period will only be used for choosing the date range. The schedule period does not
filter employees or function in any other way. The output will span the start of any time bank
that intersects the time frame, to the end of the last Base Period that does not start after the
end date of the time frame.
Outputs
Organization: The time bank's organization name. Note that time bank’s
organization does not necessarily correspond to be the employee’s organization.
Time Bank: The name of a time bank to which the employee is assigned for the
report date range.
Base Period: The start and end date of the base period, for example, a work week,
within the report's date range.
IMPORTANT To ensure balances are as accurate as possible, the report includes all balances from the start of
the time bank up to the end of the last base period within the end date specified.
For example, assume an employee is in a time bank starting on 1/1/12 and ending on 12/31/
12. You run a report using a date range from 3/1/12 12:00 AM to 4/1/12 11:59 PM. In this
scenario, the report includes all base periods from 1/1/12 (the start of the time bank) to 4/1/11
(the end of the last base period within the report date range).
If there exists a base period from 3/31/12 to 4/6/12, then it will be included in the report
because it starts within the date range.
However, a base period that starts on 4/2/12 will not be included in the report.
NOTE Overtime (OT) does not count as paid time (as in Forecasting and Scheduling).
Paid time includes only time within a shift assignment.
Paid time includes voluntary time off (VTO) and paid vacations.
Adjusted (Hours): Any schedule adjustments for the employee within the base
period.
Paid + Adjusted (Hours): Sum of paid and adjustment hours.
Target (Hours): Number of hours the employee is required to work within the
base period. The target figure is the same Target Hours shown in Forecasting and
Scheduling for the base period.
Balance (Hours): Total Paid + Adjustments (Hours) less Target hours.
Balance (%): Ratio of Balance hours to Target hours, expressed as a percentage.
Related topics
Weekly Planned Time Assessment by Employee, page 200
Topics
Absence Hours and Absence Shrinkage for Employee by Time, page 206
Absence Hours and Absence Shrinkage for Employee Filter by Employee, page 209
Absence Hours and Absence Shrinkage for Employee Filter by Organization,
page 211
Absence Hours and Absence Shrinkage for Employee Filter by Time, page 212
Absence Numbers for Employee by Time, page 215
Absence Numbers for Employee Filter by Employee, page 216
Absence Numbers for Employee Filter by Organization, page 218
Absence Numbers for Employee Filter by Time, page 219
Time Off Allocations by Time, page 221
Time Off Requests for Employee by Time, page 223
Time Off Requests for Employee Filter by Organization, page 225
Time Off Requests for Employee Filter by Time, page 227
Time Off Summary for Employee, page 228
Time Off Summary for Employee Filter, page 232
Time Off Waitlisted Requests for Employee Filter, page 235
Time Off Withdrawn Requests for Employee Filter, page 238
Vacation Hours, page 240
Inputs
Employee: Which employee should be reported on.
Time Off Activity: Which time off activity should be reported on. (Select All Time
Off for all activities.)
Group By: Which time resolution should appear in the report for grouping. Select
Day, Week, Month or Year.
Time Frame:
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Published: Which activities should be reported on: published or unpublished
activities (that is, activities that are part of a published or unpublished schedule).
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For example,
2 hours 30 minutes would be shown as 2.5 hours.
Inputs
Employee Filter: Which employees should be reported on.
Time Off Activity: Which time off activity should be reported on. (Select All Time
Off for all activities.)
Time Frame:
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Published: Which activities should be reported on: published or unpublished
activities (that is, activities which are part of a published or unpublished schedule).
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For example,
2 hours 30 minutes would be shown as 2.5 hours.
Employee Filter: The filter for which the employees’ activities are being reported.
Source: Published Schedules if the Published input parameter check box was
checked. Unpublished Schedules if it was unchecked.
Employee Name: The employee’s whose activities are being reported.
Total Absence: The amount of time the agent was absent for the reported activity,
for each employee.
Paid Hours Scheduled: The amount of paid hours scheduled for the reported
activity, for each employee.
Absence Shrinkage (%): The percentage of absence hours out of paid hours, for
each employee. It is the ratio between Total Absence and Paid Hours
Scheduled.
In the Summary section:
Total Absence: A summation of Total Absence for all employees in the filter.
Total Paid Hours Scheduled: A summation of Paid Hours Scheduled for all
employees in the filter.
Absence Shrinkage: (%): The percentage of absence hours out of paid hours, for
all employees in the filter. It is the ratio between Total Absence (the second,
summary one) and Total Paid Hours Scheduled.
Inputs
Employee Filter: Which employees should be reported on.
Time Off Activity: Which time off activity should be reported on. (Select All Time
Off for all activities.)
Time Frame:
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Published: Which activities should be reported on: published or unpublished
activities (that is, activities which are part of a published or unpublished schedule).
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For example,
2 hours 30 minutes would be shown as 2.5 hours.
Employee Filter: The filter for which the employees’ activities are being reported.
Source: Published Schedules if the Published input parameter check box was
checked. Unpublished Schedules if it was unchecked.
Organization Name: The organization’s whose activities are being reported.
Total Absence: The amount of time the agent was absent for the reported activity,
for all filtered employees belonging to the organization.
Paid Hours Scheduled: The amount of paid hours scheduled for the reported
activity, for all filtered employees belonging to the organization.
Absence Shrinkage (%): The percentage of absence hours out of paid hours, for
all filtered employees belonging to the organization. It is the ratio between Total
Absence and Paid Hours Scheduled.
In the Summary section:
Total Absence: A summation of Total Absence for all filtered employees.
Total Paid Hours Scheduled: A summation of Paid Hours Scheduled for all
filtered employees.
Absence Shrinkage: (%): The percentage of absence hours out of paid hours, for
all filtered employees. It is the ratio between Total Absence (the second, summary
one) and Total Paid Hours Scheduled.
Inputs
Employee Filter: Which employees should be reported on.
Time Off Activity: Which time off activity should be reported on. (Select All Time
Off for all activities.)
Group By: Which time resolution should appear in the report for grouping. Select
Day, Week, Month or Year.
Time Frame:
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Published: Which activities should be reported on: published or unpublished
activities (that is, activities that are part of a published or unpublished schedule).
Outputs
NOTE When the report has been run using the Last <x> days parameter, the
report header’s From field shows the value of that parameter, such as
From: Last 30 days. This is in contrast to previous releases, where the
From field showed a date.
NOTE In reports that show hours, minutes are shown as decimal portions of an
hour. For example, 2 hours 30 minutes would be shown as 2.5 hours.
Employee Filter: The filter for which the employees’ activities are being reported.
Source: Published Schedules if the Published input parameter check box was
checked. Unpublished Schedules if it was unchecked.
Date according to the time resolution grouping.
Total Absence: The amount of time the agent was absent for the reported activity,
for each time resolution group.
Paid Hours Scheduled: The amount of paid hours scheduled for the reported
activity, for each time resolution group.
Absence Shrinkage (%): The percentage of absence hours out of paid hours, for
each time resolution group. It is the ratio between Total Absence and Paid Hours
Scheduled.
In the Summary section:
Total Absence: A summation of Total Absence for all filtered employees.
Total Paid Hours Scheduled: A summation of Paid Hours Scheduled for all
filtered employees.
Absence Shrinkage: (%): The percentage of absence hours out of paid hours, for
all filtered employees. It is the ratio between Total Absence (the second, summary
one) and Total Paid Hours Scheduled.
Inputs
Employee: Which employee should be reported on.
Time Off Activity: Which time off activity should be reported on. (Select All Time
Off for all activities.)
Group By: Which time resolution should appear in the report for grouping. Select
Day, Week, Month or Year.
Time Frame:
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Published: Which activities should be reported on: published or unpublished
activities (that is, activities which are part of a published or unpublished schedule).
Outputs
NOTE When the report has been run using the Last <x> days parameter, the
report header’s From field shows the value of that parameter, such as
From: Last 30 days. This is in contrast to previous releases, where the
From field showed a date.
separately for each day. No more than one event with the same activity is counted per
day. Results are accumulated for all the employees in the filter.
Inputs
Employee Filter: Which employees should be reported on.
Time Off Activity: Which time off activity should be reported on. (Select All Time
Off for all activities.)
Time Frame:
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Published: Which activities should be reported on: published or unpublished
activities (that is, activities which are part of a published or unpublished schedule).
Outputs
NOTE When the report has been run using the Last <x> days parameter, the
report header’s From field shows the value of that parameter, such as
From: Last 30 days. This is in contrast to previous releases, where the
From field showed a date.
Inputs
Employee Filter: Which employees should be reported on.
Time Off Activity: Which time off activity should be reported on. (Select All Time
Off for all activities.)
Time Frame:
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Published: Which activities should be reported on: published or unpublished
activities (that is, activities which are part of a published or unpublished schedule).
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
separately for each day. No more than one event with the same activity is counted per
day. Results are accumulated for all filtered employees, by time resolution.
Inputs
Employee Filter: Which employees should be reported on.
Time Off Activity: Which time off activity should be reported on. (Select All Time
Off for all activities.)
Group By: Which time resolution should appear in the report for grouping. Select
Day, Week, Month or Year.
Time Frame:
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
Inputs
Time Off Pool: Which time-off pools should be reported on.
Group By: Which time resolution should appear in the report for grouping. Select
Day, Week, Month or Year.
Time Frame:
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Published: Which activities should be reported on: published or unpublished
activities (that is, activities which are part of a published or unpublished schedule).
Outputs
NOTE When the report has been run using the Last <x> days parameter, the
report header’s From field shows the value of that parameter, such as
From: Last 30 days. This is in contrast to previous releases, where the
From field showed a date.
Source: Published Schedules if the Published input parameter check box was
checked. Unpublished Schedules if it was unchecked.
The time-off pool that is reported on.
The allocations defined for this organization if the reported organization is also the
organization on which the time off activities were allocated. Otherwise, if the
reported organization is not also the organization on which the time off activities
were allocated, the allocations defined for all the root organizations.
Period: The period being reported on.
Allocated (Hours): The amount of time off that was allocated for all the agents in
the time-off pool, for each time resolution group.
NOTE In reports that show hours, minutes are shown as decimal portions of an
hour. For example, 2 hours 30 minutes would be shown as 2.5 hours.
Scheduled (Hours): The amount of time off that was scheduled for all the agents
in the time-off pool, for each time resolution group.
Remaining (Hours): The amount of time off that was allocated but not scheduled
for all the agents in the time-off pool, for each time resolution group.
Total: Summation for Allocated, Scheduled, and Remaining for the time-off
pool for all periods.
Inputs
Employee: Which employee should be reported on.
Time Off Activity: Which time off activity should be reported on. (Select All Time
Off for all activities.)
Group By: Which time resolution should appear in the report for grouping. Select
Day, Week, Month or Year.
Time Frame:
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Time Zone: In which time zone the results should appear.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the
report header’s From field shows the value of that parameter, such as
From: Last 30 days. This is in contrast to previous releases, where the
From field showed a date.
Inputs
Employee Filter: Which employees should be reported on.
Time Off Activity: Which time off activity should be reported on. (Select All Time
Off for all activities.)
Time Frame:
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Time Zone: In which time zone the results should be displayed.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the
report header’s From field shows the value of that parameter, such as
From: Last 30 days. This is in contrast to previous releases, where the
From field showed a date.
Inputs
Employee Filter: Which employees should be reported on.
Time Off Activity: Which time-off activity should be reported on. (Select All Time
Off for all activities.)
Group By: Which time resolution should appear in the report for grouping. Select
Day, Week, Month or Year.
Time Frame:
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Time Zone: In which time zone the results should be displayed.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the
report header’s From field shows the value of that parameter, such as
From: Last 30 days. This is in contrast to previous releases, where the
From field showed a date.
time off year. If the employee has been terminated, the last organization to which the
employee was assigned is used to determine the time-off year.
The results are presented for different time off activities. Time off requests are
presented for the selected time period. This report consists of three tables.
Inputs
Employee: Which employee should be reported on.
Time Frame:
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For
example, 2 hours 30 minutes would be shown as 2.5 hours.
If your license includes the optional Time-Off Accrual feature (and providing that Report
Dump has run), an additional column, Carryover (Hours), is shown. This column
shows the balance of hours carried over from the previous year.
Used (Hours): The amount of time off that was used by the agent (the amount of
time the agent was absent) for each activity.
Scheduled (Hours): The amount of time off scheduled for the agent, for each
activity.
Remaining (Hours): The amount of time off that was scheduled for the agent, but
not used, for each activity.
NOTE If your license includes the optional Time-Off Accrual feature, the Allotted (Hours),
Carryover (Hours), and Remaining (Hours) columns’ data only appear for the accrual
category rows, and the rows for activities whose category is set to not use accrual.
Time Off Activities: (A column in the Time Off Activities sub report.) The name
of the reported time off activity for the agent.
From: (A column in the Time Off Activities sub report.) The start date of the
reported time off activity for the agent.
To: (A column in the Time Off Activities sub report.) The start date of the
reported time off activity for the agent.
Length (HH:MM): (A column in the Time Off Activities subreport.) The length of
the reported time off activity for the agent.
Total Time Off =: (A column in the Time Off Activities subreport.) The amount of
time off for the agent.
Time Off Requests: (A column in the Time Off Requests subreport.) The name
of the requested time off activity for the agent.
From: (A column in the Time Off Requests subreport.) The start date of the
requested time off activity for the agent.
To: (A column in the Time Off Requests subreport.) The end date of the
requested time off activity for the agent.
Status: (A column in the Time Off Requests subreport.) The status of the
requested time off activity for the agent (One of the following values: Pending,
Approved, Denied, Escalated, Negotiation, Tentative, Invalid, Withdrawn).
Total Requests =: (A column in the Time Off Requests subreport.) The amount
of time off requests for the agent.
Inputs
Employee Filter: Which employees should be reported on.
Time Frame:
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For
example, 2 hours 30 minutes would be shown as 2.5 hours.
If your license includes the optional Time-Off Accrual feature (and providing that Report
Dump has run), an additional column, Carryover (Hours), is shown. This column
shows the balance of hours carried over from the previous year.
Used (Hours): The amount of time off that was used by the agent (the amount of
time the agent was absent) for each activity.
Scheduled (Hours): The amount of time off scheduled for the agent, for each
activity.
Remaining (Hours): The amount of time off that was scheduled for the agent, but
not used, for each activity.
NOTE If your license includes the optional Time-Off Accrual feature, the columns shown are Total,
Starting Balance, and Remaining (Hours).
Grouped by Organization:
Inputs
Employee Filter: Which employees should be reported on.
Time Off Activity: Which time-off activity should be reported on. (Select All Time
Off for all activities.)
Group By: Which property should appear in the report for grouping. Select
Employee or Organization.
Time Frame:
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Time Zone: In which time zone the results should be displayed.
Output
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
Grouped by Organization:
Inputs
Employee Filter: Which employees should be reported on.
Time Off Activity: Which time-off activity should be reported on. (Select All Time
Off for all activities.)
Group By: Which property should appear in the report for grouping. Select
Employee or Organization.
Time Frame:
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Time Zone: In which time zone the results should be displayed.
Output
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
Vacation Hours
This report returns time-off activity details for the group of employees selected by the
filter.
It is in contrast to the report Time Off Summary for Employee,
Inputs
Employee Filter: Which employees should be reported on.
Time Frame:
- Last <X> days (reports that are in view time zone): This mode returns <X>
24-hour periods starting from current time.
- From/To date (reports that are in view time zone): Aggregates data for
intersecting portion. Only the portion of the events that intersect the specified
time window are included in the aggregate. For reports that return events, all
events that start in the specified time window are returned.
Outputs
NOTE When the report has been run using the Last <x> days parameter, the report header’s
From field shows the value of that parameter, such as From: Last 30 days. This is in
contrast to previous releases, where the From field showed a date.
Related topics
Time Off Summary for Employee, page 228
Topics
Daily Profile Requirements, page 243
Profile Requirements, page 247
Grouped by Organization:
Grouped by Template:
Grouped by Shift:
Inputs
Schedule Period: The campaign and time period that should be reported. The
report can run on a full campaign week or a subset of the days in a campaign week.
Group By: Which property should appear in the report for grouping. Select
Organization, Template, or Shift.
Outputs
Timezone: The time zone being used.
Profile Name: The name of the staffing profile. Typically, the name will be the
name of the employee template and a number.
Start Time: The time the staffing profile's shift begins.
End Time: The time the staffing profile's shift ends.
Contact Time (Hours): The amount of time during the shift that the staffing
profile is working on an activity associated with contacts such as incoming phone
calls.
NOTE In reports that show hours, minutes are shown as decimal portions of an
hour. For example, 2 hours 30 minutes would be shown as 2.5 hours.
Paid Time (Hours): The amount of time during the shift where the staffing profile
is paid. Unpaid breaks are subtracted from the total time to compute this.
Wage: The hourly wage for the staffing profile.
Cost: The cost is equivalent to the paid time multiplied by the wage.
Shift: The shift that was scheduled for the staffing profile.
Organization: The organization where the staffing profile was defined.
Template: The employee template from which the staffing profile was created.
Number of Shifts: The total number of shifts scheduled per day and the total
number of shifts scheduled in the reporting period.
Daily Totals: Totals for Contact Time (Hours), Paid Time (Hours), and Cost.
Group Totals: Totals for all occurrences of the daily totals in the report.
In the Summary section:
Number of Profiles to be Hired: The total number of staffing profiles in the
reporting period.
Total Contact Hours Scheduled: The sum of the contact time.
Total Paid Hours Scheduled: The sum of the paid time.
Total Cost: The sum of the cost.
Profile Requirements
This report returns a complete listing of all shifts scheduled for staffing profiles in a
campaign week. Additionally, it lists the total number of staffing profiles, the total
amount of contact hours, paid hours, and the total cost of the staffing profiles given
their entered hourly wage.
The results can be grouped by the organization of the staffing profiles, the employee
template of the staffing profiles, or the shifts worked by the staffing profiles.
This report allows managers and human resource managers to know how many
additional employees should be added or hired and what weekly schedules each of these
new employees should work. This report also provides the cost associated with hiring
these employees.
Inputs
Schedule Period: The campaign and time period that should be reported. The
report can run on a full campaign week or a subset of the days in a campaign week.
Group By: Which property should appear in the report for grouping. Select
Organization or Template.
Outputs
Campaign Week: The Campaign Week that is reported on.
Profile Name: The name of the staffing profile. Typically the name will be the
name of the employee template and a number.
Date: The date being reported.
Start Time: The time the staffing profile's shift begins.
End Time: The time the staffing profile's shift ends.
Contact Time (Hours): The amount of time during the shift that the staffing
profile is working on an activity associated with contacts such as incoming phone
calls.
NOTE In reports that show hours, minutes are shown as decimal portions of an hour. For example,
2 hours 30 minutes would be shown as 2.5 hours.
Paid Time (Hours): The amount of time during the shift where the staffing profile
is paid. Unpaid breaks are subtracted from the total time to compute this.
Wage: The hourly wage for the staffing profile.
Cost: The cost is equivalent to the paid time multiplied by the wage.
Shift: The shift that was scheduled for the staffing profile.
Organization: The organization where the staffing profile was defined.
Template: The employee template from which the staffing profile was created.
Other Reports
These framework reports are covered in other guides.
Related information
Desktop and Process Analytics (DPA) User Guide
Related information
eLearning Administration Guide
Related information
eLearning Administration Guide
Obsolete Reports
This special report topic is used for existing instances of reports that now differ from the
current version of those reports.
Such differences can be caused if upgrades to your system involved a change to the
report's parameter set or if the report's record selection formulas have changed. The
obsolete versions of these reports are moved to the OBSOLETE REPORTS classification
instead of being completely overwritten and thus lost.
NOTE You can only view the instances of reports in the OBSOLETE REPORTS
classification; they cannot be executed again.
Framework Reports
Parameters
Topics
Select activities, page 254
Select organizations, page 254
Select scheduling periods, page 256
Select employees, page 258
Select work queues, page 259
Chapter 3 - Framework Reports Parameters Select activities
Select activities
The Activity drop-down list allows you to select one or more activities. It is found on
certain reports, such as the Time Off report Absence Hours and Absence Shrinkage
for Employee by Time.
Use the Ctrl key to select non-contiguous items, or the Shift key to select a contiguous
range of items.
Select organizations
You select one or more organizations using the Organization field. It is found on certain
reports such as Organization Activity Summary and Organization KPIs and Objectives.
When you click the selector icon, it opens the Organization Selector window.
Use the buttons at the bottom of the window to select all the organizations, clear your
selections, and so on. You can also click individual check boxes and then click Set to
apply your selection.
Your choices are then displayed to the left of the Organization Selector button in a
scrollable box.
Organization selector
Use this window to select one or more organization(s).
Procedure
1 Select the organization(s) by clicking on the control beside the Organization name.
2 Click Set.
When you click the icon to the right of the empty field, it opens a selector window:
Procedure
1 Select the campaign using the drop-down menu. All campaigns to which you have
access are displayed when you click the drop-down button.
2 Click Set.
3 Select the scheduling period using the drop-down menu. All scheduled periods are
shown.
4 Click Set to return to the Parameters page.
Select employees
The Employee selector allows you to search for employees based on their name. The
window contains two fields, First Name and Last Name.
The Employee selector displays an icon to the right of the Employee field. When you
click the icon, it opens the Employee Selector window.
Although you can type an employee's full first and last name here, this window is also
very useful for searches based on part of a name.
Procedure
1 Select a time range to get the campaign list. This step is optional; selecting an open
time range returns all the campaign queue assignments.
2 Select the campaign in the Campaign List drop-down menu. When you select No
Campaign, it returns all the queues in the system.
3 Select the required work queue(s). (You can select multiple work queues within the
same campaign using the Ctrl key.)
4 Click Set.
To cancel without changing the selections, click Cancel.
NOTE Some fields might not be available depending on the report’s parameters.
The Reports list provides information on each Interactions and Analytics report, such as
the reports description, calculations and source data.
Topics
Interactions and Analytics reports overview, page 262
Activity Reports, page 264
Analytics Driven Quality reports, page 275
Calibration Reports, page 279
Productivity Reports, page 282
Quality Reports, page 290
Recorded Contacts reports, page 321
Speech Usage Reports, page 342
Chapter 4 - Interactions and Analytics reports Interactions and Analytics reports overview
New contacts and new interactions 2 hr. 50 min. from the end of the
contact or interaction
Report re-run After running a report, opening the There is no access to the parameters tab
parameters window from the report from the report viewer. To re-run the
viewer displays the parameters that report with one or more different
were used in running the report. parameters, requires you to re-define all
To re-run the report with one or more the parameters.
different parameters, requires you to
change only those specifics
parameters and then re-run the
report.
Portal To set reports to display in the Portal All predefined reports can be displayed in
dashboard dashboard, they must be first the Portal dashboard. No need to
configured either from the Reports configure reports first.
application or from the Interactions
Home page with the Schedule to
Portal option.
Inbox The Reporting Framework Inbox The Reporting Framework does not
option is supported. Reports can be support Inbox.
scheduled to a specifics user’s Reports can be distributed to users using
Reporting Framework Inbox. emails.
Portal You can drill-down a report displayed You can drill-down in a report displayed in
dashboard in the dashboard, to a specific the portal dashboard, but you cannot set
drill-down employee/group/organization (if the drilled-down view as the dashboard
relevant). You can then set that default.
drilled-down view to be displayed in
the dashboard by default for that
report.
Activity Reports
Activity reports monitor the number of evaluations/assessments and flag usage within
the enterprise at the individual or group levels.
Related topics
Contact Flag Usage per Assessor, page 264
Evaluation Activity per Employee, page 267
Evaluation Activity per Evaluator, page 268
Evaluation Activity per Group, page 270
Evaluation Flag Usage per Assigning User, page 272
Text format
The list shows assessors and their flag usage.
Input parameters
The selected input parameters determine the source data in this report.
In this report, the Date Range you select is according to the local time the contact is
flagged. That is, the time zone of the person who assigned the flag.
Calculation
For each assessor, the report:
1 Identifies all assessments submitted by the assessor.
2 Counts the number of times the selected flag is used in contacts associated with
these assessments.
Flagged contacts that have not been assessed, do not appear in the report.
Contacts whose flag was removed appear as flagged in the report, unless the flag was
removed from a contact within a few minutes after being assigned to it.
Related topics
Interactions and Analytics report parameters, page 347
Text format
The list shows employees and number of evaluations performed on each employee.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each employee, the report sums up the evaluations performed on the employees.
Related topics
Interactions and Analytics report parameters, page 347
The X-axis shows the selected evaluators. The Y-axis represents the number of
evaluations. The actual number of evaluations per evaluator is shown at the top of
the corresponding bar.
Text format
The list shows evaluators and number of evaluations performed by each evaluators.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each evaluator, the report sums up the evaluations performed by the evaluator.
Related topics
Interactions and Analytics report parameters, page 347
The X-axis shows the selected organizations/groups. The Y-axis represents the
number of evaluations. The actual number of evaluations per organization/group is
shown at the top of the corresponding bar.
Text format
The list shows organizations/groups and number of evaluations performed by each
organizations/groups.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
The report sums up the number of evaluations performed on all employees associated
with each organization/group.
Related topics
Interactions and Analytics report parameters, page 347
Text format:
The list shows evaluators/employees and their flag usage.
Input parameters
The selected input parameters determine the source data in this report.
In this report:
The Date Range you select is according to the local time the evaluation is flagged.
That is, the time zone of the person who assigned the flag.
The Evaluators list includes both evaluators and employees. Select from this list
the evaluators and employees for which you want to view their flag assignments.
These evaluators and employees are displayed in the report X-axis.
The Employees field includes the employees on whom the evaluation was
performed. These employees are not displayed in the report X-axis, but rather their
evaluations are considered in the report calculations.
Calculation
The report sums up the number of times an evaluator/employee assigned an evaluation
flag.
Evaluations whose flag was removed appear as flagged in the report unless the flag was
removed from an evaluation within a few minutes after being assigned to it.
The report does not contain information on deleted flags.
The report includes self evaluations.
Related topics
Interactions and Analytics report parameters, page 347
Related topics
Analytics Driven Quality per Employee, page 275
Analytics Driven Quality per Group, page 276
Input parameters
The selected input parameters determine the source data in this report.
Calculation
The reports calculate the following for the defined time period:
#Interactions: number of category hits for each employee included in the report.
Total Sampled: number of interactions that were processed in Speech Analytics for
each employee included in the report.
Performance: the category hits percentage for each employee.
For each employee:
number of category hits/total number of transcribed interactions.
Percentile: the individual employee performance for each category, relative to the
other employees whose interactions fall within the same category. This value shows
for each category, where each employee stands compared to other employees.
All Employees: the category average percentage of hits across the employees
included in the report.
Reference Group: the category average percentage of hits for the reference
group.
Reference group number of category hits / group number of transcribed interactions
Related topics
Interactions and Analytics report parameters, page 347
Input parameters
The selected input parameters determine the source data in this report.
Calculation
The reports calculate the following for the defined time period:
#Interactions: number of category hits for each organization/group included in
the report.
Total Sampled: number of interactions that were processed in Speech Analytics for
each organization/group included in the report.
Performance: the category hits percentage for each organization/group.
For each organization/group:
number of category hits/total number of transcribed interactions.
Percentile: the individual organization/group performance for each category,
relative to the other organizations/groups whose interactions fall within the same
category. This value shows for each category, where each organization/group
stands compared to other organizations/groups.
All Groups: the category average percentage of hits across the organizations/
groups included in the report.
Reference Group: the category average percentage of hits for the reference
organization/group.
Reference group number of category hits/group number of transcribed interactions
Related topics
Interactions and Analytics report parameters, page 347
Calibration Reports
These Calibration reports compare how different assessors in the organization assess
the same contacts. In addition, the reports indicate which sections, questions, and
categories the different assessors handled most differently.
Related topics
Calibration Report, page 279
Calibration Report by Question, page 280
Calibration Report
The Calibration Report shows for each Calibration assessment form, the average
score, and the score standard (STD) deviation for each relevant contact. For
presentation purposes, the report displays up to five contacts for each form. You can
identify which contacts need to be reviewed, by selecting contacts that appear in the
report with the highest score standard deviation.
The report displays in textual format.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
The report calculates the average score and score standard deviation for each form, for
a particular contact. The report also calculates the total average score and score
standard deviation for each form.
The report indicates which contact has the highest score standard deviation for a
particular form.
If the value zero appears in one of the score columns, it implies one of the following:
The score received in this assessment is zero. In this case, the assessment is
considered in the number of assessments, average score, and score standard
deviation calculations.
This form was not filled at all for this contact. In this case, the assessment is not
considered in the number of assessments, average score, and score standard
deviation calculations.
Related topics
Interactions and Analytics report parameters, page 347
Input parameters
The selected input parameters determine the source data in this report.
Calculation
The report calculates the average score and score standard deviation of a form, for each
of its questions, sections and categories.
The report indicates how many times (and the percentage) a particular answer was
given for each question when a contact was assessed.
The report ignores text questions, numeric range questions and text list questions (of
type List or Drop Down List with Text only).
Related topics
Interactions and Analytics report parameters, page 347
Productivity Reports
Productivity reports assess productivity versus quality at the employee or organization/
group levels. The productivity metric selected from a predefined list, is compared to the
evaluation scores to derive the productivity factor.
In addition, by selecting the corresponding distribution option, you can also assess
productivity versus quality in the context of time intervals, time periods, Speech
Analytics categories, or conditional custom data.
Related topics
Employee Productivity vs. Quality, page 282
Group Productivity vs. Quality, page 286
Text format
The list shows for each employee the evaluation average score and selected
productivity factor.
Input parameters
The selected input parameters determine the source data in this report.
In this report:
Drill-down is supported. If the Enable drill-down option is selected, drill down on
an employee shows the individual evaluation scores from which the average score is
calculated. You can see how the selected productivity factor relates to the
evaluation scores of the employee.
If a Distribution option is selected, the charts show data in the context of the
distribution factor. Typically, there are multiple charts, one for each factor.
Distribution by day of week, for example, shows a separate chart for each day of
the week.
If this option is selected, only the distribution charts are displayed, without the main
report.
Calculation
For each employee included in the report, the report calculates the average score for the
selected productivity factor.
Average evaluation score for each employee
Total evaluations scores for employee/Number of evaluations
Average number of interactions per hour
The number of interactions that were started and completed during the date range
included in the report, divided by the number of hours included within the date
range.
Total number of interactions in date range/Total number of hours in date range
Average number of interactions per day
The number of interactions that were started and completed during the date range
included in the report, divided by the number of days included within the date
range.
Total number of interactions in date range/Total number of days in date range
Average interaction duration
The duration of all interactions that were started and completed during the date
range included in the report, divided by the number of interactions handled during
the date range.
Total duration of interactions in date range/Total number of interactions in date
range
Average talk time percentage
Total talk time percentage for all working days/Total number of working days
where:
Total talk time percentage for all working days is calculated by:
For each day included within the date range:
Adding the duration of each interaction handled by the employee, to get the
total interaction duration per day
Determining the length of time between the start of the first interaction and
the end of the last interaction to get the total interaction time span per day
Dividing the total interaction duration per day by the total interaction time
span per day
Summing up the results for all days included in the report.
Total number of working days is calculated by adding each day that the employee
handled at least one interaction for the date ranged defined for the report.
The following conditions affect the calculation:
A day on which the employee did not handle any interactions is not counted as a
working day.
Input parameters —if defined for the report—do not impact the number of working
days. For example, if the number of working days is 4, and CCD parameter defined
for the report matches interactions from 3 of the 4 days, the number of working
days is still 4.
On days when the employee handled one interaction only, the employee's
productivity is shown as 100 percent and not as the calculated average.
If the employee handled interactions simultaneously, the percentage talk time will
exceed 100%. For example, if within a five minute time frame the employee
handled a call with a duration of three minutes, and another call with a duration of
four minutes, the average is 7/5 (exceeding 100%).
Related topics
Interactions and Analytics report parameters, page 347
Text format
The list shows for each group/organization the evaluation average score and
selected productivity factor.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each organization/group included in the report, the report calculates the average
score for the selected productivity factor.
The calculations are based on data relating to all the employees in the organization/
group. For example, the number of working days of an organization/group is calculated
by the sum of the working days of each employee in that organization/group.
Average evaluation score for each organization/group
Total score of evaluations for group / Total number of evaluations
Average number of interactions per hour
The number of interactions that were started and completed during the date range
included in the report, divided by the number of hours included within the date
range.
Total number of interactions in date range/Total number of days in date range
Average number of interactions per day
The number of interactions that were started and completed during the date range
included in the report, divided by the number of days included within the date
range.
Total number of interactions in date range/Total number of days in date range
Average interaction duration
The duration of all interactions that were started and completed during the date
range included in the report, divided by the number of interactions handled during
the date range.
Related topics
Interactions and Analytics report parameters, page 347
Quality Reports
Quality reports focus on evaluations and assessments parameters for the employee,
organization/group and evaluator/assessor. The reports give insight into the quality of
interactions and the efficiency of the employee or group.
Assessment Pass/Fail Count per Assessor, page 290
Average Assessment Form/Form Component Scores, page 292
Average Assessment Scores per Assessor, page 294
Average Evaluation Form/Form Component Scores, page 296
Average Evaluation Scores per Employee, page 298
Average Evaluation Scores per Evaluator, page 300
Average Evaluation Scores per Group, page 302
Average Evaluation Scores per Reason, page 304
Employee Scores per Evaluation, page 306
Evaluation Pass/Fail Count per Employee, page 309
Evaluation Pass/Fail Count per Evaluator, page 311
Evaluation Pass/Fail Count per Group, page 312
Evaluations Completed per Employee, page 314
Evaluation Summary of Employees, page 315
Evaluation Summary per Employee, page 317
Evaluation Summary per Group, page 318
Evaluation Summary per Group, page 318
Recorded Contacts reports, page 321
Text format
The list shows for each assessor the number of passed and failed assessments.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each assessor included in the report, the report retrieves all assessments and sums
the assessments that met the goal and the assessments that failed to meet the goal.
Related topics
Interactions and Analytics report parameters, page 347
Text format
The list shows for each form or form component the average score and number of
assessments performed.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each form or form component included in the report, the report calculates the
average assessment score by:
Summing the forms or form component assessment scores
Dividing the total score by the number of occurrences of each form/form component
Total sum of form or form components scores/total number of occurrences of the form
or form component
Related topics
Interactions and Analytics report parameters, page 347
Text format
The list shows for each assessor the average score and number of assessments
performed.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each assessor included in the report, the report calculates the average assessment
score by:
Summing all the assessments scores
Dividing the total score by the number of assessments the assessor performed
Total sum of assessments scores/total number of assessments
Related topics
Interactions and Analytics report parameters, page 347
The Y-axis displays the average scores for the forms or form components. The
actual average score of each form or form component is shown at the top of the
corresponding bar.
Text format
The list shows for each form or form component the average score and number of
evaluations performed.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each form or form component included in the report, the report calculates the
average evaluation score by:
Summing all the forms or form component evaluation scores
Dividing the total score by the number of occurrences of each form/form component
Total sum of form or form components scores/total number of occurrences of the form
or form component
Related topics
Interactions and Analytics report parameters, page 347
The X-axis shows the employees included in the report. The Y-axis represents the
average evaluation score. The actual average evaluation score of each employee is
shown at the top of the corresponding bar.
Text format
The list shows for each employee the average score and number of evaluations
performed.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each employee included in the report, the report calculates the average evaluation
score by:
Summing all the evaluation scores
Dividing the total score by the number of evaluation performed on the employee
Total sum of evaluation score/Number of evaluations
Related topics
Interactions and Analytics report parameters, page 347
Text format
The list shows for each evaluators the average score and number of evaluations
performed.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each evaluator included in the report, the report calculates the average evaluation
score by:
Summing all the evaluations scores
Dividing the total score by the number of evaluations the evaluator performed
Total sum of evaluations scores/total number of evaluations
Related topics
Interactions and Analytics report parameters, page 347
Text format
The list shows for each organization/group the average score and number of
evaluations performed.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each organization/group included in the report, the report calculates the average
evaluation score by:
Summing the evaluations scores of all employees in the organization/group
Dividing the total score by the number of evaluations performed on all employees in
the organization/group
Total sum of evaluations scores of all employees/total number of evaluations
Related topics
Interactions and Analytics report parameters, page 347
Text format
The list shows for each reason the average score for answers tagged with the
reason, and the number of answers that were tagged the reason.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each reason included in the report, the report calculates the average score for
answers tagged with the reason by:
Summing the scores of all answers tagged with the reason
Dividing the total score by the number of answers that were tagged with the reason
Total sum of answers scores tagged with reason/total number of answers tagged with
reason
Related topics
Interactions and Analytics report parameters, page 347
Text format
The list shows for each employee the evaluation date and the individual evaluation
score.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each employee, the report retrieves and displays the individual evaluations scores,
without any calculations.
Related topics
Interactions and Analytics report parameters, page 347
Text format
The list shows for each employee the number of passed and failed evaluations.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each employee included in the report, the report retrieves all evaluations and sums
the evaluations that met the goal and the evaluations that failed to meet the goal.
Related topics
Interactions and Analytics report parameters, page 347
Text format
The list shows for each evaluator the number of passed and failed evaluations.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each evaluator included in the report, the report retrieves all evaluations and sums
the evaluations that met the goal and the evaluations that failed to meet the goal.
Related topics
Interactions and Analytics report parameters, page 347
The report shows if you are setting realistic goals for your organization/group, and if
there are organizations/groups who consistently score too high or too low.
The report displays in graphical or textual formats:
Graphical bar chart
The X-axis shows the organizations/groups included in the report. The Y-axis
represents the number of evaluations that passed or failed as stacked bars.
Text format
The list shows for each organization/group the number of passed and failed
evaluations.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each organizations/group included in the report, the report retrieves all evaluations
and sums the evaluations that met the goal and the evaluations that failed to meet the
goal.
Related topics
Interactions and Analytics report parameters, page 347
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each employee, the report presents (without any calculations):
Summary of individual evaluations
Summary of all evaluations
Related topics
Interactions and Analytics report parameters, page 347
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each employee, the report calculates the total number of evaluations and average
score by:
Total number of evaluations: summing up the evaluations performed on the
employee
Average score per employee:
Summing all the evaluation scores of the employee
Dividing the total score by the number of evaluation performed on the
employee
Total sum of evaluation score/Number of evaluations
Related topics
Interactions and Analytics report parameters, page 347
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each employee, the report calculates number of evaluations, answer occurrences
and answer average scores by:
For each evaluation form used to evaluate the employee:
Summing the number of times the individual form was used in evaluating the
employee
Based on all evaluations filled for this form, for each Yes/No and Five Rank List
question types:
Summing the number of occurrences for each answer, and its equivalent in
percentage
Summing the answers scores and dividing by number of times the question
was answered to get the Average score for each question
The report ignores text questions, numeric range questions and text list questions (of
type List or Drop Down List with Text only).
Related topics
Interactions and Analytics report parameters, page 347
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each organization/group, the report calculates number of evaluations, answer
occurrences and answer average scores by:
For each evaluation form used to evaluate the employees in the organization/group:
Summing the number of times the individual form was used in evaluating the
employees
Based on all evaluations filled for this form, for each Yes/No and Five Rank List
question types:
Summing the number of occurrences for each answer, and its equivalent in
percentage
Summing the answers scores and dividing by number of times the question
was answered to get the Average score for each question
The report ignores text questions, numeric range questions and text list questions (of
type List or Drop Down List with Text only).
Related topics
Interactions and Analytics report parameters, page 347
Related topics
Average Talk Time Percentage per Employee, page 321
Average Talk Time Percentage per Group, page 324
Average Talk Time per Employee, page 327
Average Talk Time per Group, page 330
Daily Average Interactions per Employee, page 332
Daily Average Interactions per Group, page 334
Recorded Contacts Volume, page 336
Recorded Interactions per Employee, page 337
Recorded Interactions per Group, page 339
Text format
The list shows for each employee the average talk time percentage.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each employee in the report, the report calculates the average talk time percentage:
Total talk time percentage for all working days/Total number of working days
where:
Total talk time percentage for all working days is calculated by:
For each day included within the date range:
Adding the duration of each interaction handled by the employee, to get the total
interaction duration per day
Determining the length of time between the start of the first interaction and the
end of the last interaction to get the total interaction time span per day
Dividing the total interaction duration per day by the total interaction time span
per day
Summing up the results for all days included in the report.
Total number of working days is calculated by adding each day that the employee
handled at least one interaction for the date ranged defined for the report.
The following conditions affect the calculation:
A day on which the employee did not handle any interactions is not counted as a
working day.
Input parameters —if defined for the report—do not impact the number of working
days. For example, if the number of working days is 4, and CCD parameter defined
for the report matches interactions from 3 of the 4 days, the number of working
days is still 4.
On days when the employee handled one interaction only, the employee's
productivity is shown as 100 percent and not as the calculated average.
If the employee handled interactions simultaneously, the percentage talk time will
exceed 100%. For example, if within a five minute time frame the employee
handled a call with a duration of three minutes, and another call with a duration of
four minutes, the average is 7/5 (exceeding 100%).
Related topics
Interactions and Analytics report parameters, page 347
Text format
The list shows for each organization/group, the average talk time percentage.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
The calculations are based on data relating to all the employees in the organization/
group. For example, the number of interactions of an organization/group is calculated by
the sum of the interactions performed by each employee in that organization/group.
For each organization/group in the report, the report calculates the average talk time
percentage:
Total talk time percentage for all working days/Total number of working days
where:
Total talk time percentage for all working days is calculated by:
For each day included within the date range:
Adding the duration of each interaction handled by the employees, to get the
total interaction duration per day
Determining the length of time between the start of the first interaction and the
end of the last interaction to get the total interaction time span per day
Dividing the total interaction duration per day by the total interaction time span
per day
Summing up the results for all days included in the report.
Total number of working days is calculated by adding each day that an employee
handled at least one interaction for the date ranged defined for the report.
The following conditions affect the calculation:
A day on which an employee did not handle any interactions is not counted as a
working day.
Input parameters —if defined for the report—do not impact the number of working
days. For example, if the number of working days is 4, and CCD parameter defined
for the report matches interactions from 3 of the 4 days, the number of working
days is still 4.
If employees handled interactions simultaneously, the percentage talk time will
exceed 100%. For example, if within a five minute time frame an employee handled
a call with a duration of three minutes, and another call with a duration of four
minutes, the average is 7/5 (exceeding 100%).
Related topics
Interactions and Analytics report parameters, page 347
Text format
The list shows for each employee, the average interaction handle time and number
of interactions handled.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each employee in the report, the report calculates the average interaction talk time
by:
Summing the duration of all interactions that started and completed during the date
range included in the report
Dividing the total duration number by the number of interactions handled
Total duration of interactions in date range/Total number of interactions in date range
Related topics
Interactions and Analytics report parameters, page 347
Text format
The list shows for each organization/group, the average interaction handle time and
number of interactions handled.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
The calculations are based on data relating to all the employees in the organization/
group. For example, the number of interactions of an organization/group is calculated by
the sum of the interactions performed by each employee in that organization/group.
For each organization/group in the report, the report calculates the organization/group
average interactions talk time by:
Summing the duration of all interactions that started and completed during the date
range included in the report
Dividing the total duration the number of interactions handled.
Total duration of interactions in date range/Total number of interactions in date range
Related topics
Interactions and Analytics report parameters, page 347
Text format
The list shows for each employee, the daily average number of interactions handled
and the number of days during which interactions were handled.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each employee in the report, the report calculates the daily average number of
interactions by:
Summing the number of interactions that were started and completed during the
date range included in the report
Dividing total number of interactions by the number of days included within the date
range
Total number of interactions in date range/Total number of days in date range
The following conditions affect the calculation:
A day on which an employee did not handle any interactions is not counted as a
working day.
Input parameters —if defined for the report—do not impact the number of working
days. For example, if the number of working days is 4, and CCD parameter defined
for the report matches interactions from 3 of the 4 days, the number of working
days is still 4.
Related topics
Interactions and Analytics report parameters, page 347
Text format
The list shows for each organization/group, the daily average number of interactions
handled and the number of days during which interactions were handled.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
The calculations are based on data relating to all the employees in the organization/
group. For example, the number of interactions of an organization/group is calculated by
the sum of the interactions performed by each employee in that organization/group.
For each organization/group in the report, the report calculates the daily average
number of interactions, by:
Summing the number of interactions that were started and completed during the
date range included in the report
Dividing the total number of interactions by the number of days included within the
date range
Total number of interactions in date range/Total number of days in date range
The following conditions affect the calculation:
The following conditions affect the calculation:
A day on which an employee did not handle any interactions is not counted as a
working day.
Input parameters —if defined for the report—do not impact the number of working
days. For example, if the number of working days is 4, and CCD parameter defined
for the report matches interactions from 3 of the 4 days, the number of working
days is still 4.
Related topics
Interactions and Analytics report parameters, page 347
Text format
The list shows the number of contacts recorded for the enterprise.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
The report sums all the recorded contacts in the enterprise for the date range included
in the report.
Related topics
Interactions and Analytics report parameters, page 347
Text format
The list shows the number of interactions recorded for an employee.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each employee, the report sums all the recorded interactions handled by that
employee, during the date range included in the report.
Related topics
Interactions and Analytics report parameters, page 347
Text format:
The list shows the number of interactions recorded for an organization/group.
Input parameters
The selected input parameters determine the source data in this report.
Calculation
For each organization/group, the report sums up all recorded interactions handled by all
the employees of that organization/group.
Related topics
Interactions and Analytics report parameters, page 347
Input Parameters
The selected input parameters determine the source data in this report.
This report has the following parameters:
Project Name: select the projects you want to include in the report.
Calculation
The calculation of the extensions count varies for the project as apposed to the entire
enterprise:
For project: the projects included in the report depend on the projects you select
in the report input parameters.
Extensions having interactions associated with multiple projects are considered
once for each associated project for each month. For example, in January, an
extension had interactions associated with Project A and Project B. In January, this
extension is considered once when counting extensions for Project A and once when
counting extensions for Project B.
For the entire enterprise: the extensions count value included in the report
contains data from all projects in the enterprise.
Extensions having interactions associated with multiple projects are only considered
once for the enterprise during each month. For example, in January, the extension
had interactions associated with Project A and Project B. In January this extension is
considered only once when counting extensions for the enterprise.
If the same interaction is associated with different projects in different months, the
extension is counted more than once. For example, the interaction is associated
with one project in January and another project in February. The related extension
is counted twice for the enterprise, once for each month.
In both cases, the date the interactions were indexed (rather than the date they were
recorded) determines the month that the extensions are associated with.
Input Parameters
The selected input parameters determine the source data in this report.
This report has the following parameters:
Project Name: select the projects you want to include in the report.
Calculation
The calculation of the interactions count and duration varies for the project as apposed
to the entire enterprise:
For project: the projects included in the report depend on the projects you select
in the report input parameters.
Interactions associated with multiple projects are considered once for each
associated project per month. For example, in January, the same interaction was
associated with Project A and Project B. In January this interaction is considered
once when counting interactions for project A and once when counting interactions
for project B.
For the entire enterprise: the interactions count and duration included in the
report contains data from all projects in the enterprise.
Interactions associated with multiple projects are only considered once for the
enterprise during each month. For example, in January, the same interaction was
associated with Project A and Project B. In January this interaction is considered
only once when counting interactions for the enterprise.
If the same interaction is associated with different projects in different months, the
interaction is counted more than once. For example, the interaction is associated
with one project in January and another project in February. This interaction is
counted twice for the enterprise, once for each month.
In both cases, the date the interactions were indexed (rather than the date they were
recorded) determines the month that the interactions are associated with.
Input Parameters
The selected input parameters determine the source data in this report.
This report has the following parameters:
Project Name: select the projects you want to include in the report.
Calculation
The calculation of the employees count varies for the project as apposed to the entire
enterprise:
For project: the projects included in the report depend on the projects you select
in the report input parameters.
Employees having interactions associated with multiple projects are considered
once for each associated project for each month. For example, in January, an
employee had interactions associated with Project A and Project B. In January, this
employee is considered once when counting employees for Project A and once when
counting employees for Project B.
For the entire enterprise: the employees count value included in the report
contains data from all projects in the enterprise.
Employees having interactions associated with multiple projects are only considered
once for the enterprise during each month. For example, in January, an employee
had interactions associated with Project A and Project B. In January, this employee
is considered only once when counting employees for the enterprise.
If the same interaction is associated with different projects in different months, the
employee is counted more than once. For example, an interaction is associated with
one project in January and another project in February. The related employee is
counted twice for the enterprise, once for each month.
In both cases, the date the interactions were indexed (rather than the date they were
recorded) determines the month that the employees are associated with.
Select the data you want to focus on in reports using report parameters. Analyze
employee activity, monitor KPIs, and performance for any date range with the default or
custom set of parameters.
Topics
Interaction Report Parameters Overview, page 348
Employees, page 349
Date Range, page 352
Interactions, page 354
Contacts, page 358
Custom Data, page 361
Switches, page 363
Recorders, page 365
Categories, page 366
Distribution options, page 368
Display options, page 371
Evaluations/Assessments, page 375
Chapter 5 - Interactions and Analytics report parameters Interaction Report Parameters Overview
Data parameters
Employees, page 349
Date Range, page 352
Interactions, page 354
Contacts, page 358
Custom Data, page 361
Switches, page 363
Recorders, page 365
Categories, page 366
Evaluations/Assessments, page 375
Format parameters
Distribution options, page 368
Display options, page 371
Employees
The Employees category contains parameters relating to employees, groups and
organizations to include in the report.
Related topics
Employees, page 349
Reference organization/group, page 350
Employees
The employees, organizations or groups to include in the report. The employees/
organizations/groups you can select from depend on your role scope and privileges
assigned to you, and on the type of report you are generating. You can see data of
employees assigned to the organization/group over which you have scope.
To select specific employees, organizations or groups, click the view that best suits your
requirements. You can optionally apply a predefined employee filter or create and apply
a custom employee filter.
Employee views include:
List view of up to 2500 employees in alphabetical order (the default)
Hierarchical view of employees by the organization they belong to
Organization view
Groups in organization
TIP To quickly find employees, start typing part of the name in the Search
field.
Use the Ctrl and Shift keys to select multiple employees at the same time.
Valid values
One or more employees.
One or more groups/organizations from the available list.
Wildcard usage
N/A
Reference organization/group
The organization or group to which to compare the performance of the selected
employees, organizations, or groups. The reference organization/group is another group
in the department, the entire department or the entire organization, depending on your
privileges and position in the organization.
You can select a reference organization/group even if you do not have privileges to
generate reports based on other evaluators.
Based on the report format, the reference organization/group always appears as the
first bar or as the first row in the table.
Valid values
One of the following:
None (the default).
All: the report displays the average value of the organizations/groups you are
assigned to.
Select one of the following:
The organization/group displayed depends on your position in the organizational
hierarchy and whether you are assigned the Filter by All Groups privilege:
If you are assigned the privilege, the list displays all organizations/groups in the
enterprise, including those higher than you in the hierarchy.
Wildcard usage
N/A
Date Range
The Date Range category contains parameters relating to the time period to run the
report. A report must be set to run against a specific date.
Related topics
Interaction Date, page 352
According to, page 353
Interaction Date
The time frame for which to include data in the report. The time frame is based on the
employee local time. You can select the current or previous calendar day/week/month/
year, or define a custom date range.
Depending on the report, the date range you select is according to the time of recording,
the time of the evaluation, the time of the assessment or the flagging time.
The system considers only the hour in which the event occurs and not the minute.
Valid values
One of the following:
From the Last: <n> days
The past number of days to include from today, including today. You can define from
1 up to 999 days. The default range is the last seven days from today.
For example, setting a value to 1 includes in the report data from today and
yesterday.
To include more than the last 30 days, you must define additional parameters to
narrow the scope of the report.
From the previous: day/week/month/quarter/year
The equivalent period preceding and corresponding to the current calendar day/
week/month/year.
For example, if the current month is March 2015, selecting Previous month would
set the date range to February. Selecting Previous quarter would set the date
range to October to December 2014.
From the current: day/week/month/quarter/year
The current calendar day/week/month/quarter/year up to today.
For example, selecting Week sets the date range from Monday to today. Selecting
Current quarter if the current month is February, sets the date range from January
to today.
From/To
The exact start and end dates and time for which to include data.
The time is in hh:mm format, and is always rounded to one minute before the
nearest hour.
For example, specifying 10:30 AM as the end time, includes data up to 10:59 AM.
Specifying 09:00 to 11:00 a.m. includes data from 09:00 to 10:59 a.m.
Wildcard usage
N/A
According to
Determines if to include data based on when the interaction was recorded, or when an
evaluation or assessment was submitted. This parameter is not relevant to all reports
and the list of valid values depends on the report you select.
Valid values
One of the following:
Time of recording
Includes data based on the time when the interaction is recorded. The time is either
the employee local time zone or that of the recorder.
Time of evaluation
Includes data based on the time when the evaluation is submitted, and is always
the local time of the evaluator.
Time of assessment
Includes data based on the time when the assessment is submitted, and is always
the local time of the assessor.
Wildcard usage
N/A
Interactions
The Interactions category contains parameters relating to interactions to include in the
report. Use these parameters to define the type of interactions to include in the report
for the selected employees, organizations and/or groups.
You can either include all interactions within the selected date range, or refine the type
and number of interactions to include by defining the duration, direction, and other
parameters based on your business needs.
Related topics
Duration, page 354
Direction, page 354
Dialed From (ANI), page 355
Dialed To (DNIS), page 355
Extension, page 356
PBX ID, page 357
Wrap-up Time, page 357
Duration
The interactions to include based on their duration.
Valid values
Any time between 00:00 and 59:59 in mm:ss format.
Wildcard usage
N/A
Direction
The interactions to include based on their direction. These can be inbound, outbound,
internal interactions, or all interactions whose direction the system could not determine.
Valid values
Inbound
Include only incoming interactions
Outbound
Include only outgoing interactions
Internal
Include only interactions within the enterprise
Unknown
Include those interactions whose direction the system could not determine
Wildcard usage
N/A
Valid values
Alphanumeric string of up to 256 characters, including the following special characters:
! @ # $ % ^ & * () _
+ = <> , . ? / : ; '
{} [] | ~ `
Wildcard usage
Use ? as a single character placeholder or * as a multi-character placeholder.
For example, to include all interactions from all calling party numbers that start with
516, you would enter 516*.
Note
The ANI may not match the ANI of the initial call into the enterprise, for example if a
first recorded interaction starts on a consult, call park or automatic transfers.
Some CTI integrations (such as Cisco JTAPI), do not provide a specific ANI field. In these
cases calling party information is used as a best alternative.
Some CTI integrations provide pre-routed/translated ANI values or otherwise present
manipulated ANI values. The manipulated ANI value is used if that is all that is available.
Some CTI integrations (such as Genesys and Cisco ICM) provide explicit ANI information
and these are used explicitly, with no additional logic applied.
Dialed To (DNIS)
The called party number for which to include interactions, which is the dialed number
identification service (DNIS). DNIS is useful in enterprises to which calls to multiple
numbers may be directed. You can either specify the exact number or use wildcards to
include a range of numbers.
Valid values
Alphanumeric string of up to 256 characters, including the following special characters:
! @ # $ % ^ & * () _
+ = <> , . ? / : ; '
{} [] | ~ `
Wildcard usage
Use ? as a single character placeholder or * as a multi-character placeholder.
For example, to include all interactions from all calling party numbers that start with
516, you would enter 516*.
Note
The DNIS cannot match the DNIS of the initial call into the enterprise. DNIS is derived
from the first recorded interaction of the call. For example, if a first recorded interaction
starts on a consult, then the consultation call DNIS is considered the DNIS value for the
interaction. Other examples where the DNIS cannot match the DNIS of the initial call
into the enterprise are call park or automatic transfers.
Some CTI integrations (such as Cisco JTAPI), do not provide a specific DNIS field. In
these cases called party information is used as a best alternative.
Some CTI integrations provide pre-routed/translated DNIS values or otherwise present
manipulated DNIS values. If that is all that is available, the manipulated DNIS value is
used.
Some CTI integrations (such as Genesys and Cisco ICM) provide explicit DNIS
information and are used explicitly, with no additional logic applied.
Each interaction DNIS value is stored separately within the interaction, and DNIS values
are not overwritten with values from previous interactions.
The indexed search improvements are unavailable when wildcard characters are used.
In this case, you can add extra criteria to the search.
Extension
The extension number for which include interactions. You can specify the exact
extension number or use wildcards to include a range of extension numbers.
Valid values
Alphanumeric string of up to 256 characters, including the following special
characters:
! @ # $ % ^ & * () _
+ = <> , . ? / : ; '
{} [] | ~ `
Numeric values can be any number between -2^31 (-2,147,483,648) and 2^31 -
1(2,147,483,647)
Wildcard usage
Use ? as a single character placeholder or * as a multi-character placeholder.
For example, entering 21? includes all three-digit extensions that start with 21.
PBX ID
The PBX ID for which to include interactions. The PBX ID is either the ID the employee
uses to log into the switch or the PC login name. You can specify the exact PBX ID or use
wildcards to include a range of PBX IDs.
Valid values
Alphanumeric string of up to 256 characters, including the following special characters:
! @ # $ % ^ & * () _
+ = <> , . ? / : ; '
{} [] | ~ `
Wildcard usage
Use ? as a single character placeholder or * as a multi-character placeholder. For
example, entering *44 includes all PBXs ending in 44, 2044, 2144 and 2244.
Wrap-up Time
Include interactions based on the duration between the end of the current interaction
and the beginning of the next interaction. This parameter is useful to indicate the time
spent on an interaction after it ended.
Valid values
Any number between 00:00 and 59:59 in mm:ss format
Contacts
The Contacts category contains parameters relating to contacts to include in the report.
Use these parameters to include or exclude interactions at the level of the contact in
contrast to individual interactions. You can include interactions from a specific contact
based on the contact ID, or analyze interaction handling for multiple contacts based on
other parameters such as holds, transfers and conferences.
Related topics
Number of Holds, page 358
Number of Transfers, page 358
Number of Conferences, page 359
Total Hold Time, page 359
Exceptions, page 359
Number of Holds
Include contacts based on the number of times the customer was put on hold during the
contact.
In systems with multiple switches, the Switch Call ID or ANI is used to gather the
various interactions comprising an entire contact, rather than using the Contact ID. In
this case, this field may not contain information related to the entire contact.
Valid values
Any number between 0 and 99
Wildcard usage
N/A
Number of Transfers
Include contacts based on the number of times the customer was transferred between
employees during the contact. The Number of Transfers does not include transfers
outside the PBX.
In systems with multiple switches, the Switch Call ID or ANI is used to gather the
various interactions comprising an entire contact, rather than using the Contact ID. In
this case, this field may not contain information related to the entire contact.
Valid values
Any number between 0 and 99
Wildcard usage
N/A
Number of Conferences
Include contacts based on the number of times when there were more than two
participants connected to the a contact.
In systems with multiple switches, the Switch Call ID or ANI is used to gather the
various interactions comprising an entire contact, rather than using the Contact ID. In
this case, this field may not contain information related to the entire contact.
Valid values
Any number between 0 and 99
Wildcard usage
N/A
Valid values
Any number between 00:00 and 59:59 in mm:ss format
Wildcard usage
N/A
Exceptions
Determines if to include only contacts tagged as exceptions, or all other contacts that
are not exceptions.
Valid values
One of the following:
Only exception contacts
Non-exception contacts
Wildcard usage
N/A
Custom Data
The Custom Data category contains Custom Data and Conditional Custom Data fields to
include in the report. This information is displayed when CDs and CCDs are defined in
the system. Use Custom Data parameters to include customized information from a
predefined data set. A data set comprises Custom Data (CD) and Custom Conditional
Data (CCD) fields.
Related topics
Data set, page 361
Custom data, page 361
Conditional custom data, page 362
Data set
The data set with the custom data and conditional custom data fields to include in the
report. The system-defined default data set is always selected by default. You can select
any data set from the list.
Valid values
Single data set from the available list
Wildcard usage
N/A
Custom data
The custom data (CD) fields from the selected data set to include in the report. The
fields displayed are the ones assigned to your groups and roles in the Assignment
Manager.
For text CD fields, select one or more values from the list, or type a value in the text
box. Verify that the value you type correlates to the actual value that is received from
the applications providing this information such as CTI.
TIP To quickly find CD values, start typing part or all of the CD value in the
Search field.
Valid values
Text value can contains up to 50 alphanumeric characters, including the following
special characters:
! @ # $ % ^ & * () _
+ = <> , . ? / : ; '
{} [] | ~ `
Numeric value can be any number between -2^31 (-2,147,483,648) and 2^31 - 1
(2,147,483,647)
Wildcard usage
Use ? as a single character placeholder or * as a multi-character placeholder.
Valid values
For each CCD fields, select all or specific values.
Wildcard usage
N/A
Switches
The Switches category contains parameters relating to switches to include in the report.
Use Switch parameters to include interactions by the data sources configured, with or
without a unique call identifier.
Related topics
Switches, page 363
Switch Call ID, page 363
Switches
The switch or switches to which the employees log in, to include in the report. The list
includes all the data sources configured.
If you select a PBX ID without selecting switches, the report includes interactions made
by different employees that share a PBX ID, but log on to different switches.
Valid values
One or more switches from the available list
Wildcard usage
N/A
Switch Call ID
The call identifier by which to qualify interactions to include in the report. The call
identifier is a tag that uniquely identifies the switch data source. Identifiers are assigned
according to geo-location for example, or organizations within the enterprise by the
service or function they perform. Customer service and sales are examples of switch call
IDs.
For example, to focus on interactions routed to the sales department, you would define
a Switch Call ID of Sales.
If you have selected one or more switches, defining a Switch Call ID includes
interactions from all the selected switches that match the Switch Call ID.
If the Switch Call ID was changed as the call was routed through the customer
telephony network, the system tags only the first or last one associated with the
interactions of the call that are recorded.
Valid values
Alphanumeric string of up to 256 characters, including the following special characters:
! @ # $ % ^ & * () _
+ = <> , . ? / : ; '
{} [] | ~ `
Wildcard usage
Use ? as a single character placeholder or * as a multi-character placeholder. For
example, entering Sal* would include Sale and Sales.
Recorders
The Recorder category contains parameters relating to recorders to include in the
report.
Related topics
Channel number, page 365
Recorder, page 365
Channel number
The channel number of the recording module that records the interactions.
Valid values
Any number of up to 9 digits, between -2^31 (-2,147,483,648) and 2^31-1
(2,147,483,647)
Wildcard usage
N/A
Recorder
The recorder that recorded the audio component of enterprise transactions and marks
interactions in the Contact database. It can be configured to do so selectively, based on
instructions received from the Integration Service or a recording application (such as
Record On-Demand).
Valid characters
Any number up to 6 digits, between -2^31 (-2,147,483,648) and 2^31 - 1
(2,147,483,647)
Wildcard usage
N/A
Categories
The Categories contain parameters relating to predefined Speech categories to include
in the report. Use Category parameters to analyze data for issues of business interest.
Related topics
Speech Categories, page 366
Emotions, page 366
Speech Categories
The Speech Analytics category or categories of interest to you to include in the report.
The list of available categories includes those published to the Speech Analytics
application, and assigned to your groups and roles in the Assignment Manager.
When new categories are published, or existing categories are updated, it can take
about 30 minutes to sync data between the Speech Analytics and Interactions
applications.
TIP To quickly find speech categories, start typing part or all of the category
name in the Search field.
Valid values
One or more Speech categories from the available list.
Wildcard usage
N/A
Emotions
Include interactions in which the Speech Analytics application detected “emotions”.
Emotions is a separate system-defined Speech Analytics category, available by default in
all configurations that support Speech Analytics.
If you have also selected one or more categories, the report includes those interactions
(or their related evaluations/assessments) that contain emotions and are associated
with the selected category.
If you have not selected any categories, the report includes all interactions in which
emotions are detected from all categories in projects assigned to you.
Valid values
N/A
Wildcard usage
N/A
Distribution options
Shows the values for a reported measurement, distributed across factors of interest.
The distribution option can be based on time or value such as Speech Analytics
categories, or conditional data such as lines of business or regions.
For example, when generating the average score for an organization/group, you can
display the score averages for each line of business handled by the organization or
group, by selecting a conditional distribution option.
If a distribution is selected for a graphical report, the report generates the distribution
charts together with the main report. If a distribution is selected for a textual report, the
report only generates the distribution tables.
The distribution options displayed differ depending on the report you are running.
Related topics
None, page 368
Conditional custom data, page 368
Distribute by time intervals, page 369
Distribute by time periods, page 370
Speech Analytics categories, page 370
Display selected distribution for all, page 370
None
Does not show any data distribution.
Valid values
N//A
Wildcard usage
N/A
Valid values
One of the predefined conditional custom data fields.
Wildcard usage
N/A
Valid values
<n> hour(s)/day(s)/month(s)/year(s)
where n is the frequency for the selected time interval. For example if n=2 and time
interval is month(s), the distribution is displayed for every 2 months.
Wildcard usage
N/A
Valid values
Hour of day: Hourly breakdown for a 24-hour period, from 0:00 to 23:00
Day of week: Daily breakdown for a seven-day week, from 01 to 07
Day of month: Breakdown for each day of the calendar month, from 01 to 31.
Month of year: Breakdown for each month in the calendar year, from 01 to 12.
Wildcard usage
N/A
Valid values
N/A
Wildcard usage
N/A
Display options
The visual format and layout of the data in the reports. You can define a meaningful
name for the report, choose between bar charts (graphical) and tabular (textual)
formats, and sort by name or value to order the data the way you want to see it.
The options displayed differ depending on the report you are running.
Related topics
Display name, page 371
Sort options, page 371
Display format, page 372
Productivity Type, page 373
Productivity Type, page 373
Display name
Optional. The name displayed in the report header below the report type. Use the
Display name to assign a descriptive name that identifies the report objective and helps
to differentiate it from other reports of the same type.
Valid values
One of the following:
Empty
User-defined text
Wildcard usage
N/A
Sort options
The sort order for the data in the report, and can be by name, date, or value.
Based on the report type, employees without evaluations in the system are shown at the
end of the chart as Null. You cannot differentiate between the scores of employees
without evaluations and the scores of employees that are evaluated and actually
received a Null score.
TIP For best results, it is recommended selecting up to 20 names or values in
the report.
Valid values
One of the following (depending on the report you are running):
Wildcard usage
N/A
Display format
The visual format of the report — Graphical (the default), or Textual.
When graphical format is selected, the data is displayed as a chart. The chart type
differs according to the type of report, each report type is associated with a predefined
chart type which can be one of the following:
Bar charts, the default chart type for graphical formats, generally depict how
results are distributed. Bar charts show an X:Y representation of a number of
results plotted against two criteria. Each result is represented as a bar on the chart.
The reference organization/group, if included, is the first bar in the chart.
Line charts show trends over time for data distributed by time interval and time
period. Line charts use an X:Y representation of a number of results plotted against
two criteria. Each result is represented by a different color and shape connecting the
various results of the time line. Line charts are used to display distribution by time
intervals and time periods.
Scatter charts compare quantity vs. quality. All productivity reports are displayed
as scatter charts. Scatter charts use an X:Y representation to depict three
dimensions, the employee, and two other criteria. The X-axis charts a productivity
dimension, such the number of interactions. The Y-axis charts a quality dimension,
such as information on the scores of an employee. Each dot on the chart represents
an employee or user.
Each result is represented in a different shape and color. There are eleven unique
shapes and sixteen different colors. If the chart contains more than eleven entities,
an icon is repeated in a different color. If the chart contains more than 24 entities,
the legend cannot display all the entities.
Pie charts show the relative size or percentage compared to the whole. Pie charts
are used to display distribution by conditional custom data, when the distribution
factor value is numeric.
Valid values
One of the following:
Graphical
Textual
Wildcard usage
N/A
Productivity Type
Productivity type refers to the productivity factor against which the performance of
employees and organizations/groups is measured. This parameter is displayed for
productivity reports only.
Valid values
Number of interactions per day (default)
Number of interactions per hour
Average interaction duration: calculated by taking the sum of the contact duration,
and dividing by the number of interactions
Percentage talk time: Identifies the percentage of time employees spend talking on
the telephone during their work hours (shifts)
Wildcard usage
N/A
Valid values
N/A
Wildcard usage
N/A
Evaluations/Assessments
The Evaluations/Assessments category contains evaluation/assessments related
parameters to include in the report. This information is displayed for evaluation/
assessment reports only.
You can include any number of forms, form components, and some other form-related
details in your report parameter. However, to make the parameter selection efficient,
you need to be familiar with the structure of forms in your organization, and be aware of
the ways in which form-related parameters are applied.
Related topics
Evaluated/Assessed by, page 375
Forms, page 376
Form Components, page 377
Reason, page 378
Score, page 378
Display Evaluation Data Fields, page 378
Evaluated/Assessed by
The person who evaluated/assessed an employee and whose evaluations/assessments
are to be included in the report. You must have the View Employees privileges to be
able to view evaluators/assessors.
The evaluators/assessors displayed in the list depend on your role scope and whether
you are assigned the Generate Reports for Evaluations/Assessments made by
Leaders of my Group(s) or Filter by all Evaluators/Assessors privileges
assignments:
If assigned: displays evaluators/assessors in your organization/groups and sub-
organizations/subgroups.
If not assigned: the Evaluators option is not displayed and you cannot select
evaluators/assessors to filter your report. The report results include only your
evaluations/assessments that you performed.
If you do not select specific evaluators/assessors, the report results depend on your
privileges as follows:
Evaluator/assessor-centric report types
Generate Reports for Evaluations/Assessments made by Leaders of my
Group(s) or Filter by all Evaluators/Assessors assigned:
The report includes evaluators/assessors who are directly assigned to your
organization/groups and yourself. Evaluators/assessors assigned to
organization/groups above or below you in the hierarchy are not included.
Other report-types
Valid values
One or more evaluators
Wildcard usage
N/A
Forms
Description
The evaluation/assessment form or forms for which to include data. The report results
include all the revisions of the forms.
Based on your form assignments in the Assignment Manager, the list includes only those
forms assigned to you.
If you do not select a form, and you are assigned the Search for Any Form option, the
report includes evaluations/assessments with any form. The results include forms that
do not appear in the Forms list. The results also include evaluations/assessments whose
forms have been deleted.
If applicable, you can also view Customer Feedback evaluation data in reports. To view
this information, select forms with the Customer Feedback prefix (<Survey
Number>_CF) in the name.
Valid values
One or forms in the list
Wildcard usage
N/A
Form Components
Description
The sections, categories or questions in the form to include in the report. You can select
one or more form components from the same form. Select form components instead of
the form to focus on evaluations/assessments that use only those form components.
If you select one or more components, the report results always show the evaluation/
assessment data for the components. Otherwise the results always show the data for
the forms.
The form components displayed are the components associated with the latest
published version of the form.
If you select a component that has changed (resulting in a new form version), only the
evaluations/assessments that are performed after the change are associated with the
modified form component and are included in the report.
Shared form components: a component parameters does not include any indication
of whether a component is shared (used across multiple forms). The component name
can serve as a partial indication of shared components. However, components with the
same name are not necessarily shared.
If you select a shared form component without selecting a form, the report includes all
evaluations/assessments based on the data related to this component, across all the
forms in which it appears. If you want the report to include data that relates to a shared
component and its usage in a particular form, first select the form for your report
parameter, and then select the form component.
Form components scores: To see meaningful averages, select forms or form
components with the same maximum score.
For example, you select two form components both of which have a maximum score of
10, and the employee scores 9 in one and 7 in the other, the average is (9+7)/2=8. This
average gives a clear indication of employee performance. Selecting two form
components with two different maximum scores, 20 and 5, and the employee scores 14
out of 20 and 4 out of 5, the average score is 9. This average does not indicate whether
the employee performance is good or poor.
Valid values
One or more form components from the same form
Wildcard usage
N/A
Reason
The reason or reasons to focus on in a report. The reason field is associated with a
specific question, and provides additional information as to why an evaluator or assessor
selected a specific answer to a question.
Filtering by reason is only available for the Average Evaluation Scores per Reason
report. To filter by reason, select questions in the form component that are associated
with reasons.
If no reason is selected, the report results include all the reasons associated with
the form component or the form, whichever is selected
If no form/form component is selected, the report results include all the reasons
from all forms assigned to you
Valid values
One or more reasons
Wildcard usage
N/A
Score
The number of points by which to filter evaluations/assessments for the report. The
score always refers to that of the entire form, and not that of the form component.
If you also select form components, the report will include the components only if the
score of their related form matched the score you defined.
Valid values
Any number between 0 and 99999
Wildcard usage
N/A
Valid values
One or more ECD fields
One or more Rating fields
One or more Status fields
Wildcard usage
N/A
Interactions Frequently
Asked Questions
Topics
Moving BO reports to SSRS platform, page 381
Self evaluations in reports, page 383
Transferring employees, page 384
Viewing deactivated, hidden, and deleted entities, page 385
Reports and new form versions, page 387
Chapter A - Interactions Frequently Asked Questions Moving BO reports to SSRS platform
Moving the reports from the BO platform to the SSRS platform has the following impact
on the Interactions and Analytics reports:
Not all the 11.2 Interactions and Analytics predefined reports were transferred to
SSRS. The following reports were not transferred:
Evaluator productivity vs. quality report
Assessor productivity vs. quality report
Assessment scores vs. contact data report
Historical Average Talk Time per Employee
Historical Average Talk Time per Group
Historical Average Talk Time Percentage per Employee
Historical Average Talk Time Percentage per Group
Historical Daily Average Interactions per Employee
Historical Daily Average Interactions per Group
Historical Recorded Interactions per Employee
Historical Recorded Interactions per Group
Historical Recorded Contacts Volume
For systems migrating to V15.1:
Customers are required to re-create custom and ad-hoc reports on the 15.1
system, as the BO custom and ad-hoc reports that exist in previous versions are
not migrated.
Customers are required to redefine report schedules in the 15.1 system, as the
BO reports schedules that exist in previous versions are not migrated.
Customers are required to redefine report role assignments in the 15.1 system,
as the BO reports assignments that exist in previous versions (in the Assignment
Manager) are not migrated.
Scheduling of reports that are based on SSRS models is not supported in this
release. These reports are include:
Speech reports
All Ad-Hoc reports
All Custom reports
Once a report is executed, the input parameters used to run the report are not
saved. That is, reopening the report parameters window displays the default values.
When setting up a report in the dashboard (My Home>My
Information>Dashboards), if you drill down in the report, you cannot set the
drilled down chart as the default chart to display in the dashboard.
Your employees self evaluations are included in reports that focus on organizations/
groups and employees. They are not included in reports that focus on evaluators/
assessors.
When running a report that focuses on organizations/groups/employees, in order for the
self evaluations of employees not to be displayed, you can do one of the following:
Select an evaluator in the report parameters
Create a dedicated self evaluation form in the Form Designer application, that will
be used for self evaluations only. When running a report, do not select the dedicated
self evaluation form in the report parameters.
NOTE In reports that focus on evaluators, or when the evaluator is selected as a
report parameter, self evaluations are included in the reports if the self
evaluation was performed by an employee that is also a leader.
Transferring employees
If one of my employees is transferred from my group A to group B, is his/her
historical data still included in reports that I generate?
If you generate a report for group A for a period when the employee was part of group
A then:
When generating a report that focuses on evaluations, the evaluations of the
transferred employee are included in the report
When generating a report that focuses on interactions, the interactions of the
transferred employee are not included in the report.
If you generate a report for both groups A and B for any period, and you have visibility
in both groups, you will be able to view all employees data (evaluations and
interactions).
Only if you are assigned the Filter by All Groups privilege, you can see all evaluations
that were made on an employee that is currently assigned to you, and also the
evaluation of the employee that are associated to another organization/group not in
your visibility.
You do not receive results for this employee for the period that the employee was
assigned to a different organization/group.
However, if you are assigned the Filter by all Groups privilege, the report includes
evaluations made for the employee that were associated with the employee previous
organization/group.
Yes. Although you cannot search for deactivated employees, groups, and evaluators,
you can still view their data in reports, and they can be displayed on the X axis.
Yes. Although you cannot search for hidden forms, you can still view their data in
reports, and they can be displayed on the X axis.
Upon being deleted, organizations/groups cannot appear on the X axis of reports. Yet,
you can see data of deleted organizations/groups in reports that do not focus on
organizations/groups. For example, deleted organizations/groups cannot be displayed in
the Average Evaluation Scores per Group report, but their statistics are included in
the Average Evaluation Scores per Evaluator report.
To be able to view deleted organizations/groups data in reports, you must be assigned
the Filter by all Groups privilege.
Upon being deleted, evaluators and assessors cannot appear on the X axis of reports.
Yet, you can see data of deleted evaluators and assessors in reports that do not focus on
these entities. For example, deleted evaluators cannot be displayed in the Average
Evaluation Scores per Evaluator report, but their statistics are included in the
Average Evaluation Scores per Group report.
To be able to view data of deleted evaluators and assessors, you must be assigned the
Filter by All Evaluators/Assessors privilege.
No. Deleted forms, as well as all evaluations that were based on these forms, are no
longer available in search results or in reports.
Upon being deleted, employees cannot appear on the X axis of reports. Yet, you can see
their data in reports that do not focus on employees. For example, deleted employees
cannot be displayed in the Evaluation Activity per Employee report, but their
statistics are included in the Evaluation Activity per Evaluator report.
All data that relates to deleted categories is available, and you can see it in reports.
All data that relates to deleted flags is still available, and you can see it in reports.
Note that you are not able to access deleted flags information in two reports that deal
with flags—Evaluation Flag Usage per Assigning User and Contact Flag Usage per
Assessor. These reports require you to select one of your current flags and then
retrieve the information according to selected flag. Flags that were deleted cannot be
selected.
In the Form Designer application, changing a form component in specific way creates a
new form version. For example, three versions of the same form exist:
Version 1—The initial version of the form
Version 2—Created when Answer 3 is added under Section 1 > Category 2 >
Question 1
Version 3—Created when Question 2 is added under Section 1 > Category 2
Depending on the selected form component as the report parameters, the report
includes different evaluation/assessment data.
Making a change to a textual field does not trigger the creation of a new form version.
For example, you change a question text in a form. If you generate a report using this
text, the latest question text is shown on the report. The report includes all the
evaluations that included this question, both before and after the question text is
changed.
Textual fields in a form or form component are comments, section or category names
and instructions, question texts and instructions, revision notes and header or footer
instructions in form-level fields.
[email protected]
1-800-4VERINT
www.verint.com
The contents of this material are confidential and proprietary to Verint Systems Inc.
and may not be reproduced, published, or disclosed to others without express
authorization of Verint Systems Inc.