Recording calls when an
AI receptionist answers
In Ireland, recording a call is not unlawful interception when a party to the call consents, but GDPR still applies in full. Tell callers in the first seconds that they are talking to an AI and that the call is recorded, offer a person, set short retention, and treat transcripts as personal data.
Three sets of rules apply to one phone call
An AI receptionist answers the call, converts speech to text, sends the text to a language model, speaks a reply, and often keeps a recording, a transcript and a summary. Three separate sets of rules apply:
| Rules | What they cover | Main point for you |
|---|---|---|
| Interception law (1983 Act, as amended in 1993) | Listening to or recording calls in transmission | Recording is not interception where the sender or the intended recipient consents. |
| GDPR and the Data Protection Act 2018 | The recording, transcript, summary and caller details | You need a lawful basis, a notice at the start, retention limits and a way to handle rights requests. |
| EU AI Act, Article 50 | Telling people they are talking to an AI | From 2 August 2026, say it is an AI at the start of the call. |
The interception position
Section 98 of the Postal and Telecommunications Services Act 1983 makes it an offence to intercept telecommunications messages. The Interception of Postal Packets and Telecommunications Messages (Regulation) Act 1993 inserted a definition of “intercept”: to listen to, or record by any means, a message in the course of its transmission. The definition excludes listening or recording where either the person who sends the message or the person intended to receive it has consented.
When a caller rings your business and your system answers, your business is the intended recipient of the call. On that reading, your own recording of calls to your own line is not interception under section 98. That does not make the recording lawful under data protection law. GDPR is a separate test, and it is the test the DPC applies to business call recording.
What GDPR requires for recordings and transcripts
A voice recording of an identifiable person is personal data. So is the transcript, the AI summary and the caller’s number. Plan for all of them:
- Lawful basis. Answering a caller about their own booking is usually necessary for a contract. Keeping recordings for quality or training of staff is usually legitimate interests, with a written balancing test. Do not use consent as the basis for something the caller cannot refuse.
- Notice at the start. Article 13 requires you to give information when you collect the data. On a call, use a short spoken notice and point to the full privacy notice on your website or by text message.
- Right to object. If you rely on legitimate interests, callers can object. Give them a way to continue without the recording, such as a call-back from staff.
- Processors. The telephony provider, the speech-to-text service, the model provider and your developer are processors. You need a DPA with each and a record of where they process data.
- Access requests. A caller can ask for their recording and transcript. Make sure you can find calls by phone number and date.
What to say at the start of the call
The opening must do three jobs in a few seconds: say it is an AI, say the call is recorded and why, and give a way to reach a person. Keep it short: about 15 seconds is a sensible target. An example for a dental practice:
- Speak the AI statement first, before any question. The Commission’s Article 50 guidelines give a spoken statement at the beginning of the call as the example for voice systems.
- Do not play music over the opening, and do not speed it up.
- If a caller asks “Am I talking to a real person?”, the agent must say it is an AI.
- For long calls, or calls about health, add a short reminder after a transfer or a long pause.
- If a caller objects to recording, stop the recording or pass the call to staff, and log that you did.
The same rules on wording apply to other channels. See our AI disclosure guide.
Retention, transcripts and clinic data
GDPR sets no fixed period. You decide, and you must be able to justify it. Audio is the most sensitive form and the least useful after a few weeks, so many businesses keep the summary longer than the recording. The periods below are an example to adapt, not a legal standard.
| Data | Why you keep it | Example period |
|---|---|---|
| Call audio | Resolve disputes and check the agent’s quality | 30 days, then automatic deletion |
| Full transcript | Review errors and improve prompts | 90 days |
| Booking record and short summary | Run the appointment and the customer record | As long as the customer record |
| Provider logs (speech-to-text, model) | Abuse monitoring by the provider | Match to the provider’s terms; choose zero retention where offered |
Clinics and other health services. Callers will mention symptoms, medication and conditions, even when the agent only books appointments. That is health data, a special category under Article 9 of GDPR, and it needs an Article 9 condition in addition to an Article 6 basis. Keep clinical detail out of the summary unless staff need it, prefer EU processing, use short audio retention, and do a DPIA before launch. Our clinics page and DPIA template cover this in more depth.
Emotion recognition. Some voice platforms offer sentiment or emotion scoring. Article 5 of the AI Act bans emotion recognition of staff in the workplace, and in Ireland the Workplace Relations Commission supervises that ban. If you apply emotion recognition to callers, Article 50(3) requires you to tell them. Most receptionists do not need it, so turn it off.
A checklist before the receptionist goes live
- Write the call opening and test it on a real phone line, including on a mobile with poor signal.
- Update the privacy notice to cover recording, transcription, the AI provider and retention.
- Sign DPAs with the telephony, speech-to-text and model providers, and record where each processes data.
- Set automatic deletion for audio and transcripts, and check that it runs.
- Test the routes to a person: the spoken keyword, a failed answer, and a caller who objects to recording.
- Test the question “Am I talking to a real person?” and check the answer.
- Turn off emotion or sentiment scoring unless you have a clear reason and a notice for it.
- Name one member of staff who reviews a sample of calls each week for the first month.
If you want to compare the cost of this setup with extra reception hours, our AI receptionist vs staff calculator shows both in euro.
Common questions
Is it legal to record calls in Ireland without telling the caller?
Interception law does not prohibit recording where a party to the call, such as your business as the intended recipient, consents. GDPR is the stricter test: you must tell callers about the recording when you collect the data, and have a lawful basis. In practice, a short notice at the start of every recorded call is needed.
Does the AI receptionist have to say it is an AI?
Yes, from 2 August 2026, under Article 50 of the EU AI Act, unless it is obvious, and on a phone call it is rarely obvious. The Commission’s guidelines give a spoken statement at the start of the call as the example. The agent must also answer truthfully if a caller asks whether it is a person.
How long should we keep call recordings?
As long as you need them for a stated purpose, and no longer. GDPR sets no fixed number. Many businesses keep audio for a short period, such as 30 days, and keep only the booking and a short summary after that. Write the periods in your retention schedule and automate deletion.
Are call transcripts personal data?
Yes. A transcript of an identifiable caller is personal data, and so is an AI summary of the call. Callers can request them, and they count toward your retention and security duties. In a clinic, transcripts will often contain health data, which is special category data under Article 9 of GDPR.
Sources
- Revised Acts (Law Reform Commission): Postal and Telecommunications Services Act 1983, section 98 as amended
- EDPB register: DPC record of amicable resolution on call recordings (9 September 2022)
- DPC: AI, Large Language Models and Data Protection
- DPC: Data Protection Impact Assessments
- European Commission: Guidelines on transparency obligations under Article 50 (20 July 2026)
- EUR-Lex: Regulation (EU) 2024/1689 (AI Act)
- Irish Statute Book: S.I. No. 405/2026 (WRC designation for Article 5(1)(f))
We last checked these sources on 19 November 2026. Rules, fees and prices change. Check the source before you act.
Bring us the task.
Tell us what happens today, which tools are involved and where it goes wrong. On a free 30-minute review, we’ll work out whether an agent, an automation or neither is the right fix, and what a sensible first release would be.
Start a project.

Book a call or send us a message. We read everything.
tash@neu.ie
Working with teams in Ireland and worldwide.
Free 30-minute AI review.