
Using reports for ACD planning
102 BCMS Operations
Work” that results in an expense to your organization, it will probably be desirable to
provide fewer trunks than agents.
Finally, remember that the report scheduler allows only 50 reports each night. If you do not
need to view historical data on an hour-by-hour basis, or if you prefer to see data sorted by
entity (such as agents, splits, or VDNs) rather than sorted by time, you should use the
summary reports. These reports can include up to 30 entities at one time, and thus can
allow you to make better use of the 50 available scheduler slots.
This section includes the following topics:
● System status report on page 102
● Split status report on page 103
● VDN status report on page 103
● Trunk group report on page 104
● Agent report on page 104
● Split report on page 105
● VDN report on page 105
System status report
You should use the system status report (monitor bcms system) as the first step
toward determining how the ACD is functioning. This report displays data that details how
each split queue is currently functioning. Specifically, the report lists:
● The number of calls waiting in the queue (this includes calls ringing)
● The length of time that the oldest call has been queued
● The average length of time before calls are answered
● The number of agents that are available to receive ACD calls
● The number of calls that have abandoned
● The average length of time before a call abandons the queue
● The number of ACD calls that have been answered
● The average length of time the agents spend talking
● The average length of time the agents spend in ACW mode.
● The percentage of calls answered within service level.
If any of the numbers are not within their desired range, the individual splits should be
observed more closely using the split status report. Some of the more obvious indications
of a problem are:
● An excessive number of calls waiting in the queue, or a very old “oldest call.”
Comentarios a estos manuales