Conversational Intelligence

Recordings, transcripts, summaries, outcomes and the structured fields every call leaves.

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.

Every Xebit call leaves five things behind: a recording, a transcript, a summary, an outcome and the structured fields your workflow needs. They are captured whether the agent handled the call alone or a person joined it, kept together with the call, and sent to your systems as the call ends.

What every call leaves

RecordWhat it contains
RecordingThe whole call, every leg, so a reviewer can hear what was actually said.
TranscriptTurn by turn, in the language the call happened in, attached to the recording and the event log.
SummaryWhat the caller wanted, what was agreed and what happens next, in a few lines a person can act on.
OutcomeThe call disposition, for example promise to pay, booked, callback requested or handed to a person.
Structured fieldsThe specific values your workflow needs, captured during the conversation.

View a call's record

  1. Sign in to the dashboard at voice.xebit.ai.
  2. Sign in to the Xebit VoiceKit admin console on your host.
  3. Open the calls list, or a campaign, and open the call.
  4. Read the summary and outcome first, then the captured fields.
  5. Replay the recording with the transcript and the event log side by side when you need the detail.

Transcripts

Transcripts are turn by turn, with the agent's and the caller's lines kept apart, and work in every language the realtime models support. A call in Hindi, Tamil or English, or one that switches between them, is captured the same way. When a person joins from a browser, their part of the call is in the same transcript. More in Transcripts.

Summaries

The summary is written for the person who acts next: a collections officer, a recruiter, a support lead. It states the caller's request, what was agreed and the next action, so nobody has to listen to the call to know what to do.

Outcomes

Each call ends with a disposition. Decide the set of outcomes that make sense for the agent's job, list them in its instructions, and make sure every path through the conversation ends in one of them. Campaign reports and your CRM both rely on outcomes being consistent.

Structured fields

You define the fields with the agent. They are captured during the conversation, not guessed from a transcript afterwards, and written to the right record.

Define fields for an agent

  1. Open the agent's settings in the dashboard or admin console and find the fields it captures.
  2. Add each field with a clear name, the kind of value it holds (a date, an amount, yes or no, a choice from a list, free text) and a one line description of what it means.
  3. Tell the agent in its instructions when to ask for each value and how to confirm it, for example by reading a date back to the caller.
  4. Save, then make a test call and check every field is filled.

Examples by use case

Use caseFields capturedWhere they go
CollectionsDisposition, promise to pay date and amount, dispute or hardship flagYour loan management system
RecruitmentNotice period, availability, consent to an AI interview, screening outcomeYour ATS
Customer supportReason for the call, resolution, whether it needs a person, the transcriptYour helpdesk or CRM
AutomotiveInterest, preferred model, test drive or service slotYour dealer CRM

See these in context in EMI reminders and candidate screening.

Getting the record into your systems

  • Webhooks fire on call lifecycle events, outcomes and transfers, to any endpoint you run. See Outbound Webhooks.
  • The REST API lets you pull calls, outcomes, recordings and transcripts whenever your systems need them.
  • The CRM connector writes the outcome to the right record in Zoho or Salesforce.

Setting these up is covered in Workflows & Integrations.

Where the data is stored

On Xebit VoiceCloud, recordings, transcripts and outcomes are stored in Xebit's infrastructure. See Data retention.

On Xebit VoiceKit, recordings, transcripts and outcomes stay in your environment, on the storage you provisioned, and you set how long they are kept. In an air gapped deployment nothing leaves the network.

Review and improve

Outcomes over time show how a campaign is landing: promises, bookings, callbacks and handoffs. Off script answers and failed tool calls feed into Observability, so you can catch an agent drifting before customers notice.

Next steps