zoxaAI
Homepage

Analytics

Track calls, answer rate, billed minutes, spend, outcomes, agents, and hourly activity across any date range on the Analytics dashboard.

What you'll learn

What each analytics metric means, how period-over-period comparison works, how your timezone affects day and hour boundaries, and how to export the underlying data.

Analytics

The Analytics dashboard gives you a complete, at-a-glance view of your calling activity across any date range: how many calls ran, how many connected, how long they lasted, what they cost, why they ended, and when they happen. Use it to monitor performance, control spend, and spot issues.

Home defaults to the last 7 days; Analytics covers any range you select.


Choosing a date range

At the top of the dashboard, pick a range:

OptionDescription
7 daysThe last 7 days (default on Home)
30 daysThe last 30 days (default on Analytics)
90 daysThe last quarter
CustomAny start and end date from the calendar

Every metric — including the period-over-period delta chips — recalculates for the selected range. You can also filter the dashboard by direction (All / Inbound / Outbound).


Metrics

Every metric is calculated for the range you select, alongside its value for the previous period of equal length (for example, this week vs. last week) so you can see the direction of travel.

MetricWhat it measures
Total CallsEvery call created in the range
Answer RateShare of calls that connected (the recipient answered or the web client joined)
ConnectedCount of calls that connected
Billed MinutesMinutes billed for completed calls
Avg DurationAverage length of connected calls
Avg LatencyAverage agent response startup time
Total SpendCost across the range (LLM + TTS + STT + telephony + platform)
Live CallsCalls active right now (not range-bound)
CompletedShare of calls that ran cleanly enough to bill. Platform failures are excluded, so this sits at or below Answer Rate
EngagedShare of connected calls lasting 30 seconds or more — early hangups drag it down
Human reachedShare of calls that did not end in voicemail, out of calls that reported an end reason
Active daysShare of days in the range on which at least one call ran

Delta chips are color-aware: for latency, a decrease is shown as good; for volume and answer rate, an increase is good. When the previous period had no activity, the chip reads new instead of a misleading percentage.


Timezone

All dates and hours use your configured timezone (set in user settings). Day boundaries are calculated in that timezone, so "today's calls" reflects your local day, not UTC.


Understanding your metrics

IndicatorWhat it meansAction
Low answer rateCalls not connectingReview number quality, calling times, and telephony setup
High voicemail / no-answerCalling at the wrong timesAdjust campaign scheduling
Rising avg latencySlower agent responsesCheck model/provider choice and pipeline health
Spend climbing faster than callsCost per call increasingReview model and voice choices in the cost breakdown
Calls concentrated outside business hoursCalls landing at low-engagement timesRetune campaign windows

Data export

For bulk export across all call types, use the Call History API with date-range filters, or a campaign's runs endpoint for campaign-specific results.


Frequently asked questions

QuestionAnswer
Can I break down by agent?Yes — calls are broken down by agent for the range you select.
How far back does data go?As far back as your call history is retained. Pick any custom range.
Are browser calls included?Yes. Outbound, inbound, and WebRTC (browser) calls are all included; the direction filter separates them.
Do failed calls count against spend?No. Billed minutes and spend count only completed calls; platform failures are never billed.
What timezone are dates in?Your configured user timezone. All day and hour boundaries are calculated in it.

Next steps

On this page