// Recruitment Technology, Recruitment Strategies
What Recruiters Say Before They Hit Record
Published: 08 October 2026,
9 min to read
The bottom line
Consent to record is treated as a legal blocker when the real constraint is wording. UK, EU, US and Asian law all permit recorded business calls under clear conditions. What decides the answer is the sentence your recruiter says first. Agencies that script that sentence build a usable record, and the rest collect gaps.
The consent script your team is improvising every day
Every agency has a recruiter who records everything and one who records nothing. Both are convinced they are the compliant one.
The distance between them is rarely a policy gap. GDPR call recording consent gets filed as a legal question, so it goes to whoever owns compliance. They write a disclosure. It gets read aloud at the top of a cold BD call in a flat voice. Candidates hear a legal notice, and they respond the way people respond to legal notices.
Across the 48 agencies that raised this with us on recorded calls, one pattern held. The teams with high consent rates had agreed on the exact words in advance.
That matters more every year. 80.82% of agency recruiters now use AI for admin and data entry. The commercial value of a conversation now depends on whether a system heard it. A call nobody captured leaves the business the moment the recruiter does.
What does GDPR call recording consent actually require?
Less than most agencies assume. Under the general data protection regulation you need a lawful basis for recording. Consent is only one of the six lawful bases set out in Article 6, and legitimate interests often fits a recruitment agency better.
The regulator agrees. ICO guidance works through a recruitment example. A candidate who posts a CV to a job board gives the agency a likely lawful basis in legitimate interests.
What the law does require is transparency. People must know the call is being recorded and what the stated purpose is. They also need to know who sees it and how long you keep it. That is a privacy notice plus a spoken line.
A signed consent form is rarely the requirement. The UK’s lawful business practice rules allow recording of business calls for defined purposes. Evidencing a transaction and quality assurance both qualify, provided you tell the parties involved.
Two things change the calculation. Explicit consent becomes the standard when a recording captures sensitive personal data. A candidate disclosing a health condition that affects a notice period triggers exactly that.
Candidates are also data subjects with rights, so a subject access request can reach the recording itself. Under the Data Protection Act 2018 you have to find the file. That is impossible when it lives on a recruiter’s phone.
Where do the US and Asia draw different lines on recording calls?
In the US the line moves by state, and your recruiters are rarely sitting in the state they are calling.
Federal law and most states run on one-party consent, so a participant can record a call. A smaller group requires everyone to agree. In California, all parties to a confidential conversation must consent before it is recorded. The exposure there is criminal as well as civil.
Because the strict states carry the real risk, national desks default to all-party notice on every call. One script, no exceptions. It costs a sentence. Nobody then works out which call recording laws covered a Denver to Los Angeles call.
State-level rules are summarized in the Reporter’s Recording Guide. It is the cleanest public reference for a multi-state desk.
Asia is less uniform again. Singapore’s Personal Data Protection Act sets a baseline for how organizations handle personal data, with business contact information largely carved out of scope. Japan and Hong Kong each run their own regime. A retained search can touch several in a week.
The practical conclusion is the same everywhere. Tell people before you record, in language they understand, and the different rules stop mattering to your recruiters.
Why does the wording of the ask decide the answer?
Because the words signal intent, and intent is what the other person weighs before replying.
Consider two sentences carrying identical legal weight. “This call is being recorded for training and monitoring purposes” puts the recruiter and the candidate on opposite sides. “I use a note taker so I can be fully present” puts them on the same side. Same recording, same retention period, opposite hit rate.
Vocabulary does most of the work. Recording implies surveillance and storage of something that could be used later. Note taker implies a summary, and a summary is something a candidate can picture. Agencies that switched the noun report the objection rate falling without touching a policy document.
The ask then changes with the setting:
- Cold BD calls. Keep it to one clause inside your opener and keep moving. Something like “I take AI notes on calls so nothing gets missed, say if you would rather I didn’t.” Pausing for a formal yes turns a BD call into a compliance conversation.
- Booked candidate interviews. Do the work before the meeting. Put the line in the calendar invite and the confirmation email, then repeat it in one sentence as you open. Nobody who has read it twice objects on the call.
- Client intake meetings. Frame it as accuracy, because accuracy is what the client wants. Recorded intake meetings prevent the “that is not what we briefed” conversation at shortlist stage.
- In-person meetings. This is where recruiters hesitate, since the phone has to come out of the pocket. Name what the phone is doing, put it face down, and carry on.
What happens to the recording after they say yes?
This is the half of call recording compliance that agencies skip, and the half a regulator asks about first.
A recording sitting in a personal phone folder or a standalone transcription app is a liability with no upside. It falls outside your retention policies and stays invisible to a subject access request. It is also useless to whoever covers the desk next quarter.
The version that works puts capture inside the system of record. That is what Atlas does, an AI-powered recruitment platform using agentic AI to strip admin out of recruiting. It runs the AI note taker step natively. Calls are transcribed and matched to the right candidate or client record the moment they end.
In-person conversations are captured from the phone and synced back later. They are stored securely on the device until the upload completes.
Permission stays where it belongs. If the bot is not invited to the meeting, nothing is recorded. Any recording can be deleted from the platform afterward.
What a team gets back is a searchable record instead of an archive nobody opens. Every intake meeting and interview feeds Total Memory. The salary figure mentioned in passing is still retrievable eight months later. Transcription on its own does not do this, which is the argument behind interview transcription software that outlives the transcript.
The time shows up quickly. Tech Valley Recruiting saves at least 30 minutes per candidate report. The detail is captured and structured before anyone sits down to write.
Frequently asked questions (FAQs) on call recording consent
Not in most cases. Consent is one of six lawful bases in Article 6, and legitimate interests often fits a recruitment agency better. You do need to pass the three-part test the ICO sets out. Explicit consent becomes necessary when the recording is likely to capture sensitive personal data, such as health information.
Legally, no. A note taker that creates audio or a transcript processes personal data in the same way a recording does. The same lawful basis and transparency duties apply, along with the same retention period. The difference sits in how people react to the word, which is why phrasing matters commercially.
One clause, delivered inside the opener rather than before it. A line such as “I take AI notes on these calls so nothing gets missed” meets the transparency requirement without inviting a negotiation. Keep it in the same tone as the rest of the call, then move straight into why you are ringing.
A minority of states, California among them, require every party to a confidential conversation to agree before it is recorded. Federal law and most states allow one-party consent. Because recruiters call across state lines constantly, the workable policy is all-party notice on every call, wherever either person is sitting.
Set a defined retention period tied to the stated purpose and apply it automatically. Many agencies align recordings with the retention policy already covering candidate records, then delete on the same schedule. The requirement is that the period is documented, justified, and genuinely enforced by the system holding the files.
Proceed without recording and take manual notes, then log the refusal against the candidate record so nobody asks again. In Atlas, a meeting the bot is not invited to is never captured, and an existing recording can be deleted. Refusals are rare when the purpose is explained in plain terms.
The compounding cost of conversations nobody kept
Consent is a solvable problem. It needs an agreed script and a system that stores what the script unlocks. Agencies still treating it as a legal blocker lose the detail from every conversation. That loss compounds quietly across a year of billings.
Set against that, the decision in front of most operations directors is a small one. Moving capture into an AI-powered CRM costs a sentence at the start of a call. What comes back is a database that records, transcribes, files and surfaces every conversation without a recruiter touching it. The platform built for that gap is Atlas, and the gain grows with every call your team already makes.
Worth a look if your recruiters are still rebuilding notes from memory on a Friday afternoon.



