The 3CX integrator is no longer sold as a subscription. Register interest and we will tell you if it returns.

DataCactus dataCactus
Case studies How we work
Talk to us

3CX reporting

Your 3CX calls, in Power BI

Call, queue and agent reporting from one or many 3CX phone systems, held in your own Azure and built on the definitions your managers actually use.

Talk about 3CX reporting How it works

Call centre · all sites

Refreshed 6 minutes ago

Calls today

1,284

Answered in 20s

87%

Abandoned

4.1%

Avg. handling

4m 12s

Calls by hour

07:0013:0020:00

By site

  • Leeds412 calls · 92% in SLA
  • Milan318 calls · 84% in SLA
  • Warsaw276 calls · 88% in SLA
  • Lisbon164 calls · 79% in SLA
  • Cape Town114 calls · 90% in SLA

3CX tells you a call happened

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.

Calls

Inbound, outbound, missed and abandoned, by hour, day, site and extension. Answer times and talk times against the targets you set.

Queues

Waiting times, abandonment, service level per queue, and how each queue behaves across the day so rotas follow demand rather than habit.

Agents

Calls handled, availability, average handling time and outcomes per agent, comparable across teams and sites on the same definitions.

Outcomes

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.

From the phone server to the report

  1. 01

    A small integrator runs on your 3CX server

    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.

  2. 02

    Call data lands in your Azure

    Records are sent over HTTPS to an Azure SQL database in your own subscription, in the region you choose. Several 3CX systems can feed the same database.

  3. 03

    Power BI reports built on your definitions

    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.

Your data stays yours

Encrypted in transit, stored in an Azure SQL database in your subscription. You can query it directly as well as through Power BI.

Nothing in the call path

The integrator only reads records 3CX has already written. It has run on high-availability servers without touching call handling.

Built as a project

Scoped and priced before work starts under One-Problem Automation, with Cover available afterwards.

Delivered on real phone systems

Multi-site, high-availability and near real-time deployments, each reporting in the client’s own Azure.

Manufacturing

One view of five phone systems for a global manufacturer

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

Call outcome tracking restored after a phone-system migration

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

Near real-time call reporting for RSA Web

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

Questions about 3CX reporting

Is the 3CX data integrator still available?
We no longer sell it as a stand-alone subscription. We still build 3CX reporting as a project, using the same integrator, for organisations that need call data in Power BI or in their Azure data warehouse. If there is enough interest we will bring the subscription back; the form on this page is how we gauge that.
Does it work with 3CX hosted by 3CX, or only self-hosted?
The integrator runs on the 3CX server itself, so it suits self-hosted and privately hosted instances on Debian or Windows. For 3CX-hosted instances, talk to us about what is possible with the call reports and API available on your plan.
Can it combine several 3CX systems?
Yes. Each server gets its own integrator and they all write to the same database, so a business with several sites reports on everything together, with the site as a filter.
Where does the data live?
In an Azure SQL database in your own Azure subscription. Transfer is encrypted and nothing is stored outside your tenant.
What about wrap-up codes?
3CX does not record call outcomes natively. We have built a companion app that lets agents pick a wrap-up code at the end of each call, with Microsoft sign-in, and it reports alongside the call data.
How is it priced?
As a fixed-price project, agreed before work starts, once we have seen how many servers and queues you run and what reports you need. The Process & Reporting Review is the usual first step.

Need 3CX data in Power BI?

Tell us how many servers and queues you run and what you want to see. We will say whether a project makes sense, and let you know if the integrator returns as a subscription.

Register interest