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 possible suggestions for further investigation and resolution.

Solving Problems using Queue Reports

What do I watch for in queue reports?

How do I find the source of the problem and resolve it?

Drop in Service Level

When does the Service Level drop during the day?

  • Check the Agent Group Performance by Period report to see the distribution of agents. How many agents were logged in throughout the day?
  • Examine agent talk times. Do you have a chatterbox agent?
  • Use Auditor to re-run events during a time interval to see exactly what each agent was doing.
  • Run a Forecast report with your Service Level goals to determine the number of agents required by period of the day. Compare the forecast statistics to the Average Manned Agent statistic in the Agent Group Performance by Period report. Do you have enough agents scheduled to meet your Service Level objective (for example, to answer 80% of calls within 20 seconds).
  • See Requeues


    Why are some queues not meeting their service level goals while others are?
  • Check the Agent Group Performance by Queue report. Are some agent groups overworked?

High abandon statistics

Why did the customers abandon their calls or sessions?

  • Check Average Delay to Abandon statistics. Did the customers abandon because they were impatient? Did customers wait a long time in queue? Were agent talk times excessive during this time? If so, why?
  • Using Auditor, re-run the interval to see exactly what each agent was doing.
  • Run the Queue Unavailable Trace* report and then call back the customers to determine why they abandoned their contacts.

High Call Requeue count
Increase in the Average Speed of Answer time
Decreased Service Level

Are agents forgetting to set themselves as Unavailable on their telephone sets before leaving their desks?

  • Check the Agent Group Performance by Period report to see which agents are experiencing Call requeues. Remind agents to use the Unavailable option.


Solving Problems using Agent Reports

What do I watch for in agent reports?

How do I find the source of the problem and resolve it?

Extremely high or low performance statistics

Are there agents who perform 20-30% better than other agents?

  • High ACD/Non-ACD/Outbound contact counts is not a problem if agents are maintaining high service levels. Silently monitor agents periodically to ensure they are providing a high quality of service, but not rushing callers.
  • 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. High counts relative to other agents could indicate that agents are 'padding' their ACD handle statistics by prematurely terminating calls.


    Are there agents who perform 20-30% worse than other agents?
  • Silent monitor agents periodically to ensure they are properly trained to handle callers' needs, and are not chatting unnecessarily.
  • Check Outbound or Non-ACD statistics for peg counts and times. Run an Agent Inbound or Outbound Trace* report to see a listing of all calls. Are agents spending too much time on personal calls?

High Unavailable statistics

Are agents accumulating Unavailable time and Make Busy peg counts?

  • Check the Agent Event by Period (hh:mm:ss) report to evaluate individual statistics. Determine how much Make Busy and Do Not Disturb (DND) time agents are logging. Be sure agents are adhering to your contact center policies regarding when to use Make Busy and Do Not Disturb. Check if your agents are using Unavailable instead of logging out.
  • For agents who have high Make Busy peg counts, run the Auditor with an Agent by Time monitor for the agent group. Be sure agents are not using Make Busy to avoid being the Longest Idle Agent or to avoid being routed the next ACD contact.
  • Implement Make Busy with Reason functionality. Assign reasons why agents go into the Make Busy state. Track Make Busy use by generating agent reports displaying Make Busy statistics by Code.

Long or short shift time

Are agents adhering to their schedules?

  • Examine the Agent Event by Period (hh:mm:ss) report to determine when agents are logging in and out. Check if they are logging in late, leaving early, or forgetting to log out at the end of the day.
  • Examine all of the login and logout times for the shift, and determine if agents are adhering to your contact center policies concerning when to log out and when to use Unavailable.