
Issue 5.0 May 2005 101
Using reports for ACD planning
This section includes the following topics:
● Planning/engineering objectives on page 101
● Engineering ACD applications with report data on page 106
Planning/engineering objectives
Before presenting examples of how you can use the BCMS reports to optimize the
operations of an ACD application, this chapter reviews certain relevant points.
First, recall that the ACD hunt groups and trunk groups may be administered for:
● Internal measurements (BCMS)
● External measurements (CMS)
● Both internal and external measurements (BCMS and CMS)
● No measurements
Second, the ACD feature can support a maximum number of agents, splits, and trunk
groups. Since the BCMS feature may measure fewer agents, splits, and trunk groups,
those agents, splits, and trunk groups that are not measured with the BCMS feature either
are measured with external CMS or are not measured at all.
If you are planning to implement BCMS and you do not have accurate traffic information,
you can used defaults, which are based on an estimated volume of incoming traffic. The
primary purpose of the BCMS reports is to monitor the ACD application and provide
information that details how the splits, agents, and trunk groups are being used. By
analyzing these reports, you can determine the optimum number of agents and trunks
needed to support a given ACD application.
Your overall design of an ACD should be based on to what extent your business values a
lost or blocked call. For example, if the ACD split handles sales and each blocked or
dropped call represents potential lost revenue, it will probably be desirable to provide more
trunks than agents to minimize the lost calls. As a contrast, if the ACD split handles calls
from a captive customer base and each agent performs a significant amount of “After Call
Comentarios a estos manuales