By Appointment to
His Majesty The King
Contact Centre Service Software
Cirrus Response Ltd
Epsom

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Cirrus eLearning
  • Contact Us
Lost-Image
  • Home
  • CIRRUS HALO
  • Supervisor
  • Reports

Callback Services Analysis

Written by Keith Winhall

Updated at July 14th, 2026

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • CIRRUS HALO
    Cirrus Learn Agent Supervisor Administrator Troubleshooting
  • CIRRUS CALM
    Getting Started Setup & Configuration Shift Templates Scheduling & Management Employees & People Reporting & Insights
  • CIRRUS DIGITAL
    Agents Supervisors Administrators
  • RELEASE NOTES
    Release FAQs CIRRUS HALO CIRRUS CALM CIRRUS DIGITAL
  • CUSTOMER BILLING
+ More

Table of Contents

Overview Report Example Before you begin Report views Report header Report metrics Report footer Use case example

Overview

The Callback Services Analysis report provides detailed information about callback requests created for Queue Callback services.

When callers are offered the option to request a callback instead of waiting in a queue, this report helps supervisors understand how those callback requests are handled. It shows request volumes, successful callbacks, failed attempts, waiting times and cancelled requests.

This report only includes callback requests that have been processed by a Queue Callback service.

Report Example

 
 

Before you begin

Keep the following in mind when using this report:

  • Queue Callback services are created automatically when callback is enabled on a Router through an Option Menu.
  • The report only displays data for Queue Callback services that have processed callback requests.
  • A callback request may be attempted several times if the caller does not answer. The maximum number of attempts is configured for the Queue Callback service.
  • If a caller successfully reaches the queue before their callback is made, the callback request is automatically cancelled.
  • A callback is considered successful even if it reaches voicemail or an answering machine.

Report views

The report can be displayed using different time aggregations, including:

  • Weekly summary
  • Weekday summary
  • Other available reporting periods based on your report configuration

Report header

The report header displays:

  • Report name
  • Report type
  • Reporting period
  • Selected Queue Callback service or services

Report metrics

The report includes the following metrics for each time segment.

Metric Description
Requested Total number of callback requests received.
Answered Number of callback requests successfully connected.
Answered First Attempt Number of callbacks successfully completed on the first outbound attempt.
Busy Number of callback attempts where the destination was busy.
No Answer Number of callback attempts where the customer did not answer.
Error Number of callback attempts that failed because of a dialling error, such as an invalid telephone number.
Cancelled Number of callback requests cancelled automatically by the system.
From Previous Days Callback requests carried over from previous days that were still waiting to be completed.
Average Waiting Average time between the callback request being created and the callback attempt being made.

Report footer

The report footer displays the date and time the report was generated.

Use case example

A contact centre offers customers the option to request a callback during busy periods instead of waiting in the queue.

The Operations Manager reviews the Callback Services Analysis report each morning to monitor how the callback service performed the previous day.

The report shows:

  • A high number of callback requests during the afternoon.
  • Most callbacks were completed successfully on the first attempt.
  • A significant number of callbacks were marked as No Answer between 5:00 pm and 6:00 pm.
  • The average waiting time for callbacks increased during the busiest period.

Using this information, the manager identifies that callback demand regularly exceeds available outbound capacity during late afternoons. They adjust staffing levels for the outbound team during peak periods and review the configured callback retry settings to improve the success rate.

Over the following weeks, the report confirms that average waiting times have reduced and a higher percentage of callbacks are being completed on the first attempt, helping improve the customer experience.

Do you think this article needs improving?

Yes
No
Give feedback about this article

Related Articles

  • Call Handling
  • How to Set Up Call Backs

Cirrus
The Coach House
17 West Street
Epsom, Surrey
KT18 7RL
Tel: 0333 103 3333
Email:
sales@cirrusconnects.com

Social: twitter linkedin

Privacy Policy

Postal address
Cirrus
The Coach House
17 West Street
Epsom, Surrey
KT18 7RL
Tel: 0333 103 3333
Email:
support@cirrusconnects.com

© Copyright Cirrus


Expand

Need help? Ask the Cirrus Helpbot