Rules and compliance

Call Recording Notices: Wording, Examples and Good Practice

How to tell callers a call may be recorded: when a notice is needed, sample wording for inbound, outbound and AI calls, and a practical rollout checklist.

Call editorial team · Published · 5 min read

"This call may be recorded for training and quality purposes." Most of us have heard it hundreds of times and stopped listening. That is a problem when the notice matters. A good recording notice is short enough to hear, clear enough to understand and placed where it can be acted on. This guide covers when you need one, what to say, and how to roll it out across a team.

A support agent wearing a headset at a desk answering a phone call
Illustrative image

Why a notice matters

There are three reasons to tell callers about recording. The first is law: in many places you must tell people, and in some you need their agreement. The second is trust: callers who learn afterwards that they were recorded feel deceived. The third is practical: a clear notice reduces awkward moments when a caller asks, halfway through, whether they are being taped.

The reverse also applies. A notice is not a substitute for a lawful reason to record. You still need a purpose, a limit on who can listen, and a retention period. See Call Data Retention and Backups and data minimisation in support for those.

How the rules differ in broad terms

Rules vary, but they tend to fall into a few patterns. Always confirm the details for your situation.

PatternWhat it usually meansExample reading
One-party consentOne participant on the call, such as your agent, may agree to the recordingSeveral US states and other jurisdictions; see two-party consent explained
All-party consentEveryone on the call must be told, and often must agree, before recordingSome US states and some other countries
Data-protection basedYou need a lawful reason, you must inform people, and they have rights over the recordingThe EU and UK; see GDPR and call recording
Sector rulesExtra duties for financial, health or public-sector callsVaries by sector and country

Callers can also be in different places from your business. A call between a firm in one state and a customer in another may be governed by the stricter rule, and many businesses simply apply the stricter standard to every call to keep things simple. For the US background see the Federal Trade Commission, and for UK data protection see the Information Commissioner's Office.

Sample wording

Use plain language. Say what happens, why, and what the caller can do. Test the wording by reading it aloud at normal speed; if you stumble, the caller will not follow.

Weak and strong notices

WeakStrong
WordingCalls may be monitored in accordance with our policy.This call may be recorded so we can check quality and help train our team.
TimingSaid after the caller has started explainingSaid before any recording starts, right after the greeting
ChoiceNone offeredTells the caller what to do if they do not want to be recorded
LengthA long legal paragraphOne or two short sentences

Those examples are hypothetical. Adapt them to your business and your rules. For AI agents, also read AI disclosure on calls; in many places people expect to be told they are talking to an automated system.

When a caller does not want to be recorded

Decide your policy before the first caller asks. Some businesses stop the recording, others offer another channel such as email, and some tell the caller the call cannot continue unless it is recorded because of a legal duty. Whichever you choose, staff need a calm script and the ability to act on it.

Responding to 'I don't want to be recorded'

  1. Acknowledge"That's fine, thank you for telling me."
  2. ActPause or stop the recording if your system and policy allow, or offer another channel.
  3. Explain brieflySay what you can and cannot do without the recording.
  4. Note itRecord that the caller declined, using the system's note field.
  5. Follow upReport repeated objections so the policy can be reviewed.

Outbound calls, AI agents and recorded messages

Outbound calls raise their own questions. The person called did not choose to ring you, so the opening matters even more: say who you are and why you are calling before anything else, then mention recording. If your team calls across regions, apply the stricter notice across the board. Calling rules such as permitted hours and do-not-call lists are separate duties; TCPA basics for US calls and outbound call basics cover them.

AI agents add a second statement. People are entitled in many places to know they are speaking to a machine, and they are generally entitled to know about recording too. Keep the two sentences distinct and short. Do not bury either in a long greeting. And remember that a transcript is also a record: it is stored text, so apply the same retention and access rules that you apply to audio.

Who can listen, and for how long

A notice usually says the call may be recorded for quality and training. If you also use recordings for disputes, compliance checks or coaching, say so or make sure your wider privacy notice does. Limit playback to the people who need it, such as managers and quality reviewers, and keep an eye on who has access. Delete recordings when their purpose ends; access controls for a contact centre explains how to keep listening rights tight.

Rolling it out across the team

Recording notice checklist

  • Decide which lines and queues are recorded and why
  • Write one notice per call type: inbound, outbound, voicemail, AI
  • Record or script the notice so every caller hears the same words
  • Place the notice before any recording starts
  • Train staff on the objection script
  • Store the wording and the date it took effect
  • Review annually and whenever your business or the law changes

Keep records. If a regulator, a customer or a court asks what callers were told on a given date, you want to answer from a file rather than from recollection. Handling personal information on calls covers the related duties.

Doing it in Call

In Call, each phone line has a monitoring notice setting under its rules for calls. You choose between the default, which tells callers where recording needs consent, always, or never. It saves immediately, and the page says what callers hear now. Queues can also play a recording announcement before callers are connected. Which calls are recorded at all is an operator setting, and with no rule in place every call is recorded, so check it. Required disclosures for agents can also be defined by an operator. Only owners, administrators and managers can change the monitoring notice.

Frequently asked questions

Do I always have to tell callers about recording?

Not everywhere, but in many places you do, and telling them is good practice even where it is not required. Check the rules where your callers and your business are.

Is 'calls may be monitored' enough?

Rarely strong wording. Say that calls may be recorded, why, and what the caller can do. Vague phrases are easy to miss and hard to defend.

What if the caller says no?

Have a policy: pause or stop recording, offer another channel, or explain if recording is required. Give staff a short script and a way to note the objection.

Do voicemails need a notice?

A short line saying the message will be recorded and heard by your team is sensible. People expect it, but saying it removes doubt.

Does an AI agent need to say it is recording?

Treat recording and AI disclosure as two separate statements. Both are often expected, and in some places required, so say both clearly.

How long should I keep recordings?

As long as you have a clear purpose for them and no longer. Set a retention period, apply it and review it regularly.

Set the recording notice on your phone lines in Call

In the demo console you can try incoming calls in a simulation.

Related guides