Good day!

We are developing a new integration for 3CX Phone System. This integration connects to the 3CX XAPI to bring phone system analytics into MSPBots. Please note this requires 3CX V20 or later with an 8SC+ AI license.

As we continue developing the API endpoints, we are looking for customers who would like to participate in the early access phase. Here is what is on the development list and what each set is intended to power:

Visualize call volume trends across your phone system — track peak hours, busiest extensions, and overall call patterns.

Detailed inbound call records by number, including trunk, DID, ring/talk duration, and call status.

Outbound call details by extension with cost tracking for billing and productivity analysis.

Track missed and abandoned calls in queues to identify service gaps and improve response times.

Monitor queue performance including wait times, talk duration, and service levels to optimize call handling.

Analyze per-extension talk time and call activity to measure individual and team productivity.

Dimension data that links call metrics to your organizational structure — extensions, queue assignments, and departments.

Since the scope is still open, we would also value your input on:

* Which of these matter most to you, so we build in the order that delivers value first

* Any data point you rely on today that is missing from this list

* The specific gauges or dashboard views your team wants to end up with

If you are interested, please email support@mspbots.ai and we will enable 3CX visibility for your account.

We look forward to hearing from you!

Requested by: Shaun Byres via ticket #44096

Use case:

Call reporting data from 3CX - Total calls inbound / outbound, talk time, trends.

API documentation:

https://www.3cx.com/docs/configuration-rest-api/ (public, client supplied)

Notes:

OAuth 2.0 client credentials, 60 minute token. Requires 3CX V20+ and 8SC+ AI licence. Config API docs do not show call history / CDR endpoints.

Hi Daniel, I see this post is getting alot of upvotes. One other metric I didnt see mentioned here that we would like to have is COUNT of EXTENSIONS so we know how many active users we are supporting on the platform. Helpful would be a dataset that would let us see the extensions in use month over month. Since clients can make these changes on their own, its a manual process for us to track this month by month, automating this data collection with MSPBots would be a big time saver.

3cx doesn't have the native API support the CDR data, alternate way is to use CDR export the call detail records to an onedrive folder then create datasets from there and build the dashboard: https://www.3cx.com/docs/cdr-call-data-records/

Alternatively, MSPbots can use the MSPbots Agent to pull the CDR, convert to the datasets, build the templated datasets, dashbaords, but this one will take much longer time, depends on how many votes that we can get since we have a huge back log.

There is also a post to use SQL agent to get the PostgreSQL data directly. https://sharing400.rssing.com/chan-6034941/article27.html