3CX reporting
Call, queue and agent reporting across all your 3CX systems, from £20 per month per server.
The built-in reports are fine for one site and one question. They are not built for comparing sites, planning rotas against real demand, or sitting next to your sales and service numbers. So someone exports a CSV every month and the picture is always a few weeks old.
Inbound, outbound, missed and abandoned, by hour, day, site and extension. Answer times and talk times against the targets you set.
Waiting times, abandonment, service level per queue, and how each queue behaves across the day so rotas follow demand rather than habit.
Calls handled, availability, average handling time and outcomes per agent, comparable across teams and sites on the same definitions.
Wrap-up codes recorded at the end of each call, so you can report on why customers call and whether it was resolved, not just that the phone rang.
Six report pages, set up around your queues, sites and targets. Shown here with sample data.
Installed in minutes on Debian or Windows, it reads the call detail records and queue events as 3CX writes them. No change to how calls are handled and nothing in the call path.
Records are sent over HTTPS to an Azure SQL database, hosted by us in the region you choose or deployed into your own Azure subscription. Several 3CX systems can feed the same database.
We build the reports with the people who will read them: your queues, your sites, your service levels. They refresh on a schedule and open in Teams or the browser.
Encrypted in transit and stored in Azure SQL, hosted by us or in your own Azure subscription. You can query it directly as well as through Power BI.
The integrator only reads records 3CX has already written. It has run on high-availability servers without touching call handling.
One simple monthly price covers the integrator, Azure hosting and support from our team. You pay for each 3CX server you connect.
Multi-site, high-availability and near real-time deployments, each one reporting into Power BI.
Manufacturing
Call data from five separate 3CX phone systems is pulled into one Azure data warehouse and reported in Power BI, replacing around ten hours a month of manual collection.
Read the case study
Manufacturing
After moving from Avaya to 3CX the business lost wrap-up codes. A cloud-hosted companion app with Microsoft sign-in gave agents a way to record call outcomes again, with reporting across sites.
Read the case study
Telecoms
Call data is extracted automatically from RSA Web’s 3CX phone system into its Azure data warehouse, giving support managers near real-time visibility of volumes and agent performance.
Read the case study
Tell us how many servers and queues you run and what you want to see. We take care of the setup, the reports and the ongoing running, and you get a clear price before anything starts.
Get started