Measuring
Is 3CX's built-in reporting enough? Eight questions to test on your own system
By the V4N team · Published · 2 min read
The short answer
3CX includes built-in call reports, a real-time queue wallboard and call detail records (CDR), and for many teams they are enough. Whether they are enough for you depends on the questions your managers ask. Test these eight on your own system, with your own edition, before deciding whether to add anything.
3CX is a capable phone system, and it reports on what it does. Its documentation points teams to start with the native reports and move to CDR data when they need lower-level detail, and it offers a wallboard for real-time queue statistics. What is available depends on your edition and version, so check yours rather than relying on a feature list.
The honest way to decide whether you need anything more is to try to answer the questions below from what you have now. If you can answer them in a few minutes, you are fine. If you cannot, you have found the gap.
The eight questions
- Which hour of last week had the worst abandonment, and how many agents were signed in then? You need rate by hour beside staffing, not a weekly total. (See call abandonment rate.)
- What share of calls were answered within your target time, by half hour? This is service level; an average will not show it.
- Which callers rang and never got through, and who has called them back? A list of missed numbers with an owner and a status, not just a count.
- Can a supervisor find one customer's calls by phone number in under a minute? Across queues and agents, with the recording.
- Do the agent figures mean what you think? 3CX itself advises reading agent statistics alongside queue membership, polling strategy, ring time, skills and transfers. A missed ring is not always an agent's fault.
- How many calls did you check for quality last month, and how many could you check? If it is a handful out of thousands, see checking every call.
- Who can hear recordings, and could you show a regulator who did? An access log, not a promise. See call recording in Kenya.
- Can a manager see this without logging in to the phone-system admin console? Reports are most useful in the hands of supervisors, and they should not need admin rights.
How to score yourself
| Questions you could answer | What it suggests |
|---|---|
| 7 or 8 | Your reporting is probably enough. Spend your time elsewhere. |
| 4 to 6 | You have the data but not the views. Consider a reporting layer on top of your 3CX. |
| 0 to 3 | You are running blind on the questions that cost you customers. Fix this first. |
Adding a layer without replacing the phone system
If you find gaps, you do not have to change phone systems. V4N sits on top of your 3CX: a small connector on your 3CX server reads the call log and sends each finished call to your workspace, using secure outbound connections only. A live view of calls and agents and a browser phone are available in early access, and the live view depends on 3CX's Call Control API, which comes with some editions only, so we confirm it on your system first. 3CX keeps running your queues and routing the whole time.
Details of what each part needs are on our 3CX integration page.