Call Analytics

See every call your agents placed or answered, filter by date, direction, agent and duration, and open any call's details.

Showing instructions for Xebit VoiceCloud.Showing instructions for Xebit VoiceKit, on your own infrastructure. Switch with the selector at the top. Updated 22 October 2026.

Call Analytics is the calls list: every call your agents placed or answered, with when it happened, who it was with, how long it lasted and how it ended. Use it to answer the everyday questions, such as how many calls went out today, how many connected and which ones need a person to look at them.

Where to find it

  1. Sign in to the Xebit VoiceCloud dashboard at voice.xebit.ai.
  2. Sign in to the Xebit VoiceKit admin console on your own host.
  3. Open the calls list.

What you can see

Call volume

  • How many calls were placed and answered over the period you choose.
  • The split between inbound calls (callers ringing numbers on your SIP trunk) and outbound calls (agents dialling from a campaign or an API request).

Call outcomes

Every call ends with a disposition. The common ones are:

OutcomeWhat it means
CompletedThe call connected and the conversation reached its end.
Failed to connectThe call never connected: the number was unreachable, busy, not answered or rejected by the carrier.
Caller hung upThe call connected but the other person ended it before the conversation finished.

Beyond the disposition, each call carries the structured fields you defined with the agent, such as a lead status or a booked slot. Those tell you what the conversation achieved; the disposition tells you how the call itself went.

Call duration

Each call shows how long it lasted. Very short connected calls are worth a look: they often mean the opening did not land or the caller thought it was spam. Very long ones can point to an agent going round in circles.

Call details

Open any call to see its details:

DetailWhat it shows
TimeWhen the call started
FromThe calling number. For outbound calls this is a number on your SIP trunk.
ToThe number that was called. For inbound calls this is a number on your SIP trunk.
DurationHow long the call lasted
AgentWhich agent handled the call
DirectionInbound or outbound
DispositionHow the call ended

From the details you can also play the recording, read the transcript and summary, and see the captured fields.

Filtering calls

Narrow the list with filters:

  • Date: a single day or a range.
  • Direction: inbound or outbound.
  • Agent: one agent's calls.
  • Duration: short or long calls.

A useful daily habit: filter yesterday's calls to completed calls under a minute, and listen to a handful. It is the fastest way to find a weak opening or a question the agent handles badly.

Going deeper with Observability

When a call looks wrong and the transcript does not explain why, open its replay. Observability keeps per call metrics, such as response time on every turn, silence and talk over, and an event log that shows tool calls and handoffs as they happened. If a whole group of calls failed in the same window, the SRE agent will usually already have opened an incident. See Observability.

Pull calls from code

Everything in the calls list is also available through the REST API, so your own reporting can use the same data.

The base URL is https://api.voice.xebit.ai/v1, with a key from the Xebit VoiceCloud dashboard.

The base URL is https://<your-xebit-voicekit-host>/v1, with a key from the Xebit VoiceKit admin console.

See Auth Setup and API Keys.

Next steps