AI & automation

AI, call recording and GDPR: what UK installers need to know

AI receptionists, chatbots and call recording under UK GDPR: what installers must tell customers, the paperwork to have in place and a checklist before go-live.

Tom Spink · Founder, Attain Digital · 19 November 2026 · 7 min read
AI, call recording and GDPR: what UK installers need to know

AI assistants that reply to enquiries, answer calls and book surveys handle a lot of personal information: names, numbers, addresses, details about people's homes and sometimes much more. If you are thinking about using one, or already do, you need to know what UK data protection law expects of you.

This is a practical overview for owners as of November 2026, not legal advice. Rules change, and your setup will have its own details. If you are unsure, speak to a data protection specialist or check the ICO's guidance linked at the end.

What data an AI assistant actually handles

List it out before you do anything else. For a typical installer, the assistant will see:

  • Contact details: name, phone, email, address and postcode.
  • Property details: type, ownership, roof, heating system, energy bills.
  • Photos and videos customers send, which can show the inside of their home and sometimes people.
  • Call recordings and transcripts, if it answers the phone.
  • Conversation history across web chat, SMS and WhatsApp.
  • Sometimes sensitive information: health conditions, disability or vulnerability. This comes up in stairlift, mobility bathroom and heating enquiries, where someone explains why they need the work.

Health information is special category data under UK GDPR and needs extra care. If you do not need it to do the job, design the assistant not to ask for it, and decide what happens when a customer volunteers it anyway.

Who is responsible for what

You are the controller: you decide why and how your customers' data is used, and you carry the main responsibility. The firms that provide your AI assistant, CRM, phone system and messaging are usually processors, acting on your instructions.

That means you need:

  • A written contract with each processor covering security, confidentiality, sub-processors and deletion when you leave.
  • To know where data is stored. If it goes outside the UK, there must be a lawful transfer mechanism in place.
  • To know whether your provider uses your customers' conversations to train its models, and to be comfortable with the answer.

Your lawful basis

Every use of personal data needs a lawful basis. For an installer, the common ones are:

  • Replying to an enquiry and booking a survey: the customer asked you to, so this usually sits under taking steps at their request before a contract, or legitimate interests.
  • Recording calls for an accurate record or training: usually legitimate interests, sometimes contract.
  • Marketing follow-up later on: this brings in PECR as well as UK GDPR, with its own consent and soft opt-in rules. We cover that in our piece on reviving old leads, so we will not repeat it here.

Tell people: transparency

People have a right to know how their data is used. In practice:

  • Update your privacy notice to mention the AI assistant, call recording and transcripts, which providers you share data with, where it is stored and how long you keep it.
  • Say it at the start. On calls: "Calls are recorded, and you may be speaking to our assistant." In chat: "I'm the assistant for [business]." We explain why this also makes customers happier in our piece on whether customers mind AI.
  • Put consent and contact wording on forms. A line under the submit button naming your business and the channels you will use (phone, text, WhatsApp, email) covers contact, and links to your privacy notice. WhatsApp has its own opt-in rules from Meta, covered in our WhatsApp guide.

Call recording

The ICO's guidance on monitoring calls makes a few clear points:

  • Tell people their calls are recorded and why. A recorded message at the start is good practice.
  • Recording the content of calls should be justified, for example to evidence what was agreed, or for training and quality.
  • Include call recording in your privacy information.
  • Recordings are personal data. If a customer makes a subject access request, recordings and transcripts of their calls may need to be provided.

Separate rules on intercepting communications (the Investigatory Powers Regulations 2018) also allow businesses to record calls for purposes like record-keeping and quality, on condition that reasonable efforts are made to tell people. A clear announcement at the start of the call does most of the work.

Automated decisions

The Data (Use and Access) Act 2025 changed the rules on decisions made solely by automated means, and the ICO says all its data protection provisions are now in force. Organisations can make solely automated decisions in more situations than before, but where a decision has a legal or similarly significant effect, people must be told about it and be able to make representations, get human intervention and contest it. The restriction on using special category data for these decisions stays.

For most installers, an assistant asking qualifying questions and booking a survey is not making that kind of decision. But be careful if it ever:

  • Turns people away based on eligibility for a scheme or finance.
  • Decides who gets offered finance and who does not.
  • Uses health or vulnerability information to route or reject people.

Keep a person in those decisions, and always give customers a route to someone on your team.

Do a DPIA

The ICO says that in the vast majority of cases, using AI to process personal data is likely to be high risk and so needs a data protection impact assessment, done before you start. For a small business this can be a short document that answers:

  1. What data the assistant collects, and why each item is needed.
  2. Where it goes, who can see it and how long it is kept.
  3. What could go wrong: wrong answers, data shared with the wrong person, sensitive information captured, a breach at a provider.
  4. What you are doing about each risk.
  5. Who signed it off, and when you will review it.

Keep less, for less time

  • Ask only what you need. Every extra question is extra data to protect.
  • Set retention periods for recordings, transcripts and photos, and actually delete them when the time is up.
  • Clean out dead leads. Old enquiries with no activity and no reason to keep them should not sit in your CRM forever.
  • Control access. Staff should see what they need, and lose access the day they leave.
  • Keep it off personal phones. Customer conversations on a rep's personal WhatsApp are hard to secure, impossible to delete properly and leave with them.

Pay the ICO fee

Most businesses that process personal data electronically must pay the ICO's data protection fee each year, unless an exemption applies. Using a CRM and an AI assistant almost certainly means you are processing personal data electronically. The ICO can fine businesses that should pay and do not.

Pre-launch checklist

  1. Data map written: what the assistant collects and where it goes.
  2. Contracts in place with every provider.
  3. Privacy notice updated.
  4. Form wording and call announcement live.
  5. DPIA done and signed off.
  6. Retention periods set, with deletion actually switched on.
  7. Hand-over rules agreed, including for vulnerable customers.
  8. ICO fee paid.

Where we fit

When we set up an AI chatbot or WhatsApp AI for a client, the form wording, the assistant's introduction and the hand-over rules are written with you and approved by you before anything goes live, and conversations are saved against the lead in Installer Flow, our own CRM. Your own privacy notice and legal advice stay your call. If you want to talk through how the data flows in your setup, book a video call with us.

Sources

Questions owners ask

Do I need customers' consent to record calls?

Not always. Consent is one lawful basis, but businesses often rely on legitimate interests or contract for recording, for example to keep an accurate record of what was agreed. Whatever the basis, the ICO expects you to tell people calls are recorded and why, and to cover it in your privacy notice. Take advice for your own setup.

Do I need a DPIA for an AI chatbot?

Very likely. The ICO says that in the vast majority of cases, using AI to process personal data is likely to be high risk and so needs a data protection impact assessment before you start. For a small installer's assistant it can be a short, practical document, and it is worth doing anyway.

Who is responsible if the AI provider gets it wrong?

You are still the controller of your customers' data, so you carry the main responsibility. Your AI, CRM and phone providers are usually processors acting on your instructions. Have a written contract with each that covers security, where data is stored and what happens to it when you leave.

Tom Spink
Tom SpinkFounder of Attain Digital. Over ten years running Google and Facebook ads, the last five specialising in renewables and home improvement. About Attain Digital →

Book a video call

Let’s talk about growing your business

No hard sell. No pressure. A straightforward conversation about your business, your area, and whether we can help. If it is a fit, we will explain exactly how the system works. If it is not, we will tell you straight.

Calendar not loading? Open it in a new tab.

Rather message first?
Message Tom on WhatsApp
Book a call