Technology and AI

Automated call handling and UK GDPR

A UK GDPR plan for automated call handling in a law firm: DPIA, lawful basis, the spoken notice, processor terms, retention and automated decisions.

Ava research teamPublished 7 min read

On this page
  1. Why automated calls need a data protection plan
  2. The plan in eight steps
  3. The DPIA
  4. Lawful basis and sensitive data
  5. Telling callers at the right moment
  6. The processor contract
  7. Retention by data type
  8. Automated decisions
  9. Rights requests, complaints and breaches
  10. Example: a DPIA summary
  11. Related guides
  12. Frequently asked questions
  13. References

Key takeaways

  • Callers to a law firm often share health, criminal and family details, so automated call handling usually warrants a DPIA before launch.
  • Give a short spoken notice at the start of the call and a full privacy notice online; UK GDPR requires information when data is obtained.
  • The call handling supplier is a processor: the contract must cover instructions, security, sub-processors, deletion and audits.
  • Set retention per data type and keep people in charge of any decision that significantly affects a caller.

Why automated calls need a data protection plan

People ringing a solicitor rarely keep to names and addresses. Within a minute they may mention a diagnosis, an arrest, a violent partner or a child's circumstances. When an automated service answers, that information is captured, transcribed, perhaps recorded, and stored by a supplier, often before anyone at the firm has spoken to the caller. That is exactly the kind of processing UK GDPR expects you to plan for in advance.

Callers are alert to the risk. In the Legal Services Board's 2026 public panel research, AI acting without the user's knowledge or consent was the single most urgent AI concern, named by 56% of legal service users[1]. A clear plan protects callers and gives the firm a straightforward answer when someone asks what happens to their information.

Legal service users naming AI acting without their knowledge or consent as the most urgent concernLegal Services Board public panel, 2026
Legal service users naming AI acting without their knowledge or consent as the most urgent concernDonut chart. Most urgent concern: 56%.Most urgent concern: 56%56%
  • Most urgent concern 56%

Source: Legal Services Board, 2026[1]

Show the data
ItemValue
Most urgent concern56%

The plan in eight steps

  1. Map the data

    List what the service collects: audio, transcripts, structured notes, phone numbers, booking details. Record where each is stored and who can see it.

  2. Carry out a DPIA

    Assess the risks and the measures that reduce them before the service goes live.

  3. Choose lawful bases

    Identify the lawful basis for each purpose, and the additional condition for any special category or criminal offence data.

  4. Write the notices

    Prepare a short spoken notice for the start of each call and update the full privacy notice on your website.

  5. Sign processor terms

    Put a compliant contract in place with the supplier and check its sub-processors.

  6. Set retention

    Decide how long each type of data is kept and make sure the supplier's settings match.

  7. Design for rights and complaints

    Make sure you can find, export and delete a caller's data, and handle data protection complaints.

  8. Plan for breaches

    Agree how the supplier tells you about incidents and how you decide whether to notify.

The DPIA

UK GDPR requires a data protection impact assessment before processing that, in particular using new technologies, is likely to result in a high risk to people's rights and freedoms[2]. A DPIA is specifically required for large-scale processing of special category data or criminal offence data, among other cases[2]. A small firm's call line may not be large-scale, but automated handling is new technology, callers routinely volunteer sensitive information, and the consequences of mistakes can be serious. Most firms will find it easier and safer to complete a DPIA than to document why one is not needed.

The assessment must contain at least a description of the processing and its purposes, an assessment of its necessity and proportionality, an assessment of the risks to individuals, and the measures to address those risks[2]. Keep it practical. For an automated call line, the key risks are usually: over-collection of sensitive details, disclosure to the wrong person, retention for longer than needed, callers not understanding they are dealing with an automated system, and supplier access to recordings.

Lawful basis and sensitive data

For new enquiries, firms commonly rely on taking steps at the caller's request before entering into a contract, or on legitimate interests in responding to enquiries and managing the firm's work. Recording calls, using transcripts to check quality, or reviewing calls for training are separate purposes; consider each one and record your reasoning.

Health details, information about sex life or sexual orientation, and similar special category data need an additional condition, as does information about criminal offences. For a law firm, conditions relating to legal claims and legal advice are often relevant, but take advice and record your conclusion in the DPIA. A simple design choice reduces the risk: script the assistant to ask only what is needed to route and book the enquiry, and not to probe for sensitive details.

Telling callers at the right moment

Where personal data is collected from the person, UK GDPR requires the controller to provide privacy information at the time when personal data are obtained[3]. That information includes who the controller is, the purposes and lawful basis, recipients, how long data will be kept, the person's rights, the right to complain, and the existence of automated decision-making where it applies[3].

