MiCC ContactCenterReportsGuide
MiCC ContactCenterReportsGuide
Business
Reporting Guides
December 2022
Notices
Trademarks
The trademarks, service marks, logos and graphics (collectively “Trademarks”)
appearing on Mitel's Internet sites or in its publications are registered and
unregistered trademarks of Mitel Networks Corporation (MNC) or its subsidiaries
(collectively "Mitel") or others. Use of the Trademarks is prohibited without the
express consent from Mitel. Please contact our legal department at [email protected]
for additional information. For a list of the worldwide Mitel Networks Corporation
registered trademarks, please refer to the website:http://www.mitel.com/trademarks.
3 Forecasting........................................................................... 16
3.1 Forecasting Concepts...................................................................................... 16
3.2 Forecasting Terms........................................................................................... 17
4 Creating Reports.................................................................. 19
4.1 Generating On-Demand Reports.....................................................................20
4.1.1 Setting up My email contacts for emailing reports..................................21
4.1.2 Setting up My email contact groups for emailing reports........................21
4.1.3 Reporter Parameters.............................................................................. 22
4.1.4 Generating reports.................................................................................. 23
4.1.5 Emailing Reports.....................................................................................26
4.1.6 Printing reports........................................................................................27
4.2 Report Inbox parameters.................................................................................27
4.3 Viewing reports................................................................................................ 29
4.3.1 Producing your own graphs in Excel......................................................30
4.4 Deleting reports............................................................................................... 30
4.5 Troubleshooting missing data..........................................................................31
5 Scheduling reports to run automatically................................................................... 33
5.1 Scheduled reports parameters........................................................................ 33
5.2 Generating scheduled reports......................................................................... 33
5.2.1 Creating report schedules.......................................................................34
5.2.2 Creating MiContact Center Business - Contact Center Report
schedules......................................................................................................... 35
5.2.3 Creating User report schedules and Employee schedule mailer
schedules......................................................................................................... 37
5.3 Adding reports to schedules............................................................................38
5.3.1 Adding MiContact Center Business - Contact Center reports to
schedules......................................................................................................... 39
5.3.2 Adding agent and employee reports to User reports schedules............. 39
5.3.3 Adding work schedules to Employee schedule mailer schedules...........41
5.4 Generating scheduled reports immediately..................................................... 41
5.5 Editing schedules.............................................................................................42
5.6 Deleting schedules...........................................................................................42
20 Glossary............................................................................ 579
• Overview
• Contact Center Reports Workgroup Reports
• About this Guide
• Searching for Key Words and Topics
• Printing this Reports Guide
• Understanding ACD and SMDR report data
• Service Level and Your Reports
1.1 Overview
Note:
For detailed information on MiVoice Analytics and MiVoice Analytics reports, see the
MiVoice Analytics Reports Guide.
The Mitel MiContact Center Business - Contact Center Reports Guide provides a
description and an image of the following report types:
• Administrative reports:
• Voice reports:
Voice reports provide detailed information about call performance. Voice reports can
be run on the following devices: Agent and Agent group, Queue and Queue group,
Employee and Employee group, Team, Extension, Trunk, Forecast, and DNIS.
• Conversation Detail reports:
Email reports provide detailed information about email performance. Email reports can
be run on the following devices: Agent, Agent group, Queue, and Queue group. You
can run these reports if you are licensed for Multimedia Contact Center.
• Chat reports:
Chat reports provide detailed information about Chat performance. Chat reports can
be run on the following devices: Agent, Agent group, Queue, and Queue group. You
can run these reports if you are licensed for Multimedia Contact Center.
• SMS reports:
SMS reports provide detailed information about SMS performance. SMS reports can
be run on the following devices: Agent, Agent Group, Queue, and Queue group. You
can run these reports if you are licensed for Multimedia Contact Center.
• Multimedia reports:
Multimedia reports provide detailed information across media types: voice, email, chat,
and SMS. Multimedia reports can be generated on the following devices: Agent group,
Employee group, Queue group, and Unified Queue Group. You can generate these
reports if you are licensed for Multimedia Contact Center.
• Workforce Scheduling reports:
IVR Routing reports summarize data on ports, DNIS groups, callback queues, hunt
groups, and agents to enable supervisors to make informed decisions regarding the
future of their contact center.
• Traffic Analysis reports:
• Workflow reports:
Workflow reports summarize data on IVR Routing and Multimedia Contact Center
workflows. You can run these reports if you are licensed for either IVR Routing or
Multimedia Contact Center.
• Custom Reports:
Custom Reports are a collection of reports that are developed based on specific
customer requests. You can run these reports if your MiContact Center Business
license includes this type of report.
The raw ACD routing data is compared to the configuration of the YourSite database and
forwards relevant files to the Structured Query Language (SQL) database in real-time.
The MiContact Center Business - - Contact Center Reporter service runs reports based
on the data in the SQL database. You can produce detailed reports on contact center
statistics. The following table displays the reporting features included with MiContact
Center Business.
Produce presentation x x
quality tables and charts
(Microsoft Excel format)
you can save
Note:
MiContact Center Business includes all MiContact Center Business reports. Workgroup
includes a subset of essential reports only. For a list and descriptions of these reports,
see the relevant sections of this guide.
All reports include a banner that contains the following details. (For simplification
purposes this area has been excluded from the report examples included in this guide.)
See the following figure for an example of the report banner.
In addition, several reports contain embedded notes. These notes provide additional
information about the report’s purposes and statistics. For an example, see the "Voice
Queue Performance chart".
Because of space constraints not all report examples in this guide display in their
entirety. However, all column headings for each report are described in the table
preceding the report example. In some cases, a single device report contains slightly
different information than a group report of the same name. In these cases, the
differences are noted in the table preceding the report example or examples of both
single and group reports are supplied.
Note:
• Report statistics do not always align between reports because some report data
is derived from the ACD data stream and some from the SMDR data stream. For
more information, see "Understanding ACD and SMDR report data".
• Up to 28 columns of report data will display in a single page printed report.
You can search for content in this PDF by using the search function built into Adobe
Acrobat or Reader. Consult your Adobe documentation for other search options.
• Double-sided
• Landscape
• Flip pages up (on the long side)
All data used in reports and real-time monitors derives from ACD (Automatic Call
Distributor) real-time data streams or SMDR (Station Message Detailed Recording) data
streams. Each of these streams connects the Enterprise Server to the telephone system
using a serial com port or a TCP/IP network connection.
Each data stream is generated independently and has its own set of control attributes
within the telephone system. The same telephone switch and devices generate both
data streams but the data that is produced does not always correlate. The only similarity
between the two data streams is the Answered ACD Queue Calls record, which is
generated for both the ACD and SMDR data streams when an ACD call is answered,
depending on telephone system configuration.
The ACD data stream and the SMDR data stream can have records that are generated
from the same action, for example, an agent answering an ACD call, an agent
connecting to an outbound call, and an agent answering an incoming call. ACD real-time
events can be generated without an accompanying SMDR record, for example, when
agents log in and log out. SMDR records can be generated without an accompanying
ACD real-time event, for example, when agents enter Account Codes or transfer calls, or
when calls overflow, interflow, or abandon.
Agent information from the SMDR data stream can have multiple calls credited to an
Agent ID, as an agent with multiple extensions can handle multiple calls at once. Agent
information from the ACD real-time event data stream displays the state of an agent and
will only allow an agent to be in one state at a time.
SMDR call information for an agent is related to the soft or hard set telephone, whereas
ACD real-time event information is related to what the agent is doing.
If you are reporting on a device (agent, extension, DNIS, queue, etc.), the first record
where the device was present will dictate whether the call is pegged as ACD or non
ACD. For example, if a call was to be sent from an auto attendant to an ACD path and
then answered by an agent, if you were to run a DNIS report on this call, the call would
be pegged as non ACD, so long as the DNIS is in the first call record. Alternatively, if you
were to run an agent event report on this same call, the call would be pegged as an ACD
call.
If an ACD path or an agent group has the Real-time events option enabled, the
telephone system will generate a summary of the ACDpath and agent group queue
statistics (for example, calls waiting in queue, longest waiting caller, and available
agents) every 15 seconds.
Agent event data is used to build Agent Event by Period reports. These reports show the
data derived from the ACD real-time event stream (for example, Logout date/time, Total
shift time, Idle time, ACD true talk time, etc.).
Agent information that is stored in the database is credited to the start time of the shift or
the time that the agent logged in. When you run a report for an Agent Event by Period
report, the report will display all agent shifts for the day(s) you selected. An agent that
logs in at 07:59 and works an eight-hour shift will have a single record generated in the
MiContact Center Business database. The record that is generated will be credited to the
day they logged in and will have a start time that falls within 07:45 to 07:59 interval.
There are two classes of SMDR records: External SMDR (generated when a trunk is
involved in the call) and Internal SMDR (generated when there are no trunks involved in
the call). Each sub-stream is governed by separate configuration options programmed on
the telephone system and must be enabled to send data to the Enterprise Server.
• A call is completed (when all parties involved in the call have hung up).
• A call is transferred.
• An Account Code is entered while the call is connected.
• A call is abandoned.
• A call is interflowed from the ACD queue to a new destination.
• A call is requeued back to the ACD queue because it was not answered.
• A call is Queue Unavailable and routed to another answer point.
• An Internal SMDR record is generated when a call is completed between two internal
devices (extensions or agents) with no outside parties (trunks) involved in the call
• The call is an internal answered call only
• Calls to ACD queues report based on the dialable number of the queue not the
reporting number, as with External SMDR records
SMDR-based reports and statistics are events that originate when a caller initiates a
call. The call can be handled by multiple queues and members within the contact center.
An external call that arrives on a trunk can be offered to several ACD paths and agents
as the call is routed and transferred around the contact center. The trunk sees this as a
single call but the call will be credited to every device through which it passes. MiContact
Center Business will credit all parties and devices involved in the call and will record
the talk time of each party and device involved in the call. It is important to understand
how call routing is being handled by the telephone system to properly interpret report
statistics.
All SMDR derived statistics are credited to the 15-minute interval in which the call or call
segment originated. For example, if an ACD queue call starts at 07:59 and continues for
65 minutes, this call will credit the ACD queue with 65 minutes of talk time in the interval
07:45 to 07:59. In this example, in a 15-minute interval, a single call will account for
65 minutes of queue talk time. Calls are credited in this way to support Erlang C traffic
calculations. When call data is derived from the SMDR stream you cannot examine a call
that is spread over multiple 15-minute increments as the data would not make sense.
2 Service Level and Your Reports
To create meaningful reports, you must understand the concepts behind the reports.
Choosing a service level objective is the first step in a comprehensive planning and
management solution.
The service objective identifies the average length of time a client who has contacted
your company waits for an available queue member. It is the basis for planning and
budgeting and links the resources you require to your service objectives. Once you set a
service objective, you should routinely access it to see how consistently you are meeting
it, on a 15-minute or half-hour basis. (The service level objective is defined in YourSite
Explorer under YourSite > Queues > Performance tab.)
Contact centers in different industries use different criteria for measuring service. Your
service objective should reflect the type of service you provide and the expectations of
your customers.
In revenue-based contact centers selling products or services, the net revenue per
interaction (call, email, chat, or SMS) is considered when defining a service objective.
Revenue-based contact centers strive to provide a high level of service with minimal
blocking and delays.
• Cost-based contact centers:
Why is Service Level the standard measurement of service? Service Level provides the
most accurate representation of the clients’ experience; it is ultimately the client who
decides what constitutes good service, and whether or not to end an interaction (call,
email, chat, or SMS). It applies to inbound transactions that must be addressed as they
arrive.
When an Interaction enters a queue, the interaction is processed in one of three ways:
• The Interaction is removed from the queue, and sent to another handling point (for
example, to voice mail, an automated attendant, or another queue), (interflowed
Interaction).
Understanding the following terms will help you determine your Service Level objective:
2.1.1 Offered
All interactions received by the ACD queue, regardless of how they are handled or
routed, are referred to as offered interactions. Offered interactions include ACD handled
interactions, abandoned (long) interactions, and interflowed interactions. ACD requeued
interactions, Queue unavailable interactions, and abandoned (short) interactions are not
considered.
2.1.2 Abandoned
An abandoned interaction is an interaction terminated before being answered. An
abandoned chat is one that does not reach an agent because the client ended the chat
session before the agent opened it. Abandoned statistics are not applicable to email and
SMS.
Abandoned (long) interactions end with an abandon time > Short Abandon. You define
the Short Abandon you want under YourSite > Queues > Performance tab. The Short
Abandon default is 6 seconds. If a customer terminates the interaction hangs after
waiting 7 seconds, the interaction is considered a long abandon. Long abandon
interactions are included in report statistics.
Abandoned (short) interactions end with an abandon time < Short Abandon. You define
the Short Abandon you want under YourSite > Queues > Performance tab. The Short
Abandon default is 6 seconds. For example, if a customer terminates the interaction
after waiting just 6 seconds or less, the interaction is considered a Short Abandon. Short
Abandon interactions are not included in call statistics.
2.1.3 Interflowed
Interflow refers to a mechanism that directs an interaction in queue to another answering
point. For example, a call sent from one queue to another queue or to voicemail
is interflowed. In reporting, the interflowed statistic represents the total number of
interactions removed from a queue and sent to another queue or alternate answer point.
This includes interactions transferred manually from the queue. Interactions routed to
other answering points before the Short Abandon threshold are not included in Interflow
statistics.
• The interflow time for the interaction is predicted to exceed the interflow time.
• A client chooses the Dial Out of Queue option, which removes the interaction (calls
only) from the queue and sends it to a predefined answering point.
Note:
The Dial Out of Queue feature is a user-initiated interflow feature. A Dial Out
of Queue call is considered to be an interflowed call, and is pegged as a Calls
Interflowed statistic in reports.
2.1.4 Handled
A handled interaction is an interaction that has been opened or, in the case of calls,
answered. Calls that listen to in-queue RAD messages are not considered to be handled
until a queue member connects.
For example, your Queue Service Objective may require queue members to handle 80%
(Service Level Percent) of interactions within 120 seconds (Service Level Time). Queue
Service Objectives are configured on individual queues, in YourSite Explorer.
The default Service Level Time for calls and multimedia interactions = 120 seconds.
For calls and chats, the Service Level Percent is the number of interactions that are
handled, abandoned, and interflowed before a defined threshold time (Service Level
time), compared to the total number ofinteractions handled, abandoned, and interflowed.
The Service Level Percent = (Handled + Abandoned (long) + Interflowed (long)) within
the Service Level time ÷ Total (Handled + Abandoned (long) + Interflowed (long)).
For email and SMS, the Service Level Percent is the number of interactions that are
handled and interflowed before a defined threshold time (Service Level time), compared
to the total number of interactions handled and interflowed. The Service Level Percent
= (Handled + Interflowed (long)) within the Service Level time ÷ Total (Handled +
Interflowed (long)).
In the following figure, the Service Level Objective is to handle 80% of interactions within
30 seconds. The interactions waiting in queue for 60 seconds are routed to voice mail.
Note:
When you manually redirect (drag and drop) a call in Interactive Visual Queue,
MiContact Center Business changes the way the call is pegged on the Queue
Performance reports. If you redirect a call before the short abandon time set for the
queue, the call is pegged as Unavailable. If you redirect a call after the short abandon
time set for the queue, the call is pegged as Interflowed.
Although there is no industry standard Service Level objective, generally sales queues
are set for 80 percent of interactions to be answered within 20 seconds, and technical
support queues are set for 80 percent of interactions to be answered within 120 seconds.
You can also determine your Service Level objective based on six weeks' data. After
collecting the data, calculate the duration it takes for the average customer to abandon
the interaction. If most interactions are abandoned after two minutes, then you set the
Service Level objective for 80 percent of interactions to be answered within 120 seconds.
Once you determine what Service Level objective you want to use, you set your set your
queue service objective to match it.
To set the Service Level objective (Queue service objective), click YourSite > Queues >
Performance tab.
To optimize service, you can use the following routing strategies that involve resources
outside of the target queues and agent groups:
Forecasting involves taking historical data generated by your telephone system and using it to
predict future traffic volumes and patterns. Using forecasting reports, you can create forecasts
based on historical contact center traffic volumes. You can perform 'what-if' scenarios, and
optimize the balance between the agents scheduled and your Service Level objectives.
Note:
Forecasting with reports is limited to voice media servers. Forecasting with Ring Groups
is not supported. Forecasting with email, chat, and SMS is available in the Forecasting
tool included in Contact Center Client and Workforce Scheduling. The Forecasting tool
enables exporting forecasts to Workforce Scheduling schedules. For more information,
see the Forecasting and Workforce Scheduling chapters of the Mitel MiContact Center
Business User Guide.
The accuracy of your forecast increases with the size of your data sample. You take a
year (or preferably two or three years) of ACD queue traffic data, examine trends in Call
Load patterns, break down the information, and determine the ACD Handling Times of
the calls. You then modify the forecast based on current contact center activities and
other considerations, such as absenteeism, agent breaks, holidays, and training.
The range of dates you specify in a forecast depends on its purpose. You use long-
term forecasts to estimate future budgets and expansion opportunities, and establish
corporate objectives. You use shorter-term forecasts of one to three months to assist you
in determining seasonal staffing requirements, planning for short-term sales campaigns,
and assessing upcoming hiring needs. Using weekly, daily, and hour or half-hour
forecasts, you can tweak agent schedules and adjust for absenteeism.
After you run a forecast, you can examine the data and make adjustments based on
current contact center conditions. You can tweak the forecast by adding or reducing calls,
based on your intuition, and information gathered by yourself and others. You can devise
a system that involves the collaboration of supervisors and managers from various
departments. You can meet routinely to discuss factors that may influence the forecast
for the year and adjust it accordingly.
Some issues to consider are as follows: hardware or software system changes, expected
callers, advertising and media, changes to your products, services and/or pricing,
new products, product performance, competitors' actions, and international, national,
and company events. It is vital you devise a systematic forecasting process that all
departments support.
Wrap Up Time is the time an agent spends completing transactions associated with a
call after the agent hangs up. The Wrap Up Time is a standardized period. If an agent
requires additional time to complete paperwork or online transactions the agent can
leave the ACD queue temporarily for this purpose.
• Agent Efficiency Percent:
Agent Efficiency Percent is the percentage of time agents spend on ACD calls relative
to the time agents are scheduled to work. An Agent efficiency percentage of 100
Average Talk Time is the average time agents spend talking to callers.
• Calls Offered:
See "Offered".
• Manned Agents:
Manned Agents is the average number of agents who were logged on for the interval of
time being forecasted.
• Time to Handle:
Time to Handle is the average time calls wait in queue before being handled.
• ACD Handling Time:
ACD Handling Time is the talk time plus the hold time. If a queue member calls a
supervisor in search of more information (while the caller is on hold) or transfers or
conferences the call, the system adds these times to the ACD Handling Time value.
For example, a member speaks to a caller for two minutes and then puts the caller on
hold for three minutes and tries to solve the problem. This might include a call to the
supervisor. The queue member then initiates a conference call with the caller and a
third party and they speak for three minutes and resolve an issue. Therefore, the ACD
Handling time for the queue member is 2 + 3 + 3 = 8 minutes.
• Call Load:
The term Call Load refers to the combined effect of the number of calls received by the
ACD queue and their duration or the calls offered x (average ACD Handling Time +
average Wrap Up Time).
Creating Reports 4
This chapter contains the following sections:
• Generating On-Demand Reports
• Report Inbox parameters
• Viewing reports
• Deleting reports
• Troubleshooting missing data
We recommend you install the Client Component Pack on computers used to run and view
reports. Without the Client Component Pack installed, users may experience errors caused
by permissions or network security. These issues are outside the scope of Mitel Technical
Support.
You generate reports to monitor device performance (agents, queues, employees, etc.) and
the service levels provided to customers. Running 5 to 10 reports per month is common
practice. Supervisors monitor the devices with consistently low scores more frequently.
Resource limitations typically influence the frequency of monitoring.
Before you run reports, set up contacts or contact groups to whom you will email reports. See
"Setting up My email contact for emailing reports" and "Setting up My email contact groups for
emailing reports".
Note:
• Protected View is a Microsoft Office security feature that can impact your ability to view
Excel reports. If you use Excel 2010 to view reports, configure the following in Excel:
You can run any report on demand. Using security roles, you can restrict access to any
or all reports with advanced security features using report lists. For more information, see
the Mitel MiContact Center Business Installation and Administration Guide .
We recommend you install the Client Component Pack on computers used to run and
view reports. Without the Client Component Pack installed, users may experience errors
caused by permissions or network security. These issues are outside the scope of Mitel
Technical Support.
Note:
• Global contacts:
These consist of personal email addresses you configure in My options > Contacts >
My email contacts.
• My email contact groups:
These consist of mailing lists, comprised of global contacts and your My email
contacts, you configure in My options > Contacts > My email contact groups.
1. Hover over My options and select Contacts > My email contacts group.
2. Click Add.
3. Type the name and description of the email group to which you will email reports.
4. To share this contact group with other users, select Shared Contact Group.
5. Click Save to create the contact group or click Save & Add to add the contact group
while leaving the current page open to create new contacts.
1. To add members to the contact group, on the My email contact groups page, click
Members.
2. To add members from your contacts configured in CCMWeb, click Contacts.
3. To add members from the employees configured in YourSite Explorer, click
Employees.
4. Select the members to add to the group, and click Add.
5. To remove members from the group, select the members and click Remove.
Note:
• Report type:
Specifies the device you are reporting on, such as queues, and lists the devices for
which you can generate reports.
• Start date/End date:
Specifies the range of dates used in the report. You can pick any calendar date as the
start date and any date later in the calendar year as the end date.
• Start hour/End hour:
• Days to include:
Gives you the option of a default report that spans one day, or an over-midnight report
that spans two days (for example, an over-midnight report can cover from 10 P.M. on
day one to 10 A.M. on day two).
Note:
The Output language lists the language used in the report tables and charts: English
(North American and United Kingdom), Canadian French, European French, Latin
American Spanish, European Spanish, Brazilian Portuguese, Dutch, Italian, German,
Russian, Norwegian, Swedish, and Simplified Chinese.
• Render Type:
The Email the report to check boxes email the report spreadsheet and associated
graph to the selected contacts. You add contacts and contact groups to the Email to
list under the My options menu.
• Print the report:
The Print the report check box prints the report spreadsheet and associated graph.
caused by permissions or network security. These issues are outside the scope of Mitel
Technical Support.
You generate reports in the following manner. These steps explain how to run a Voice
Queue Group Performance by Period report.
Note:
• Some reports are stored in SQL data tables as devices instead of intervals.
Reports stored as devices cannot be run for a specific time range and can only be
run for 24-hour periods. If the Start Hour and End Hour options in CCMWeb are
disabled, the report can be generated for 24-hour periods only.
• If you run a report that results with Data Limit Exceeded in the inbox, you must re-
run the report using a shorter time span.
• Report feature availability varies by report type.
To generate a report
Hold down the <Shift> key or <Ctrl> key to select more than one queue group.
4. After Start date and End date, specify the start and end dates for the report.
Note:
If you want one report that spans two days (for example, from December 3 at 9
P.M. to December 4 at 5 A.M.), then make the Start date and the End date the
date the shift begins (December 3). If you make the Start date the date the shift
begins (December 3) and the End date the date the shift ends (December 4), you
will generate a report that spans three days (December 3 from 9 P.M. to December
5, 5 A.M.). The time span for each shift cannot exceed 24 hours.
5. If you are running a Conversation Detail Reportor a Multimedia Trace report, to create
an employee-level report plus reports for each of the employee's media types select
Create one report for each of the employee's supported media servers.
6. To create a separate report for each day in the date range you selected, select the
Create one report for each day in the selected date range check box.
7. After Start hour and End hour, specify the start and end hours for the report.
Note:
If you are running reports with the Over midnight Report mode option, the time
span between the Start hour and the End hour cannot exceed 24 hours.
8. After Interval, specify the time interval in which the statistics will display in the report.
9. After Days to include, select the days of the week to include in the report.
10. If your contact center does not operate 24 hours a day, after Report mode, select
Default.
11. To run a report over midnight, after Report Mode, select Over midnight.
The Over midnight report mode is most appropriate for 24-hour contact centers.
12. After Report output language, select the language used in the report output.
13. After Render type, specify how you will view reports, either in Excel or .pdf format.
14. Click the Filter tab, if available for the report type selected.
15. Specify the filtering options to include in the report. Separate multiple values with
commas.
You add contacts and contact groups to the Email to list under My options=>Contacts.
18. To print the report, select Print the report.
19. Click Submit.
The Report Inbox application displays the on-demand and scheduled reports generated
under your user name over the past 30 days. Inbox manager deletes reports from your
inbox by date range.
Note:
• In Report Inbox, if the report status is Pending for an extended period of time, start
Client Component Pack Manager and confirm the Enterprise Server IP address
and your user name and password are correct.
• In Report Inbox, if Data Limit Exceeded opens, re-generate the report using a
shorter time span.
• Today’s reports:
Today’s reports displays all of the reports generated today under your user name.
• Yesterday’s reports:
Yesterday’s reports displays all of the reports generated yesterday under your user
name.
• All of your reports:
All of your reports displays all of the reports generated under your user name over the
last 30 days.
• Inbox Manager:
• Report type:
The Media server field defines the media server against which you are running the
report.
• Name:
If you are creating a Queue group report, then the Name field specifies the name of
the Queue group. If you are creating a Queue report, then the Name field specifies the
name of the Queue.
• Reporting number:
If you are creating a Queue group report, then the Reporting field specifies the
reporting number of the Queue group. If you are creating an Queue report, then the
Reporting field specifies the reporting number of the Queue.
• Start date:
The Status field confirms if your report is ready. When a Complete icon appears
in the status field the report is waiting in your Report Inbox. When a Pending icon
appears, the report is not ready. A No data icon means no records are available for the
parameters you specified. A Failed icon means the report did not generate. If a report
fails, the Reporter service logs errors in the NT Event log.
• View:
Complete
Pending
No Data
Failed
Email Complete
Email Pending
Email Failed
Printing Complete
Printing Pending
Printing Failed
Note:
• The date format is tied to the regional settings on your client computer. For
example, if you configure your computer to display the date as mm/dd/yyyy, when
you browse to CCMWeb, the MiContact Center Business applications display the
date as mm/dd/yyyy.
• If you run a report that results with Data Limit Exceeded in the Inbox, you must re-
run the report using a shorter time span.
The Report Inbox application displays all forecast, on-demand, and scheduled reports
generated under your user name.
1. Click View Report Inbox (on the Reports submitted page) or hover over Report
Inbox and select Today's Reports.
2. Select the Automatically refresh this page every 10 seconds check box to
automatically update the Status column.
• When Complete appears in the status field the report is waiting in your report inbox.
• When Pending appears in the inbox, the report is not ready.
• When No data appears in the inbox, no records were available for the parameters
you specified.
• When Data limit exceeded appears in the inbox, the time span selected was too
great. Select a shorter time span and rerun the report.
• When Failed appears in the inbox, the report did not generate. If a report fails, the
Report writer logs errors in the event log. Re-submit regenerates the report.
3. Click View to view the report.
The MiContact Center Business Maintenance Alarm Dispatcher service deletes all
reports that are 30 days or older from your Report Inbox. You save any reports you want
to retain beyond 30 days to your hard drive or network directory.
• On-demand reports:
For on-demand reports, the request date governs the report’s age.
• Scheduled reports:
For scheduled reports, the date the system generates the report governs the report’s
age. Inbox manager does not delete reports you schedule to run in the future.
Note:
You must create associations in the YourSite database in order to report on devices.
The MiContact Center Business Data Processor service compares raw data to the
configuration of the YourSite database and forwards relevant files to the Structured
Query Language (SQL) database in real-time. Reports are based on the data in the SQL
database.
If you run a report and notice that the data for a particular device is missing from the
report output, verify the device is programmed in the ACD routing system and in the
YourSite database. If you determine the device is missing from the database, add it to
the database and use the Summarize Data command (on the Management Console
application) to update the SQL database with the complete ACD routing system data
stored on the local hard drive. You can then produce reports on the device.
To summarize data:
Scheduled Reports enables you to set up timetables for generating reports automatically.
Scheduled Reports renders a grid in Microsoft Excel in your browser. It retains the report
start hour, end hour, interval, and report days last selected.
You can restrict access to any or all reports with security roles using report lists. For more
information, see the MiContact Center Business Installation and Administration Guide.
Scheduled Reports renders a grid and chart in Microsoft Excel in your browser. It retains
the report start hour, end hour, interval, and report days last selected.
To create a scheduled report, you must complete the following parameters on the
properties and distribution tabs:
• Schedule name:
The Schedule name field defines the name of the report schedule.
• Schedule will run:
The Schedule will run field specifies the day(s) the report will run.
• at:
The at field defines the time the scheduled report will run.
• Reports time span:
The Reports time span field defines the period which the report will cover.
• Email the report to:
The Email the report to field defines the contacts to which you are sending the report.
• Print the report:
The Print check box indicates that the scheduled report will be printed every time it is
generated.
Note:
During the nightly maintenance routine, the entire day’s raw data is re-summarized
from the local hard drive into the SQL database. In the event the SQL database is
stopped and restarted during the day, re-summarizing the data ensures the SQL
database has the entire set of raw data files. Reports are based on the data in the
SQL database. We recommend you schedule your reports to run after the nightly
maintenance routine runs, that is, after 2:00 A.M., to ensure the reports are based on
the entire day’s raw data.
You can create the following report schedules: Report schedules, User report schedules ,
and Employee schedule mailer schedules.
Note:
• You must create a schedule and save that schedule before you can add reports to
that schedule.
• You add contacts and contact groups to the Mail Reports from This Schedule To
list under the My options menu.
• If you select printing and mailing options, the Reporter service prints and emails all
of the reports included in the schedule on the date the system runs the reports.
You can create report schedules for MiContact Center Business– Contact Center
reports, User reports, and Workforce Scheduling Employee schedules. Using User
report schedules and Employee schedule mailer, you can distribute agent/employee
reports and work schedules using an automatic email system. The auto-mailer emails the
reports and schedules to the individual agents/employees who are members of the agent
groups, employee groups, and teams you select for distribution.
Note:
If you select printing and mailing options, the Reporter service prints and emails all of
the reports included in the schedule on the date the system runs the reports.
When you select the day, all of the reports associated with the schedule will be
generated that day, every week.
5. After at, click the time of day the schedule will be activated.
For example, if you select Wednesday at 14:30, all of the reports associated with the
schedule will be generated every Wednesday at 2:30 P.M.
Note:
Reports are based on the data in the SQL database. We recommend you
schedule your reports for after the nightly maintenance routine runs, that is, after
2:00 A.M., to ensure the reports are based on the entire day’s raw data.
If you select Year to date, the report output includes all of the days from January 1 to
the present date. If you select From given start date to current date you will produce
reports for your fiscal year.
Note:
You add contacts and contact groups to the email to list under My options >
Contacts.
9. Click Save.
The date of when the schedule will next run will appear after Schedule will run next on.
10. To print the report, select the Print the report check box.
11. Add reports you want to automatically distribute.
3. Click Next>>.
When you select the day, all the reports associated with this schedule will be
generated that day, every week.
6. After at, click the time of day the schedule will be activated.
For example, if you select Wednesday at 7:00 A.M., all the reports associated with this
schedule will be printed every Wednesday at 7:00 A.M.
7. After Reports time span, select a time span.
If you select Year to date, the report output includes all days from 1 January to the
present date. If you select From given start date to current date, you will produce reports
for your fiscal year.
8. Click the Distribution tab.
Note:
Before you can add reports to schedules, you must save the schedules.
Note:
Before you can add reports to schedules, you must save the schedules.
1. In Reporter > Scheduled Reports, on the Report Schedules tab, select a schedule
and click Edit schedule.
2. Click Add a report.
3. Select a report category.
4. Select a report type.
5. Follow the steps in 'Running reports' for the Basic tab to set up the report.
6. Click Submit.
Note:
The report options available vary depending on the type of report being added.
1. In Reporter > Scheduled Reports, on the User report schedule tab, select a
schedule and click Manage schedule properties.
2. Click Add a report.
3. Select the report category.
4. Under Report type, select the report you want to add to the schedule.
5. In the Start hour and End hour lists, select a start hour and end hour for the report.
Note:
If you are running reports with the Over midnight Report mode option, the time
span between the Start hour and the End hour cannot exceed 24 hours.
6. After Interval, select the time interval for reporting: 15, 30, or 60 minutes.
Note:
You must select Over midnight if midnight occurs between the start and end times
you selected. For example, the Over midnight report mode is most appropriate for
24-hour contact centers.
7. Under Days to include, select the days of the week to include in the report (the days
of the week your business is open).
8. After Report mode, select either Default or Over midnight.
Note:
If you want a report that spans over midnight (for example, from December 3 at
9 P.M. to December 4 at 5 A.M.), then make the Start date and the End date the
date the shift begins (December 3). If you make the Start date the date the shift
begins (December 3) and the End date the date the shift ends (December 4), you
will generate a report that spans three days (December 3 from 9 P.M. to December
5, 5 A.M.). The time span for each shift cannot exceed 24 hours.
1. In Reporter > Scheduled Reports, on the Employee schedule mailer tab, select a
schedule and click Manage schedule properties.
2. Click Add Report.
3. Select a category of report, such as Workforce Scheduling reports.
4. Under Report type, select the work schedule you want to add to the schedule.
5. After Report output language, select a language.
6. After Render type, specify how you will review reports, either in Excel or .pdf format.
7. Click Submit.
To generate your scheduled reports at a specific time (other than immediately), you
specify the date and time they will be generated when you create the schedule. See
"Creating report schedules".
If you want a report that spans over midnight (for example, from December 3 at
9 P.M. to December 4 at 5 A.M.), then make the Start date and the End date the
date the shift begins (December 3). If you make the Start date the date the shift
begins (December 3) and the End date the date the shift ends (December 4), you
will generate a report that spans three days (December 3 from 9 P.M. to December
5, 5 A.M.). The time span for each shift cannot exceed 24 hours.
5. In the Start date and End date calendars, click a start date and end date the report
will generate.
6. Click Submit.
The reports associated with the schedule are generated immediately and placed in
your Report Inbox.
To edit a schedule
To delete a schedule
In addition to MiContact Center Business reporting, you can view contact center data in
Flexible Reporting and SQL Views.
Each method provides you with a unique view of the data collected from your contact center.
Selecting the most effective method to display your data depends on your current contact
center situation. Optionally, you can use these methods in conjunction to provide enhanced
flexibility and enable integration with other applications.
Report statistic naming conventions differ from Flexible Reporting reports to MiContact
Center Business– Contact Center reports. The following tables list Flexible Reporting
report statistics and their MiContact Center Business –Contact Center report statistic
equivalents.
The following table compares the Flexible Reporting statistics to the MiContact Center
Business–Contact Center reporting statistics for the Voice Queue Performance by Period
report.
Note: Note:
Note: Note:
Note: Note:
Note: Note:
Note: Note:
Note: Note:
Note: Note:
Note: Note:
Note: Note:
Note: Note:
Total Queue talk time total Total ACD handling time (hh:mm:ss)
Total Queue talk time average Total Average ACD handling time
(hh:mm:ss)
Abandon % Abandon %
Answer % Answer %
The following table compares the Flexible Reporting statistics to the MiContact Center
Business - Contact Center reporting statistics for the Voice Agent Performance by Period
report.
Agent Non ACD duration average Average Non ACD handling time
(hh:mm:ss)
Agent group average manned agents Average manned (Agent Group only)
The following table below compares the Flexible Reporting statistics to the MiContact
Center Business - Contact Center reporting statistics for the Voice Queue Performance
by DNIS report.
Device Device
Note: Note:
the total duration of non-ACD calls the total duration of non-ACD calls
(including hold time and transfer/ (including hold time and transfer/
conference time) conference time)
The following table compares the Flexible Reporting statistics to the MiContact Center
Business - Contact Center reporting statistics for the Voice Queue Answer Spectrum by
Period report.
The following table compares the Flexible Reporting statistics to the MiContact Center
Business - Contact Center reporting statistics for voice reports containing Agent event
statistics.
Agent event ACD duration average Average ACD true talk time (hh:mm:ss)
Agent event calls per hour True ACD calls per hour
Agent event non ACD duration Non ACD true talk time (hh:mm:ss)
Agent event non ACD count Non ACD inbound call count
Agent event occupancy the total duration for which the agents of
the queue are engaged in any one of the
States (but not idle). The States includes
ACD, ACD Hold, Non ACD, Non ACD
Hold, Out, Out Hold, Ringing, WorkTimer,
Makebusy, and/or DND.
You can now customize and generate the Flexible Reporting report.
A SQL View is a virtual table that aggregates data from several MiContact Center
Business report tables into a single usable view. With SQL Views, you can access the
raw telephone system data before any math or quantifiers have been applied. This is
especially useful if you need to feed raw contact center statistics to a third-party reporting
tool or create custom reports that define performance metrics in ways specific to your
business.
Note:
Some SQL Views listed here may not be applicable to your MiContact Center
Business licensing.
Note:
Calls display as two segments in Trace reports if you use route optimization. The
first segment indicates the pre-optimized talk time (indicated by an r in the SMDR
record), and the second segment indicates the post-optimized talk time (indicated
by an R in the SMDR record). In Trace reports, combining the talk time for these
two segments represents the length of the call.
Note:
The SQL Views (.sql files) are included in the product installation and can be
accessed using SQL Query Analyzer, SQL Management Studio, SQL Reporting
Services, or Crystal Reports.
Report Descriptions and Examples 7
This chapter contains the following sections:
• Top Five recommended reports
• Using reports to identify problems
This reports guide provides the descriptions and examples for each report for the following
media types and applications:
You must be licensed for Multimedia Contact Center and have generated data for the
respective media type to run these reports.
See "Workforce Scheduling reports". You must be licensed for Workforce Scheduling to run
Workforce Scheduling reports.
• IVR Routing
See "Traffic Analysis reports". You must be licensed for Traffic Analysis to run Traffic
reports.
• Workflow
See "Workflow reports". You must be licensed for or Multimedia Contact Center to run
Workflow reports on multimedia workflows.
Note:
In reports, durations greater than .5 are rounded up and durations less than .5 are
rounded down.
The Queue Performance by Period report shows traffic level highs and lows, and the
service level you provide at these times. Run this report each day and watch for trends
in the traffic level, abandon rate, and service level.
2. Queue Group Performance by Queue:
The Queue Group Performance by Queue report compares queues, and provides
information on the performance of your entire contact center.
3. Queue Group (Answer, Handle, Abandon) Spectrum by Queue:
The spectrum reports provide valuable information on how interactions are dispersed
in your contact center. You can configure answer, handle, abandon thresholds, and
describe the percent breakdown by time for
• Interactions Answered - Which interaction waited in queue the longest before it was
answered or opened? How quickly are most interactions answered or opened?
• Interactions Handled - How many interactions were handled for the queue? What
was the greatest duration for which a queue member interacted with a customer?
• Interactions Abandoned - What was the number of interactions abandoned? How
long did a customer wait before abandoning the interaction?
4. Agent Group Performance by Period:
The Agent Group Performance by Period report allows you to identify trends in agent
group performance. This report tells you how many agents are logged on, and how an
agent group's performance varies throughout the day.
5. Agent Group Event by Period (hh:mm:ss):
The Agent Group Event by Period (hh:mm:ss) report lets you compare the
performance of agents who perform similar jobs. This report provides the shift time
by agent, and a variety of contact counts and agent event counts, such as instances
where agents were unavailable.
Queue reports
Agent reports
There are several key things to watch for while running and reading reports. The
following tables describe potential problems you can identify using queue and agent
reports and make suggestions for resolution.
Drop in Service Level When does the Service Level drop during
the day?
Extremely high or low performance Are there agents who perform 20-30%
statistics worse than other agents?
1. High ACD/Non-ACD/Outbound
contact counts is not a problem if
agents are maintaining high service
levels. For voice, silently monitor
agents periodically to ensure they are
providing a high quality of service, but
not rushing callers.
2. For voice, check the ACD short handle
call count statistic in the Agent Event
by Period (hh:mm:ss) report. Not
many voice transactions can occur
in less than 20 seconds. This could
indicate that agents are 'padding' their
ACD handle statistics by prematurely
terminating calls.
Voice reports provide call statistics on the following devices. You can create on-demand
and scheduled reports.
• Lifecycle reports
• Account Code reports
• Agent reports
• Queue reports
• Extension reports
• Trunk reports
• Employee reports
• Team reports
• DNIS reports
• Forecast reports
Lifecycle reports provide detailed information on events related to the life of a call, from
the moment the call enters the telephone system to call termination. You can generate
Lifecycle reports on the following devices:
• Agent/Agent group
• DNIS/DNIS group
• Extension/Extension group
• Queue/Queue group
• Trunk/Trunk group
• Site
• Media server
• Port
• Hunt Group
Lifecycle reports can be filtered by call direction, DNIS, trunk, queue, duration in queue,
agent, Account Code, Classification Code, hold duration, call duration, phone number,
and extension. If you have clustered your enterprise into a single site, you can run a
Lifecycle report on site to report on your entire enterprise.
Call data does not make the transition to Lifecycle reports immediately upon call
completion. Real-time summary checks for completed calls to file to the Lifecycle data
table every 15 minutes by default. The maximum amount of time a call with no additional
activity will be held before being considered complete is 60 minutes. However, for
customers who routinely handle lengthy calls, this time can be extended. It is important
to delay the transition of call data to Lifecycle reports until the call is entirely completed,
otherwise the data may be inadvertently split into multiple pieces of information.
We recommend you run Lifecycle reports the next day for this day's activities to ensure
all data has transitioned to the Lifecycle data table.
Note:
• Calls display as two segments in Lifecycle reports if you use route optimization.
The first segment indicates the preoptimized talk time (indicated by an r in the
SMDR record), and the second segment indicates the postoptimized talk time
(indicated by an R in the SMDR record). In Lifecycle reports, combining the talk
time for these two segments represents the length of the call.
• Lifecycle reports containing data for internal transferred ACD calls will not link data
properly, unless the Call ID feature on the telephone system is enabled.
• Voice Lifecycle reports contain ACD and SMDR data. ACD events reflect real-time
data and SMDR events reflect historical data.
• Non-ACD extensions will only return data in the Call Segment Complete row as
well as any links to call recordings.
• Ring Groups and Ring Group extensions will provide Call Segment Complete and
MiTAI events for calls for Ring Groups in which they were involved.
• Ring Group extensions will provide Call Segment Complete only for Non-Ring
Group calls to the extensions.
• Internal calls from a Ring Group extension to a Ring Group will be represented on
the Ring Group Lifecycle Report using the Call Segment Complete.
• Ring Group calls to extensions that also have an active Hot Desk User, will
generate records for the extension and Hot Desk User, this will be reflected in the
Lifecycle Report.
• Non-ACD extensions and ring groups will only return data in the Call Segment
Complete row as well as any links to call recordings.
• The parent row’s duration is meant to represent the customer’s call experience.
Child rows call event durations are meant to represent contact center call handling
activities. Call events not affecting the customer’s call experience are omitted from
the parent row’s Duration values. Therefore, the parent row’s duration and the sum
of child row durations might not align.
• Lifecycle reports also include call notes from CCC and links to call recordings;
However, case notes in Web ignite are NOT included.
The following table defines the events that can occur in Voice Lifecycle reports. The
following figure provides an example of Lifecycle reports.
Note:
Chart reporting is not supported for individual voice reports. Instead, a set of charts on
voice agents and queues are available. Individual graphs make up the charts, providing
visual summaries of report statistics. These charts display a graphical representation of
agent and queue performance.
For more information on voice agent and voice queue reporting, see "Voice Agent
reports" and "Voice Queue reports".
For information on the Unified Queue Group chart, see "Unified Queue Group chart".
The Handled Call Types graph shows the distribution of interaction traffic by time of day.
The graph contains the following information:
The blue tiles in the Voice Agent Performance chart display the following information.
Total time the total talk time, including hold time, that
the agent spent on ACD, non-ACD, or
Outbound interactions
Average total time the average talk time, including hold time,
that the agent spent on ACD, non-ACD, or
Outbound interactions
The Agent Time in States graph displays the percentage of time the agent spent in
various agent states, as follows.
Non ACD duration the total time that the agent spent in a
non-ACD state
Make Busy duration the total time that the agent spent in a
Make Busy state
The Top 5 Queues graph displays the percentage of interaction counts that the agent
handled. The top five queues are determined by the number of ACD interactions
handled.
Note:
This graph can include queues for which agents do not answer if, for example, an
agent received an interaction transferred from another queue.
The second row of blue tiles displays agent shift information for the report’s specified
time period.
Login time (hh:mm:ss) the time at which the agent logged into the
system, for the reporting period
Shift duration the total time the agent spent logged into
the system, for the reporting period
Logout time (hh:mm:ss) the time at which the agent either last
logged out of the system or last performed
an event (for example, went into Make
Busy), for the reporting period
The Make Busy graph displays counts and the amount of time, in minutes, that agents
spent in Make Busy for the reporting period. These statistics are broken down by Make
Busy Reason Codes.
The bars in the graph indicate the number of Make Busy counts per Reason Code.
The orange line represents the amount of time spent in Make Busy per Reason Code,
enabling supervisors to see how Make Busy duration is distributed across reasons.
The Handled Call Types and Agents On graph displays the following information:
The blue tiles in the Voice Agent Group Performance chart display the following
information.
Total time the total talk time, including hold time, that
agents in the agent group spent on ACD,
non-ACD, or Outbound interactions
Average total time the average talk time, including hold time,
that agents in the agent group spent on
ACD, non-ACD, or Outbound interactions
The Agent Group by Queue graph displays the percentage of interaction counts that the
agent group handled. The queues that display are determined by the number of ACD
interactions handled.
The Agent Group Time in States graph displays the percentage of time in which the
agent group spent in various agent states, as follows.
Non ACD duration the total time that agents in the agent
group spent in a non-ACD state
Make Busy duration the total time that agents in the agent
group spent in a Make Busy state
The Agent Activity Count graph displays the number of times in which agents in the
agent group spent in various states, as follows.
The Agent Time in State graph displays the amount of time, in minutes, in which agents
in the agent group spent in various states, as follows.
Non ACD duration the total time that the agent spent in a
non-ACD state
Make Busy duration the total time that the agent spent in a
Make Busy state
If Handled bars display higher than Service count bars, interactions are not being
answered in the queue’s Service Level time. If Service count bars are higher than
Handled bars, interactions are being abandoned and/or interflowed.
The Voice Queue Group Performance chart displays the following graphs and
information:
The Handled by Hour graph shows the number of ACD interactions handled by the
queue group during the reporting interval. This includes offered, completed, and
abandoned interactions.
Graph Description
In addition to the information displayed by the graphs listed above, the Voice Queue
Group Performance chart displays the following information.
The Account Code reports provides statistics based on Account Code activity.
If Account Codes are configured to use Classification Codes, this affects how Account
Code duration is calculated. When Classification Codes are enabled, the Account Code
duration spans from the time the call arrives until the call ends. When Classification
Codes are disabled, the Account Code duration spans from the time the code was
entered until the next code is entered or the call ends.
Note:
For Classification Codes, duration statistics in this report include transfer time, time
calls were handled at other extensions, and Work Timer durations if configured for
the queue.
The Account Code Group by Account Code report provides the following information:
Total duration (hh:mm:ss) the total duration the Account Code was
used
Account Codes entered during ACD the number of times the Account Code
was entered during ACD calls
ACD Account Code duration (hh:mm:ss) the duration the Account Code was used
against ACD calls
Average ACD Account Code duration the average duration the Account Code
(hh:mm:ss) was used against ACD calls
Account Codes entered during non ACD the number of times the Account Code
was entered during non-ACD calls
Non ACD Account Code duration the duration the Account Code was used
(hh:mm:ss) against ACD calls
Average non ACD Account Code duration the average duration the Account Code
(hh:mm:ss) was used against non-ACD calls
Account Codes entered during outbound the number of times the Account Code
was entered during outbound calls
Outgoing Account Code duration the duration the Account Code was used
(hh:mm:ss) against outbound calls
Average outbound Account Code duration the average duration the Account Code
(hh:mm:ss) was used against outbound calls
Note:
• Voice Agent Event, Voice Agent Group Event, and Voice Agent Shift reports
derive their data from the ACD real-time event stream. Event reports on non-
ACD extensions use the MiTAI stream. All other reports derive their data from the
SMDR stream.
• If you are running a report on an agent group that has non-voice agents, the
statistical values in the generated report will be for voice agents only.
Agent and Agent Group reports provide statistics on agents and all activity of agents
belonging to the agent group including activity those members performed for other agent
skill groups. The Agent reports are listed below:
• Performance reports
• Event reports
• Agent and Agent Group Event by Period (hh:mm:ss) (You cannot generate this
report over midnight.)
• Agent and Agent Group Event by Period (Percentages) (You cannot generate this
report over midnight.)
• Agent Group by Agent by Make Busy / DND Code
• Agent Group Event by Agent by Day of Month
• Agent Group Event by Agent by Day of Week
• Internal/External reports
Note:
If you are unable to run a trace report with data, ensure the Inbound/Outbound /
Make Busy Trace reporting check box is selected for the media server. (YourSite >
Media server > Data summary options)
• Agent by Answering Agent Group (You cannot generate this report over midnight.)
• Answering Agent Group by Agent (You cannot generate this report over midnight.)
The Agent and Agent Group Performance by Account Code report provide the following
information:
Note:
Note:
The Agent and Agent Group Performance by Day of Month reports provide the following
information:
Non ACD calls handled the total number of non ACD calls
answered
Calls transferred from agent the total number of calls transferred from
the agent’s position
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non ACD calls
(including hold time and transfer/
conference time)
Average non ACD handling time the average duration of non ACD
(hh:mm:ss) calls (including hold time and transfer/
conference time)
Outbound handling time (hh:mm:ss) the total duration of non ACD calls
(including hold time and transfer/
conference time)
The Agent and Agent Group Performance by Day of Week reports provide the following
information:
Non ACD calls handled the total number of non ACD calls
answered
Calls transferred from agent the total number of calls transferred from
the agent’s position
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non ACD calls
(including hold time and transfer/
conference time)
Average non ACD handling time the average duration of non ACD
(hh:mm:ss) calls (including hold time and transfer/
conference time)
Outbound handling time (hh:mm:ss) the total duration of non ACD calls
(including hold time and transfer/
conference time)
to sort by Reporting, Full Name, Call duration, Reason Code Count and Reason Code
Type, in ascending or descending order. (See the following figure.)
The Agent and Agent Group Performance by Make Busy / DND Code reports provide the
following information:
Average duration (hh:mm:ss) the average time the agent spent in the
voice Make Busy and/or Do Not Disturb
state, controlled by the agent or the
supervisor
Figure 16: Voice Agent Group Performance by Make Busy / DND Code
The Agent and Agent Group Performance by Month reports provide the following
information:
Non ACD calls handled the total number of non ACD calls
answered
Calls transferred from agent the total number of calls transferred from
the agent’s position
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non ACD calls
(including hold time and transfer/
conference time)
Average non ACD handling time the average duration of non ACD
(hh:mm:ss) calls (including hold time and transfer/
conference time)
Outbound handling time (hh:mm:ss) the total duration of non ACD calls
(including hold time and transfer/
conference time)
The Agent and Agent Group Performance by Period reports provides the following
information:
Calls transferred from agent the number of calls transferred from the
agent's position
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
Average manned agents (Agent Group the average number of voice agents
only) scheduled for the shift
After you associate agents with agent groups in the YourSite database, you can run an
Agent Group Performance by Queue Report on a particular agent group.
The Agent Group Performance by Queue report shows ACD call statistics on the queues
for which the agents in the agent group answered calls, and the summary total of
statistics for non ACD calls involving the agents (in the agent group) for the shift duration
and day(s) you specify.
The first five fields contain multiple records reflecting the ACD queues serving the ACD
Agent and Agent Group. The remaining fields contain a single record that reflects the
totals irrespective of ACD queue. (See the following figure.)
Note:
This report displays call statistics for queues to which the agent is not associated, if
the agent handled a call for an unassociated queue.
The Agent and Agent Group Performance by Queue reports provide the following
information:
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD calls handled the total number of non ACD calls
answered
Calls transferred from agent the total number of calls transferred from
the agent’s position
Non ACD handling time (hh:mm:ss) the total duration of non ACD calls
(including hold time and transfer/
conference time)
Outbound handling time (hh:mm:ss) the total duration of non ACD calls
(including hold time and transfer/
conference time)
The Agent Group Performance by Agent report provides the following information for
individual agents in the group:
Non ACD calls handled the total number of non ACD calls
answered
Shift duration the total time the agent spent logged into
the system, for the reporting period
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non ACD calls
(including hold time and transfer/
conference time)
Average non ACD handling time the average duration of non ACD
(hh:mm:ss) calls (including hold time and transfer/
conference time)
Outbound handling time (hh:mm:ss) the total duration of calls that you made to
destinations outside the office (including
hold time and transfer/conference time)
Average outbound handling time the average duration of calls that you
(hh:mm:ss) made to destinations outside the office
Total Make Busy time (hh:mm:ss) the total time spent in Make Busy,
controlled by the agent or the supervisor
Total DND time (hh:mm:ss) the total duration the agent spent in Do
Not Disturb, controlled by the agent or the
supervisor
The Agent Group by Agent by Account Code Compliance report provides the following
information for individual agents in the group:
Non ACD calls handled the total number of non ACD calls
answered
ACD calls with Account Codes the number of ACD calls to which account
codes were applied
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non ACD calls
(including hold time and transfer/
conference time)
Average non ACD handling time the average duration of non ACD
(hh:mm:ss) calls (including hold time and transfer/
conference time)
Originated outbound handling time the total duration of calls that you made to
(hh:mm:ss) destinations outside the office (including
hold time and transfer/conference time)
Average originated outbound handling the average duration of calls that you
time (hh:mm:ss) made to destinations outside the office
(including hold time and transfer/
conference time)
The Agent Event by Period (hh:mm:ss) report displays log on and log off times for the
agent and the total duration the agent spent in various agent states for the day(s) you
specify. It reports the call statistics in hours, minutes, and seconds and provides call
counts for the agent. (See the following figure.)
The Agent Group Event by Period (hh:mm:ss) report displays log on and log off times
for the members of the agent group and the total duration each agent of the agent group
spent in various agent states for the day(s) you specify. It reports the call statistics in
hours, minutes, and seconds and provides call counts for the agent.
Your choice of Shift Mode determines how this report calculates data. In Reporter, after
Shift Mode, select the checkbox for either Default or Agent Group Presence. 'Default'
ignores presence data. 'Agent Group Presence' subtracts agent absence from shift data.
Data relating to individual agent presence is not displayed under the corresponding
report columns.
The Agent Event by Period (hh:mm:ss) report is truncated to the first 1000 records. It
provides the following information:
Total shift time (hh:mm:ss) the total time the agent spent logged into
the system, for the reporting period
Idle time (hh:mm:ss) the total duration the agent was logged on
and available to receive calls
Average ringing time (hh:mm:ss) the average duration calls rang on the
agent’s phone before the agent answered
the calls
ACD short handle call count the total number of ACD calls answered
where talk time is less than the Short
handle parameter
ACD true talk time (hh:mm:ss) the total duration of ACD calls, from agent
pick up to client hang up (excluding hold
time)
ACD hold time (hh:mm:ss) the time for which ACD interactions were
put on hold
Average ACD true talk time (hh:mm:ss) the average duration of ACD calls, from
agent pick up to client hang up (excluding
hold time)
True ACD calls per hour the total ACD call count minus the ACD
short handle call count, divided by the
shift time for this agent
Wrap up time (hh:mm:ss) the duration the agent spent in the wrap
up state. Wrap up time does not include
any time spent making or taking calls
during the wrap up timer
Average wrap up time (hh:mm:ss) the average duration the agent spent in
the wrap up state. Wrap up time does not
include any time spent making or taking
calls during the wrap up timer
Non ACD true talk time (hh:mm:ss) the total duration of non-ACD calls
(excluding hold time)
Note:
Outbound hold time (hh:mm:ss) the time for which outbound interactions
were put on hold
Note:
Total hold time (hh:mm:ss) the total hold duration across all call types
(ACD, non ACD, and outbound calls)
Average hold time (hh:mm:ss) the average hold time across all call types
(ACD, non ACD, and outbound calls)
(Total hold time / Total hold count)
Total hold count the total hold count across all call types
(ACD, non ACD, and outbound calls)
Total Make Busy time (hh:mm:ss) the total time spent in Make Busy,
controlled by the agent or the supervisor
Average Make Busy time (hh:mm:ss) the average time the agent spent in
Make Busy, controlled by the agent or the
supervisor
Total DND time (hh:mm:ss) the total duration the agent spent in Do
Not Disturb, controlled by the agent or the
supervisor
Average DND time (hh:mm:ss) the average duration the agent spent in
Do Not Disturb, controlled by the agent or
the supervisor
The Agent Group Event by Period (hh:mm:ss) report is truncated to the first 1000
records. It provides the following information:
First login date/time the date and time at which the first agent
in the group logged into the system
Last logout date/time the date and time at which the last agent
in the group either last logged out of the
system or last performed an event (for
example, went into Make Busy)
Total shift time (hh:mm:ss) the total time the agent spent logged into
the system, for the reporting period
Idle time (hh:mm:ss) the total duration the agent was logged on
and available to receive calls
Average ringing time (hh:mm:ss) the average duration ACD calls rang
on the agent’s phone before the agent
answered the calls
ACD calls handled the total number of ACD calls the agent
answered
ACD short handle call count the total number of ACD calls answered
where talk time is less than the Short
handle parameter
ACD true talk time (hh:mm:ss) the total duration of ACD calls, from agent
pick up to client hang up (excluding hold
time)
ACDhold time (hh:mm:ss) the time for which ACD interactions were
put on hold
Average ACD true talk time (hh:mm:ss) the average duration of ACD calls, from
agent pick up to client hang up (excluding
hold time)
True ACD calls per hour the total ACD call count minus the ACD
short handle call count, divided by the
shift time for this agent
Wrap-up time (hh:mm:ss) the duration the agent spent in the wrap
up state. Wrap up time does not include
any time spent making or taking calls
during the wrap up timer
Average wrap up time (hh:mm:ss) the average duration the agent spent in
the wrap up state. Wrap up time does not
include any time spent making or taking
calls during the wrap up timer
Non ACD true talk time (hh:mm:ss) the total duration of non-ACD calls
(excluding hold time)
Note:
Outbound hold time (hh:mm:ss) the time for which outbound interactions
were put on hold
Note:
Total hold time (hh:mm:ss) the total hold duration across all call types
(ACD, non ACD, and outbound calls)
Average hold time (hh:mm:ss) the average hold time across all call types
(ACD, non ACD, and outbound calls)
(Total hold time / Total hold count)
Total hold count the total hold count across all call types
(ACD, non ACD, and outbound calls)
Total Make Busy time (hh:mm:ss) the total time spent in Make Busy,
controlled by the agent or the supervisor
Average Make Busy time (hh:mm:ss) the average time the agent spent in
Make Busy, controlled by the agent or the
supervisor
Total DND time (hh:mm:ss) the total duration the agent spent in Do
Not Disturb, controlled by the agent or the
supervisor
Average DND time (hh:mm:ss) the average duration the agent spent in
Do Not Disturb, controlled by the agent or
the supervisor
If you specify conditions in which agents enter unavailable states (logged off, Make Busy,
Do Not Disturb), you can accurately measure the time agents spent on various activities.
For example, you could specify that agents log off when they go on breaks, for lunch, or
when they are away from their desks for greater than five minutes. You could specify that
agents go into Make Busy when they are away from their desks less than five minutes,
and that they enter do not disturb when they are in meetings or in training.
Your choice of Shift Mode determines how this report calculates data. In Reporter, after
Shift Mode, select the checkbox for either Default or Agent Group Presence. 'Default'
ignores presence data. 'Agent Group Presence' subtracts agent absence from shift data.
Data relating to individual agent presence is not displayed under the corresponding
report columns.
The Agent Event by Period (Percentages) report provides the following information:
Total shift time (hh:mm:ss) the total time the agent spent logged into
the system, for the reporting period
ACD true talk percentage the % of time the agent answered ACD
calls (excluding hold time)
Non ACD talk percentage the % of time the agent answered non-
ACD calls (excluding hold time)
Non ACD hold percentage the % of time non-ACD calls spent on hold
Note:
In Event reports, Outbound statistics
do not include unanswered calls
Note:
Make Busy percentage the % of time the agent spent in the voice
Make Busy state
The Agent Group Event by Period (Percentages) report provides the following
information:
Total shift time (hh:mm:ss) the total time the agent spent logged into
the system, for the reporting period
ACD true talk percentage the % of time the agent answered ACD
calls (excluding hold time)
Non ACD talk percentage the % of time the agent answered non-
ACD calls (excluding hold time)
Non ACD hold percentage the % of time non-ACD calls spent on hold
Note:
Note:
In Event reports, Outbound statistics
do not include unanswered calls
Make Busy percentage the % of time the agent spent in the voice
Make Busy state
The Agent Group by Agent by Make Busy / DND Code report provides the following
information:
Reason Code name the name of the Reason Code (If the
Make Busy Reason Code 01 means the
morning break, the name of the Make
Busy Reason code could be Morning
Break)
Average duration (hh:mm:ss) the average time the agent spent in the
voice Make Busy and/or Do Not Disturb
state, controlled by the agent or the
supervisor
Note:
The Make Busy statistics differ between the Voice Agent by Make Busy / DND Trace
report and the Voice Agent Group by Agent by Make Busy / DND Code report. In the
Voice Agent by Make Busy / DND Trace report, the Make Busy statistics include the
total duration from the time the agent entered the Make Busy state to the time the
agent left the Make Busy state. In the Voice Agent Group by Agent by Make Busy /
DND Code report, the Make Busy statistics do not include the time spent in any
overriding state.
Figure 24: Voice Agent Group by Agent by Make Busy / DND Code
The Agent Group Event by Agent by Day of Month report displays log on and log off
times for each agent of the agent group, and the total duration that each agent spent
in various agent states for each day of the month. It reports the call statistics in hours,
minutes, and seconds and provides call counts for the agent. (See the following figure.)
Your choice of Shift Mode determines how this report calculates data. In Reporter, after
Shift Mode, select the checkbox for either Default or Agent Group Presence. 'Default'
ignores presence data. 'Agent Group Presence' subtracts agent absence from shift data.
Data relating to individual agent presence is not displayed under the corresponding
report columns.
The Agent Group Event by Agent by Day of Month report provides the following
information:
First login time the date and time at which the first agent
in the group logged into the system
Last logout time the time at which the last agent in the
group either last logged out of the system
or last performed an event (for example,
went into Make Busy)
Total shift time (hh:mm:ss) the total time the agent spent logged into
the system, for the reporting period
Idle time (hh:mm:ss) the total duration the agent was logged on
and available to receive calls
ACD calls handled the total number of ACD calls the agent
answered
ACD short handle call count the total number of ACD calls answered
where talk time is less than the Short
handle parameter
ACD true talk time (hh:mm:ss) the total duration of ACD calls, from agent
pick up to client hang up (excluding hold
time)
Average ACD true talk time (hh:mm:ss) the average duration of ACD calls, from
agent pick up to client hang up (excluding
hold time)
True ACD calls per hour the total ACD call count minus the ACD
short handle call count, divided by the
shift time for this agent
Average wrap up time (hh:mm:ss) the average duration the agent spent in
the wrap up state. Wrap up time does not
include any time spent making or taking
calls during the wrap up timer
Non ACD true talk time (hh:mm:ss) the total duration of non-ACD calls
(excluding hold time)
Note:
In Event reports, Outbound statistics
do not include unanswered calls
Note:
In Event reports, Outbound statistics
do not include unanswered calls
Average hold time (hh:mm:ss) the average hold time across all call types
(ACD, non ACD, and outbound calls)
(Total hold time / Total hold count)
Total hold count the total hold count across all call types
(ACD, non ACD, and outbound calls)
Total Make Busy time (hh:mm:ss) the total time spent in Make Busy,
controlled by the agent or the supervisor
Average Make Busy time (hh:mm:ss) the average time the agent spent in
Make Busy, controlled by the agent or the
supervisor
Total DND time (hh:mm:ss) the total duration the agent spent in Do
Not Disturb, controlled by the agent or the
supervisor
The Agent Group Event by Agent by Day of Week report displays log on and log off times
for each agent of the agent group, and the total duration that each agent spent in various
agent states over the days of the week. It reports the call statistics in hours, minutes, and
seconds and provides call counts for the agent. When this report is run for more than
one week, the data is summed for each day of the week. For example, if the report is run
for two weeks, the data found under Monday is the summed total of the two Mondays
and the data found under Tuesday is the summed totals of the two Tuesdays. (See the
following figure.)
Your choice of Shift Mode determines how this report calculates data. In Reporter, after
Shift Mode, select the checkbox for either Default or Agent Group Presence. 'Default'
ignores presence data. 'Agent Group Presence' subtracts agent absence from shift data.
Data relating to individual agent presence is not displayed under the corresponding
report columns.
The Agent Group Event by Agent by Day of Week report provides the following
information:
First login time the date and time at which the first agent
in the group logged into the system
Last logout time the time at which the last agent in the
group either last logged out of the system
or last performed an event (for example,
went into Make Busy)
Total shift time (hh:mm:ss) the total time the agent spent logged into
the system, for the reporting period
Idle time (hh:mm:ss) the total duration the agent was logged on
and available to receive calls
ACD calls handled the total number of ACD calls the agent
answered
ACD short handle call count the total number of ACD calls answered
where talk time is less than the Short
handle parameter
ACD true talk time (hh:mm:ss) the total duration of ACD calls, from agent
pick up to client hang up (excluding hold
time)
Average ACD true talk time (hh:mm:ss) the average duration of ACD calls, from
agent pick up to client hang up (excluding
hold time)
True ACD calls per hour the total ACD call count minus the ACD
short handle call count, divided by the
shift time for this agent
Average wrap up time (hh:mm:ss) the average duration the agent spent in
the wrap up state. Wrap up time does not
include any time spent making or taking
calls during the wrap up timer
Non ACD true talk time (hh:mm:ss) the total duration of non-ACD calls
(excluding hold time)
Note:
In Event reports, Outbound statistics
do not include unanswered calls
Note:
In Event reports, Outbound statistics
do not include unanswered calls
Average hold time (hh:mm:ss) the average hold time across all call types
(ACD, non ACD, and outbound calls)
(Total hold time / Total hold count)
Total hold count the total hold count across all call types
(ACD, non ACD, and outbound calls)
Total Make Busy time (hh:mm:ss) the total time spent in Make Busy,
controlled by the agent or the supervisor
Average Make Busy time (hh:mm:ss) the average time the agent spent in
Make Busy, controlled by the agent or the
supervisor
Total DND time (hh:mm:ss) the total duration the agent spent in Do
Not Disturb, controlled by the agent or the
supervisor
• Internal Out is a call that you made from the office to a destination within the office.
• External Out is a call that you made from the office to a destination outside the office.
• Internal Non ACD is a call that you received in the office from an origin within the
office.
• External Non ACD is a call that you received in the office from an origin outside the
office.
• Internal ACD is an ACD call that originated from inside the office to a destination
within the office.
• External ACD is an ACD call that originated from outside the office with a destination
within the office.
The Agent and Agent Group Internal/External Call Counts by the Day of Month reports
show internal and external call activity of an agent and agent group for the days of the
month. (See the following figure.)
Note:
Due to the limited SMDR Reorder Buffer required for real-time filing, some calls
may be reported incorrectly as Internal until overnight maintenance or a manual
summarization is run.
All agent internal/external call count reports have the following headings:
Total internal ACD calls the total number of ACD calls that you
received that originated inside the office
Total internal ACD handling time the total duration of ACD calls that
(hh:mm:ss) you received that originated in the
office (including hold time and transfer/
conference time)
Average internal ACD duration (hh:mm:ss) the average duration of ACD calls that you
received that originated in the office
Total external ACD calls the total number of ACD calls that
originated outside the office with a
destination within the office
Total external ACD handling time the total duration of ACD calls that
(hh:mm:ss) originated outside the office with a
destination within the office (including hold
time and transfer/conference time)
Average external ACD handling time the average duration of ACD calls that
(hh:mm:ss) originated outside the office with a
destination within the office
Non ACD calls handled the total number of non ACD calls
answered
Total internal non ACD calls the total number of non ACD calls that you
received that originated in the office
Total internal non ACD handling time the total duration of non ACD calls
(hh:mm:ss) that you received that originated in the
office (including hold time and transfer/
conference time)
Average internal non ACD duration the average duration of non ACD calls
(hh:mm:ss) that you received that originated in the
office
Total external non ACD calls the total number of non ACD calls that
originated outside the office with a
destination within the office
Total external non ACD handling time the total duration of non ACD calls
(hh:mm:ss) that originated outside the office with a
destination within the office (including hold
time and transfer/conference time)
Average external non ACD duration the average duration of non ACD calls
(hh:mm:ss) that originated outside the office with a
destination within the office
Total internal out calls the total number of calls that you made to
destinations within the office
Total internal out handling time the total duration of calls that you made
(hh:mm:ss) to destinations within the office (including
hold time and transfer/conference time)
Average internal out duration (hh:mm:ss) the average duration of calls that you
made to destinations within the office
Total external out calls the total number of calls that you made to
destinations outside the office
Total external out handling time the total duration of calls that you made to
(hh:mm:ss) destinations outside the office (including
hold time and transfer/conference time)
Average external out duration (hh:mm:ss) the average duration of calls that you
made to destinations outside the office
Figure 27: Voice Agent Group Internal/External Call Counts by Day of Month
• Internal Out is a call that you made from the office to a destination within the office.
• External Out is a call that you made from the office to a destination outside the office.
• Internal Non ACD is a call that you received in the office from an origin within the
office.
• External Non ACD is a call that you received in the office from an origin outside the
office.
• Internal ACD is an ACD call that originated from inside the office to a destination
within the office.
• External ACD is an ACD call that originated from outside the office with a destination
within the office.
The Agent and Agent Group Internal/External Call Counts by the Day of Week reports
show internal and external call activity of an agent and agent group over the days of
the week. When this report is run for more than one week, the data is summed for each
day of the week. For example, if the report is run for two weeks, the data found under
Monday is the summed total of the two Mondays and the data found under Tuesday is
the summed totals of the two Tuesdays. (See the following figure.)
Note:
Due to the limited SMDR Reorder Buffer required for real-time filing, some calls
may be reported incorrectly as Internal until overnight maintenance or a manual
summarization is run.
All agent internal/external call count reports have the following headings:
Total internal ACD calls the total number of ACD calls that you
received that originated inside the office
Total internal ACD handling time the total duration of ACD calls that
(hh:mm:ss) you received that originated in the
office (including hold time and transfer/
conference time)
Average internal ACD duration (hh:mm:ss) the average duration of ACD calls that you
received that originated in the office
Total external ACD calls the total number of ACD calls that
originated outside the office with a
destination within the office
Total external ACD handling time the total duration of ACD calls that
(hh:mm:ss) originated outside the office with a
destination within the office (including hold
time and transfer/conference time)
Average external ACD duration the average duration of ACD calls that
(hh:mm:ss) originated outside the office with a
destination within the office
Non ACD calls handled the total number of non ACD calls
answered
Total internal non ACD calls the total number of non ACD calls that you
received that originated in the office
Total internal non ACD handling time the total duration of non ACD calls
(hh:mm:ss) that you received that originated in the
office (including hold time and transfer/
conference time)
Average internal non ACD duration the average duration of non ACD calls
(hh:mm:ss) that you received that originated in the
office
Total external non ACD calls the total number of non ACD calls that
originated outside the office with a
destination within the office
Total external non ACD handling time the total duration of non ACD calls
(hh:mm:ss) that originated outside the office with a
destination within the office (including hold
time and transfer/conference time)
Average external non ACD duration the average duration of non ACD calls
(hh:mm:ss) that originated outside the office with a
destination within the office
Total internal out calls the total number of calls that you made to
destinations within the office
Total internal out handling time the total duration of calls that you made
(hh:mm:ss) to destinations within the office (including
hold time and transfer/conference time)
Average internal out duration (hh:mm:ss) the average duration of calls that you
made to destinations within the office
Total external out calls the total number of calls that you made to
destinations outside the office
Total external out handling time the total duration of calls that you made to
(hh:mm:ss) destinations outside the office (including
hold time and transfer/conference time)
Average external out duration (hh:mm:ss) the average duration of calls that you
made to destinations outside the office
Figure 28: Voice Agent Group Internal/External Call Counts by Day of Week
• Internal Out is a call that you made from the office to a destination within the office.
• External Out is a call that you made from the office to a destination outside the office.
• Internal Non ACD is a call that you received in the office from an origin within the
office.
• External Non ACD is a call that you received in the office from an origin outside the
office.
• Internal ACD is an ACD call that originated from inside the office to a destination
within the office.
• External ACD is an ACD call that originated from outside the office with a destination
within the office.
The Agent and Agent Group Internal/External Call Counts by Month reports show internal
and external call activity of an agent and agent group for the month. (See the following
figure.)
Note:
Due to the limited SMDR Reorder Buffer required for real-time filing, some calls
may be reported incorrectly as Internal until overnight maintenance or a manual
summarization is run.
All agent internal/external call count reports have the following headings:
Total internal ACD calls the total number of ACD calls that you
received that originated inside the office
Total internal ACD handling time the total duration of ACD calls that
(hh:mm:ss) you received that originated in the
office (including hold time and transfer/
conference time)
Average internal ACD duration (hh:mm:ss) the average duration of ACD calls that you
received that originated in the office
Total external ACD calls the total number of ACD calls that
originated outside the office with a
destination within the office
Total external ACD handling time the total duration of ACD calls that
(hh:mm:ss) originated outside the office with a
destination within the office (including hold
time and transfer/conference time)
Average external ACD handling time the average duration of ACD calls that
(hh:mm:ss) originated outside the office with a
destination within the office
Non ACD calls handled the total number of non ACD calls
answered
Total internal non ACD calls the total number of non ACD calls that you
received that originated in the office
Total internal non ACD handling time the total duration of non ACD calls
(hh:mm:ss) that you received that originated in the
office (including hold time and transfer/
conference time)
Average internal non ACD duration the average duration of non ACD calls
(hh:mm:ss) that you received that originated in the
office
Total external non ACD calls the total number of non ACD calls that
originated outside the office with a
destination within the office
Total external non ACD handling time the total duration of non ACD calls
(hh:mm:ss) that originated outside the office with a
destination within the office (including hold
time and transfer/conference time)
Average external non ACD duration the average duration of non ACD calls
(hh:mm:ss) that originated outside the office with a
destination within the office
Total internal out calls the total number of calls that you made to
destinations within the office
Total internal out handling time the total duration of calls that you made
(hh:mm:ss) to destinations within the office (including
hold time and transfer/conference time)
Average internal out duration (hh:mm:ss) the average duration of calls that you
made to destinations within the office
Total external out calls the total number of calls that you made to
destinations outside the office
Total external out handling time the total duration of calls that you made to
(hh:mm:ss) destinations outside the office (including
hold time and transfer/conference time)
Average external out duration (hh:mm:ss) the average duration of calls that you
made to destinations outside the office
• Internal Out is a call that you made from the office to a destination within the office.
• External Out is a call that you made from the office to a destination outside the office.
• Internal Non ACD is a call that you received in the office from an origin within the
office.
• External Non ACD is a call that you received in the office from an origin outside the
office.
• Internal ACD is an ACD call that originated from inside the office to a destination
within the office.
• External ACD is an ACD call that originated from outside the office with a destination
within the office.
The Agent and Agent Group Internal/External Call Counts by Period reports show
internal and external call activity of an agent and agent group across 15-, 30-, or 60-
minute intervals for the shift duration and day(s) you specify. (See the following figure.)
NOTE: Due to the limited SMDR Reorder Buffer required for real-time filing, some
calls may be reported incorrectly as Internal until overnight maintenance or a manual
summarization is run.
All agent internal/external call count reports have the following headings:
Total internal ACD calls the total number of ACD calls that you
received that originated inside the office
Total internal ACD handling time the total duration of ACD calls that
(hh:mm:ss) you received that originated in the
office (including hold time and transfer/
conference time)
Average internal ACD duration (hh:mm:ss) the average duration of ACD calls that you
received that originated in the office
Total external ACD calls the total number of ACD calls that
originated outside the office with a
destination within the office
Total external ACD handling time the total duration of ACD calls that
(hh:mm:ss) originated outside the office with a
destination within the office (including hold
time and transfer/conference time)
Average external ACD handling time the average duration of ACD calls that
(hh:mm:ss) originated outside the office with a
destination within the office
Non ACD calls handled the total number of non ACD calls
answered
Total internal non ACD calls the total number of non ACD calls that you
received that originated in the office
Total internal non ACD handling time the total duration of non ACD calls
(hh:mm:ss) that you received that originated in the
office (including hold time and transfer/
conference time)
Average internal non ACD duration the average duration of non ACD calls
(hh:mm:ss) that you received that originated in the
office
Total external non ACD calls the total number of non ACD calls that
originated outside the office with a
destination within the office
Total external non ACD handling time the total duration of non ACD calls
(hh:mm:ss) that originated outside the office with a
destination within the office (including hold
time and transfer/conference time)
Average external non ACD duration the average duration of non ACD calls
(hh:mm:ss) that originated outside the office with a
destination within the office
Total internal out calls the total number of calls that you made to
destinations within the office
Total internal out handling time the total duration of calls that you made
(hh:mm:ss) to destinations within the office (including
hold time and transfer/conference time)
Average internal out duration (hh:mm:ss) the average duration of calls that you
made to destinations within the office
Total external out calls the total number of calls that you made to
destinations outside the office
Total external out handling time the total duration of calls that you made to
(hh:mm:ss) destinations outside the office (including
hold time and transfer/conference time)
Average external out duration (hh:mm:ss) the average duration of calls that you
made to destinations outside the office
• Internal Out is a call that you made from the office to a destination within the office.
• External Out is a call that you made from the office to a destination outside the office.
• Internal Non ACD is a call that you received in the office from an origin within the
office.
• External Non ACD is a call that you received in the office from an origin outside the
office.
• Internal ACD is an ACD call that originated from inside the office to a destination
within the office.
• External ACD is an ACD call that originated from outside the office with a destination
within the office.
The Agent Group Internal/External Call Counts by Agent report shows internal and
external call activity of each agent in the agent group. (See the following figure.)
Note:
Due to the limited SMDR Reorder Buffer required for real-time filing, some calls
may be reported incorrectly as Internal until overnight maintenance or a manual
summarization is run.
All agent internal/external call count reports have the following headings:
Total internal ACD calls the total number of ACD calls that you
received that originated inside the office
Total internal ACD handling time the total duration of ACD calls that
(hh:mm:ss) you received that originated in the
office (including hold time and transfer/
conference time)
Average internal ACD duration (hh:mm:ss) the average duration of ACD calls that you
received that originated in the office
Total external ACD calls the total number of ACD calls that
originated outside the office with a
destination within the office
Total external ACD handling time the total duration of ACD calls that
(hh:mm:ss) originated outside the office with a
destination within the office (including hold
time and transfer/conference time)
Average external ACD duration the average duration of ACD calls that
(hh:mm:ss) originated outside the office with a
destination within the office
Non ACD calls handled the total number of non ACD calls
answered
Total internal non ACD calls the total number of non ACD calls that you
received that originated in the office
Total internal non ACD handling time the total duration of non ACD calls
(hh:mm:ss) that you received that originated in the
office (including hold time and transfer/
conference time)
Average internal non ACD duration the average duration of non ACD calls
(hh:mm:ss) that you received that originated in the
office
Total external non ACD calls the total number of non ACD calls that
originated outside the office with a
destination within the office
Total external non ACD handling time the total duration of non ACD calls
(hh:mm:ss) that originated outside the office with a
destination within the office (including hold
time and transfer/conference time)
Average external non ACD duration the average duration of non ACD calls
(hh:mm:ss) that originated outside the office with a
destination within the office
Total internal out calls the total number of calls that you made to
destinations within the office
Total internal out handling time the total duration of calls that you made
(hh:mm:ss) to destinations within the office (including
hold time and transfer/conference time)
Average internal out duration (hh:mm:ss) the average duration of calls that you
made to destinations within the office
Total external out calls the total number of calls that you made to
destinations outside the office
Total external out handling time the total duration of calls that you made to
(hh:mm:ss) destinations outside the office (including
hold time and transfer/conference time)
Average external out duration (hh:mm:ss) the average duration of calls that you
made to destinations outside the office
Note:
The only ACD stream-based report that will work with the over-midnight setting
enabled is the Agent Shift by Period report.
Your choice of Shift Mode determines how this report calculates data. In Reporter, after
Shift Mode, select the checkbox for either Default or Agent Group Presence. 'Default'
ignores presence data. 'Agent Group Presence' subtracts agent absence from shift data.
Data relating to individual agent presence is not displayed under the corresponding
report columns.
Total shift time (hh:mm:ss) the total time the agent spent logged into
the system, for the reporting period
Idle time (hh:mm:ss) the total duration the agent was logged on
and available to receive calls
Average ringing time (hh:mm:ss) the average duration calls rang on the
agent’s phone before the agent answered
the calls
ACD short handle call count the total number of ACD calls answered
where talk time is less than the Short
handle parameter
ACD true talk time (hh:mm:ss) the total duration of ACD calls, from agent
pick up to client hang up (excluding hold
time)
Average ACD true talk time (hh:mm:ss) the average duration of ACD calls, from
agent pick up to client hang up (excluding
hold time)
Wrap up time (hh:mm:ss) the duration the agent spent in the wrap
up state. Wrap up time does not include
any time spent making or taking calls
during the wrap up timer
Non ACD true talk time (hh:mm:ss) the total duration of non-ACD calls
(excluding hold time)
Note:
In Shift reports, Outbound statistics
do not include unanswered calls
Note:
In Shift reports, Outbound statistics
do not include unanswered calls
Total hold time (hh:mm:ss) the total hold duration across all call types
(ACD, non ACD, and outbound calls)
Total Make Busy time (hh:mm:ss) the total time spent in Make Busy,
controlled by the agent or the supervisor
Average Make Busy time (hh:mm:ss) the average time the agent spent in
Make Busy, controlled by the agent or the
supervisor
Total DND time (hh:mm:ss) the total duration the agent spent in Do
Not Disturb, controlled by the agent or the
supervisor
Average DND time (hh:mm:ss) the average duration the agent spent in
Do Not Disturb, controlled by the agent or
the supervisor
The Agent by Make Busy / DND Trace report provides the following information:
Note:
The Make Busy statistics differ between the Voice Agent by Make Busy / DND Trace
report and the Voice Agent Group by Agent by Make Busy / DND Code report. In the
Voice Agent by Make Busy / DND Trace report, the Make Busy statistics include the
total duration from the time the agent entered the Make Busy state to the time the
agent left the Make Busy state. In the Voice Agent Group by Agent by Make Busy /
DND Code report, the Make Busy statistics do not include the time spent in any
overriding state.
Note:
• Trace Reporting must be enabled on all media servers where participating devices
reside. This includes agents, base extensions, and queues.
• If the agent is using Classification Codes, these codes will not be displayed on the
Voice Agent Inbound Trace report.
Note:
• Trace Reporting must be enabled on all media servers where participating devices
reside. This includes agents, base extensions, and queues.
• If a call is originated as an outbound call on the media server, then it is categorized
as outbound, irrespective of its origination with the agent that has been reported.
• This report displays both external outbound calls and internal outbound calls to
numbers within a voice media server cluster. Statistics for internal calls to devices
on the same voice media server do not display. This includes calls to queues,
extensions, and other agents/agent groups.
• Classification Codes will not be displayed on the Voice Agent Outbound Trace
report.
Note:
If the agents of the group are using Classification Codes, these codes will not be
displayed on the Voice Agent Group Inbound Trace report.
The Agent Group Inbound Trace report provides the following information:
Note:
Note:
This report displays both external outbound calls and internal outbound calls to
numbers within a voice media server cluster. Statistics for internal calls to devices
on the same voice media server do not display. This includes calls to queues,
extensions, and other agents/agent groups.
The Agent Group Outbound Trace report provides the following information:
The Agent by Answering Agent Group report shows an agent’s workload distribution
across the agent groups for which the agent answered calls for the shift duration and
day(s) you specify. It reports the call statistics in hours, minutes, and seconds, and
provides call counts. (If you have agents who answer for multiple agent groups, do not
use the Agent Group by Agent Report: it assumes the agents belong to only one agent
group.) (See the following figure.)
The Agent by Answering Agent Group report provides the following information for
individual agents in the group.
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
The Answering Agent Group by Agent report compares the workload distribution across
the voice agents in an agent group for the shift duration and day(s) you specify. It reports
the statistics in hours, minutes, and seconds, and provides call counts across agents.
(If you have agents who answer for multiple agent groups, do not use the Agent Group
Answering by Agent Report: it assumes the agents belong to only one agent group.)
(See the following figure.)
The Answering Agent Group by Agent report provides the following information for
individual agents in the group:
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Voice Queue and Queue Group reports provide statistics on individual queues and queue
groups that reflect caller behavior and the service experienced by callers.
In report descriptions, the term ‘members’ refers to the individuals answering for the
queue. For ACD paths, ‘members’ refers to agents in the queue’s answering agent
groups. For Ring Groups, ‘members’ refers to the extensions assigned to the Ring
Groups.
Voice Queue reports apply to both ACD paths and Ring Group configurations. Within
reports, these devices are differentiated by their reporting numbers. The reporting
numbers of ACD paths always begin with ‘P’.
Statistics not applying to Ring Groups are indicated in each report description and
display as ‘0’ in your reports. In Queue reports applicable to ACD paths only, Ring
Groups do not display as reportable devices.
If you are running a voice report on a queue group that has non-voice members, the
statistical values in the generated report will be for voice queues only.
• Hot desking users logging into Ring Group member extensions must also be a
member of the Ring Group, to ensure accurate Ring Group reporting. For more
information on configuring Ring Groups, see the MiContact Center Business
Installation and Administration Guide.
• Ring Groups require a minimum of MiVoice Business 7.0. Customers running versions
of MiVoice Business lower than 7.0 using Ring Groups may have real-time and
reporting statistics populate based on their Ring Groups, but these statistics are not
supported and will be inaccurate due to changes in the data provided by MiVoice
Business.
• Performance reports
Note:
This report applies to ACD paths only. The report does not apply to Ring Group
data.
Note:
This report applies to ACD paths only. The report does not apply to Ring Group
data.
• By queue reports
Note:
This report applies to ACD paths only. The report does not apply to Ring Group
data.
• Internal/External reports
• ANI reports
• Trace reports
The Queue and Queue Group Performance by Account Code reports provide the
following information:
Note:
Note:
Note:
Note:
Members answering calls, taking transferred calls, or taking part in conference calls
from the queue will appear in this report even if the member is not associated to the
queue or the queue group on which you are reporting.
The Queue and Queue Group Performance by Member reports provides the following
information:
Total speed of answer (hh:mm:ss) the total delay before the call was
answered
Note:
Average speed of answer (hh:mm:ss) the average delay before calls were
answered (including time in queue and
member ringing time)
Note:
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
If your interflow statistic is zero, you probably did not program the telephone system with
an interflow value.
The Queue and Queue Group Performance by Day of Month reports provide the
following information:
Note:
the total duration of non-ACD calls
(including hold time and transfer/
conference time)
If your interflow statistic is zero, you probably did not program the telephone system with
an interflow value.
The Queue and Queue Group Performance by Day of Week reports provides the
following information:
Note:
not applicable to Ring Group
reporting. Statistics for Ring Groups
will display as '0'.
Note:
not applicable to Ring Group
reporting. Statistics for Ring Groups
will display as '0'.
Note:
not applicable to Ring Group
reporting. Statistics for Ring Groups
will display as '0'.
Note:
not applicable to Ring Group
reporting. Statistics for Ring Groups
will display as '0'.
Note:
not applicable to Ring Group
reporting. Statistics for Ring Groups
will display as '0'.
Average speed of answer (hh:mm:ss) the average delay before calls were
answered (including time in queue and
member ringing time)
Note:
for Ring Groups, this includes
time calls spent ringing on other
extensions in the Group (Terminal
Cascade, Circular, and Circular
Cascade ringing only)
Average delay to abandon (hh:mm:ss) the average elapsed time before the call
was abandoned
Average delay to interflow (hh:mm:ss) the average elapsed time before the call
was interflowed
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Dialed Number Identification Service (DNIS) is a feature of toll-free lines that identifies
the telephone number the caller dials. Each toll-free line is tagged with a DNIS number.
If your interflow statistic is zero, you probably did not program the telephone system with
an interflow value.
The Queue and Queue Group Performance by DNIS reports provide the following
information:
Note:
the total duration of non-ACD calls
(including hold time and transfer/
conference time)
Average speed of answer (hh:mm:ss) the average delay before calls were
answered (including time in queue and
member ringing time)
Note:
for Ring Groups, this includes
time calls spent ringing on other
extensions in the Group (Terminal
Cascade, Circular, and Circular
Cascade ringing only)
Maximum speed of answer (hh:mm:ss) the maximum delay before the call was
answered
Average delay to abandon (hh:mm:ss) the average elapsed time before the call
was abandoned
Maximum delay to abandon (hh:mm:ss) the maximum delay before the call was
abandoned
Average delay to interflow (hh:mm:ss) the average elapsed time before the call
was interflowed
Maximum delay to interflow (hh:mm:ss) the maximum delay before the call was
interflowed
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
If your interflow statistic is zero, you probably did not program the telephone system with
an interflow value.
The Queue and Queue Group Performance by Month reports provide the following
information:
Note:
Note:
Note:
Note:
Average speed of answer (hh:mm:ss) the average delay before calls were
answered (including time in queue and
member ringing time)
Note:
Average delay to abandon (hh:mm:ss) the average elapsed time before the call
was abandoned
Average delay to interflow (hh:mm:ss) the average elapsed time before the call
was interflowed
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
If your interflow statistic is zero, you probably did not program the telephone system with
an interflow value.
Note:
If you run the Queue Performance report against a Ring Group, you will see only
Answered by ACD group 1 column. If you run the Queue Performance report against
ACD, you will see Answered by ACD group 1, 2, 3, and 4 columns.
The Queue and Queue Group Performance by Period reports provide the following
information:
Note:
Note:
Note:
Note:
Note:
Average speed of answer (hh:mm:ss) the average delay before calls were
answered (including time in queue and
member ringing time)
Note:
Average delay to abandon (hh:mm:ss) the average elapsed time before the call
was abandoned
Average delay to interflow (hh:mm:ss) the average elapsed time before the call
was interflowed
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Note:
The Queue Group Performance by Queue report provides the following information:
Note:
Note:
Note:
Note:
Note:
Average speed of answer (hh:mm:ss) the average delay before calls were
answered (including time in queue and
member ringing time)
Note:
Average delay to abandon (hh:mm:ss) the average elapsed time before the call
was abandoned
Average delay to interflow (hh:mm:ss) the average elapsed time before the call
was interflowed
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
Note:
This report applies to ACD paths only. The report does not apply to Ring Group data.
The Queue Group Performance by Queue Group – Multi-select report provides the
following information:
Offered calls per day the number of calls offered to the queue
group for the day you specify
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Average ACD time to answer (hh:mm:ss) the average amount of time before ACD
calls were answered
Average external outbound calls handling the average call handling time for
time (hh:mm:ss) outbound external calls
External outbound calls handling time the total handling time for external
(hh:mm:ss) outbound calls
The report displays abandoned calls for the first day of the reporting period and indicates
whether these calls were reattempted and answered during the remainder of the
reporting period.
Note:
This report applies to ACD paths only. The report does not apply to Ring Group data.
The Queue Abandon vs. Answer Comparison report provides the following information:
Time of first abandon the date and time the call experience first
abandoned
Calls abandoned - Total abandoned calls the number of abandoned calls before a
call was answered, by call experience
Time to abandon - Average delay to the average time a call experience waited
abandon (hh:mm:ss) before abandoning calls
Time to abandon - First abandon to the total amount of time elapsed from the
answer duration first abandon to the answered call
Time of answer the date and time of the first answered call
after the first abandon
Calls answered - Agent name the agent name of the agent who
answered the call experience
Note:
Total calls abandoned on day one for call the total of the Calls Abandoned - On day
experiences 1 statistic for all callers
Total abandons for call experiences after the total of the Calls Abandoned - After
day one day 1 statistic for all callers
Total abandons for all call experiences the total of the Calls Abandoned - Total
Abandon Calls statistic for all callers
Average number of abandons per call the total number of abandoned calls
experience divided by the total number of callers
Abandon call experiences answered the number of callers who abandoned and
were finally answered
Abandon call experiences not answered the number of callers who abandoned and
were never answered
Longest duration between first abandon the greatest elapsed time from a caller’s
and answer first abandon to his answered call
Average duration between first abandon the average elapsed time from first
and answer abandon to an answered call
Same day, Day 1, Day 2, Day 3, Day 4, the number of call experiences that were
Day 5, After day 5 answered on the same day, day 1, day 2,
day 3, day 4, day 5, and after day 5 and
their respective percentages of the total
number of calls abandoned
Abandon call experiences not answered the number of call experiences not
answered and the percentage of the total
number of calls abandoned
Note:
• This report applies to ACD paths only. The report does not apply to Ring Group
data.
• Some statistics in this report will not align because the report uses both ACD and
SMDR data streams. For example, ‘Average speed of answer’ is derived from the
SMDR data streams while ‘Longest caller waiting’ is derived from the ACD data
stream. For the information on how the different streams, see "Understanding ACD
and SMDR report data".
The Queue Group by Queue with Agent Information report provides the following
information:
Calls answered by agents not configured the total number of calls answered by a
in the MiContact Center Business device where that device was not in the
YourSite database list of agents in the agent groups specified
in the database
Calls answered by direct agent the total number of calls answered by any
agent
Average handling time for direct agent the average duration of calls when only
(hh:mm:ss) one agent is involved/the call did not have
to be transferred to anyone else (including
hold time and transfer/conference time)
Hold count for direct agent the total number of holds for all calls when
only one agent is involved
Average hold time by direct agent the average hold duration of calls when
(hh:mm:ss) only one agent is involved
ACD calls trans/conf to another agent the number of ACD calls that were
transferred or conferenced to another
agent, where that agent is in the database
Average handling time for trans/conf to the average duration of calls that were
agent (hh:mm:ss) transferred or conferenced (including hold
time and transfer/conference time)
Hold count for trans/conf to agent the total number of holds for all calls that
were transferred or conferenced
Average hold time by trans/conf to agent the average hold duration of calls that
(hh:mm:ss) were transferred or conferenced
Average Make Busy time (hh:mm:ss) the average time the agent spent in
Make Busy, controlled by the agent or the
supervisor
Average Work Timer time (hh:mm:ss) the average duration the agent spent in
the Work Timer state
Average DND time (hh:mm:ss) the average duration the agent spent in
Do Not Disturb, controlled by the agent or
the supervisor
The Abandoned column contains the total number of both short and long abandoned
calls. If you need to view a report that clearly separates long and short abandoned calls,
see "Voice Queue and Queue Group Performance by Period".
Note:
‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been added to the
Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x converts
Spectrum by Day of Week reports into Spectrum by Period reports, with data
displaying by day of week intervals.
The following are the first three fields of the Voice Queue and Queue Group Abandon
Spectrum by Period reports:
Maximum delay to abandon (hh:mm:ss) the maximum delay before the call was
abandoned
Note:
The remaining fields of the Voice Queue and Queue Group Abandon Spectrum by Period
reports provide a frequency distribution of call patterns based on a defined time scale.
(5, 10, 15, 20, 30, 40, 60, 80, 120, and < 120 seconds). For each time period, the Count
< x sec field reflects the total number of calls for that interval and all preceding intervals.
The % of Calls abandoned field reflects the percentage of calls for that interval and all
preceding intervals.
Note:
• For each time period, except > 120 seconds, the Count < x sec field reflects the
total number of calls for that interval and all preceding intervals.
• For the >120 seconds time period, the Count < x sec field reflects the total number
of calls for that interval only.
• The % of field reflects the percentage of calls for that interval and all preceding
intervals.
Note:
The Abandoned column contains the total number of both short and long abandoned
calls. If you need to view a report that clearly separates long and short abandoned
calls, see "Voice Queue and Queue Group Performance by Period".
The Queue Group Abandon Spectrum by Queue report provides a frequency distribution
of call handling on a queue group across intervals from 1-10. (See the following figure.)
The following are the first three fields of the Queue Group Abandon Spectrum by Queue
report:
Maximum delay to abandon (hh:mm:ss) the maximum delay before the call was
abandoned
Note:
The remaining fields of the Queue Group Spectrum by Queue report provide a frequency
distribution of call patterns based on a defined time scale (Spectral Interval 1-10). The
Spectrum Interval field reflects the total number of calls for that interval and all preceding
intervals. The % of calls abandoned field reflects the percentage of calls for that interval
and all preceding intervals.
Note:
Spectrum Interval 10 reflects the total number of calls for that interval only.
Note:
‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been added to the
Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x converts
Spectrum by Day of Week reports into Spectrum by Period reports, with data
displaying by day of week intervals.
The following are the first three fields of the Queue and Queue Group Answer Spectrum
by Period reports:
Maximum time to open (hh:mm:ss) the maximum delay before the call was
answered
Note:
The remaining fields of the Voice Queue and Queue Group Answer Spectrum by Period
reports provide a frequency distribution of call patterns based on a defined time scale.
For each time period, the Count < x sec field reflects the total number of calls for that
interval and all preceding intervals. The % of Calls answered field reflects the percentage
of calls for that interval and all preceding intervals.
Note:
• For each time period, except > 120 seconds, the Count < x sec field reflects the
total number of calls for that interval and all preceding intervals.
• For the >120 seconds time period, the Count < x sec field reflects the total number
of calls for that interval only.
• The % of field reflects the percentage of calls for that interval and all preceding
intervals.
The following are the first four fields of the Queue Group Answer Spectrum by Queue
report:
Maximum time to open (hh:mm:ss) the maximum delay before the call was
answered
Note:
The remaining fields of the Queue and Queue Group Spectrum by Queue reports provide
a frequency distribution of call patterns based on a defined time scale (Spectral Interval
1-10). The Spectrum Interval field reflects the total number of calls for that interval and all
preceding intervals. The % of calls answered field reflects the percentage of calls for that
interval and all preceding intervals.
Note:
Spectrum Interval 10 reflects the total number of calls for that interval only.
Note:
‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been added to the
Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x converts
Spectrum by Day of Week reports into Spectrum by Period reports, with data
displaying by day of week intervals.
The following are the first three fields of the Queue and Queue Group Handle Spectrum
by Period reports:
Maximum duration (hh:mm:ss) the duration of the longest call for the
period
Note:
The remaining fields of the Voice Queue and Queue Group Handle Spectrum by Period
reports provide a frequency distribution of call patterns based on a defined time scale
(<10, <60, <180, <240, <300, <360, <420, <480, <540, and >541 seconds). For each
time period, the Count < x sec field reflects the total number of calls for that interval and
all preceding intervals. The % of calls handled field reflects the percentage of calls for
that interval and all preceding intervals.
Note:
• For each time period, except > 541 seconds, the Count < x sec field reflects the
total number of calls for that interval and all preceding intervals.
• For the >541 seconds time period, the Count < x sec field reflects the total number
of calls for that interval only.
• The % of field reflects the percentage of calls for that interval and all preceding
intervals.
The following are the first four fields of the Queue Group Handle Spectrum by Queue
report:
Maximum duration (hh:mm:ss) the duration of the longest call for the
period
Note:
The remaining fields of the Queue and Queue Group Spectrum by Queue reports provide
a frequency distribution of call patterns based on a defined time scale (Spectral Interval
1-10). The Spectrum Interval field reflects the total number of calls for that interval and all
preceding intervals. The % of calls answered field reflects the percentage of calls for that
interval and all preceding intervals.
Note:
Spectrum Interval 10 reflects the total number of calls for that interval only.
If your interflow statistic is zero, you probably did not program the telephone system with
an interflow value.
Note:
‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been added to the
Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x converts
Spectrum by Day of Week reports into Spectrum by Period reports, with data
displaying by day of week intervals.
The following are the first three fields of the Queue and Queue Group Interflow Spectrum
by Period reports:
Maximum delay to interflow (hh:mm:ss) the maximum delay before the call was
interflowed
Note:
The remaining fields of the Voice Queue and Queue Group Interflow Spectrum by Period
reports provide a frequency distribution of call patterns based on a defined time scale (5,
10, 15, 20, 30, 40, 60, 80, 120, and >120 seconds). For each time period, the Count <
x sec field reflects the total number of calls for that interval and all preceding intervals.
The % of Calls interflowed field reflects the percentage of calls for that interval and all
preceding intervals.
Note:
• For each time period, except > 120 seconds, the Count < x sec field reflects the
total number of calls for that interval and all preceding intervals.
• For the >120 seconds time period, the Count < x sec field reflects the total number
of calls for that interval only.
• The % of field reflects the percentage of calls for that interval and all preceding
intervals.
If your interflow statistic is zero, you probably did not program the telephone system with
an interflow value.
The following are the first four fields of the Queue Group Interflow Spectrum by Queue
report:
Maximum delay to interflow (hh:mm:ss) the maximum delay before the call was
interflowed
Note:
The remaining fields of the Queue Group Spectrum by Queue reports provide a
frequency distribution of call patterns based on a defined time scale (Spectral Interval
1-10). The Spectrum Interval field reflects the total number of calls for that interval and
all preceding intervals. The % of calls interflowed field reflects the percentage of calls for
that interval and all preceding intervals.
Note:
Spectrum Interval 10 reflects the total number of calls for that interval only.
Note:
• This report applies to ACD paths only. The report does not apply to Ring Group
data.
• ‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been added to the
Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x converts
Spectrum by Day of Week reports into Spectrum by Period reports, with data
displaying by day of week intervals.
The following are the first five fields of the Queue Group Ring Time Spectrum by Period
report. The first three of these fields are also contained in the Queue Ringing Spectrum
by Period report.
Note:
The remaining fields of the Voice Queue Ringing Spectrum by Period and Queue Group
Ring Time Spectrum by Period reports provide a frequency distribution of call patterns
based on a defined time scale (5, 10, 15, 20, 30, 40, 60, 80, 120, and >120 seconds). For
each time period, the Count < x sec field reflects the total number of calls for that interval
and all preceding intervals. The % of Calls received field reflects the percentage of calls
for that interval and all preceding intervals.
Note:
• For each time period, except > 120 seconds, the Count < x sec field reflects the
total number of calls for that interval and all preceding intervals.
• For the >120 seconds time period, the Count < x sec field reflects the total number
of calls for that interval only.
• The % of field reflects the percentage of calls for that interval and all preceding
intervals.
If your ring time statistic is zero, you probably did not program the telephone system with
a ring time value.
The following are the first six fields of the Queue Group Ring Time Spectrum by Queue
report:
Note:
The remaining fields of the Queue Group Spectrum by Queue reports provide a
frequency distribution of call patterns based on a defined time scale (Spectral Interval
1-10). The Spectrum Interval field reflects the total number of calls for that interval and all
preceding intervals. The % of calls received field reflects the percentage of calls for that
interval and all preceding intervals.
Note:
Spectrum Interval 10 reflects the total number of calls for that interval only.
Note:
Due to the limited SMDR Reorder Buffer required for real-time filing, some calls
may be reported incorrectly as Internal until overnight maintenance or a manual
summarization is run.
If your interflow statistic is zero, you probably did not program the telephone system with
an interflow value.
• Internal ACD is an ACD call that originated from inside the office to a destination
within the office.
• External ACD is an ACD call that originated from outside the office with a destination
within the office.
The Queue and Queue Group Internal/External Call Counts by Period reports provide the
following information:
Note:
not applicable to Ring Group
reporting. Statistics for Ring Groups
will display as ‘0’.
Internal call duration (hh:mm:ss) the total duration of ACD calls that
you received that originated in the
office (including hold time and transfer/
conference time)
Total external ACD handling time the total duration of ACD calls that
(hh:mm:ss) originated outside the office with a
destination within the office (including hold
time and transfer/conference time)
Average internal duration (hh:mm:ss) the average duration of calls that you
received that originated in the office
Average speed of answer (hh:mm:ss) the average delay before calls were
answered (including time in queue and
member ringing time)
Note:
for Ring Groups, this includes
time calls spent ringing on other
extensions in the Group (Terminal
Cascade, Circular, and Circular
Cascade ringing only)
Average delay to abandon (hh:mm:ss) the average elapsed time before the call
was abandoned
Average delay to interflow (hh:mm:ss) the average elapsed time before the call
was interflowed
If your interflow statistic is zero, you probably did not program the telephone system with
an interflow value.
The Queue and Queue Group ANI by Area Code report provides the following
information:
ACD calls offered the number of ACD calls reported for the
area code
Note:
Note:
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Average speed of answer (hh:mm:ss) the average delay before calls were
answered (including time in queue and
member ringing time)
Note:
Average delay to abandon (hh:mm:ss) the average elapsed time before the call
was abandoned
Average delay to interflow (hh:mm:ss) the average elapsed time before the call
was interflowed
The Voice Queue and Queue Group Unavailable Trace reports provide the following
information.
Date time the date and start time of the call record
Calling line number the number from which the caller dialed
You can only report on licensed extensions. The number of extensions you license in
YourSite Explorer must be consistent with your software license.
Note:
• Performance reports
The Extension and Extension Group Performance by Account Code reports provide the
following information:
Note:
Note:
Note:
The Extension and Extension Group Performance by Day of Month reports provide the
following information:
Note:
Note:
Calls transferred from extension the total number of calls transferred from
the extension
Average speed of answer (hh:mm:ss) the average duration before ACD calls
were answered
Note:
Average time to answer non ACD call the average delay before the Non ACD
(hh:mm:ss) call was answered
Average delay to abandon (hh:mm:ss) the average elapsed time before the call
was abandoned
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
The Extension and Extension Group Performance by Day of Week reports provide the
following information:
Note:
Note:
Calls transferred from extension the total number of calls transferred from
the extension
Average speed of answer (hh:mm:ss) the average duration before ACD calls
were answered
Note:
Average time to answer non ACD call the average delay before the Non ACD
(hh:mm:ss) call was answered
Average delay to abandon (hh:mm:ss) the average elapsed time before the call
was abandoned
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
The Extension and Extension Group Performance by Month reports provide the following
information:
Note:
Note:
Calls transferred from extension the total number of calls transferred from
the extension
Average speed of answer (hh:mm:ss) the average duration before ACD calls
were answered
Note:
Average time to answer non ACD call the average delay before the Non ACD
(hh:mm:ss) call was answered
Average delay to abandon (hh:mm:ss) the average elapsed time before the call
was abandoned
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
The Extension and Extension Group Performance by Period reports provide the following
information:
Note:
Note:
Calls transferred from extension the total number of calls transferred from
the extension
Average speed of answer (hh:mm:ss) the average duration before ACD calls
were answered
Note:
Average time to answer non ACD call the average delay before the Non ACD
(hh:mm:ss) call was answered
Average delay to abandon (hh:mm:ss) the average elapsed time before the call
was abandoned
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
Note:
Note:
Calls transferred from extension the total number of calls transferred from
the extension
Average speed of answer (hh:mm:ss) the average duration before ACD calls
were answered
Note:
Average time to answer non ACD call the average delay before the Non ACD
(hh:mm:ss) call was answered
Average delay to abandon (hh:mm:ss) the average elapsed time before the call
was abandoned
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
Voice Trunk reports on individual trunks and trunk groups provide an indication of how
busy your trunks are.
• Performance reports
The Trunk and Trunk Group Performance by Period reports provide the following
information:
Average speed of answer (hh:mm:ss) the average delay before calls were
answered (including time in queue and
ringing time)
Average delay to abandon (hh:mm:ss) the average elapsed time before calls
were abandoned
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
The Trunk and Trunk Group Performance by Day of Week reports provide the following
information:
Average speed of answer (hh:mm:ss) the average delay before calls were
answered (including time in queue and
ringing time)
Average delay to abandon (hh:mm:ss) the average elapsed time before calls
were abandoned
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
The Trunk Group Performance by Trunk report provides the following information:
Average speed of answer (hh:mm:ss) the average delay before calls were
answered (including time in queue and
ringing time)
Average delay to abandon (hh:mm:ss) the average elapsed time before calls
were abandoned
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
The Trunk Group Busy Minute reports provide the following information:
Employee and Employee Group reports provide statistics based on employee and
employee group activity. Each voice employee report shows the call activity across all of
the employee’s agent IDs.
Note:
• Performance reports
• Employee Event by Period (hh:mm:ss) (You cannot generate this report over
midnight.)
• Internal/External Call Count reports
Note:
Make Busy and Do Not Disturb operate at the employee level. For example, when an
employee puts one of their agents into Make Busy, all of the employee’s agents go
into Make Busy. Employee reports therefore reflect the accumulated Make Busy and
Do Not Disturb statistics for all of the employee’s agents.
Shift duration the total time the agent spent logged into
the system, for the reporting period
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
Outbound handling time (hh:mm:ss) the total duration of calls that you made to
destinations outside the office (including
hold time and transfer/conference time)
Average outbound handling time the average duration of calls that you
(hh:mm:ss) made to destinations outside the office
(including hold time and transfer/
conference time)
Total Make Busy time (hh:mm:ss) the total time spent in Make Busy,
controlled by the agent or the supervisor
The Employee and Employee Group Performance reports provide the following
information:
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when the calls are
answered to when they are disconnected (including h
old time and transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from when the calls
are answered to when they are disconnected (including
hold time and transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls (including hold time
and transfer/conference time)
Average non ACD handling time (hh:mm:ss) the average duration of non-ACD calls (including hold ti
me and transfer/conference time)
Outbound handling time (hh:mm:ss) the total duration of outbound calls (including hold time
and transfer/conference time)
Average outbound handling time (hh:mm:ss) the average duration of outbound calls
Totals the total of each of the columns
The Employee and Employee Group Performance reports provide the following
information:
Calls abandoned the number of calls abandoned while ringing the empl
oyee; abandoned ACD calls are not included in this total
Calls outbound the total number of outbound calls
Calls requeued the total number or requeues at the employee's position
- if an employee fails to answer a call, the system places
the call back in the same queue
Calls transferred to agent the number of calls transferred to the agent's position
Calls transferred from agent the number of calls transferred from the agent's position
Conference calls the total number of conference calls involving the agent
Account Code the number of Account Codes entered
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when the calls are
answered to when they are disconnected (including h
old time and transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from when the calls
are answered to when they are disconnected (including
hold time and transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls (including hold time
and transfer/conference time)
Average non ACD handling time (hh:mm:ss) the average duration of non-ACD calls (including hold ti
me and transfer/conference time)
Outbound handling time (hh:mm:ss) the total duration of outbound calls (including hold time
and transfer/conference time)
Average outbound handling time (hh:mm:ss) the average duration of outbound calls
Totals the total of each of the columns
The Employee Performance by Extension report provides the following employment and
performance information:
Note:
Note:
Calls transferred from extension the total number of calls transferred from the agent's p
osition
Conference calls the total number of conference calls involving the agent
Inbound Account Code count the total number of inbound account codes entered du
ring inbound calls
Outbound Account Code count the total number of outbound account codes entered d
uring outbound calls
Note:
Average delay to abandon (hh:mm:ss) the average elapsed time before the call was abandon
ed
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when the calls are
answered to when they are disconnected (including h
old time and transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from when the calls
are answered to when they are disconnected (including
hold time and transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls (including hold time
and transfer/conference time)
Average non ACD handling time (hh:mm:ss) the average duration of non-ACD calls (including hold ti
me and transfer/conference time)
Outbound handling time (hh:mm:ss) the total duration of outbound calls (including hold time
and transfer/conference time)
Average outbound handling time (hh:mm:ss) the average duration of outbound calls
Totals the total of each of the columns
Note:
• Make Busy and Do Not Disturb operate at the employee level. For example, when
an employee puts one of their agents into Make Busy, all of the employee’s agents
go into Make Busy. Employee reports therefore reflect the accumulated Make
Busy and Do Not Disturb statistics for all of the employee’s agents.
• Make Busy statistics do not apply to an employee's extensions.
The Employee and Employee Group Performance by Make Busy / DND Code report s
provide s the following information:
The Employee and Employee Group Performance reports provide the following
information:
Calls abandoned the number of calls abandoned while ringing the empl
oyee; abandoned ACD calls are not included in this total
Calls outbound the total number of outbound calls
Calls requeued the total number or requeues at the employee's position
- if an employee fails to answer a call, the system places
the call back in the same queue
Calls transferred to agent the number of calls transferred to the agent's position
Calls transferred from agent the number of calls transferred from the agent's position
Conference calls the total number of conference calls involving the agent
Account Code the number of Account Codes entered
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when the calls are
answered to when they are disconnected (including h
old time and transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from when the calls
are answered to when they are disconnected (including
hold time and transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls (including hold time
and transfer/conference time)
Average non ACD handling time (hh:mm:ss) the average duration of non-ACD calls (including hold ti
me and transfer/conference time)
Outbound handling time (hh:mm:ss) the total duration of outbound calls (including hold time
and transfer/conference time)
Average outbound handling time (hh:mm:ss) the average duration of outbound calls
Totals the total of each of the columns
The Employee and Employee Group Performance reports provide the following
information:
Calls transferred from agent the number of calls transferred from the
agent's position
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
Average manned agents (group reports the average number of voice agents
only) scheduled for the shift
The Employee Group Performance by Queue report shows ACD call statistics on
the queues for which the employees in the employee group answered calls, and the
summary total of statistics for non ACD calls involving the employee (in the employee
group) for the shift duration and day(s) you specify. (See the following figure.)
The Employee and Employee Group Performance by Queue reports provides the
following information:
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Calls transferred from agent the number of calls transferred from the
agent's position
Note:
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
Note:
• Make Busy and Do Not Disturb operate at the employee level. For example, when
an employee puts one of their agents into Make Busy, all of the employee’s agents
go into Make Busy. Employee reports therefore reflect the accumulated Make
Busy and Do Not Disturb statistics for all of the employee’s agents.
• Make Busy statistics do not apply to an employee's extensions.
Shift duration the total time the agent spent logged into
the system, for the reporting period
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
Outbound handling time (hh:mm:ss) the total duration of calls that you made to
destinations outside the office (including
hold time and transfer/conference time)
Outbound handling time (hh:mm:ss) the average duration of calls that you
made to destinations outside the office
(including hold time and transfer/
conference time)
Total Make Busy time (hh:mm:ss) the total time spent in Make Busy,
controlled by the agent or the supervisor
Total DND time (hh:mm:ss) the total duration the agent spent in Do
Not Disturb, controlled by the agent or the
supervisor
Your choice of Shift Mode determines how this report calculates data. In Reporter, after
Shift Mode, select the checkbox for either Default or Agent Group Presence. 'Default'
ignores presence data. 'Agent Group Presence' subtracts agent absence from shift data.
Data relating to individual agent presence is not displayed under the corresponding
report columns.
Note:
Make Busy and Do Not Disturb operate at the employee level. For example, when an
employee puts one of their agents into Make Busy, all of the employee’s agents go
into Make Busy. Employee reports therefore reflect the accumulated Make Busy and
Do Not Disturb statistics for all of the employee’s agents.
The Employee Event by Period (hh:mm:ss) report is truncated to the first 1000 records. It
provides the following information:
First login date/time the date and time at which the agent
logged into the system
Last logout date/time the date and time at which the agent
either last logged out of the system or last
Total shift time (hh:mm:ss) the total time the agent spent logged into
the system, for the reporting period
Idle time (hh:mm:ss) the total duration the agent was logged on
and available to receive calls
ACD calls handled the total number of ACD calls the agent
answered
ACD short handle call count the total number of ACD calls answered
where talk time is less than the Short
handle parameter
ACD true talk time (hh:mm:ss) the total duration of ACD calls, from agent
pick up to client hang up (excluding hold
time)
ACD hold time (hh:mm:ss) the time for which ACD interactions were
put on hold
Average ACD true talk time (hh:mm:ss) the average duration of ACD calls, from
agent pick up to client hang up (excluding
hold time)
True ACD calls per hour the total ACD call count minus the ACD
short handle call count, divided by the
shift time for this agent
Wrap up time (hh:mm:ss) the duration the agent spent in the wrap
up state. Wrap up time does not include
Average wrap up time (hh:mm:ss) the average duration the agent spent in
the wrap up state. Wrap up time does not
include any time spent making or taking
calls during the wrap up timer
Non ACD hold time (hh:mm:ss) the time for which non-ACD interactions
were put on hold
Note:
Outbound hold time (hh:mm:ss) the time for which outbound interactions
were put on hold
Note:
Total hold time (hh:mm:ss) the total duration ACD calls spent on hold
Average hold time (hh:mm:ss) the average duration ACD calls spent on
hold
Total hold count the total hold count for ACD calls
Total Make Busy time (hh:mm:ss) the total time spent in Make Busy,
controlled by the agent or the supervisor
Average Make Busy time (hh:mm:ss) the average time the agent spent in
Make Busy, controlled by the agent or the
supervisor
Total DND time (hh:mm:ss) the total duration the agent spent in Do
Not Disturb, controlled by the agent or the
supervisor
Average DND time (hh:mm:ss) the average duration the agent spent in
Do Not Disturb, controlled by the agent or
the supervisor
• Internal Out is a call that you made from the office to a destination within the office.
• External Out is a call that you made from the office to a destination outside the office.
• Internal Non ACD is a call that you received in the office from an origin within the
office.
• External Non ACD is a call that you received in the office from an origin outside the
office.
• Internal ACD is an ACD call that originated from inside the office to a destination
within the office.
• External ACD is an ACD call that originated from outside the office with a destination
within the office.
The Employee Group Internal/External Call Counts by Agent report shows internal and
external call activity of each agent in the employee group.
Note:
Due to the limited SMDR Reorder Buffer required for real-time filing, some calls
may be reported incorrectly as Internal until overnight maintenance or a manual
summarization is run.
All employee internal/external call count reports have the following headings:
Total internal out handling time (hh:mm:ss) the total duration of calls that you made to destinations
within the office (including hold time and transfer/confer
ence time)
Average internal out duration (hh:mm:ss) the average duration of calls that you made to destinati
ons within the office
Total external out calls the total number of calls that you made to destinations
outside the office
Total external out handling time (hh:mm:ss) the total duration of calls that you made to destinations
outside the office (including hold time and transfer/confe
rence time)
Average external out duration (hh:mm:ss) the average duration of calls that you made to destinati
ons outside the office
Totals the total of each of the columns
• Internal Out is a call that you made from the office to a destination within the office.
• External Out is a call that you made from the office to a destination outside the office.
• Internal Non ACD is a call that you received in the office from an origin within the
office.
• External Non ACD is a call that you received in the office from an origin outside the
office.
• Internal ACD is an ACD call that originated from inside the office to a destination
within the office.
• External ACD is an ACD call that originated from outside the office with a destination
within the office.
The Employee and Employee Group Internal/External Call Counts by the Day of Month
reports show internal and external call activity of an employee and employee group for
the days of the month.
Note:
Due to the limited SMDR Reorder Buffer required for real-time filing, some calls
may be reported incorrectly as Internal until overnight maintenance or a manual
summarization is run.
All employee internal/external call count reports have the following headings:
Total internal out handling time (hh:mm:ss) the total duration of calls that you made to destinations
within the office (including hold time and transfer/confer
ence time)
Average internal out duration (hh:mm:ss) the average duration of calls that you made to destinati
ons within the office
Total external out calls the total number of calls that you made to destinations
outside the office
Total external out handling time (hh:mm:ss) the total duration of calls that you made to destinations
outside the office (including hold time and transfer/confe
rence time)
Average external out duration (hh:mm:ss) the average duration of calls that you made to destinati
ons outside the office
Totals the total of each of the columns
• Internal Out is a call that you made from the office to a destination within the office.
• External Out is a call that you made from the office to a destination outside the office.
• Internal Non ACD is a call that you received in the office from an origin within the
office.
• External Non ACD is a call that you received in the office from an origin outside the
office.
• Internal ACD is an ACD call that originated from inside the office to a destination
within the office.
• External ACD is an ACD call that originated from outside the office with a destination
within the office.
The Employee and Employee Group Internal/External Call Counts by the Day of Week
reports show internal and external call activity of an employee and employee group
over the days of the week. When this report is run for more than one week, the data is
summed for each day of the week. For example, if the report is run for two weeks, the
data found under Monday is the summed total of the two Mondays and the data found
under Tuesday is the summed totals of the two Tuesdays.
Note:
Due to the limited SMDR Reorder Buffer required for real-time filing, some calls
may be reported incorrectly as Internal until overnight maintenance or a manual
summarization is run.
All employee internal/external call counts reports have the following headings:
• Internal Out is a call that you made from the office to a destination within the office.
• External Out is a call that you made from the office to a destination outside the office.
• Internal Non ACD is a call that you received in the office from an origin within the
office.
• External Non ACD is a call that you received in the office from an origin outside the
office.
• Internal ACD is an ACD call that originated from inside the office to a destination
within the office.
• External ACD is an ACD call that originated from outside the office with a destination
within the office.
The Employee Group Internal/External Call Counts by Employee report shows the
internal and external call activity of each employee.
Note:
Due to the limited SMDR Reorder Buffer required for real-time filing, some calls
may be reported incorrectly as Internal until overnight maintenance or a manual
summarization is run.
All employee group internal/external call count reports have the following headings:
Total internal out handling time (hh:mm:ss) the total duration of calls that you made to destinations
within the office (including hold time and transfer/confer
ence time)
Average internal out duration (hh:mm:ss) the average duration of calls that you made to destinati
ons within the office
Total external out calls the total number of calls that you made to destinations
outside the office
Total external out handling time (hh:mm:ss) the total duration of calls that you made to destinations
outside the office (including hold time and transfer/confe
rence time)
Average external out duration (hh:mm:ss) the average duration of calls that you made to destinati
ons outside the office
Totals the total of each of the columns
• Internal Out is a call that you made from the office to a destination within the office.
• External Out is a call that you made from the office to a destination outside the office.
• Internal Non ACD is a call that you received in the office from an origin within the
office.
• External Non ACD is a call that you received in the office from an origin outside the
office.
• Internal ACD is an ACD call that originated from inside the office to a destination
within the office.
• External ACD is an ACD call that originated from outside the office with a destination
within the office.
The Employee and Employee Group Internal/External Call Counts by Month reports
show internal and external call activity of an employee and employee group for the
month.
Note:
Due to the limited SMDR Reorder Buffer required for real-time filing, some calls
may be reported incorrectly as Internal until overnight maintenance or a manual
summarization is run.
All employee internal/external call count reports have the following headings:
Total internal out handling time (hh:mm:ss) the total duration of calls that you made to destinations
within the office (including hold time and transfer/confer
ence time)
Average internal out duration (hh:mm:ss) the average duration of calls that you made to destinati
ons within the office
Total external out calls the total number of calls that you made to destinations
outside the office
Total external out handling time (hh:mm:ss) the total duration of calls that you made to destinations
outside the office (including hold time and transfer/confe
rence time)
Average external out duration (hh:mm:ss) the average duration of calls that you made to destinati
ons outside the office
Total the total of each of the columns
• Internal Out is a call that you made from the office to a destination within the office.
• External Out is a call that you made from the office to a destination outside the office.
• Internal Non ACD is a call that you received in the office from an origin within the
office.
• External Non ACD is a call that you received in the office from an origin outside the
office.
• Internal ACD is an ACD call that originated from inside the office to a destination
within the office.
• External ACD is an ACD call that originated from outside the office with a destination
within the office.
The Employee and Employee Group Internal/External Call Counts by Period reports
show internal and external call activity of an employee and employee group across 15-,
30-, or 60-minute intervals for the shift duration and day(s) you specify.
Note:
Due to the limited SMDR Reorder Buffer required for real-time filing, some calls
may be reported incorrectly as Internal until overnight maintenance or a manual
summarization is run.
All employee internal/external call count reports have the following headings:
Total internal out handling time (hh:mm:ss) the total duration of calls that you made to destinations
within the office (including hold time and transfer/confer
ence time)
Average internal out duration (hh:mm:ss) the average duration of calls that you made to destinati
ons within the office
Total external out calls the total number of calls that you made to destinations
outside the office
Total external out handling time (hh:mm:ss) the total duration of calls that you made to destinations
outside the office (including hold time and transfer/confe
rence time)
Average external out duration (hh:mm:ss) the average duration of calls that you made to destinati
ons outside the office
Totals the total of each of the columns
Teams are collections of agent groups. A team report provides statistics on individual
agents across multiple agent groups in one report. Team reports provide an indication of
how individual agents spent their time and compare the performance of agents.
• Performance reports
• Event reports:
Event reports derive their data from the ACD real-time event stream. Event reports on
non-ACD extensions use the MiTAI stream. All other reports derive their data from the
SMDR stream.
• Team Event by Period (Percentages) (You cannot generate this report over
midnight.)
The Team Performance by Agent reports provide the following information on individual
agents:
Average outbound handling time (hh:mm:ss) the average duration of calls that you made to destinati
ons outside the office (including hold time and transfer/
conference time)
Percent of shift the percentage of shift time representing outbound call
activity
Total Make Busy time (hh:mm:ss) the total time spent in Make Busy, controlled by the age
nt or the supervisor
Percent of shift the total duration the agent spent in the Make Busy stat
e, controlled by the agent or the supervisor
Total DND time (hh:mm:ss) the total duration the agent spent in Do Not Disturb, co
ntrolled by the agent or the supervisor
Percent of shift the percentage of shift time representing voice Do Not D
isturb activity
Totals the total of each of the columns
The Team Performance by Day of Week reports provide the following information:
The Team Performance by Day of Month reports provide the following information:
The first five fields contain multiple records reflecting the ACD queues serving the ACD
Agent and Agent Group. The remaining fields contain a single record reflecting the totals
irrespective of ACD queue. (See the following figure.)
Your choice of Shift Mode determines how this report calculates data. In Reporter, after
Shift Mode, select the checkbox for either Default or Agent Group Presence. 'Default'
ignores presence data. 'Agent Group Presence' subtracts agent absence from shift data.
Data relating to individual agent presence is not displayed under the corresponding
report columns.
The Team Event by Period (Percentages) reports provide the following information:
Note:
Note:
Wrap up percentage the % of time the agent spent in the wrap up state
Make Busy percentage the % of time the agent spent in the voice Make Busy
state
DND percentage the % of time the agent spent in the voice Do Not Distur
b state
Totals the total of each of the columns
DNIS reports on individual queues or queue groups reflect the service experienced by
callers and caller behavior. DNIS reports provide queue statistics for all calls involving
a particular DNIS number. DNIS Group reports provide queue statistics for all calls
involving a particular group of DNIS numbers.
• Performance
If your interflow statistic is zero, you probably did not program the telephone system with
an interflow value.
The DNIS and DNIS Group Performance by Day of Month reports provide the following
information:
Average speed of answer (hh:mm:ss) the average delay before calls were answered (includ
ing time in queue and ringing time)
Average delay to abandon (hh:mm:ss) the average elapsed time before the call was abandon
ed
Average delay to interflow (hh:mm:ss) the average elapsed time before the call was interflowed
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when the calls are
answered to when they are disconnected (including h
old time and transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from when the calls
are answered to when they are disconnected (including
hold time and transfer/conference time)
Service Level % the percentage of calls answered within the specified Se
rvice Level time
Answer % the percentage of offered calls answered
Totals the total of each of the columns
If your interflow statistic is zero, you probably did not program the telephone system with
an interflow value.
The DNIS and DNIS Group Performance by Day of Week reports provide the following
information:
ACD calls offered the number of ACD calls offered to the queue (Handled
+ Long abandoned + Interflowed)
ACD calls handled the number of ACD calls answered
Calls abandoned (short) the total number of calls abandoned before the Short
Abandon threshold (the Short Abandon is 6 seconds).
Calls abandoned (long) the total number of calls abandoned after the Short
Abandon threshold.
Calls interflowed the number of calls that were redirected from the queue
to an alternate answer point, such as another queue or v
oicemail, after the Short Abandon time
Calls requeued the total number of requeues at the agent's position - if
an agent fails to answer a call, the system places the cal
l back in the same queue
Answered by ACD group 1 the number of ACD calls answered by the first answer
point
Answered by ACD group 2 the number of ACD calls answered by the second a
nswer point
Answered by ACD group 3 the number of ACD calls answered by the third answer
point
Answered by ACD group 4 the number of ACD calls answered by the fourth answe
r point
Average speed of answer (hh:mm:ss) the average delay before calls were answered (includ
ing time in queue and ringing time)
Average delay to abandon (hh:mm:ss) the average elapsed time before the call was abandon
ed
Average delay to interflow (hh:mm:ss) the average elapsed time before the call was interflowed
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when the calls are
answered to when they are disconnected (including h
old time and transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from when the calls
are answered to when they are disconnected (including
hold time and transfer/conference time)
Service Level % the percentage of calls answered within the specified Se
rvice Level time
Answer % the percentage of offered calls answered
Totals the total of each of the columns
If your interflow statistic is zero, you probably did not program the telephone system with
an interflow value.
The DNIS and DNIS Group Performance by Month reports provide the following
information:
Average speed of answer (hh:mm:ss) the average delay before calls were answered (includ
ing time in queue and ringing time)
Average delay to abandon (hh:mm:ss) the average elapsed time before the call was abandon
ed
Average delay to interflow (hh:mm:ss) the average elapsed time before the call was interflowed
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when the calls are
answered to when they are disconnected (including h
old time and transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from when the calls
are answered to when they are disconnected (including
hold time and transfer/conference time)
Service Level % the percentage of calls answered within the specified Se
rvice Level time
Answer % the percentage of offered calls answered
Totals the total of each of the columns
If your interflow statistic is zero, you probably did not program the telephone system with
an interflow value.
The DNIS and DNIS Group Performance by Period reports provide the following
information:
Average speed of answer (hh:mm:ss) the average delay before calls were
answered (including time in queue and
ringing time)
Average delay to abandon (hh:mm:ss) the average elapsed time before the call
was abandoned
Average delay to interflow (hh:mm:ss) the average elapsed time before the call
was interflowed
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
The DNIS and DNIS Group Performance by Queue reports provide the following
information:
ACD queue name the name of the ACD queue for which the
agent answered calls
Note:
Average speed of answer (hh:mm:ss) the average delay before calls were
answered (including time in queue and
ringing time)
Note:
Maximum speed of answer (hh:mm:ss) the maximum delay before the call was
answered
Average delay to abandon (hh:mm:ss) the average elapsed time before the call
was abandoned
Maximum delay to abandon (hh:mm:ss) the maximum delay before the call was
abandoned
Average delay to interflow (hh:mm:ss) the average elapsed time before the call
was interflowed
Maximum delay to interflow (hh:mm:ss) the maximum delay before the call was
interflowed
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
If your interflow statistic is zero, you probably did not program the telephone system with
an interflow value.
The DNIS Group Performance by DNIS reports provide the following information:
Average speed of answer (hh:mm:ss) the average delay before calls were
answered (including time in queue and
ringing time)
Average delay to abandon (hh:mm:ss) the average elapsed time before the call
was abandoned
Average delay to interflow (hh:mm:ss) the average elapsed time before the call
was interflowed
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
Forecast reports use historical voice data to predict future traffic volumes, patterns, and
agent requirements.
Effective contact center management involves having the right resources in place at the
right times to handle an accurately forecasted workload at the desired level of service.
The task of estimating resource requirements is particularly challenging as the number
of calls and the total duration of calls expected for a given time interval are difficult to
predict. Finding the right balance between resources and traffic volumes is critical.
Forecasting accurately predicts your resource requirements.
Note:
• You can only generate and view Forecast reports using Microsoft Excel.
• You cannot export a Forecast report to a Workforce Management application.
• Queue Forecasting
Note:
This report applies to ACD paths only. The report does not apply to Ring Group
data.
Note:
This report applies to ACD paths only. The report does not apply to Ring Group
data.
Note:
• Forecasting reports must be run using historical data up to the present date. A
forecasting report run for a future date will not display data. For more information,
see "Forecasting".
• This report applies to ACD paths only. The report does not apply to Ring Group
agents.
The Queue and Queue Group Forecasting reports provide the following information on
individual agents.
Conversation Detail reports illustrate, by device, how interactions transition through your
system and provide a high-level view of how customer interactions were handled. For
example, Conversation Detail reports indicate if requeues are occurring or if interactions
are bouncing from queue to queue.
To avoid delays in generating this report and any pending reports, we recommend
Note:
• Conversation Detail reports are available for SIP and multimedia devices. You
must be licensed for SIP and/or Multimedia Contact Center to run Conversation
Detail reports.
• For MiVB platform, voice, email, chat, and SMS data in a single report, run a
Multimedia Trace report
• If you are unable to run a Conversation Detail report with data, ensure the
'Conversation detail reporting' check box is selected for the appropriate media
server (multimedia only). After selecting this check box, data must be summarized
for the applicable date ranges.
• If the report range is greater than one day, the durations on the report show date
and time. If the report is for only one day, the report shows time only.
• For email, interaction segments represent one exchange between agent and
customer. A single interaction will not represent an ongoing email exchange.
• We do not recommend printing this report due to its size. However, if you do wish
to print this report, please modify the size manually as it spans multiple pages.
• Agent Group
• Queue/Queue Group
• Employee/Employee Group
Note:
For Employee Conversation Detail and Multimedia Employee Trace reports, on the
Basic tab, you can select 'Create one report for each of the employee’s supported
media servers; This option creates reports for each of the employee’s media types,
based on the media server to which their devices are associated. An employee-
level report will also be created. Otherwise, a single employee-level report will be
created.
• Site
• Media server
• Account Code/Account Code Group
• Include interaction segments that extend outside the selected date range.
• Include only interaction segments for the selected device (‘Include my details only’).
• Include only specific types of interaction causes (select from ‘Cause’ list provided).
• Include specific interactions using the Conversation ID (enter ID in text field). Filtering
by ID will include all segments associated to the interaction.
• Suppress visual formatting for improved readability if you want to format the report in
Excel.
The following table defines the reasons for a segment that can occur in Conversation
Detail reports. The following figure provides an example of a Conversation Detail report.
Reason Description
Reason Description
Reason Description
Park Email the agent logged out with the email interaction in
the Inbox, if requeue on logout disabled.
Conversation started the start time of the interaction, based on the first
segment reason for the interaction.
Conversation ended the end time of the interaction, based on the last
segment reason for the interaction.
Note:
The segment does not necessarily start and
end based on the previous and following
events.
Note:
The segment end time do not necessarily start
and end based on the previous and following
events.
The data table used for storing Conversation Detail reporting data resides in the
CCMStatisticalData catalog of MiContact Center Business SQL Server instance. The
table name is ConversationSummary. This table stores conversation details for both SIP
and MiContact Center Multimedia conversations.
0 Unknown
1 Queued
2 AgentDecline
3 Interflow
4 Requeue
5 Unavailable
6 AgentAnswer
7 EmailPark
8 AccountCode
9 Transfer
10 Complete
11 Abandon
12 Worktimer
13 Failed
14 Conference
15 Outbound
16 Hold
17 Ringing
18 CalledPartyAnswer
19 ClassificationCode
0 Answered_No_Reply 1
1 Answered_With_Reply
2 InterflowedTo
3 InterflowedFrom
4 UnAvailableRoutedTo
5 UnAvailableRoutedFrom
6 TransferTo
7 TransferFrom
8 Ringing_New
9 Ringing_Continuing
10 Ringing_NewMsg
11 Ringing_ContinuingMsg
12 Answered_JunkMail
13 Ringing_Agent_ReQueued
14 Ringing_Agent_ForceForward
15
Ringing_System_ForceForward
16 TransferFrom_BySystem
17 RoutingFailure
18 DeletedFromQueue
19 Abandoned
20 Unknown
21 Redirected
22 DeliveredToPreferredAgent
23 ACD_Delivered
24 NonAcdDelivered
25 Picked
26 Queued
27 Ringing_Abandon
28 Declined
29 FailedToEstablish
30 Timeout
31 System
32 TransferToMailbox
9.1.1 vw_Dispositions
To help simplify understanding the value of the Conversation Disposition, a new SQL
View has been created in the CCMStatisticalData catalog of the MiContact Center
Business SQL Server. This view can be joined with the Conversation Summary data.
ID Display Description
0 Unknown
select
ConversationID,
SegmentStartTime,
SegmentEndTime,
d.ConversationDisposition,
c.Display as DispositionName,
FromName,
ToName,
AnsweringParty,
CurrentQueueReporting
from ConversationSummary d
inner join dbo.vw_Dispositions c
on d.ConversationDisposition = c.ID
Email reports provide email statistics on agents, agent groups, queues, and queue
groups. You can create on-demand and scheduled reports.
You can optionally configure email reports to exclude junk mail from email Handled and
Completed counts. For more information, see the following Mitel Knowledge Base article:
https://mitel.custhelp.com.
To run Conversation Detail reports for email devices, go to Reporter > Conversation
Detail. For more information on Conversation Detail reports, see "Conversation Detail
reports".
• Agent reports
• Queue reports
Agent and Agent group reports provide statistics based on agents and agent group
activity.
• Performance reports
• Agent and Agent Group Event by Period (hh:mm:ss) (You cannot generate this
report over midnight.)
Note:
If you are running a report on an agent group that has non-email agents, the
statistical values in the generated report will be for email agents only.
The Email Agent and Agent Group by Make Busy Code reports provide the following
information:
Make Busy count the total number of times the Make Busy
state was entered
Total Make Busy time (hh:mm:ss) the total time spent in the Make Busy
state, controlled by the agent or the
supervisor
Average Make Busy time (hh:mm:ss) the average time the agent spent in the
Make Busy state, controlled by the agent
or the supervisor
The Email Agent and Agent Group Performance by Account Code reports provide the
following information:
Note:
'Handling time' in the Email Agent Group Performance by Agent report may not
align with ‘ACD handled time’ in the Email Agent and Agent Group Performance by
Period reports. In the Email Agent Group Performance by Agent report, the ‘Handling
time’ calculation takes into account an agent’s overriding state. ‘ACD handled time’
in these reports do not. For example, if an agent responding to an email receives
another email, their state will change from ‘ACD’ to ‘Ringing’. 'Handling time' in the
Agent Group Performance by Agent report will not be calculated while the agent is in
Ringing, but 'ACD handled time' will.
The Email Agent and Agent Group Performance by Period report provides the following
information:
Average ACD offered time (hh:mm:ss) the average time taken to put offered
interactions into reply mode or to classify
interactions as junk or requiring no reply,
from the Inbox
Note:
ACD handled time (hh:mm:ss) the amount of time, excluding hold, spent
completing interactions sent to the queue
ACD hold time (hh:mm:ss) the total time for which interactions were
put on hold
ACD completed time (hh:mm:ss) the total amount of time, including hold,
spent connected to interactions
Average ACD completed time (hh:mm:ss) the average amount of time, including
hold, spent connected to interactions
Total Make Busy time (hh:mm:ss) the total time spent in the Make Busy
state, controlled by the agent or the
supervisor
System Make Busy time (hh:mm:ss) the total time the agent spent in the
system Make Busy state. This type of
Make Busy cannot be set by an agent or
supervisor
The Email Agent Group Performance by Agent Report provides the following information
for individual agents in the group:
Total shift time (hh:mm:ss) the total time the agent spent logged into
the system, for the reporting period
Hold time (hh:mm:ss) the total time for which interactions were
put on hold
Average completed duration (hh:mm:ss) the average duration of emails, from when
the email is opened until it is replied to
(including hold time)
Total Make Busy time (hh:mm:ss) the total time spent in the Make Busy
state, controlled by the agent or the
supervisor
System Make Busy time (hh:mm:ss) the total time the agent spent in the
system Make Busy state. This type of
Make Busy cannot be set by an agent or
supervisor
day(s) you specify. It reports the email statistics in hours, minutes, and seconds and
provides email counts for the agent.
The Email Agent Group Event by Period (hh:mm:ss) report displays log on and log off
times for the members of the email agent group and the total duration each agent of the
agent group spent in various agent states for the day(s) you specify. It reports the email
statistics in hours, minutes, and seconds and provides email counts for the agent. (See
the following figure.)
The Email Agent Event by Period (hh:mm:ss) report is truncated to the first 1000 records.
It provides the following information:
Login date/time the date and time the agent logged into
Multimedia Contact Center
Logout date/time the date and time at which the email agent
either last logged out of the system or last
performed an event (for example, went
into Make Busy)
Total shift time (hh:mm:ss) the total time the agent spent logged into
the system, for the reporting period
Idle time (hh:mm:ss) the total duration the agent was logged on
and available to receive email interactions
Hold time (hh:mm:ss) the total time for which interactions were
put on hold
Total Make Busy time (hh:mm:ss) the total time spent in the Make Busy
state, controlled by the agent or the
supervisor
Average Make Busy time (hh:mm:ss) the average time the agent spent in the
Make Busy state, controlled by the agent
or the supervisor
Make Busy count the total number of times the Make Busy
state was entered
System Make Busy time (hh:mm:ss) the total time the agent spent in the
system Make Busy state. This type of
Make Busy cannot be set by an agent or
supervisor
Average system Make Busy time the average duration the agent spent in
(hh:mm:ss) the system Make Busy state. This type of
Make Busy cannot be set by an agent or
supervisor
System Make Busy count the total number of times the Make
Busy state was entered. This type of
Make Busy cannot be set by an agent or
supervisor
Total DND time (hh:mm:ss) the total time that the agent spent in a Do
Not Disturb state
Average DND time (hh:mm:ss) the average time that the agent spent in a
Do Not Disturb state
Wrap up time (hh:mm:ss) the time the agent spent in a Work Timer
state, for the media type
Average wrap up time (hh:mm:ss) the average time the agent spent in a
Work Timer state, for the media type
The Email Agent Group Event by Period (hh:mm:ss) report provides the following
information:
Queue and queue group reports provide statistics on queues and queue groups that
reflect email behavior and the service experienced by customers who contact you by
email.
• Performance reports
Note:
The Email Queue and Queue Group Performance by Account Code reports provides the
following information:
Note:
Members answering emails, taking transferred emails from the queue will appear in
this report even if the member is not associated to the queue or the queue group on
which you are reporting.
The Email Queue Performance by Agent report provides the following information:
Average handling time (hh:mm:ss) the average duration of emails, from when
the email is opened until it is completed
(excluding hold time)
Hold time (hh:mm:ss) the total time for which interactions were
put on hold
Average hold time (hh:mm:ss) the average duration of emails, from when
the email is opened until it is completed
(including hold time)
Average completed duration (hh:mm:ss) the average duration of emails, from when
the email is opened until it is replied to
(including hold time)
The Email Queue and Queue Group Performance by Period reports provides the
following information:
Note:
Average speed of open (hh:mm:ss) the average elapsed time before the email
was opened
Average delay to interflow (hh:mm:ss) the average elapsed time before the email
was interflowed
Hold time (hh:mm:ss) the total time for which interactions sent to
the queue were put on hold
Average completed duration (hh:mm:ss) the average duration of emails, from when
the email is opened until it is replied to
(including hold time)
The Email Queue Group Performance by Queue report provides the following
information:
1
the number of emails answered by the
Answered by ACD group first answer point
Note:
Average speed of open (hh:mm:ss) the average elapsed time before the email
was opened
Average delay to interflow (hh:mm:ss) the average elapsed time before the email
was interflowed
Hold time (hh:mm:ss) the total time for which interactions sent to
the queue were put on hold
Average completed duration (hh:mm:ss) the average duration of emails, from when
the email is opened until it is replied to
(including hold time)
Note:
‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been added to the
Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x converts
Spectrum by Day of Week reports into Spectrum by Period reports, with data
displaying by day of week intervals.
The following are the first three fields of the Email Queue and Queue Group Answer
Spectrum by Period reports:
Maximum time to open (hh:mm:ss) the maximum delay before the interaction
was opened
Note:
The remaining fields of the Email Queue Answer Spectrum by Period report provide a
frequency distribution of email patterns based on the time scale defined for the queue
in YourSite Explorer. For each time period, the Count <=X Minutes field reflects the total
number of emails for that interval and all preceding intervals. Queue spectrum values
that cannot be rounded to whole minute values will display as decimal values with 2
places in the Count <=X Minutes report fields.
The remaining fields of the Email Queue Group Answer Spectrum by Period report
provide a frequency distribution of emails patterns based on a defined time scale
(Spectral Interval 1-10). The Spectrum Interval field reflects the total number of emails
for that interval and all preceding intervals. The % of contacts opened field reflects the
percentage of emails for that interval and all preceding intervals.
Note:
• For each time period, except > 120 seconds, the Count < x min field reflects the
total number of emails for that interval and all preceding intervals.
• For the >120 minutes' time period, the Count < x min field reflects the total number
of emails for that interval only.
• The % of Total field reflects the percentage of emails for that interval and all
preceding intervals.
Note:
‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been added to the
Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x converts
Spectrum by Day of Week reports into Spectrum by Period reports, with data
displaying by day of week intervals.
The following are the first three fields of the Email Queue and Queue Group Handle
Spectrum by Period reports:
Note:
The remaining fields of the Email Queue Handle Spectrum by Period provide a frequency
distribution of email patterns based on the time scale defined for the queue in YourSite
Explorer. For each time period, the Count <=X Minutes field reflects the total number of
emails for that interval and all preceding intervals. Queue spectrum values that cannot be
rounded to whole minute values will display as decimal values with 2 places in the Count
<=X Minutes report fields.
The remaining fields of the Email Queue Group Handle Spectrum by Period report
provide a frequency distribution of email patterns based on a defined time scale
(Spectral Interval 1-10). The Spectrum Interval field reflects the total number of emails
for that interval and all preceding intervals. The % of contacts handled field reflects the
percentage of emails for that interval and all preceding intervals.
Note:
• For each time period, except > 541 seconds, the Count < x min field reflects the
total number of emails for that interval and all preceding intervals.
• For the >541 minutes' time period, the Count < x min field reflects the total number
of emails for that interval only.
• The % of Total field reflects the percentage of emails for that interval and all
preceding intervals.
Note:
In Release 7.0,‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been
added to the Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x
converts Spectrum by Day of Week reports into Spectrum by Period reports, with
data displaying by day of week intervals.
The following are the first three fields of the Email Queue and Queue Group Interflow
Spectrum by Period reports:
Maximum delay to interflow (hh:mm:ss) the maximum delay before the interaction
was interflowed
Note:
The remaining fields of the Email Queue Interflow Spectrum by Period provide a
frequency distribution of email patterns based on the time scale defined for the queue
in YourSite Explorer. For each time period, the Count <=X Minutes field reflects the total
number of emails for that interval and all preceding intervals. Queue spectrum values
that cannot be rounded to whole minute values will display as decimal values with 2
places in the Count <=X Minutes report fields.
The remaining fields of the Email Queue Group Interflow Spectrum by Period report
provide a frequency distribution of email patterns based on a defined time scale (Spectral
Interval 1-10). The Spectrum Interval field reflects the total number of emails for that
interval and all preceding intervals. The % of contacts interflowed field reflects the
percentage of emails for that interval and all preceding intervals.
Note:
• For each time period, except > 120 seconds, the Count < x min field reflects the
total number of emails for that interval and all preceding intervals.
• For the >120 minutes’ time period, the count < x min field reflects the number of
emails for that interval only.
• The % of Total field reflects the percentage of emails for that interval and all
preceding intervals.
The following are the first three fields of the Email Queue Group Answer Spectrum by
Queue report:
Maximum time to open (hh:mm:ss) the maximum delay before the interaction
was opened
Note:
The remaining fields of the Email Queue Group Answer Spectrum by Queue report
provide a frequency distribution of email patterns based on a defined time scale
(Spectral Interval 1-10). The Spectrum Interval field reflects the total number of emails
for that interval and all preceding intervals. The % of contacts opened field reflects the
percentage of emails for that interval and all preceding intervals.
Note:
Spectrum Interval 10 reflects the total number of emails for that interval only.
The following are the first three fields of the Email Queue Group Handle Spectrum by
Queue report:
Note:
The remaining fields of the Email Queue Group Handle Spectrum by Queue report
provide a frequency distribution of email patterns based on a defined time scale
(Spectral Interval 1-10). The Spectrum Interval field reflects the total number of emails
for that interval and all preceding intervals. The % of contacts handled field reflects the
percentage of emails for that interval and all preceding intervals.
Note:
Spectrum Interval 10 reflects the total number of email for that interval only.
The following are the first three fields of the Email Queue Group Interflow Spectrum by
Queue report:
Maximum delay to interflow (hh:mm:ss) the maximum delay before the interaction
was interflowed
Note:
The remaining fields of the Email Queue Group Interflow Spectrum by Queue report
provide a frequency distribution of email patterns based on a defined time scale (Spectral
Interval 1-10). The Spectrum Interval field reflects the total number of emails for that
interval and all preceding intervals. The % of contacts interflowed field reflects the
percentage of emails for that interval and all preceding intervals.
Note:
Spectrum Interval 10 reflects the total number of emails for that interval only.
Chat reports provide chat statistics on agents, agent groups, queues, and queue groups.
Also, you can create on-demand and scheduled reports for over-midnight shifts.
To run Conversation Detail reports for chat devices, go to Reporter > Conversation
Detail. For more information on Conversation Detail reports, see "Conversation Detail
reports".
• Agent reports
• Queue reports
Agent and Agent Group reports provide statistics based on the activity of agents and
agent groups.
• Performance reports
• Agent and Agent Group Event by Period (hh:mm:ss) (You cannot generate this
report over midnight.)
Note:
If you are running a report on an agent group that has non-chat agents, the statistical
values in the generated report will be for chat agents only.
The Chat Agent and Agent Group by Make Busy Code reports provide the following
information:
Total Make Busy time (hh:mm:ss) the total time spent in the Make Busy
state, controlled by the agent or the
supervisor
Average Make Busy time (hh:mm:ss) the average time the agent spent in the
Make Busy state, controlled by the agent
or the supervisor
The Chat Agent and Agent Group Performance by Account Code report provides the
following information:
Note:
‘Handling time’ in the Chat Agent Group Performance by Agent report may not align
with ‘ACD handled time’ in these reports. In the Chat Agent Group Performance by
Agent report, the ‘Handling time’ calculation takes into account an agent’s overriding
state. ‘ACD handled time’ in these reports does not. For example, if an agent
responding to a chat receives another chat, their state will change from ‘ACD’ to
‘Ringing’. 'Handling time' in the Agent Group Performance by Agent report will not be
calculated while the agent is in Ringing, but 'ACD handled time' will.
Average ACD offered time (hh:mm:ss) the average time taken to put offered
chats into reply mode
ACD handled time (hh:mm:ss) the amount of time, excluding hold, spent
completing interactions sent to the queue
ACD hold time (hh:mm:ss) the total time for which interactions were
put on hold
ACD completed time (hh:mm:ss) the total amount of time, including hold,
spent connected to interactions
Average ACD completed time (hh:mm:ss) the average amount of time, including
hold, spent connected to interactions
Note:
Total Make Busy time (hh:mm:ss) the total time spent in the Make Busy
state, controlled by the agent or the
supervisor
System Make Busy time (hh:mm:ss) the total time the agent spent in the
system Make Busy state. This type of
Make Busy cannot be set by an agent or
supervisor
reports the chat statistics in hours, minutes, and seconds, and provides interaction
counts across agents. (See the following figure.)
The Chat Agent Group Performance by Agent report provides the following information:
Idle time (hh:mm:ss) the total duration the agent was logged on
and available to receive chat interactions
Total shift time (hh:mm:ss) the total time the agent spent logged into
the system, for the reporting period
Total Make Busy time (hh:mm:ss) the total time spent in the Make Busy
state, controlled by the agent or the
supervisor
Total system Make Busy time (hh:mm:ss) the total time the agent spent in the
system Make Busy state. This type of
Make Busy cannot be set by an agent or
supervisor
The Chat Agent Group Event by Period (hh:mm:ss) report displays log on and log off
times for the agent group and the total duration the agent group spent in various agent
states for the day(s) you specify. It reports the chat statistics in hours, minutes, and
seconds and provides chat counts for the agent.
The Chat Agent Event by Period (hh:mm:ss) report is truncated to the first 1000 records.
It provides the following information:
Login date/time the date and time at which the chat agent
logged into the system
Logout date/time the date and time at which the chat agent
either last logged out of the system or last
performed an event (for example, went
into Make Busy)
Total shift time (hh:mm:ss) the total time the agent spent logged into
the system, for the reporting period
Idle time (hh:mm:ss) the total duration the agent was logged on
and available to receive chat interactions
Completed contacts < short handle time the number of interactions closed or
transferred before the queue's Short
handle less than time, as configured in
YourSite Explorer. This is the last queue
the interaction touched. The default is 20
seconds.
Total Make Busy time (hh:mm:ss) the total time spent in the Make Busy
state, controlled by the agent or the
supervisor
Average Make Busy time (hh:mm:ss) the average time the agent spent in the
Make Busy state, controlled by the agent
or the supervisor
System Make Busy time (hh:mm:ss) the total time the agent spent in the
system Make Busy state. This type of
Make Busy cannot be set by an agent or
supervisor
Average system Make Busy time the average duration the agent spent in
(hh:mm:ss) the system Make Busy state. This type of
Make Busy cannot be set by an agent or
supervisor
System Make Busy count the total number of times the Make
Busy state was entered. This type of
Make Busy cannot be set by an agent or
supervisor
Total DND time (hh:mm:ss) the total time that the agent spent in a Do
Not Disturb state
Average DND time (hh:mm:ss) the average time that the agent spent in a
Do Not Disturb state
Wrap up time (hh:mm:ss) the time the agent spent in a Work Timer
state, for the media type
Average wrap up time (hh:mm:ss) the average time the agent spent in a
Work Timer state, for the media type
The Chat Agent Group Event by Period (hh:mm:ss) report compares the total duration
agents spent in various agent states, for the agent group and day(s) you specify. It
reports the chat statistics in hours, minutes, and seconds. It also compares chat counts
across agents.
The Chat Agent Group Event by Period (hh:mm:ss) report provides the following
information:
Total shift time (hh:mm:ss) the total time the agent spent logged into
the system, for the reporting period
Ringing time (hh:mm:ss) the total duration before the chats were
opened
Completed contacts < short handle time the number of interactions closed or
transferred before the queue's Short
handle less than time, as configured in
YourSite Explorer. This is the last queue
the interaction touched. The default is 20
seconds.
Total Make Busy time (hh:mm:ss) the total duration the agent spent in the
Make Busy state, controlled by the agent
or the supervisor
Average Make Busy time (hh:mm:ss) the average duration the agent spent in
the Make Busy state, controlled by the
agent or the supervisor
System Make Busy time (hh:mm:ss) the total duration the agent spent in the
system Make Busy state
Average system Make Busy time the average duration the agent spent in
(hh:mm:ss) the system Make Busy state
System Make Busy count the total number of times the agent
entered the system Make Busy state
Total DND time (hh:mm:ss) the total time that agents in the agent
group spent in a Do Not Disturb state
Average DND time (hh:mm:ss) the average time that agents in the agent
group spent in a Do Not Disturb state
Wrap up time (hh:mm:ss) the time that agents in the agent group
spent in a Work Timer state, for the media
type
Average wrap up time (hh:mm:ss) the average time the agents in the agent
group spent in a Work Timer state, for the
media type
Queue and Queue Group reports provide statistics on queues and queue groups that
reflect chat behavior and the service experienced by clients.
• Performance reports
Note:
The Chat Queue and Queue Group Performance by Account Code report provides the
following information.
Note:
Members answering chats, taking transferred chats from the queue will appear in
this report even if the member is not associated to the queue or the queue group on
which you are reporting.
The Chat Queue Performance by Agent report provides the following information.
Hold time (hh:mm:ss) the total time for which interactions were
put on hold
Average hold time (hh:mm:ss) the average time for which the agent put
interactions on hold
The Chat Queue Performance by Period reports provide the following information:
Note:
Average speed of answer (hh:mm:ss) the average delay before the chat was
answered (including time in queue and
agent ringing time)
Average delay to abandon (hh:mm:ss) the average elapsed time before the chat
was abandoned
The Chat Queue Group Performance by Queue report provides the following information:
Note:
Average speed of open (hh:mm:ss) the average delay before the chat was
answered (including time in queue and
agent ringing time)
Average delay to abandon (hh:mm:ss) the average elapsed time before the chat
was abandoned
Note:
‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been added to the
Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x converts
Spectrum by Day of Week reports into Spectrum by Period reports, with data
displaying by day of week intervals.
The following are the first three fields of the Chat Queue and Queue Group Abandon
Spectrum by Period reports:
Maximum delay to abandon (hh:mm:ss) the maximum delay before the interaction
was abandoned
Note:
The remaining fields of the Chat Queue and Queue Group Abandon Spectrum by Period
reports provide a frequency distribution of chat patterns based on a defined time scale
(5, 10, 15, 20, 30, 40, 60, 80, 120, and >120 seconds). For each time period, the Count
< x sec field reflects the total number of chats for that interval and all preceding intervals.
The % of contacts abandoned field reflects the percentage of chats for that interval and
all preceding intervals.
Note:
• For each time period, except > 120 seconds, the Count < x sec field reflects the
total number of chats for that interval and all preceding intervals.
• For the >120 seconds time period, the Count < x sec field reflects the total number
of chats for that interval only.
• The % of field reflects the percentage of chats for that interval and all preceding
intervals.
Note:
‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been added to the
Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x converts
Spectrum by Day of Week reports into Spectrum by Period reports, with data
displaying by day of week intervals.
The following are the first three fields of the Chat Queue and Queue Group Answer
Spectrum by Period reports:
Maximum time to open (hh:mm:ss) the maximum delay before the chat was
answered
Note:
The remaining fields of the Chat Queue and Queue Group Answer Spectrum by Period
reports provide a frequency distribution of chat patterns based on a defined time scale
(5, 10, 15, 20, 30, 40, 60, 80, 120, and >120 seconds). For each time period, the Count
< x sec field reflects the total number of chats for that interval and all preceding intervals.
The % of contacts opened field reflects the percentage of chats for that interval and all
preceding intervals.
Note:
• For each time period, except > 120 seconds, the Count < x sec field reflects the
total number of chats for that interval and all preceding intervals.
• For the >120 seconds time period, the Count < x sec field reflects the total number
of chats for that interval only.
• The % of field reflects the percentage of chats for that interval and all preceding
intervals.
Note:
‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been added to the
Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x converts
Spectrum by Day of Week reports into Spectrum by Period reports, with data
displaying by day of week intervals.
The following are the first three fields of the Chat Queue and Queue Group Handle
Spectrum by Period reports:
Maximum duration (hh:mm:ss) the duration of the longest chat for the
period
Note:
The remaining fields of the Chat Queue and Queue Group Handle Spectrum by Period
reports provide a frequency distribution of chat patterns based on a defined time scale
(<10, <60, <180, <240, <300, <360, <420, <480, <540, and >541 seconds). For each
time period, the Count < x sec field reflects the total number of chats for that interval and
all preceding intervals. The % of contacts handled field reflects the percentage of chats
for that interval and all preceding intervals.
Note:
• For each time period, except > 541 seconds, the Count < x sec field reflects the
total number of chats for that interval and all preceding intervals.
• For the >541 seconds time period, the Count < x sec field reflects the total number
of chats for that interval only.
• The % of field reflects the percentage of chats for that interval and all preceding
intervals.
Note:
‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been added to the
Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x converts
Spectrum by Day of Week reports into Spectrum by Period reports, with data
displaying by day of week intervals.
The following are the first three fields of the Chat Queue and Queue Group Interflow
Spectrum by Period reports:
Maximum delay to interflow (hh:mm:ss) the maximum delay before the interaction
was interflowed
Note:
The remaining fields of the Chat Queue and Queue Group Interflow Spectrum by Period
reports provide a frequency distribution of chat patterns based on a defined time scale
(5, 10, 15, 20, 30, 40, 60, 80, 120, and >120 seconds). For each time period, the Count
< x sec field reflects the total number of chats for that interval and all preceding intervals.
The % of contacts interflowed field reflects the percentage of chats for that interval and
all preceding intervals.
Note:
• For each time period, except > 120 seconds, the Count < x sec field reflects the
total number of chats for that interval and all preceding intervals.
• For the >120 seconds time period, the Count < x sec field reflects the total number
of chats for that interval only.
• The % of field reflects the percentage of chats for that interval and all preceding
intervals.
The following are the first four fields of the Chat Queue Group Abandon Spectrum by
Queue report:
Maximum delay to abandon (hh:mm:ss) the maximum delay before the interaction
was abandoned
Note:
The remaining fields of the Chat Queue Group Abandon Spectrum by Queue report
provide a frequency distribution of chat patterns based on a defined time scale (Spectral
Interval 1-10). The Spectrum Interval field reflects the total number of chats for that
interval and all preceding intervals. The % of contacts abandoned field reflects the
percentage of chats for that interval and all preceding intervals.
Note:
Spectrum Interval 10 reflects the total number of chats for that interval only.
The following are the first four fields of the Chat Queue Group Answer Spectrum by
Queue report:
Maximum time to open (hh:mm:ss) the maximum delay before the chat was
answered
Note:
The remaining fields of the Chat Queue Group Answer Spectrum by Queue report
provide a frequency distribution of chat patterns based on a defined time scale
(Spectral Interval 1-10). The Spectrum Interval field reflects the total number of chats
for that interval and all preceding intervals. The % of contacts opened field reflects the
percentage of chats for that interval and all preceding intervals.
Note:
Spectrum Interval 10 reflects the total number of chats for that interval only.
The following are the first four fields of the Chat Queue Group Handle Spectrum by
Queue report:
Maximum duration (hh:mm:ss) the duration of the longest chat for the
period
Note:
The remaining fields of the Chat Queue Group Handle Spectrum by Queue report
provide a frequency distribution of chat patterns based on a defined time scale (Spectral
Interval 1-10). The Spectrum Interval field reflects the total number of chats for that
interval and all preceding intervals. The % of contacts handled field reflects the
percentage of chats for that interval and all preceding intervals.
Note:
Spectrum Interval 10 reflects the total number of chats for that interval only.
The following are the first four fields of the Chat Queue Group Interflow Spectrum by
Queue report:
Maximum delay to interflow (hh:mm:ss) the maximum delay before the interaction
was interflowed
Note:
The remaining fields of the Chat Queue Group Interflow Spectrum by Queue report
provide a frequency distribution of chat patterns based on a defined time scale (Spectral
Interval 1-10). The Spectrum Interval field reflects the total number of chats for that
interval and all preceding intervals. The % of contacts interflowed field reflects the
percentage of chats for that interval and all preceding intervals.
Spectrum Interval 10 reflects the total number of chats for that interval only.
SMS reports provide SMS statistics on agents, agent groups, queues, and queue groups.
You can create on-demand and scheduled reports.
You can optionally configure SMS reports to exclude junk mail from SMS Handled and
Completed counts. For more information, see the following Mitel Knowledge Base article:
https://mitel.custhelp.com.
To run Conversation Detail reports for email devices, go to Reporter > Conversation
Detail. For more information on Conversation Detail reports, see "Conversation Detail
reports".
• Agent reports
• Queue reports
Agent and Agent group reports provide statistics based on agents and agent group
activity.
• Performance reports
• Agent and Agent Group Event by Period (hh:mm:ss) (You cannot generate this
report over midnight.)
Note:
If you are running a report on an agent group that has non-SMS agents, the statistical
values in the generated report will be for SMS agents only.
The SMS Agent and Agent Group by Make Busy Code reports provide the following
information:
Make Busy count the total number of times the Make Busy
state was entered
Total Make Busy time (hh:mm:ss) the total time spent in the Make Busy
state, controlled by the agent or the
supervisor
Average Make Busy time (hh:mm:ss) the average time the agent spent in the
Make Busy state, controlled by the agent
or the supervisor
The SMS Agent and Agent Group Performance by Account Code reports provide the
following information:
Note:
'Handling time' in the SMS Agent Group Performance by Agent report may not
align with ‘ACD handled time’ in the SMS Agent and Agent Group Performance by
Period reports. In the SMS Agent Group Performance by Agent report, the ‘Handling
time’ calculation takes into account an agent’s overriding state. ‘ACD handled time’
in these reports do not. For example, if an agent responding to an SMS receives
another SMS, their state will change from ‘ACD’ to ‘Ringing’. 'Handling time' in the
Agent Group Performance by Agent report will not be calculated while the agent is in
Ringing, but 'ACD handled time' will.
Average ACD offered time (hh:mm:ss) the average time taken to put offered
interactions into reply mode or to classify
interactions as junk or requiring no reply,
from the Inbox
Note:
ACD handled time (hh:mm:ss) the amount of time, excluding hold, spent
completing interactions sent to the queue
ACD hold time (hh:mm:ss) the total time for which interactions were
put on hold
ACD completed time (hh:mm:ss) the total amount of time, including hold,
spent connected to interactions
Average ACD completed time (hh:mm:ss) the average amount of time, including
hold, spent connected to interactions
Total Make Busy time (hh:mm:ss) the total time spent in the Make Busy
state, controlled by the agent or the
supervisor
System Make Busy time (hh:mm:ss) the total time the agent spent in the
system Make Busy state. This type of
Make Busy cannot be set by an agent or
supervisor
The SMS Agent Group Performance by Agent Report provides the following information:
Idle time (hh:mm:ss) the time the agent was logged on and
available to receive SMS interactions
Total shift time (hh:mm:ss) the total time the agent was logged into
the system
Total Make Busy time (hh:mm:ss) the total time spent in the Make Busy
state, controlled by the agent or the
supervisor
System Make Busy time (hh:mm:ss) the total time the agent spent in the
system Make Busy state. This type of
Make Busy cannot be set by an agent or
supervisor
The SMS Agent Event by Period (hh:mm:ss) report is truncated to the first 1000 records.
It provides the following information:
Login date/time the date and time at which the SMS agent
logged into the system
Logout date/time the date and time at which the SMS agent
either last logged out of the system or last
performed an event (for example, went
into Make Busy)
Total shift time (hh:mm:ss) the total time the SMS agent was logged
into the system
Idle time (hh:mm:ss) the time the agent was logged on and
available to receive SMS interactions
Ringing time (hh:mm:ss) the time that SMS interactions were in the
agent’s Inbox before being opened
Completed Contacts < short handle time the number of interactions closed or
transferred before the queue's Short
handle less than time, as configured in
YourSite Explorer. This is the last queue
the interaction touched. The default is 20
seconds.
Total Make Busy time (hh:mm:ss) the total time spent in the Make Busy
state, controlled by the agent or the
supervisor
Average Make Busy time (hh:mm:ss) the average time the agent spent in the
Make Busy state, controlled by the agent
or the supervisor
Make Busy count the total number of times the Make Busy
state was entered
System Make Busy time (hh:mm:ss) the total time the agent spent in the
system Make Busy state. This type of
Make Busy cannot be set by an agent or
supervisor
Average system Make Busy time the average duration the agent spent in
(hh:mm:ss) the system Make Busy state. This type of
Make Busy cannot be set by an agent or
supervisor
System Make Busy count the total number of times the Make
Busy state was entered. This type of
Make Busy cannot be set by an agent or
supervisor
Total DND time (hh:mm:ss) the total time that the agent spent in a Do
Not Disturb state
Average DND time (hh:mm:ss) the average time that the agent spent in a
Do Not Disturb state
Wrap up time (hh:mm:ss) the time the agent spent in a Work Timer
state, for the media type
Average wrap up time (hh:mm:ss) the average time the agent spent in a
Work Timer state, for the media type
The SMS Agent Group Event by Period (hh:mm:ss) report provides the following
information:
Total shift time (hh:mm:ss) the total time the SMS agent was logged
into the system
Idle time (hh:mm:ss) the time the agent was logged on and
available to receive SMS interactions
Ringing time (hh:mm:ss) the time that SMS interactions were in the
agent’s Inbox before being opened
Completed Contacts < short handle time the number of interactions closed or
transferred before the queue's Short
handle less than time, as configured in
YourSite Explorer. This is the last queue
the interaction touched. The default is 20
seconds.
Total Make Busy time (hh:mm:ss) the total time spent in the Make Busy
state, controlled by the agent or the
supervisor
Average Make Busy time (hh:mm:ss) the average time the agent spent in the
Make Busy state, controlled by the agent
or the supervisor
System Make Busy time (hh:mm:ss) the total time the agent spent in the
system Make Busy state. This type of
Make Busy cannot be set by an agent or
supervisor
Average system Make Busy time the average duration the agent spent in
(hh:mm:ss) the system Make Busy state. This type of
Make Busy cannot be set by an agent or
supervisor
System Make Busy count the total number of times the Make
Busy state was entered. This type of
Make Busy cannot be set by an agent or
supervisor
Total DND time (hh:mm:ss) the total time that agents in the agent
group spent in a Do Not Disturb state
Average DND time (hh:mm:ss) the average time that agents in the agent
group spent in a Do Not Disturb state
Wrap up time (hh:mm:ss) the time that agents in the agent group
spent in a Work Timer state, for the media
type
Average wrap up time (hh:mm:ss) the average time the agents in the agent
group spent in a Work Timer state, for the
media type
Queue and queue group reports provide statistics on queues and queue groups that
reflect SMS behavior and the service experienced by customers who contact you by
SMS.
• Performance reports
Note:
The SMS Queue and Queue Group Performance by Account Code reports provides the
following information:
Note:
Members answering SMS, taking transferred SMS from the queue will appear in
this report even if the member is not associated to the queue or the queue group on
which you are reporting.
The SMS Queue Performance by Agent report provides the following information:
Hold time (hh:mm:ss) the total time for which interactions sent to
the queue were put on hold
Average hold time (hh:mm:ss) the average time for which the agent put
interactions from the queue on hold
The SMS Queue and Queue Group Performance by Period reports provides the
following information:
Note:
Average speed of open (hh:mm:ss) the average time between when the
interaction rings in the agent’s Inbox and
when it was opened
Hold time (hh:mm:ss) the total time for which interactions sent to
the queue were put on hold
The SMS Queue Group Performance by Queue report provides the following information:
Note:
Average speed of open (hh:mm:ss) the average time between when the
interaction rings in the agent’s Inbox and
when it was opened
Hold time (hh:mm:ss) the total time for which interactions sent to
the queue were put on hold
Note:
‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been added to the
Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x converts
Spectrum by Day of Week reports into Spectrum by Period reports, with data
displaying by day of week intervals.
The following are the first three fields of the SMS Queue and Queue Group Answer
Spectrum by Period reports:
Maximum time to open (hh:mm:ss) the maximum delay before the interaction
was opened
Note:
The remaining fields of the SMS Queue Answer Spectrum by Period report provide a
frequency distribution of SMS interaction patterns based on the time scale defined for the
queue in YourSite Explorer. For each time period, the Count <=X Minutes field reflects
the total number of SMS interactions for that interval and all preceding intervals. Queue
spectrum values that cannot be rounded to whole minute values will display as decimal
values with 2 places in the Count <=X Minutes report fields.
The remaining fields of the SMS Queue Group Answer Spectrum by Period report
provide a frequency distribution of SMS patterns based on a defined time scale (Spectral
Interval 1-10). The Spectrum Interval field reflects the total number of SMS interactions
for that interval and all preceding intervals. The % of contacts opened field reflects the
percentage of SMS interactions for that interval and all preceding intervals.
Note:
• For each time period, > 120 seconds, the Count < x min field reflects the total
number of SMS interactions for that interval and all preceding intervals.
• For the >120 minutes' time period, the Count < x min field reflects the total number
of SMS interactions for that interval only.
• The % of Total field reflects the percentage of SMS interactions for that interval
and all preceding intervals.
Note:
‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been added to the
Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x converts
Spectrum by Day of Week reports into Spectrum by Period reports, with data
displaying by day of week intervals.
The following are the first three fields of the SMS Queue and Queue Group Handle
Spectrum by Period reports:
Note:
The remaining fields of the SMS Queue Handle Spectrum by Period provide a frequency
distribution of SMS patterns based on the time scale defined for the queue in YourSite
Explorer. For each time period, the Count <=X Minutes field reflects the total number of
SMS interactions for that interval and all preceding intervals. Queue spectrum values that
cannot be rounded to whole minute values will display as decimal values with 2 places in
the Count <=X Minutes report fields.
The remaining fields of the SMS Queue Group Handle Spectrum by Period report
provide a frequency distribution of SMS patterns based on a defined time scale (Spectral
Interval 1-10). The Spectrum Interval field reflects the total number of SMS interactions
for that interval and all preceding intervals. The % of contacts handled field reflects the
percentage of SMS interactions for that interval and all preceding intervals.
Note:
• For each time period, except <= 541 seconds, the Count <= min field reflects the
total number of SMS interactions for that interval and all preceding intervals.
• For the <= 541 minutes' time period, the Count <= min field reflects the total
number of SMS interactions for that interval only.
• The % of Total field reflects the percentage of SMS interactions for that interval
and all preceding intervals.
Note:
‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been added to the
Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x converts
Spectrum by Day of Week reports into Spectrum by Period reports, with data
displaying by day of week intervals.
The following are the first three fields of the SMS Queue and Queue Group Interflow
Spectrum by Period reports:
Maximum delay to interflow (hh:mm:ss) the maximum delay before the interaction
was interflowed
Note:
The remaining fields of the SMS Queue Interflow Spectrum by Period provide a
frequency distribution of SMS patterns based on the time scale defined for the queue in
YourSite Explorer. For each time period, the Count <=X Minutes field reflects the total
number of SMS interactions for that interval and all preceding intervals. Queue spectrum
values that cannot be rounded to whole minute values will display as decimal values with
2 places in the Count <=X Minutes report fields.
The remaining fields of the SMS Queue Group Interflow Spectrum by Period report
provide a frequency distribution of SMS patterns based on a defined time scale (Spectral
Interval 1-10). The Spectrum Interval field reflects the total number of SMS interactions
for that interval and all preceding intervals. The % of contacts interflowed field reflects the
percentage of SMS interactions for that interval and all preceding intervals.
Note:
• For each time period, except > 120 seconds, the Count < x min field reflects the
total number of SMS interactions for that interval and all preceding intervals.
• For the >120 minutes' time period, the Count < x min field reflects the total number
of SMS interactions for that interval only.
• The % of Total field reflects the percentage of SMS interactions for that interval
and all preceding intervals.
The following are the first three fields of the SMS Queue Group Answer Spectrum by
Queue report:
Maximum time to open (hh:mm:ss) the maximum delay before the interaction
was opened
Note:
The remaining fields of the SMS Queue Group Spectrum by Queue report provide a
frequency distribution of SMS patterns based on a defined time scale (Spectral Interval
1-10). The Spectrum Interval field reflects the total number of SMS interactions for
that interval and all preceding intervals. The % of contacts opened field reflects the
percentage of SMS interactions for that interval and all preceding intervals.
Note:
Spectrum Interval 10 reflects the total number of SMS interactions for that interval
only.
The following are the first three fields of the SMS Queue Group Handle Spectrum by
Queue report:
Note:
The remaining fields of the SMS Queue Group Handle Spectrum by Queue report
provide a frequency distribution of SMS patterns based on a defined time scale (Spectral
Interval 1-10). The Spectrum Interval field reflects the total number of SMS interactions
for that interval and all preceding intervals. The % of contacts handled field reflects the
percentage of SMS interactions for that interval and all preceding intervals.
Note:
Spectrum Interval 10 reflects the total number of SMS interactions for that interval
only.
The following are the first three fields of the SMS Queue Group Interflow Spectrum by
Queue report:
Maximum delay to interflow (hh:mm:ss) the maximum delay before the interaction
was interflowed
Note:
The remaining fields of the SMS Queue Group Interflow Spectrum by Queue report
provide a frequency distribution of SMS patterns based on a defined time scale (Spectral
Interval 1-10). The Spectrum Interval field reflects the total number of SMS interactions
for that interval and all preceding intervals. The % of contacts interflowed field reflects the
percentage of SMS interactions for that interval and all preceding intervals.
Spectrum Interval 10 reflects the total number of SMS interactions for that interval
only.
Open Media reports provide statistics on agents, agent groups, queues, and queue
groups. You can create on-demand and scheduled reports.
You can optionally configure open media reports to exclude junk mail from Open Media
Handled and Completed counts. For more information, see the following Mitel Knowledge
Base article: https://mitel.custhelp.com.
• Agent reports
• Queue reports
Agent and Agent group reports provide statistics based on agents and agent group
activity.
• Performance reports
• Open Media Agent Group and Agent Performance by Make Busy Code
• Open Media Agent and Agent Group Performance by Account Code
• Agent Group Performance by Agent
• Event reports
The Open Media Agent and Agent Group by Make Busy Code reports provide the
following information:
Make Busy count the total number of times the Make Busy
state was entered
Total Make Busy time (hh:mm:ss) the total time spent in the Make Busy
state, controlled by the agent or the
supervisor
Average Make Busy time (hh:mm:ss) the average time the agent spent in the
Make Busy state, controlled by the agent
or the supervisor
The Open Media Agent and Agent Group Performance by Account Code reports provide
the following information:
Figure 153: Agent Performance and Agent Group Performance by Account Code
The Open Media Agent Group Performance by Agent report provides the following
information:
Total shift time (hh:mm:ss) the total time the agent was logged into
the system
Total Make Busy time (hh:mm:ss) the total time spent in the Make Busy
state, controlled by the agent or the
supervisor
System Make Busy time (hh:mm:ss) the total time the agent spent in the
system Make Busy state. This type of
Make Busy cannot be set by an agent or
supervisor
The Open Media Agent and Agent Group Event by Period (hh:mm:ss) report is truncated
to the first 1000 records. It provides the following information:
Total shift time (hh:mm:ss) the total time the open media agent was
logged into the system
Idle time (hh:mm:ss) the total duration the agent was logged
on and available to receive open media
interactions
Total Make Busy time (hh:mm:ss) the total time spent in the Make Busy
state, controlled by the agent or the
supervisor
Average Make Busy time (hh:mm:ss) the average time the agent spent in the
Make Busy state, controlled by the agent
or the supervisor
Make Busy count the total number of times the Make Busy
state was entered
System Make Busy time (hh:mm:ss) the total time the agent spent in the
system Make Busy state. This type of
Make Busy cannot be set by an agent or
supervisor
Average system Make Busy time the average duration the agent spent in
(hh:mm:ss) the system Make Busy state. This type of
Make Busy cannot be set by an agent or
supervisor
System Make Busy count the total number of times the Make
Busy state was entered. This type of
Make Busy cannot be set by an agent or
supervisor
Total DNDtime (hh:mm:ss) the total time that the agent spent in a Do
Not Disturb state
Average DNDtime (hh:mm:ss) the average time that the agent spent in a
Do Not Disturb state
Wrap up time (hh:mm:ss) the time the agent spent in a Work Timer
state, for the media type
Average wrap up time (hh:mm:ss) the average time the agent spent in a
Work Timer state, for the media type
Queue and queue group reports provide statistics on queues and queue groups that
reflect open media behavior and the service experienced by customers who contact you
by open media.
• Performance reports
The Open Media Queue and Queue Group Performance by Account Code reports
provides the following information:
The Open Media Queue performance by Agent reports provide the following information:
Average handling time (hh:mm:ss) the average time taken to reply, transfer,
or classify the interaction as junk or
requiring noreply
Hold time (hh:mm:ss) the total time for which ACD, non-ACD,
and Outbound interactions were put on
hold by agents in the agent group
Average hold time (hh:mm:ss) the average time for which ACD, non-
ACD, and outbound interactions were put
on hold by agents
Average Completed Duration (hh:mm:ss) the average time, including hold, spent
connected to interactions
Hold time (hh:mm:ss) the total time for which ACD, non-ACD,
and Outbound interactions were put on
hold by agents
Note:
‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been added to the
Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x converts
Spectrum by Day of Week reports into Spectrum by Period reports, with data
displaying by day of week intervals.
The following are the first three fields of the Open Media Queue and Queue Group
Answer Spectrum by Period reports:
Maximum time to open (hh:mm:ss) the maximum delay before the interaction
was opened
Note:
The 'Maximum' column displays the
highest value for the reporting period.
The remaining fields of the Open Media Queue Answer Spectrum by Period report
provide a frequency distribution of open media contact patterns based on the time
scale defined for the queue in YourSite Explorer. For each time period, the Count <=X
Minutes field reflects the total number of open media interactions for that interval and
all preceding intervals. Queue spectrum values that cannot be rounded to whole minute
values will display as decimal values with 2 places in the Count <=X Minutes report
fields.
The remaining fields of the Open Media Queue Group Answer Spectrum by Period report
provide a frequency distribution of open media patterns based on a defined time scale
(Spectral Interval 1-10). The Spectrum Interval field reflects the total number of open
media interactions for that interval and all preceding intervals. The % of contacts opened
field reflects the percentage of open media interactions for that interval and all preceding
intervals.
Note:
• For each time period, > 120 seconds, the Count < x min field reflects the total
number of open media interactions for that interval and all preceding intervals.
• For the >120 minutes' time period, the Count < x min field reflects the total number
of open media interactions for that interval only.
• The % of Total field reflects the percentage of open media interactions for that
interval and all preceding intervals.
Note:
‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been added to the
Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x converts
Spectrum by Day of Week reports into Spectrum by Period reports, with data
displaying by day of week intervals.
The following are the first three fields of the Open Media Queue and Queue Group
Handle Spectrum by Period reports:
Note:
The remaining fields of the Open Media Queue Handle Spectrum by Period provide a
frequency distribution of open media patterns based on the time scale defined for the
queue in YourSite Explorer. For each time period, the Count <=X Minutes field reflects
the total number of open media interactions for that interval and all preceding intervals.
Queue spectrum values that cannot be rounded to whole minute values will display as
decimal values with 2 places in the Count <=X Minutes report fields.
The remaining fields of the Open Media Queue Group Handle Spectrum by Period report
provide a frequency distribution of open media patterns based on a defined time scale
(Spectral Interval 1-10). The Spectrum Interval field reflects the total number of open
media interactions for that interval and all preceding intervals. The % of contacts handled
field reflects the percentage of open media interactions for that interval and all preceding
intervals.
Note:
• For each time period, except <= 541 seconds, the Count <= min field reflects the
total number of open media interactions for that interval and all preceding intervals.
• For the <= 541 minutes' time period, the Count <= min field reflects the total
number of openmedia interactions for that interval only.
• The % of Total field reflects the percentage of openmedia interactions for that
interval and all preceding intervals.
Note:
‘Day of week’, ‘Month’, and ‘Day of month’ intervals have been added to the
Spectrum by Period reports. Upgrading from Version 6.x to Version 7.x converts
Spectrum by Day of Week reports into Spectrum by Period reports, with data
displaying by day of week intervals.
The following are the first three fields of the Open Media Queue and Queue Group
Interflow Spectrum by Period reports:
Maximum delay to interflow (hh:mm:ss) the maximum delay before the interaction
was interflowed
Note:
The remaining fields of the Open Media Queue Interflow Spectrum by Period provide a
frequency distribution of open media patterns based on the time scale defined for the
queue in YourSite Explorer. For each time period, the Count <=X Minutes field reflects
the total number of open media interactions for that interval and all preceding intervals.
Queue spectrum values that cannot be rounded to whole minute values will display as
decimal values with 2 places in the Count <=X Minutes report fields.
The remaining fields of the Open Media Queue Group Interflow Spectrum by Period
report provide a frequency distribution of open media patterns based on a defined time
scale (Spectral Interval 1-10). The Spectrum Interval field reflects the total number of
open media interactions for that interval and all preceding intervals. The % of contacts
interflowed field reflects the percentage of open media interactions for that interval and
all preceding intervals.
Note:
• For each time period, except > 120 seconds, the Count < x min field reflects the
total number of openmedia interactions for that interval and all preceding intervals.
• For the >120 minutes' time period, the Count < x min field reflects the total number
of openmedia interactions for that interval only.
• The % of Total field reflects the percentage of open media interactions for that
interval and all preceding intervals.
The following are the first three fields of the Open Media Queue Group Answer Spectrum
by Queue report:
Reporting
the queue's reporting number
Note:
The remaining fields of the Open Media Queue Group Spectrum by Queue report provide
a frequency distribution of open media patterns based on a defined time scale (Spectrum
Interval 1-10). The Spectrum Interval field reflects the total number of open media
interactions for that interval and all preceding intervals. The % of contacts opened field
reflects the percentage of open media interactions for that interval and all preceding
intervals.
Note:
Spectrum Interval 10 reflects the total number of open media interactions for that
interval only.
The following are the first three fields of the Open Media Queue Group Handle Spectrum
by Queue report:
Note:
The remaining fields of the Open Media Queue Group Handle Spectrum by Queue report
provide a frequency distribution of open media patterns based on a defined time scale
(Spectral Interval 1-10). The Spectrum Interval field reflects the total number of open
media interactions for that interval and all preceding intervals. The % of contacts handled
field reflects the percentage of open media interactions for that interval and all preceding
intervals.
Note:
Spectrum Interval 10 reflects the total number of open media interactions for that
interval only.
The following are the first three fields of the Open Media Queue Group Interflow
Spectrum by Queue report:
Maximum delay to interflow (hh:mm:ss) the maximum delay before the interaction
was interflowed
Note:
The remaining fields of the Open Media Queue Group Interflow Spectrum by Queue
report provide a frequency distribution of open media patterns based on a defined time
scale (Spectral Interval 1-10). The Spectrum Interval field reflects the total number of
open media interactions for that interval and all preceding intervals. The % of contacts
interflowed field reflects the percentage of open media interactions for that interval and
all preceding intervals.
Note:
Spectrum Interval 10 reflects the total number of open media interactions for that
interval only.
Period Description
Multimedia reports provide detailed information across media types: voice, email, chat,
and SMS. Using Multimedia reports, you can compare performance across media types.
Workflow reports are also available for Multimedia workflows. See "Workflow reports" for
more information.
You can optionally configure multimedia reports to exclude junk mail from email and SMS
Handled and Completed counts. For more information, see the following Mitel Knowledge
Base article: https://mitel.custhelp.com.
• Queue reports
• Employee reports
• Agent reports
Note:
If employees follow our best practices of using agent group presence to control their
availability, these durations should be the same across an employee’s agents.
Multimedia queue reports provide statistics on queues and queue groups that reflect
multimedia behavior and the service experienced by clients.
Note:
The Queue Group Multimedia by Queue with Agent Information report displays the
following queue performance information.
The Multimedia Queue Group Multimedia by Queue with Agent Information report
displays the following agent information.
Figure 166: Multimedia Queue Group Multimedia by Queue with Agent Information
Note that the ‘Media server name’ field indicates the type of interaction to which the
statistics pertain. For example, the queue’s chat statistics are located in the same row as
the chat server.
The Multimedia Queue Group Performance by Queue report provides the following
information
Note:
The report is broken down by the queues comprising the queue group. This enables
supervisors to view performance statistics for multiple queues, within a single report.
(See the following figure.)
The Multimedia Queue Group Performance by Queue by Account Code report provides
the following information.
Note:
Note:
Note that Media server values indicate the queues to which the statistics pertain. For
example, statistics for a chat queue are indicated by a chat media server.
Note:
• Unified Queue Groups can contain one email, one chat, and one SMS queue only.
• In networked ACD environments, the voice media server’s name in the Handled by
Hour and Available Agent by Hour graphs may differ. These names are accurate to
each 3300 ICP on which the devices are programmed.
The Unified Queue Group chart displays the following graphs and information.
Graph Description
Graph Description
In addition to the information displayed by the graphs listed above, the Unified Queue
Group chart displays the following information.
The Subtotal row for Total shift time (hh:mm:ss) displays only the highest logged shift
time for an employee’s agents. For example, if an employee’s chat agent worked a four-
hour shift and their email agent worked a five-hour shift, the Subtotal row displays five
hours.
The Multimedia Employee Group by Employee by Agent report provides the following
information.
Total shift time (hh:mm:ss) the total time the employee's agent was
logged into the system
Note:
Note:
queue. It reports the interaction statistics in hours, minutes, and seconds, and provides
interaction counts across employees. (See the following figure.)
Shift duration the total time the agent was logged into
the system
ACD handling time (hh:mm:ss) the amount of time, excluding hold, spent
completing interactions sent to the queue
Note:
Average ACD handling time (hh:mm:ss) the average amount of time, excluding
hold, spent completing interactions sent to
the queue
You can use the Multimedia Employee Inbound Trace report to determine how
interactions are being handled in your organization. For example, you can see if
requeues are occurring or if interactions are bouncing from queue to queue.
Note:
Note:
‘Cause’ refers to email, chat, and SMS segment reasons. 'Call type' refers to voice
segment reasons.
• Suppress visual formatting for improved readability if you want to format the report in
Excel.
The following table defines the reasons for chat, email, and SMS segments in the
Multimedia Employee Inbound Trace report.
Table 14: Multimedia Employee Inbound Trace Reason type: Chat, email, and SMS
Reason Description
Reason Description
The following table defines the reasons for voice segments. A description of the fields in
the report follows.
Reason Description
Reason Description
Internal ACD requeued an internal, ACD call was sent back to the
queue after being offered to an agent
Local ACD requeued a local, ACD call was sent back to the
queue after being offered to an agent
Reason Description
The Multimedia Employee Inbound Trace report provides the following information:
Multimedia Agent reports provide statistics on agents and agent groups that reflect
multimedia behavior and the service experienced by clients.
Note that the media server field indicates the type of interaction to which the statistics
pertain. For example, the agent’s chat statistics are located in the same row as the chat
server.
The Multimedia Agent Group by Media Server by Agent report provides the following
information:
Note:
Total shift time (hh:mm:ss) the total time the agent was logged into
the system
You can use the Multimedia Agent Group Inbound Trace report to determine how
interactions are being handled in your organization. For example, you can see if
requeues are occurring or if interactions are bouncing from queue to queue.
Note:
• For email, interaction segments represent one exchange between agent and
customer. A single interaction will not represent an ongoing email exchange.
• We do not recommend printing this report due to its size. However, if you do wish
to print this report, please modify the size manually as it spans multiple pages.
• If an employee or an agent group contains MiVB Voice Agents using Classification
Codes, then these codes will not be displayed in the Multimedia Agent Group
Inbound Trace Report.
You can filter the Multimedia Agent Group Inbound Trace report to
• Include only specific types of interaction reasons (select from ‘Cause’ and ‘Call type’
lists provided)
Note:
‘Cause’ refers to email, chat, and SMS segment reasons. 'Call type' refers to voice
segment reasons.
• Suppress visual formatting for improved readability if you want to format the report in
Excel.
The following table defines the reasons for chat, email, and SMS segments in the
Multimedia Agent Group Inbound Trace report.
The following figure provides an example of a Multimedia Agent Group Inbound Trace
report.
Table 16: Multimedia Agent Group Inbound Trace Reason type: Chat, email, and
SMS
Reason Description
Reason Description
Reason Description
The following table defines the reasons for voice segments. Reason applicability varies
by media type. A description of the fields in the report follows.
Table 17: Multimedia Agent Group Inbound Trace Reason type: Voice
Reason Description
Internal ACD requeued an internal, ACD call was sent back to the
queue after being offered to an agent
Reason Description
Local ACD interflowed a local, ACD call was redirected to another answer point
, such as another queue or voicemail
Local ACD requeued
a local, ACD call was sent back to the
queue after being offered to an agent
Local ACD unavailable the device was unavailable to receive a local, ACD call
Unknown
an unknown reason occurred
The Multimedia Agent Group Inbound Trace report provides the following information
• Schedules reports
• Employee Portal reports
You can optionally filter the Detailed Schedule by Employee with Totals report based on
the following variables
The Workforce Scheduling Detailed Schedule by Employee with Totals report provides
the following schedule information:
Assigned time off the time off type assigned to the employee
The Workforce Scheduling Schedule by Employee by Time Off by Day of Week report
provides the following schedule information:
Day of the week the day of the week for which employees
are scheduled for time off
You can filter the Workforce Scheduling Schedule Coverage Totals by Type report based
on the following event totals
• Forecasted
• On break
• Scheduled
• Non ACD job
• ACD job
• At work
• Over/Under
• Overtime
The Workforce Scheduling Schedule Coverage Totals by Type report provides the
following schedule information:
Weekday name (Day, Month, Year) the day of the year for which the
employee is scheduled, where T is time
off, S is shift, and U is unavailable
Note:
• If you want to run this report for a large number of employees, do so by creating
and selecting an employee group containing all of the employees you want to
report on, otherwise, if the list of employees is excessively long, some selected
employees may be excluded from the report.
• If you choose to run this report over a seven-day span, the final report will instead
contain two weeks of data. The least number of days you can produce this report
for is nine days because the report needs at least nine columns to support the
report banner structure.
Weekday name (Day, Month, Year) the day of the year for which the
employee is scheduled, where T is time
off, S is shift, and U is unavailable
Day of the week the day of the week for which employees
are scheduled for time off
The Work Hours Summary Schedule by Employee report provides the following schedule
information:
Total paid hours scheduled the total number of paid hours scheduled
for the employee from start to end, for
Average paid hours per shift the average number of hours the
employee works per shift
The Employee Portal Availability Requests report provides the following schedule
information:
Current availability by day of week the current availability for the specified
day of the week
Availability change request by day of week the requested availability for the specified
day of the week
Current availability by time of day - start the time the employee is currently
available to work for the specified time of
day
Availability change request by time of day the requested availability for the specified
- start time of day
Current availability by time of day - end the time the employee is currently
available to work for the specified time of
day
Availability change request by time of day the requested availability for the specified
- end time of day
The Employee Portal Shift Change Status report provides the following schedule
information:
Offered shift name the name of the shift that the employee is
offering
New shift name the name of the shift the employee is now
scheduled to work
The Employee Portal Shift Requests report provides the following schedule information:
Offered shift name the name of the shift that the employee is
offering
Offered shift start time the time at which the shift being offered
begins
Offered shift end time the time at which the shift being offered
ends
New shift name the name of the shift being offered for
trade by the proposing employee
Proposed shift start time the time at which the shift being offered for
trade begins
Proposed shift end time the time at which the shift being offered for
trade ends
The Employee Portal Time Off Requests report provides the following schedule
information:
Time off request - start the start date and time of the time off
request
Time off request - end the end date and time of the time off
request
Note:
Calls display as two segments in Trace reports if you use route optimization. The first
segment indicates the pre-optimized talk time (indicated by an r in the SMDR record),
and the second segment indicates the post-optimized talk time (indicated by an R in
the SMDR record). In Trace reports, combining the talk time for these two segments
represents the length of the call.
The Schedule Adherence Employee Adherence Trace report provides the following
schedule information:
Out of adherence start time the time at which the employee entered
the out of adherence state
Out of adherence end time the time at which the out of adherence
employee began adhering to the
scheduled event
Scheduled event start time the time at which the employee was
scheduled to start the scheduled event
Scheduled event end time the time at which the employee was
scheduled to end the scheduled event
The Schedule Adherence Employee Group Adherence by Period report provides the
following schedule information:
The Schedule Adherence Employee Group Time Out of Adherence by Day of Week/
Month report provides the following schedule information:
Schedule shift duration (hh:mm:ss) the duration of time for which the
employee was scheduled
Actual shift duration (hh:mm:ss) (by Day the duration of the employee's scheduled
of Month report only) shift, not including time spent out of
adherence
Total in adherence duration (hh:mm:ss) the duration of time the employee spent
adhering to the schedule
Total out of adherence duration the duration of time the employee spent
(hh:mm:ss) out of adherence with the schedule
Percent of shift out of adherence the percent of time the employee spent
out of adherence with the schedule
Total out of adherence time for breaks the percent of time the employee spent
only (by Day of Month report only) out of adherence with the scheduled
breaks
Total out of adherence time for shifts only the percent of time the employee spent
(by Day of Month report only) out of adherence with the scheduled shifts
Total out of adherence time for jobs only the percent of time the employee spent
(by Day of Month report only) out of adherence with the scheduled jobs
Out of adherence count (by Day of Week the number of times the employee was
report only) out of adherence during the scheduled
shift
Schedule name (by Day of Week report the name of the schedule for which the
only) employee was scheduled for the shift
Figure 187: Employee Group Time Out of Adherence by Employee by Day of Week
16 IVR Routing reports
IVR Routing reports summarize data on select devices to enable supervisors to make
informed decisions regarding the future of their contact center. Workflow reports are also
available for IVR Routing workflows. See "Workflow reports" for more information.
• Callback reports
• Port reports
Note:
To run Port reports, select Reporter > IVR Routing > Enterprise reports.
• DNIS reports
• Hunt Group reports
Note:
To run Hunt Group reports, select Reporter > IVR Routing > Enterprise reports.
• Agent reports
Note:
To run Agent reports, select Reporter > IVR Routing > Callback.
The IVR Routing Callback Queue Performance by Agent report provides the following
information:
Report Description
Field
Callbacks the number of callbacks that rang the agent and were answered
answered
Callbacks the number of callbacks where the agent connected to either the
handled customer or to voicemail
Handling time the total duration of callback calls, from when the calls are answered
(hh:mm:ss) to when they are disconnected (including hold time and transfer/
conference time)
Average the average duration of callback calls, from when the calls are
handling time answered to when they are disconnected (including hold time and
(hh:mm:ss) transfer/conference time)
Report Description
Field
Callbacks the number of callbacks where the agent declined to complete the
rejected by callback
agent
The IVR Routing Callback Queue Performance by Period report provides the following
information:
The IVR Routing Callback Queue Group Performance by Agent report provides the
following information:
The IVR Routing Callback Queue Group Performance by Period report provides the
following information:
Total callbacks offered the total number of callbacks that entered the
queue [New + Requeues]
New callback presented the number of new callbacks that entered the
queue group’s callback queue(s)
Handling time (hh:mm:ss:) the total duration of callback calls, from when the
calls are answered to when they are disconnected
(including hold time and transfer/conference time)
Average handling time (hh:mm:ss) the average duration of callback calls, from
when the calls are answered to when they are
disconnected (including hold time and transfer/
conference time)
Max retries exceeded the number of callbacks that will not be requeued
The IVR Routing Callback Queue Group Performance by Queue reports provides the
following information:
Note:
To run Port reports, select Reporter > IVR Routing > Enterprise reports
The IVR Routing Port Performance by Hunt Group report provides the following
information:
Total duration (hh:mm:ss) the total time that calls spent connected to
the port
Description
The IVR Routing Port Performance by Period report provides the following information:
Total duration (hh:mm:ss) the total time that calls spent connected to
the port
The IVR Routing DNIS Performance by Period report provides the following information:
IVR calls to queue the total number of calls that went from
the IVR to a queue
ACD calls abandoned (long) the number of ACD calls abandoned after
the Short Abandon time
Total time in system (hh:mm:ss) the total time calls spent in the system
(Time in IVR + Total ACD time to answer
+ Time to interflow + Time to abandon +
ACD handle time + Non ACD handle time
(includes hold time))
Average time in system (hh:mm:ss) the average time calls spent in the system
(Time in IVR + Total ACD time to answer
+ Time to interflow + Time to abandon +
ACD handle time + Non ACD handle time
(includes hold time))
Total time in IVR (hh:mm:ss) the total amount of time calls spent in the
IVR
Average time in IVR (hh:mm:ss) the average amount of time calls spent in
the IVR
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
ACD time to answer (hh:mm:ss) the total amount of time before all ACD
calls were answered
Average ACD time to answer (hh:mm:ss) the average amount of time before ACD
calls were answered
ACD time to abandon (hh:mm:ss) the elapsed time before the call was
abandoned
Average ACD time to abandon (hh:mm:ss) the average time before the call was
abandoned
ACD time to interflow (hh:mm:ss) the elapsed time before the call was
interflowed
Average ACD time to interflow (hh:mm:ss) the average elapsed time before the call
was interflowed
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
The IVR Routing DNIS Group Performance by DNIS report provides the following
information:
IVR calls to queue the total number of calls that went from
the IVR to a queue
ACD calls abandoned (long) the number of ACD calls abandoned after
the Short Abandon time
Total time in system (hh:mm:ss) the total time calls spent in the system
(Time in IVR + Total ACD time to answer
+ Time to interflow + Time to abandon +
ACD handle time + Non ACD handle time
(includes hold time))
Average time in system (hh:mm:ss) the average time calls spent in the system
(Time in IVR + Total ACD time to answer
+ Time to interflow + Time to abandon +
ACD handle time + Non ACD handle time
(includes hold time))
Total time in IVR (hh:mm:ss) the total amount of time calls spent in the
IVR
Average time in IVR (hh:mm:ss) the average amount of time calls spent in
the IVR
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
ACD time to answer (hh:mm:ss) the total amount of time before all ACD
calls were answered
Average ACD time to answer (hh:mm:ss) the average amount of time before ACD
calls were answered
ACD time to abandon (hh:mm:ss) the elapsed time before the call was
abandoned
Average ACD time to abandon (hh:mm:ss) the average time before the call was
abandoned
ACD time to interflow (hh:mm:ss) the elapsed time before the call was
interflowed
Average ACD time to interflow (hh:mm:ss) the average elapsed time before the call
was interflowed
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
The IVR Routing DNIS Group Performance by DNIS by Period report provides the
following information:
IVR calls to queue the total number of calls that went from
the IVR to a queue
ACD calls abandoned (long) the number of ACD calls abandoned after
the Short Abandon time
Total time in system (hh:mm:ss) the total time calls spent in the system
(Time in IVR + Total ACD time to answer
+ Time to interflow + Time to abandon +
ACD handle time + Non ACD handle time
(includes hold time))
Average time in system (hh:mm:ss) the average time calls spent in the system
(Time in IVR + Total ACD time to answer
+ Time to interflow + Time to abandon +
ACD handle time + Non ACD handle time
(includes hold time))
Total time in IVR (hh:mm:ss) the total amount of time calls spent in the
IVR
Average time in IVR (hh:mm:ss) the average amount of time calls spent in
the IVR
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
ACD time to answer (hh:mm:ss) the total amount of time before all ACD
calls were answered
Average ACD time to answer (hh:mm:ss) the average amount of time before ACD
calls were answered
ACD time to abandon (hh:mm:ss) the elapsed time before the call was
abandoned
Average ACD time to abandon (hh:mm:ss) the average time before the call was
abandoned
ACD time to interflow (hh:mm:ss) the elapsed time before the call was
interflowed
Average ACD time to interflow (hh:mm:ss) the average elapsed time before the call
was interflowed
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
The IVR Routing DNIS Group Performance by Period report provides the following
information:
IVR calls to queue the total number of calls that went from
the IVR to a queue
ACD calls abandoned (long) the number of ACD calls abandoned after
the Short Abandon time
Total time in system (hh:mm:ss) the total time calls spent in the system
(Time in IVR + Total ACD time to answer
+ Time to interflow + Time to abandon +
ACD handle time + Non ACD handle time
(includes hold time))
Average time in system (hh:mm:ss) the average time calls spent in the system
(Time in IVR + Total ACD time to answer
+ Time to interflow + Time to abandon +
ACD handle time + Non ACD handle time
(includes hold time))
Total time in IVR (hh:mm:ss) the total amount of time calls spent in the
IVR
Average time in IVR (hh:mm:ss) the average amount of time calls spent in
the IVR
ACD handling time (hh:mm:ss) the total duration of ACD calls, from when
the calls are answered to when they are
disconnected (including hold time and
transfer/conference time)
Average ACD handling time (hh:mm:ss) the average duration of ACD calls, from
when the calls are answered to when they
are disconnected (including hold time and
transfer/conference time)
ACD time to answer (hh:mm:ss) the total amount of time before all ACD
calls were answered
Average ACD time to answer (hh:mm:ss) the average amount of time before ACD
calls were answered
ACD time to abandon (hh:mm:ss) the elapsed time before the call was
abandoned
Average ACD time to abandon (hh:mm:ss) the average time before the call was
abandoned
ACD time to interflow (hh:mm:ss) the elapsed time before the call was
interflowed
Average ACD time to interflow (hh:mm:ss) the average elapsed time before the call
was interflowed
Non ACD handling time (hh:mm:ss) the total duration of non-ACD calls
(including hold time and transfer/
conference time)
Note:
To run IVR Routing Hunt Group reports, select Reporter > IVR Routing >
Enterprise reports.
The IVR Routing Hunt Group Performance by Period report provides the following
information:
Total inbound calls the total inbound calls handled by the hunt
group
Total duration (hh:mm:ss) the total length of time for all calls handled
The IVR Routing Hunt Group Performance by Port report provides the following
information:
Total duration (hh:mm:ss) the total time that calls spent connected to
the port
Note:
To run IVR Routing Agent reports, select Reporter > IVR Routing > Callback.
The IVR Routing Agent Performance by Callback Queue report provides the following
information:
Callbacks presented the total number of callbacks presented to the agent (Handled
+ Requeued + Rejected)
Callbacks answered the number of callbacks that rang the agent and were
answered
Callbacks handled the number of callbacks where the agent connected to the
customer or voicemail
Handling time the total duration of callback calls, from when the calls are
(hh:mm:ss) answered to when they are disconnected (including hold time
and transfer/conference time)
Average handling time the average duration of callback calls, from when the calls are
(hh:mm:ss) answered to when they are disconnected (including hold time
and transfer/conference time)
Callbacks rejected by the number of callbacks where the agent declined to complete
agent the callback
The IVR Routing Agent Group Performance by Callback Queue report provides the
following information:
Traffic Analysis reports are not available in real-time. In order to have summarized data
for Traffic Analysis reports you must wait until the nightly maintenance routine runs the
summary (at midnight each night). Alternatively, you can click Summarize Data on the
Management Console to summarize immediately. The data for these reports is derived
from the traffic stream.
Traffic Analysis reports provide call statistics on DTMF receivers, route lists, route plans,
routes, and trunks. You can create on-demand and scheduled reports.
Note:
Average service time is output from the Mitel telephone system and not calculated by
Traffic Analysis.
The Attendant Console Traffic by Period report provides the following information:
Logout time (hh:mm:ss) the time at which the attendant logged out
Duration of attendant shift (hh:mm:ss) the duration the attendant was logged in
First login time (hh:mm:ss) the time at which the attendant first logged
in
Last logout time (hh:mm:ss) the time at which the attendant last logged
off
Duration of attendant shift (hh:mm:ss) the total duration the attendant was
logged in. Total shift time is not
necessarily the difference between the
first login and the last logout. An attendant
who logs in at 8:00 A.M. and logs out at
noon, then logs in at 1:00 P.M. and logs
out at 3:00 P.M. would have a total shift
time of 6 hours.
The Attendant Group Traffic by Period report provides the following information:
The DTMF Receiver Group Traffic by Period report provides the following information:
The Route Plan Traffic by Period report provides the following information:
Peak outbound time lists the busiest traffic day and hour, and
the busiest traffic peg
Peak outbound peg the date and hour during which the route
plan was most in use. The time displayed
is the ending time of the busy hour. For
example, if the route plan was busiest
between 13:15 P.M. and 14:15 P.M., 14:15
P.M. will be displayed as the busiest hour.
Total outbound usage (hh:mm:ss) the total duration of outgoing calls on the
route plan for the activity period
The Route List Traffic by Period report provides the following information:
Peak outbound time the date and hour during which the route
list was most in use. The time displayed
is the ending time of the busy hour. For
example, if the route list was busiest
between 13:15 P.M. and 14:15 P.M., 14:15
P.M. will be displayed as the busiest hour.
Peak outbound peg the number of calls the route list handled
during the busiest hour of the day
Total outbound usage (hh:mm:ss) the total duration of outgoing calls on the
route list for the activity period
Peak outbound time the date and hour during which the route
was most in use. The time displayed is
the ending time of the busy hour. For
example, if the route was busiest between
13:15 P.M. and 14:15 P.M., 14:15 P.M. will
be displayed as the busiest hour.
Total overflow peg the total count of when a route could not
be accessed due to busy conditions but
another route was taken
Note:
MiContact Center does not support Traffic reporting for SIP Trunks.
The Trunk Busy Hour Traffic by Day of Week report provides the following information:
Busiest start hour the hour at which the trunk starts being
the busiest for the day
Busiest end hour the hour at which the trunk ends being the
busiest for the day
Total usage (hh:mm:ss) the total duration of the use of the trunk
for the day
Low peg high usage Yes indicates a low number of call counts
but a high value for duration (suggesting
the trunk is not releasing properly). When
this column contains Yes only, the total will
indicate Yes.
High peg low usage Yes indicates a high number of call counts
but a low value for duration (suggesting
there could be a problem accessing the
trunk). Only one Yes is necessary in this
column for the total to indicate Yes.
The Trunk Traffic Usage by Day of Week report provides the following information:
Monday usage (hh:mm:ss) the duration of the calls that used the
trunk/trunk group Monday
Tuesday usage (hh:mm:ss) the duration of the calls that used the
trunk/trunk group Tuesday
Wednesday usage (hh:mm:ss) the duration of the calls that used the
trunk/trunk group Wednesday
Thursday usage (hh:mm:ss) the duration of the calls that used the
trunk/trunk group Thursday
Friday usage (hh:mm:ss) the duration of the calls that used the
trunk/trunk group Friday
Saturday usage (hh:mm:ss) the duration of the calls that used the
trunk/trunk group Saturday
Sunday usage (hh:mm:ss) the duration of the calls that used the
trunk/trunk group Sunday
The Trunk Group Outgoing Busy Hour Traffic by Day of Week report provides the
following information:
Busiest start hour the hour at which the trunk starts being
the busiest for the day
Busiest end hour the hour at which the trunk ends being the
busiest for the day
Figure 213: Trunk Group Outgoing Busy Hour Traffic by Day of Week
The Trunk Group Outgoing Traffic by Period report provides the following information:
The Trunk Group Outgoing Traffic Usage by Day of Week report provides the following
information:
Monday usage (hh:mm:ss) the duration of the calls that used the
trunk/trunk group Monday
Tuesday usage (hh:mm:ss) the duration of the calls that used the
trunk/trunk group Tuesday
Wednesday usage (hh:mm:ss) the duration of the calls that used the
trunk/trunk group Wednesday
Thursday usage (hh:mm:ss) the duration of the calls that used the
trunk/trunk group Thursday
Friday usage (hh:mm:ss) the duration of the calls that used the
trunk/trunk group Friday
Saturday usage (hh:mm:ss) the duration of the calls that used the
trunk/trunk group Saturday
Sunday usage (hh:mm:ss) the duration of the calls that used the
trunk/trunk group Sunday
Workflow reports summarize data on IVR Routing and Multimedia Contact Center
workflows. These reports are available to customers licensed for IVR Routing and
Multimedia Contact Center.
• Condition reports
Workflow Condition reports summarize data on conditions contacts meet and the
workflow branches contacts follow.
Workflow Condition reports require that, when configuring workflow activities, ‘Child
Reporting Enabled’ is selected for any relevant branches and conditions. If ‘Child
Reporting Enabled’ is not selected, the branch or condition does not display as a
reportable option. See either the MiContact Center Business Installation and Administration
Guide or the Multimedia Contact Center Installation and Deployment Guide for more
information on workflow activity configuration.
Note:
For Multimedia Contact Center, Workflow Condition reports display statistics for one
workflow per media server.
• Branch by Condition
• Condition by Branch
• Condition by Condition
Number of times terminated in branch by the number of times the interaction ended
user in the branch because the customer/client
disconnected
Number of times terminated in branch by the number of times the interaction ended
user in the branch because the customer/client
disconnected
Number of times terminated in branch by the number of times the interaction ended
user in the branch because the customer/client
disconnected
The Employee report shows all the employee data entered in YourSite Explorer under
YourSite > Employee. (See the following figure.)
A more extensive list of MiContact Center Business terms and definitions, beyond reporting,
can be found in the Micontact Center Business User Guide.
About reports
You can create on-demand or scheduled reports. Your licensing of MiContact Center
Business determines the report types available to you.
On-demand reports
Using the Reporter application, you can generate on-demand reports immediately.
Scheduled reports
Using the Scheduled reports application, you can set up timetables for generating future
reports at specific times and on specific days.
At an interval you can configure, MiContact Center Business–Contact Center Reporter service
seeks print and email jobs and attempts to process them. Clicking the report in your Report
Inbox displays the status of your printing and emailing jobs. Reporter Service must be running
at all times in order to print and email reports automatically.
All of your reports displays all of the reports generated under your user name over the last 30
days.
Today’s reports
Today’s reports displays all of the reports generated today under your user name.
Yesterday’s reports
Yesterday’s reports displays all of the reports generated yesterday under your user name.
Voice reports
Voice reports provide detailed information about call performance. Voice statistics are
collected when the client calls the contact center and communicates via telephone. Voice
reports can be run on the following devices: Agent and Agent Group, Queue and Queue
group, Employee and Employee group, Team, Extension, Trunk, Forecast, and DNIS.
Conversation Detail reports provide detailed information on events generated during the life
of a contact. Conversation Detail reports can be run on the following devices: Agent group,
Queue and Queue group, Employee and Employee group, Site, Media server, and Account
Code and Account Code group. You can run these reports if you are licensed for Multimedia
Contact Center. You cannot run Conversation Detail reports against Voice devices.
Email reports
Email reports provide detailed information about email performance. Email statistics are
collected when the client contacts the agent and communicates via email. Email reports have
the following report types: Agent, Agent Group, Queue, and Queue Group.
Chat reports
Chat reports provide detailed information about chat performance. Chat statistics are collected
when the client contacts the agent and communicates via a real-time conversation online.
Chat reports have the following report types: Agent, Agent Group, Queue, and Queue Group.
SMS reports
SMS reports provide detailed information about SMS performance. SMS statistics are
collected when the client contacts the agent and communications via SMS interactions. SMS
reports have the following report types: Agent, Agent Group, Queue, and Queue Group.
Multimedia reports
Multimedia reports provide detailed information across media types: voice, email, chat, and
SMS. Multimedia reports enable you to compare performance across media types. Multimedia
reports have the following report types: Agent Group, Queue, Queue Group, Unified Queue
Group, and Employee Group.
Workflow reports
Workflow reports summarize data on IVR Routing and Multimedia workflows. These reports
are available to customers licensed for IVR Routing and Multimedia Contact Center
Scheduling reports provide detailed information about schedules. Scheduling reports have the
following report types: Agent and Agent Group.
Reporting terms and definitions 10
This glossary contains terms that pertain to the entire MiContact Center Business–reporting
suite. Some of these concepts may not be applicable to your version of MiContact Center
Business .
A more extensive list of MiContact Center Business terms and definitions, beyond reporting,
can be found in the MiContact Center Business User Guide.
Abandoned
An abandoned call is one where the client hangs up before the call is answered. An
abandoned chat is one where the client ends the chat before an agent opens the session.
Abandoned statistics are not applicable to email and SMS.
Abandoned (long)
Abandoned (long) calls/chats are calls/chats that end with an abandon time > Short Abandon.
You define the Short Abandon you want in YourSite Explorer under YourSite > Queues. The
Short Abandon default is 6 seconds. If a caller hangs up after waiting 7 seconds, the call
is considered a long abandon. These long abandoned calls/chats are included in call/chat
statistics.
Abandoned (short)
Abandoned (short) calls/chats are calls/chats that end with an abandon time <= Short
Abandon. You define the Short Abandon you want in YourSite Explorer under YourSite >
Queues. The Short Abandon default is 6 seconds. For example, if a caller hangs up after
waiting just 6 seconds or less, the call is considered a Short Abandon. Short Abandon calls
are not included in call statistics.
See Offered.
ACD path
An ACD path is a predefined route that a call follows before reaching an agent. ACD paths
direct callers to the agents or agent groups best suited to handle the calls. For example, a
contact center can have an ACD path for sales, which routes callers to the agents taking
sales orders.
The ACD true-talk time is the duration of an ACD call, from when an agent answers the call to
when it is disconnected. The ACD true-talk time excludes hold time.
ANI
The average speed of answer (ASA) is a statistic measuring how long the average caller
waits on hold before the call is picked up by a queue member (including time in queue and
ringing time).
Calls answered
See Handled.
Call load
Call load refers to the aggregate effect of the number of calls received by the ACD queue and
their duration, or the calls offered x (average handling time + average wrap-up time).
Calls waiting
Calls waiting is the number of callers in queue waiting for a member to become available,
including those listening to silence, music, or a recorded announcement.
Delayed interaction
DNIS
Dialed Number Identification Service (DNIS) is a feature of toll-free lines that provides the
number the caller dials. This assists queue members who handle calls for more than one
business or product line. Each business or product line has its own toll-free number. When
a caller dials a toll-free number, the ACD routing system forwards information to the queue
member, so the member can identify whom the caller dialed.
DND
Do Not Disturb (DND) is a state that prevents queue members from receiving inbound
interactions and transfers. For agents, Do Not Disturb is an employee-level configuration.
When an employee is in Do Not Disturb, they enter Do Not Disturb across all agent
capabilities.
Enterprise
The enterprise is all of the contact center sites that comprise your company. The enterprise
consists of the single site where the Enterprise Server is installed and all branch offices.
Erlang
An Erlang measures telephone traffic, or the flow of calls and call attempts to your contact
center during a given period of time. One Erlang equals one hour or 60 x 60 = 3,600 seconds
of telephone interaction. This could be one call lasting 1 hour, six calls lasting 10 minutes,
or any combination of calls and call durations which equal 60 minutes. The Erlang series
of formulae provide a mathematical basis for making predictions about randomly arriving
workloads.
Erlang C
The Erlang C equation is commonly used for queue member and delay calculations where
ACD queuing is involved. It predicts the resources required to keep wait (delay) times within
your Service Level objective. The Erlang C formula uses your historical Call Load data and
the Service Level Percentage, Service Level Time, and Wrap-Up Time you specify and
predicts the member requirement for the time interval and date range in the forecast.
Extension
An extension is an endpoint for answering calls. Extensions can be either assigned to Ring
Groups or logged into by agents.
Handled
A handled interaction is an interaction opened by a queue member. Calls that listen to in-
queue RAD messages are not considered to be handled until a queue member connects.
Handling time
For calls, the handling time is from when a queue member answers the call to when it is
disconnected (including hold time and transfer/conference time). If the member handling the
call interactions the supervisor for information (while the caller is on hold) and/or transfers or
conferences the call, these times are added to the ACD Handling Time value.
For example, a queue member speaks to a caller for two minutes and then puts the caller
on hold for three minutes and tries to solve the problem. This might include a call to the
supervisor. The member then initiates a conference call with the caller and a third party and
they speak for three minutes and resolve the issue. Therefore, the ACD handling time for the
member is 2 + 3 + 3 = 8 minutes.
For email and SMS, the handling time is from when the member opens the interaction to
when they send the reply, transfer the interaction, or classify the interaction as Junk or
requiring No Reply, from the Inbox. For chats, the handling time starts when the queue
member opens the chat and ends when either the member or the client ends the chat.
Inbound
Interflowed
Logged on
An agent is logged on when the agent signs in to the ACD routing system. The agent might or
might not be ready to receive interactions.
Logged off
An agent is logged off when the agent signs out of the ACD routing system.
Longest waiting
The longest waiting is the duration, in minutes and seconds, of the interaction that has been
waiting the longest in queue.
Make Busy
Make Busy is an agent state in which an agent is unavailable to the ACD path queue. Voice
Agents in Make Busy are able to receive non-ACD calls. Make Busy is an employee-level
configuration. When an employee is in Make Busy, they enter Make Busy across all agent
capabilities.
The Make Busy statistic displays differently in Trace reports than Performance and Event
reports. In Trace reports, the Make Busy statistic indicates the total duration from the time
when the agent entered the Make Busy state to the time they left the Make Busy state. In
Performance and Event reports, this statistic does not include time spent in an overriding
state. For example, if an agent in Make Busy receives a transferred ACD interaction, she
can be simultaneously in Make Busy and in an ACD state. Her Make Busy statistic in the
Performance and Event reports will not include the time she was simultaneously in an ACD
state.
Media server
The media servers are the means by which the client communicates with you. The Media
server field defines the media server against which you are running the report.
Non-ACD
The non-ACD true talk time is the duration of a non-ACD call, from when an agent answers
the call to when it is disconnected. The true talk time excludes hold time.
Offered
All interactions received by the queue, regardless of how they are handled or routed, are
referred to as offered interactions. Offered interactions include ACD handled interactions,
abandoned (long) interactions, and interflowed interactions. ACD requeued interactions,
Queue unavailable interactions, and abandoned (short) interactions are not considered. ACD
routing system data on the offered interactions and Average Talk Time is used by the Erlang
C equation in calculating the queue members required.
Overflow
The term overflow refers to a mechanism that limits the delay faced by clients by queuing
ACD interactions against two or more agent groups. An ACD interaction that cannot be
answered immediately is placed in an ACD path queue. If the interaction is not answered after
a set amount of time (the overflow time), it is placed in the ACD path queue of another agent
group, in addition to keeping its place in the first queue. The first available agent in either
group handles the interaction.
Quality of service
The quality of service reflects an agent’s ability to provide excellent assistance to each client.
Queue member
A queue member is an individual answering for the queue. For ACD paths queues, ‘members’
refers to agents in the queue’s answering agent groups. For Ring Groups, ‘members’ refers to
the extensions assigned to the Ring Groups.
Queue unavailable
Queue unavailable is a routing option that reroutes calls to an unavailable answer point/
overflow point. Queues are unavailable when the call enters the system outside business
hours, and when all queue members have removed their presence. , when all queue
members are in DND, or when the queue has been placed in DND. Calls interflowed before
the Short Abandon time are included in Queue Unavailable statistics. Queue unavailable
statistics are applicable to voice only.
Schedule adherence
The term schedule adherence describes whether or not agents are performing activities
they are scheduled to be doing. Workforce management tools keep supervisors informed of
discrepancies between agents’ work schedules and the actual activities they perform.
Reporting number
The term reporting number refers to the number assigned to devices for reporting purposes.
Requeued
When an agent receives an ACD interaction and fails to accept the interaction within a certain
period of time, the system places the agent in Make Busy and requeues the interaction
(places the call back in the same ACD path queue) and offers it to the next available agent.
For multimedia, requeued contacts are interactions that the agent declined or did not open
before the requeue timer expired, or interactions that were requeued after being on hold past
the permitted time. Interactions can also requeue if the agent logs out while the interaction is
in the Inbox
Ring Group
Your Queue Service Objective might require queue members to handle 80% (Service Level
Percent) of interactions within 120 seconds (Service Level Time). You specify the Queue
Service Objective under YourSite Explorer under YourSite > Queues.
The Service Level Percent is the total number of interactions which are handled, abandoned,
and interflowed before a defined threshold time (Service Level Time), compared to the total
number of interactions handled, abandoned, and interflowed. The Service Level Percent =
(interactions answered + interactions abandoned (long) + interactions interflowed (long))
within the specified Service Level Time ÷ (interactions answered + interactions abandoned
(long) + interactions interflowed (long)).
The Service Level Time is the threshold time used in calculating the Queue Service Objective.
Your Queue Service Objective might be for your queue members to handle 80% (Service
Level Percent) of interactions within 120 seconds (Service Level Time). You specify the
Queue Service Objective under in YourSite Explorer under YourSite > Queues.
SQL
Structured Query Language (SQL) is the language used to talk to popular Relational
Database Management Systems (RDBMSs). SQL is a standard query language that can
be used to enter, query, and change data in a database. SQL is also used to create and
administer databases. Administration of YourSite is done using Microsoft’s SQL Server, a
database management system.
Talk time
Time to answer
Time to answer is the number of seconds from the time an incoming external request enters
the queue until the request is answered. This does not include the duration the request waits
in queue outside of regular business hours for the queue.
Trunk load
The trunk load includes the time from when a trunk picks up a call until the queue member
finishes speaking to the caller and disconnects. The trunk load does not include Wrap-up
time.
Workforce management
Wrap-up time
Wrap-up time is a real-time and reporting statistic detailing the total time an agent spends in
the Work Timer state.
Copyright 2022, Mitel Networks Corporation. All Rights Reserved. The Mitel word and logo are trademarks of
mitel.com Mitel Networks Corporation, including itself and subsidiaries and authorized entities. Any reference to third party
trademarks are for reference only and Mitel makes no representation of ownership of these marks.