Activity — what happened
Calls in and out, answered, missed and abandoned, busiest hours, and tables by line and by group. Everything exports to CSV, because somebody always wants it in a spreadsheet.
Stage in a call · AFTER
Two dashboards, not seven reports.
Most phone systems ship a reporting module nobody opens, because finding anything requires knowing which of eleven reports has it. There are two surfaces here: what happened, and how the calls sounded.
What the call does
- inCall ends
- step 1Call record
- answeredActivity and quality
Call quality — how it sounded
Mean opinion score, jitter and packet loss, down to a single call with its endpoint and network. Filterable by site, line and device. This is the surface that answers "the calls were breaking up yesterday afternoon" with something other than a shrug.
Retention is published in the product
How long each surface keeps data is shown on the surface itself. If your plan keeps thirty days of activity history, the dashboard says thirty days, where you can see it before you go looking for last quarter.
Two modes
Simple by default, detailed when you ask
Most people never open the second column. It is one click away rather than spread across the first.
Simple mode
- Two dashboards, a date range, and an export button
- Every queue and attendant links to its own filtered view
Advanced mode
- Per-call detail with endpoint, codec and network path
- Scheduled CSV export
Where analytics stops
- Retention depends on plan, and shorter retention is a real limit, not a nudge — once the window passes, the detail is gone.
- There is no custom report builder. If the two dashboards plus CSV do not answer your question, tell us what the question was.