Nobody wants a privacy notice read out in full at the start of a call. A layered approach works: a short spoken notice, then the full notice on your website and in any follow-up message. For example: “You’re speaking to our automated assistant. It will take your details so that one of our team can help you, and this call may be recorded and transcribed. It can’t give legal advice. You can ask for a person at any time, and our privacy notice is on our website.”

The processor contract

The supplier of the call handling service processes personal data on the firm's behalf. Controllers may only use processors that give sufficient guarantees of appropriate technical and organisational measures, and the contract must require the processor to act only on documented instructions, ensure staff confidentiality, keep data secure, follow rules on sub-processors, help with individuals' rights and with security and impact assessments, delete or return data at the end, and allow audits[4]. Ask specifically whether call audio or transcripts are used to train or improve the supplier's systems, and where any such processing takes place.

Retention by data type

Set actual periods in your retention schedule and make sure supplier settings match them.
DataPurposeSuggested approach
Call audioQuality checks, disputes about what was saidShort period, then delete automatically, unless needed for a specific dispute
TranscriptProducing and checking the noteDelete once the note is checked, or keep for the same short period as audio
Structured enquiry noteConflict search, booking, follow-upMove to the matter file if instructed; otherwise keep per your enquiry retention policy
Enquiries that did not proceedConflict history, complaintsKeep minimal details for a defined period, then delete
Booking recordsAppointments and remindersFollow the matter or enquiry record
Supplier logsSecurity and troubleshootingSupplier's period, stated in the contract

Telling callers how long data will be kept is part of the privacy information[3], so the periods you choose must be ones you can actually apply. Check that deletion at the supplier really happens, including in backups, and record the check.

Automated decisions

Under the Data (Use and Access) Act 2025, significant solely automated decisions require safeguards, including letting people challenge decisions and obtain human intervention[5]. An assistant that decides on its own that a caller is not eligible for an appointment, or that their matter is not worth a call back, comes close to that territory. The safer design is for the assistant to gather details and book or request a consultation, while people decide whether the firm can act, and for every caller to have a route to a person.

Rights requests, complaints and breaches

Make sure you can find a caller's data quickly, using a phone number or name, across audio, transcripts and notes. Subject access requests will increasingly include call data. The 2025 Act also requires organisations to handle data protection complaints from individuals, for example by providing an electronic complaint form, and to tell them the outcome[5].

If something goes wrong, such as a recording sent to the wrong person or a supplier incident, a notifiable personal data breach must be reported to the regulator without undue delay and, where feasible, within 72 hours of becoming aware of it[6]. Agree with the supplier how quickly it will tell you, what information it will provide and who your contact is out of hours.

Example: a DPIA summary

Example (fictional): a ten-person firm's DPIA for its automated call line identifies four main risks: callers volunteering health or criminal details, disclosure of existing matter information, recordings kept indefinitely, and callers not realising the line is automated. The measures are a script that asks only routing and booking questions, a rule that existing matters are never discussed, audio deleted after 30 days and transcripts once notes are checked, and a spoken opening notice. Residual risk is assessed as low, and the DPIA is reviewed after three months of live calls and whenever the supplier changes a sub-processor.

Regulatory points beyond data protection are covered in AI phone answering and the SRA. For design choices that reduce data risk, see designing an AI intake assistant and when an AI assistant should hand a call to a person. Follow-up contact rules are explained in unsolicited approaches to prospective clients, and the difference between service types in AI receptionist vs AI employee.

Frequently asked questions

Do we need a DPIA for AI call answering?

Usually it is the safe course. UK GDPR requires one where processing using new technology is likely to be high risk, and callers to law firms often share health, criminal and family information.

What should an automated call line tell callers about their data?

At the start: that it is automated, that details are taken so the team can help, whether the call is recorded or transcribed, that it cannot give advice and where the full privacy notice is. The full notice covers purposes, lawful basis, retention, rights and complaints.

How long should call recordings be kept?

Only as long as needed for a clear purpose such as quality checks or resolving disputes. Many firms set short periods and delete transcripts once the note is checked. Record the periods in your retention schedule.

Can an AI assistant decide whether to give a caller an appointment?

It is safer for people to make decisions that significantly affect callers. Significant solely automated decisions require safeguards, including human intervention and the ability to challenge.

References

  1. Legal Services Board (2026). AI in Legal Services: Research Report (LSB Public Panel) (opens in a new tab) ↑

  2. legislation.gov.uk (The National Archives) (2016). UK GDPR Article 35: Data protection impact assessment (opens in a new tab) ↑

  3. 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) ↑

  4. legislation.gov.uk (The National Archives) (2016). UK GDPR Article 28: Processor (opens in a new tab) ↑

  5. GOV.UK (DSIT) (2025). Data (Use and Access) Act 2025: data protection and privacy changes (opens in a new tab) ↑

  6. legislation.gov.uk (The National Archives) (2016). UK GDPR Article 33: Notification of a personal data breach to the supervisory authority (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo