Key takeaways
- Write the summary for the next person who acts on it: what happened, what was promised and who does what next.
- Six lines in a fixed order cover almost every call: header, reason, details, done on the call, next step and flags.
- A booking, a quote request and a complaint need different detail; the examples below show what each one carries.
- Check the number, names, outcome, owner and promises before acting on any summary; speech recognition errors are not evenly spread across voices[2].
- Calls that need nothing still get a one-line header, so the summaries that matter stay easy to find.
Who reads a call summary, and when
The person who reads a call summary is rarely the person who took the call, and they usually read it in a hurry: between jobs, just before a callback, or weeks later when a customer disputes what was said. A good summary works for all three readers. It tells the technician what to bring, tells the office what was promised, and tells the owner what happened if the call ever turns into a complaint or a refund request.
Record-keeping is not an afterthought in customer-facing work. BLS lists recording the details of customer contacts and actions taken among the core duties of customer service representatives[3], and O*NET rates keeping records of customer interactions at 88 out of 100 for importance, just below the conversation itself at 92[1]. Checking that a problem was actually fixed scores 85, and that check depends on a record someone can find.
This guide covers the record of a finished call. If the call ended with someone needing to ring the caller back, the guide to taking a phone message has the fields for that, and most of them reappear in the summaries below.
The six lines of a useful summary
Healthcare teams hand patients over with a structure called SBAR: situation, background, assessment, recommendation. AHRQ describes it as a menu rather than a form, to be adapted to what the team needs[4]. The same idea works for a business phone call. Six lines, always in the same order, so the reader knows where to look before they have read a word.
| Line | What goes in it | Example entry |
|---|---|---|
| 1. Header | Caller, number, new or existing, call type, outcome tag | Dana Reyes, 555-0118, new client, booking, BOOKED |
| 2. Reason | Why they called, in one plain sentence | Cut and color consultation before her wedding |
| 3. Details | Only the facts the next person needs | Colored elsewhere three months ago; Saturdays only |
| 4. Done on the call | What was booked, sent, quoted or promised | Consultation booked Saturday 10:30 with Priya |
| 5. Next step | Who does what, and by when | Priya to allow 30 minutes and suggest a trial date |
| 6. Flags | Urgent, upset, repeat caller, deadline, compliance note | Hard deadline: wedding on the 28th |
The outcome tag in the header does the heavy lifting. Keep a short, fixed list (BOOKED, QUOTE REQUESTED, MESSAGE, TRANSFERRED, COMPLAINT, NO ACTION) so anyone scanning twenty summaries sees at a glance which five need something today. Free-text outcomes such as "sorted" or "see notes" defeat the purpose, because nobody can filter on them.
Use the caller's own words in the reason line only where wording matters: the exact symptom of a fault, the exact thing a customer says they were promised, the exact date of an event. Everywhere else, plain paraphrase is shorter and easier to scan.
Example 1: a booking call
Booking summaries are the easiest to get right and the easiest to pad. The reader needs the appointment, anything that changes how the appointment runs, and nothing else. Example, weak version: "New client called, booked consult Saturday, wedding coming up." It is not wrong. It just leaves the stylist to guess the time, the service and how long to allow.
Example, strong version, at the same fictional salon:
- Dana Reyes, 555-0118, new client, booking. Outcome: BOOKED.
- Reason: cut and color consultation ahead of her wedding on the 28th.
- Details: shoulder-length hair, colored at another salon about three months ago; prefers Saturdays; referred by a friend.
- Done: consultation booked Saturday 10:30 with Priya; asked to bring photos of the look she wants.
- Next: Priya to allow 30 minutes and pencil in a trial before the 28th.
- Flags: hard deadline.
Notice what is missing: the small talk, the two other dates she considered, and her question about parking. If the parking question comes up on every third call, it belongs in the answers your front desk gives, not in every summary.
Example 2: a quote request
Quote summaries fail when they skip the details that decide the price. The estimator should be able to read one and know whether to drive out, what to bring, and what the customer is comparing you against. Example, at a fictional HVAC company:
- Tom Okafor, 555-0163, new customer, replacement quote. Outcome: QUOTE REQUESTED.
- Reason: central air conditioning is blowing warm air and he wants a price to replace it.
- Details: single-story house; system about 18 years old by his estimate; gas furnace; unsure of the tonnage; another company quoted last week.
- Done: estimate visit requested for Thursday or Friday afternoon; told the estimator will confirm the time by phone.
- Next: estimator to call by Wednesday noon to confirm, and bring options at two efficiency levels.
- Flags: competing quote in hand; an older relative lives in the house and the heat is a problem.
The competing-quote flag changes how fast someone should call. So does the older relative in a hot house. Neither would survive a summary written as "wants AC quote, call back", and together they decide whether this is a call for today or for next week. The home services guide to call summaries and CRM notes shows how trades offices carry these fields into their job software.
Example 3: a complaint
Complaint summaries carry the most risk, because they may be read again by an owner deciding on a refund or by someone answering a public review. Separate what the caller says happened from what your records show, and write down exactly what was offered. Example, at a fictional plumbing company:
- Ruth Lam, 555-0190, existing customer, complaint. Outcome: COMPLAINT.
- Reason: the kitchen drain cleared on Monday is running slow again.
- Caller's account: says the technician did not run the water long enough to test it and left a mess under the sink.
- Our record: job notes show a cable run on the kitchen line Monday at 2 pm; no photos attached.
- Done: apologized for the hassle; offered a return visit at no charge for the same problem, which she accepted; told her the service manager would call today.
- Next: service manager to call by 4 pm today, book the return visit and check the warranty terms on the job.
- Flags: upset; mentioned leaving a review.
Two habits make this summary useful next week. The caller's account and the job record sit on separate lines, so nobody mistakes an allegation for a finding, or the reverse. And the offer is written word for word, because "return visit at no charge for the same problem" and "we'll make it right" lead to very different conversations when she calls back. For the live call itself, see how to handle an angry customer on the phone.
Example 4: the calls that need one line
Not every call deserves six lines. Wrong numbers, sales pitches, silent calls and "are you open today" calls need the header and an outcome tag, nothing more. Example: "Unknown caller, 555-0101, sales pitch for card processing. Outcome: NO ACTION."
Keeping these short does two things. The summaries that matter stay visible in the inbox instead of being buried under noise. And the headers still let you count how much of the week went on calls that brought no business, which is the first number you need if you are deciding whether to filter them before they reach anyone.
Mistakes that make summaries useless
Most weak summaries fail in one of a handful of ways, and all of them are easy to spot once you know to look.
- Telling the call in order. A summary that starts "Caller asked if we were open, then said..." makes the reader dig for the request. Lead with the outcome and the reason.
- Leaving out what was promised. If the caller was told Thursday, the summary must say Thursday, or the next person will cheerfully promise Friday.
- Mixing opinion with fact. "Customer was rude" helps nobody; "raised his voice about the second-visit fee" tells the manager what to prepare for.
- Dropping the number because caller ID has it. People ring from work lines and borrowed phones, so write the number they asked to be called on.
- Merging two calls into one. If the same customer rings twice, write two headers, so the history shows the second call happened and how long the first went unanswered.
Check a summary in ten seconds
Whether a colleague or software wrote it, read every summary with five quick checks before anyone acts on it.
Number
Does the callback number match the caller ID, or is there a note explaining why it differs?
Names
Are names spelled the way the caller spelled them? Speech recognition gets more wrong for some voices: one study of five commercial systems found an average word error rate of 0.35 for Black speakers against 0.19 for white speakers[2].
Outcome
Does the outcome tag match what actually happened on the call, as the transcript or your memory tells it?
Owner
Does the next step name a person and a time? "Follow up" with no name means nobody will.
Promises
Is every promise in the done line one the business can keep? Fix it now, while the caller can still be told.
If calls are recorded, the recording settles any summary that matters. Recording rules vary by state. Federal law allows recording when one party to the call consents[5], while Washington requires every party's consent and counts a recorded announcement that the call is being recorded as obtaining it[6]. A recording notice at the start of the call is the usual way businesses meet the stricter rules; check your own state before relying on it.
How summaries reach the team when software writes them
When calls are answered by an SI Employee, a summary in this same short shape is written after every call and emailed to the person you choose, with the recording and transcript kept beside it in the account. Calls your rules mark urgent arrive as an urgent email. The after-hours plumbing example shows the morning routine this creates: the office reads the night's summaries first and calls back in order of urgency.
- Caller
- SI Employee
- System
- Your team
01Caller
Call ends
The caller has booked, asked for a quote, complained or left a message.
02SI Employee
Summary written
Header, reason, details, what was done and the next step, in a fixed layout.
03System
Emailed to the right inbox
Summary emailed to the person the business chose; recording and transcript kept.
04System
Urgent calls flagged
Calls that meet the business's urgent rules arrive marked URGENT.
05Your team
Ten-second check
Number, names, outcome, owner and promises checked against the call.
06Your team
Next step done
Callback made or visit booked, and the outcome noted on the contact.
Example flow. The inbox, the urgent rules and who checks each summary are set by the business.
Summaries also build a customer history. Each caller becomes a contact with past calls attached, which matters the second time they ring. Contacts can be exported as a CSV, or sent on to other systems by webhook. Real estate teams have their own version of this discipline in call notes to log after every lead call.
If you are comparing this with a traditional service, SI Employee vs answering service sets out what each one sends you after a call, and how an AI receptionist works explains where machine-written summaries come from and where they slip. Either way, the six lines and the ten-second check stay the same.
Frequently asked questions
How long should a call summary be?
Six short lines for a call that needs action and one line for a call that does not. If a summary runs past one screen, the next step usually gets lost; move background into the contact record instead.
Should a summary include the caller's exact words?
Only where the wording matters: a symptom, a complaint, or a promise the caller says they were given. Mark those lines as the caller's account so nobody reads them as the business's findings.
Who should write the summary?
The person who handled the call, within a minute of hanging up. Details fade quickly, and the person who heard the tone of the call is best placed to add the right flags.
Can I rely on an automated call summary?
Treat it as the first draft of the record and check the number, names and promises as you would a colleague's note. The recording and transcript are there for anything that matters.
What is the difference between a call summary and a call log?
A log lists every call with time, number and outcome; a summary explains one call well enough to act on it. Most businesses need both, and the outcome tags should match between them; a call log template covers the log side.
References
O*NET OnLine (U.S. Department of Labor, Employment and Training Administration) (2025). 43-4051.00 - Customer Service Representatives (tasks) (opens in a new tab) ↑
Proceedings of the National Academy of Sciences, via PubMed Central (2020). Racial disparities in automated speech recognition (PNAS 117(14)) (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (2025). Customer Service Representatives: Occupational Outlook Handbook (opens in a new tab) ↑
Agency for Healthcare Research and Quality (AHRQ) (2023). Tool: SBAR (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (2026). 18 U.S. Code 2511: Interception and disclosure of wire, oral, or electronic communications prohibited (opens in a new tab) ↑
Washington State Legislature (2026). RCW 9.73.030: Intercepting, recording, or divulging private communication; consent required (opens in a new tab) ↑