11 September 2026

Transcribing calls and visits: keeping a record of what was agreed

— But we agreed you'd do all of it, including painting the part.
— No, that was never said.

Neither of them is lying. They spoke for twenty minutes on the phone five weeks ago, each understood whatever seemed most reasonable, and nobody wrote it down. Now there is an invoice on the table and an uncomfortable conversation that will end, at best, by splitting the difference.

This happens every week in workshops, practices, installers and professional offices. And it is almost never anybody's memory at fault.

The problem is not remembering. It is that no trace is left

An air-conditioning installer does the site visit, takes measurements, talks the customer through three options and says out loud which one he recommends and why. He gets back in the van, writes four figures in a notebook and drives to the next job. That evening, writing the quote, he can no longer remember whether they discussed removing the old unit or whether the customer was going to do that himself.

What was lost is not the price — the price always gets written down. What was lost is the nuance: who was doing what, what was left to confirm, what objection the customer had and what was promised to settle it. Six months later, when that customer calls again, nobody in the company knows anything about the conversation. And if the person who had it has left, the trace is zero.

First, the boring part: you have to disclose

Before we talk about any tool: if you record a conversation with a customer, you have to tell them. That is not a politeness recommendation. It is what handling personal data requires.

In practice it is enough to be direct and say it at the start: "I'm going to record the call so I don't miss any detail for the quote — is that all right?" Most customers say yes without hesitating, precisely because it benefits them: it means nobody will later invent what was said.

• Always disclose, and do it at the beginning. Recording secretly and tidying up the paperwork afterwards is not an option.
• Let them say no. If the customer does not want it, you take notes by hand. Nothing is lost.
• If you record systematically, document it. It has to appear in your privacy policy, with a retention period you have actually decided. Talk to whoever advises you before you start, not after.

This part is not optional, and it is exactly where most small organisations get it wrong.

How it works in practice

The loop is simpler than it sounds. The conversation gets recorded — a call, or a phone on the table during a visit. A transcription system turns it into text. And on top of that text, an automatic summary pulls out what you actually need: what was agreed, what is pending, who has to do it and by when.

The summary is the part that earns its keep. Nobody will ever reread twenty minutes of verbatim transcript, but half a page with five points and three tasks does get used. And, above all, it ends up attached to that customer's record rather than inside one person's notebook.

A useful summary carries the date and who was present, the points agreed, what is pending confirmation, and the tasks with an owner. That is all. If the summary runs to two pages, nobody reads it and we are back where we started.

Three things it must never do

• It must not decide for you. The summary is a proposal. You, or whoever made the visit, validate it before it goes into the customer record.
• It must not replace the source. The summary should link back to the recording or the transcript. A summary that stands alone is a quiet way to lose the exact words somebody was promised.
• It must not keep everything forever. Decide a retention period and apply it. "We keep it just in case" is not a retention policy, and it is the first thing anyone auditing you will ask about.

The same problem, one level up

Everything above scales. A support organisation recording calls for quality has the same four obligations — disclose at the start, allow a refusal where consent is the basis, document the practice with a retention period, and keep the summary traceable to its source — multiplied by thousands of conversations a day and several jurisdictions.

And the governance question is identical to the one I keep coming back to: when a summary is generated automatically and somebody acts on it, can you still reconstruct what was actually said, and who decided to act? If the answer is no, the efficiency gain was borrowed, not earned.

This article is general information, not legal advice. Recording and consent rules vary by country. For a specific decision with legal consequences, consult a qualified lawyer.