Skip to main content

Read workspace analytics

The Analytics page derives its displayed metrics in the browser from the active workspace's call and contact records. Use the time-range and agent filters to narrow both datasets.

Time ranges​

RangeDisplay
24hHourly buckets for the previous 24 hours.
7dDaily buckets for the previous seven days.
30dDaily buckets for the previous 30 days.
AllUp to 90 days beginning with the oldest call in the loaded data.

The All chart is capped at 90 days even if older records exist. Treat it as a rolling visual horizon, not a lifetime archive chart.

KPI definitions​

KPICalculation
Total interactionsNumber of filtered call-list items. This can include asynchronous usage events displayed as pseudo-calls.
Total contactsNumber of filtered contact records.
Total conversionsCalls whose outcome is booked or intake, or whose status is booked.
Conversion rateTotal conversions divided by total interactions.
Average lengthSum of stored call durations divided by total interactions, rounded to seconds.

An asynchronous ledger event has no duration but can still increase the interaction denominator because analytics consumes the same combined call-list response. Keep this in mind when reconciling low-volume workspaces with standalone tool activity.

Charts​

Interaction volume compares call items with conversions by hour or day. Outcome distribution groups each item by outcome, then status, then unknown. Agent performance lists calls, booked or intake outcomes, and the resulting rate for each selected agent.

These calculations are operational indicators, not immutable financial reports. In particular:

  • conversions depend on stored statuses and AI-derived outcomes;
  • contacts and calls are separate counts;
  • late post-call analysis can change a recently completed call's outcome; and
  • deleting an agent removes the underlying calls and contacts from these views.

Validate a metric​

  1. Select the same time range and agent in Analytics.
  2. Open Call Logs and filter to that agent.
  3. Inspect the records contributing to the metric.
  4. Validate booked, intake, or transferred results in the connected destination.
  5. Use the usage ledger-backed cost breakdown for credit reconciliation rather than inferring cost from Analytics counts.