Compliance Resource
Consent and Call Notifications for Automated Answering
Callers should know who they are speaking to, what is being collected and why, before they start giving details. This guide covers where notifications belong in a call, how to keep them short, and what to do when a caller objects.
What a caller should be told
Three things, in the opening seconds: which business they have reached, that they are speaking to an automated receptionist, and that the call may be recorded and why. Anything further usually belongs on your privacy page rather than in the caller’s ear.
Under the Personal Data Protection Act, organisations are generally expected to notify individuals of the purposes for collecting their personal data and to obtain consent for those purposes. How that applies to your calls depends on your circumstances, so confirm the position with your own advisers rather than copying another business’s wording.
Being straightforward about automation is also simply better practice. Callers usually work it out within a sentence or two, and a business that appeared to conceal it starts the relationship badly.
Where each notification belongs
Front-load only what the caller needs before giving information. Everything else can wait until it is relevant.
Opening
Business name, automated receptionist, recording notice if calls are recorded. One or two short sentences before the caller is asked anything.
At the point of collection
When asking for a contact number or an appointment detail, say briefly what it will be used for. Purpose stated at the moment of collection is easier to understand than a long preamble.
Before a transfer
Tell the caller what information will be passed to the colleague taking the call, so nothing arrives with a person unexpectedly.
At the close
State what happens next and where the caller can find your privacy information or ask a data question, without reciting a policy.
Writing the wording
Notification wording fails in two directions: too long, so callers interrupt or stop listening, or too vague, so nobody could say what was actually disclosed. Aim for short, specific and spoken in ordinary language.
| Problem | Why it fails | Better approach |
|---|---|---|
| Reciting the policy | Callers stop listening within seconds and interrupt | State the essentials aloud and point to the written policy for detail |
| Legal register | Phrasing written for a document does not survive being spoken | Read every line aloud before approving it |
| Vague purpose | A general reference to business purposes tells the caller nothing | Name the actual purpose, such as confirming bookings and resolving disputes |
| Hiding the automation | Erodes trust the moment the caller realises | Say plainly that this is an automated receptionist |
| Notice after collection | The caller has already given details before being told | Place the notice before the first question |
| No route to object | The caller has been told, but given no choice | Offer a defined alternative, usually a transfer or callback |
Have the final wording reviewed by whoever advises you on data protection, then treat it as fixed text in the call flow rather than something individual staff can vary. Guidance on drafting the surrounding conversation is in our call script writing guide.
When a caller objects
Objections are uncommon, but the response must be decided in advance rather than improvised.
Objects to recording
Decide whether the call can continue without recording, or whether it transfers to a person. Whichever you choose, the caller should be told plainly rather than left guessing.
Wants a human
Honour the request without argument or a second attempt to help. A receptionist that resists handing over teaches callers to distrust it.
Asks what you hold
Access and correction requests belong with your data protection officer. The receptionist should capture the request and route it, not attempt to answer it.
Withdraws consent
Withdrawal needs a route that reaches a person and a record that it happened. Decide who acts on it and how quickly before go-live.
Wants deletion
Route the request and make sure deletion can follow the data through every connected system, as set out in data retention for call records.
Objects to marketing
Record the preference immediately and make sure it reaches whatever list drives your follow-up. See the Do Not Call Registry and call follow-up.
Notification checklist
- The business is named in the first sentence
- The caller is told they are speaking to an automated receptionist
- Recording, where it happens, is disclosed before any question is asked
- The purpose is stated specifically rather than in general terms
- Every objection route has been defined and tested
- Access, correction, withdrawal and deletion requests reach a named person
- The wording has been read aloud and timed
- The spoken notice matches your published privacy information
- Your advisers have reviewed the final wording
Notification is not a substitute for escalation. Telling a caller that the call is automated does not make it appropriate for the receptionist to handle a safeguarding concern, a symptom, a security incident, an allergen question, a distressed caller, a grievance or a request for regulated advice. Those reach a person immediately, whatever the caller consents to.
Frequently asked questions
How long should the opening notice be?
Short enough that callers do not interrupt it, which in practice means one or two sentences. Anything longer belongs in your written privacy information.
Must we say that the receptionist is automated?
We recommend it in every deployment, and expectations around disclosure of automated systems continue to develop. Check the current position with your advisers, but transparency is the safer starting point regardless.
Do we need the notice on every call?
Repeat callers still need to know what is being collected on this call, and a short consistent opening is simpler to operate than logic that tries to recognise returning numbers.
What about callers who speak another language?
A notice the caller cannot understand does little. Where you support a language, the notification should exist in that language; where you do not, route the caller to a person rather than proceeding.
Can consent be recorded automatically?
The call record can show what the caller was told and how they responded. Whether that is adequate evidence for your purposes is a question for your advisers, so agree the standard before go-live.
Where should the written privacy information live?
On a page callers can reach easily, with the same purposes described in the spoken notice. Mismatches between the two are the most common problem we see, and they are also the easiest to fix.
Related reading
Further compliance guides are collected in the resources library.
Hear how the opening actually sounds
We will play the notification wording in a live call flow so you can judge the length and tone, then adjust it to whatever your advisers require.