Using Call

Using Call History and Summaries in Call: A Practical Guide

How to read call history, check AI summaries against transcripts, turn calls into callbacks and handovers, and keep call records private in Call.

Call editorial team · Published · 5 min read

Every call leaves a trail: who rang, when, for how long, how it ended, and, where available, what was said. Used well, that trail turns phone work from a series of forgotten conversations into a shared record. Used badly, it becomes a pile nobody opens.

A support agent reviewing call notes on a screen next to a phone
Illustrative image

This guide explains how to read and use call history and summaries in Call, how to check a summary before you act on it, and how to turn calls into callbacks and handovers. For the principles behind automatic summaries, see AI Call Summaries, and for how to ask for a good summary, Call Summarization Prompts.

What call history shows

Call history lists every call on your workspace with who, when, how long, the result and the summary. In Full mode the page is called the call log; in Easy mode you open phone call history under Essentials. You can narrow the list with filters, such as name or business, phone number, direction, status, line, outcome and dates, and sort by a column like duration or outcome.

What each call record contains

  • The top lineDirection, status, outcome, time, length and who handled it.
  • SummaryA short account of what the call was about and how it ended.
  • RecordingWhere recording is on, you can play it from the page.
  • TranscriptWhat was said, turn by turn, with the speaker marked.
  • Write-up toolsDrafts of a note, a follow-up email or a suggested outcome, which you can copy.
  • Call againA button to call the person back through your line.

Statuses help you sort the day. Connected, no answer, voicemail, busy and failed calls all appear, with counts above the list. Clicking a status shows only those calls, which is a quick way to find the ones that need a follow-up.

Summary versus transcript

A transcript is a record of the words; a summary is an interpretation of them. Each has a place. Read the summary for the gist and the transcript for the evidence.

Choosing what to read

SummaryTranscript
Best forDeciding what to do next, in secondsChecking exactly what was said
Typical useMorning triage, handover, callbacksDisputes, names, numbers, promises
RiskMay drop or misstate a detailLong and slow to read
HabitRead firstOpen when a fact matters

Names, dates, amounts and addresses are the facts most often wrong in a summary, because they are the facts most often misheard. Treat those as things to verify, not accept.

A short routine for reading a summary

Read, check, act

  1. Open the callFind it from the list or through a link in a ticket.
  2. Read the summaryUnderstand why they called and how it ended.
  3. Check what mattersLook in the transcript for names, numbers, dates and any promise.
  4. DecideCallback, ticket, note or nothing to do.
  5. RecordLog the outcome so the call is not left unfinished.

If a summary is wrong, treat it as information. The wrong parts show you where the speech or the sources failed, and they should lead to a fix: a corrected pronunciation, a clearer source or a better prompt. Where a call was a test or a demo, mark it clearly so it does not confuse reports.

Teams that do this well keep their summaries short on purpose. A good one-line opening states who called, what they wanted and what happened, and leaves detail to the transcript. Agree a standard with colleagues, so that everyone writes and reads summaries the same way, and so that a stranger can pick up a case on the first line.

From summaries to callbacks

Summaries are most valuable when they feed the next action. A callback that starts with "I'm returning your call about the invoice you asked about on Tuesday" feels very different from "Hello, you called us?".

Callers who asked for a person, or whom nobody answered, can appear in a help-desk list with the request, the summary and the whole conversation. Staff can take a request, assign it, add a note, call back and resolve it, which keeps a clear trail of who did what. Callbacks that are due also appear on the Home page in the Your shift card. See Callback Completion Rate for measuring this.

Searching and sharing

Beyond single calls, you can search stored transcripts for a phrase, a competitor or a promise, and open the matching calls. This is useful for checking how often a topic comes up, or for finding what was said in a particular conversation. Speaker labels can show who spoke when in a recording, and can be corrected if the system names the wrong person.

When you share a call, share the smallest thing that does the job. A link to the call is better than pasting the whole conversation into a chat. If you need to hand over, write a minimal note: who, what they want, what has been done, what is next.

Handover noteExample
WhoCaller's name and number
What they wantIn one sentence, in their words
What has been doneAlready answered, already promised, already booked
What is nextCallback by a time, or waiting for them
Anything sensitiveMark it and limit who sees it

Privacy, access and retention

Calls hold names, phone numbers and often more. Restrict access to the people who need it, and be aware that some views mask card and phone numbers by default, with an option to reveal them. Stored conversations are kept for a limited time, and what remains depends on your retention rules and how the call was recorded.

A weekly habit for call history

  • Filter to missed and unhandled calls and clear them
  • Open five summaries at random and compare each with its transcript
  • Note any recurring errors in names or numbers
  • Check that callbacks due this week are logged
  • Remove or mark test and demo calls
  • Confirm that only the right people can see recordings

Using it in Call

In Call, open Calls and then Call history, press a call to see its details, and use Transcript to read it turn by turn. Under Write it up, you can draft a note, a follow-up email or a suggested outcome and copy it. AI call history shows the whole conversation beside the list, with the rule the agent followed. In Easy mode, a button on each ended call can email you a summary, sent only to your own account address.

Exports to CSV are available from the list, and the Reports page can group calls by agent, queue, outcome and more. Where a summary or transcript is missing, short or unanswered calls often have none, and the page says so.

Frequently asked questions

How accurate are automatic call summaries?

They are usually helpful for the gist but can misstate names, numbers and dates. Check those against the transcript or recording before acting.

Where do I find a call's transcript?

Open the call from call history and use the Transcript section. Short or unanswered calls often have no transcript.

Can I email myself a summary?

In Easy mode, an ended call has an email-me button that sends the summary to your own account address. It cannot send to someone else.

What should I do when a summary is wrong?

Correct your action, then find the cause. It may be a misheard name, a missing source or a prompt that needs rewording.

Who should be able to see recordings?

Only the people who need them, such as the person on the call and managers. Limit access and set a retention period.

Can I search across all calls?

Yes. You can search stored transcripts for a phrase and open the matching calls. Only calls with a stored transcript can be found.

Review call history and summaries in Call

In the demo console you can try incoming calls in a simulation.

Related guides