Key takeaways
- Businesses may record calls on their own systems for purposes such as establishing facts and checking standards, if they make all reasonable efforts to tell callers[1].
- UK GDPR requires you to tell people who you are, why you record, your legal basis and how long you keep recordings[2].
- Keep recordings only as long as you need them for the purpose, and delete them on a schedule[3].
- Recordings are data worth stealing; 43% of UK businesses reported a breach or attack in a year[4].
- If AI tools transcribe or summarise calls, have a person check anything that matters before acting on it[5].
The short answer
A plumbing or heating firm can record calls with customers. Plenty do, to settle disputes about what was agreed, to train new office staff and to check that urgent calls were handled properly. Recording is lawful when you do four things: tell callers it is happening, have a legitimate reason and a lawful basis, keep the recordings secure, and delete them when you no longer need them.
What you cannot do is record quietly and decide later what to use the recordings for. Most of the rules below are about being open and disciplined, not about paperwork for its own sake. This article is general information rather than legal advice; if you record calls for unusual purposes, or in large volumes, take advice specific to your business.
The two sets of rules
| Law | What it covers | What it means in practice |
|---|---|---|
| Investigatory Powers (Interception by Businesses etc.) Regulations 2018 | When a business may intercept and record communications on its own system | Record for business purposes such as evidence and standards, and make all reasonable efforts to tell users |
| UK GDPR and the Data Protection Act 2018 | How you handle the personal data in a recording | Transparency, a lawful basis, security, limited retention and customers' rights |
The 2018 regulations authorise a business to monitor or record communications on its own telecommunication system for listed purposes, including to establish the existence of facts and to ascertain or demonstrate the standards achieved[1]. One condition is that the system controller has made all reasonable efforts to inform every person who may use the system that communications may be intercepted[1]. For customers, that means a recorded message or a spoken line at the start of the call.
Telling callers properly
Telling people has two layers. The first is a short notice on the call itself. The second is your privacy notice, which carries the detail.
- Greeting line for inbound calls: "Calls are recorded to help us get your job right and for training. Our privacy notice is on our website."
- Spoken line for outbound calls, where no greeting plays: "Just so you know, this call is recorded so we have an accurate note of the job."
- If a caller objects: offer to continue without recording if your system allows it, or to take the details by email instead.
UK GDPR lists what people must be told when you collect their personal data, including the identity and contact details of the controller, the purposes and legal basis of the processing, any legitimate interests relied on, who receives the data, how long it is kept, and their rights, including the right to complain to the regulator, which the current text names as the Information Commission[2]. A single page on your website called 'How we use your information' can cover call recording alongside bookings, invoices and job photos.
Choosing a lawful basis
You need a lawful basis for recording, and you must state it in your privacy notice[2]. For a trade business recording its own customer calls for evidence and quality, legitimate interests is usually the natural fit: you have a genuine business reason, the recording is expected by most callers once they are told, and it does not override their interests if handled carefully. Write down the reasoning in a short note, sometimes called a legitimate interests assessment, and keep it on file.
Consent is a poor fit for routine recording. It must be freely given and can be withdrawn, which is awkward when the recording exists to protect both sides in a dispute. If you want to use recordings for something beyond the original purpose, such as marketing or publishing clips, stop and think again; that is a different purpose, and it needs its own justification.
How long to keep recordings
UK GDPR requires personal data to be adequate, relevant and limited to what is necessary, and kept in a form that identifies people for no longer than necessary[3]. There is no single legal retention period for call recordings. Set your own, based on why you record, and write it into the privacy notice.
- Routine enquiry and booking calls: a short period, long enough to resolve any confusion about the booking.
- Calls linked to a completed job: long enough to cover the period in which disputes about the work usually arise, then delete.
- Calls involved in a live complaint or claim: keep until the matter is closed, then return to the normal schedule.
- Training: pick a few anonymised examples and delete the rest on schedule; do not keep everything for training.
Check whether your phone system lets you set automatic deletion. If it keeps everything forever by default, change the setting; an unlimited archive is hard to justify and becomes a liability if it is ever breached.
Security of the recordings
Recordings contain names, addresses, phone numbers and sometimes details about health or vulnerability, such as a caller explaining that an elderly parent has no heating. In the government's 2025 survey, 43% of UK businesses reported a cyber security breach or attack in the previous 12 months[4]. Treat the recording archive like any other sensitive system.
- Limit access to the people who need it, usually the owner and the office manager.
- Use two-step login on the phone system and any app that plays recordings.
- Do not download recordings to personal phones or send them by messaging apps.
- Keep a simple log of who accessed a recording and why, for complaints and disputes.
Engineers' mobiles and recording apps
Some engineers install call-recording apps on their own phones to keep a note of what customers say. That creates the same legal duties without any of the controls: no greeting, no retention setting and recordings mixed with personal calls. If engineers need recordings, route their customer calls through the business phone system, where the notice, retention and access rules already apply. If you do not record, a short written note of what was agreed, sent to the customer by message or email, is often just as useful in a dispute.
Transcripts, summaries and AI tools
Many phone systems now offer transcripts and automatic summaries. They are useful, but they are also personal data and they can be wrong. Among UK businesses using AI in 2025, 84% reported at least some human checking of AI outputs and 67% reported significant checking[5]. For a trade firm, the parts to check are the ones that drive action: the address, the problem, the agreed time and anything said about safety.
If a service answers or records calls for you, for example an answering company or an AI employee such as Ava that sends a job summary with the recording and transcript, that service processes data on your behalf. Put a written data processing agreement in place, check where recordings are stored, and make sure your privacy notice mentions it.
Example: when a recording settles a dispute
Example: a fictional heating firm takes a call from a landlord who asks for a boiler repair at a rented flat and says the tenant will provide access on Thursday morning. The engineer arrives, the tenant is out, and the landlord later disputes the no-access charge, saying he asked for Friday. The office manager finds the recording by date and number, listens to the relevant minute, and sends the landlord a short written summary of what was said. The landlord accepts it. Nobody needs to share the audio itself.
Two things made that easy. The firm's greeting told callers that calls were recorded, so using the recording was no surprise. And the retention schedule kept job-related calls for long enough to cover the period in which disputes usually arise, but no longer. Without either, the recording would have been either unusable or a risk in itself.
A set-up checklist
Decide why you record
Evidence of what was agreed, quality and training are common reasons. Write them down.
Add the greeting line
One plain sentence at the start of inbound calls, and a spoken line for outbound ones.
Update the privacy notice
Purposes, lawful basis, who can access recordings, retention period and people's rights.
Set retention and access
Automatic deletion where possible, and access limited to named people.
Brief the team
What to say if a caller objects, and how to handle a request for a copy of a recording.
Frequently asked questions
Do I have to tell customers that calls are recorded?
Yes. Businesses recording on their own systems must make all reasonable efforts to inform users, and UK GDPR requires you to explain why you record and how long you keep recordings. A short greeting line plus a privacy notice on your website is the usual approach.
How long can a plumbing firm keep call recordings?
There is no fixed legal period. Keep recordings only as long as you need them for the purpose, such as resolving booking queries or disputes about a job, then delete them on a schedule you have written down.
Can a customer ask for a copy of a call recording?
Yes. A recording of a customer is their personal data, and they can ask for a copy. Keep recordings searchable by date and number so you can find and provide them promptly.
References
legislation.gov.uk (The National Archives) (2018). The Investigatory Powers (Interception by Businesses etc. for Monitoring and Record-keeping Purposes) Regulations 2018 (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR, Article 13: information to be provided where personal data are collected from the data subject (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR, Article 5: principles relating to processing of personal data (opens in a new tab) ↑
Department for Science, Innovation and Technology (GOV.UK) (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
Department for Science, Innovation and Technology (GOV.UK) (2025). AI adoption survey report 2025 (opens in a new tab) ↑