Recording a Client Call: What to Check Before You Start
Recording internal meetings is low-stakes enough that most people never think about it. A paying client is different, and the difference is not mainly about consent. It is that three other things can go wrong: a confidentiality clause you have not read, a capture that silently fails because the client's own platform blocked it, and an archive of their commercial conversations that outlives the engagement. Here is the two-minute check to run before the call, and the longer questions worth answering once.
This is practice, not legal advice. Recording rules and contract terms vary, and if a specific clause or situation is genuinely unclear, that is a question for your client or your own advisor.
The two-minute check before a client call
Run this before any call where money or confidential information is involved:
- Have I told them? Ideally in the calendar invite, not for the first time as the call starts.
- Does the contract say anything? If you have never checked, do it once now rather than per call.
- Will the capture actually work on their platform? Particularly if they host the call.
- Do I know where this will be stored, and for how long?
- Is this the kind of conversation I should be recording at all?
Most of these are one-time answers for a given client. It is the first call that needs the thought.
Read the confidentiality clause once, properly
If you have an NDA, an MSA, or a services agreement with this client, it very likely says something about their confidential information: how you handle it, where it may be stored, and who may access it. A recording of a client conversation is a copy of their confidential information sitting on a third-party vendor's systems.
Things worth actually looking for: whether the agreement restricts sharing their information with third parties or subprocessors, whether it requires their data to stay in a particular jurisdiction, whether it obliges you to return or delete their material at the end of the engagement, and whether it requires notice before any recording.
You are not trying to reach a legal conclusion on your own. You are trying to find out whether there is a clause that makes this a question. If there is and it reads ambiguously, ask the client directly. In practice that conversation is far easier than people expect, and it is much easier before you have a year of recordings than after.
The wider question of what your obligations are across every tool your company uses is a broader governance topic than one notetaker, and is not covered here.
Ask before the call, not at the top of it
Asking a client for permission at the start of a call puts them on the spot in front of their own colleagues. Most will say yes because it is socially awkward not to, which means you have a yes that is not worth much.
Put it in the calendar invite instead, so they can raise a concern privately in advance, and confirm briefly at the start. Our guide to telling people you are recording has the specific wording for a client call and three other situations, so it is not repeated here.
One point specific to commercial calls: say what happens to the recording, not just that it exists. "It stays with me and my team and I use it for accurate notes" answers the question they are actually forming, which is whether their pricing conversation is about to circulate.
Check the capture will actually work
This is the item most people skip and the one most likely to bite, because when it fails you do not find out until afterward.
If the client hosts the call, their platform settings and their administrator govern whether your tool gets in. Two documented examples show how real this is.
Per tl;dv's own documentation, if its bot cannot join the meeting, the meeting is not recorded, and the host has to admit it. Per Google's own support documentation on meeting access controls (checked 2026-08-04), under certain host access settings, anonymous users and third-party bots such as note takers that try to use "Ask to join" are automatically denied without any action by the host. In that configuration nobody rejects your bot on purpose. It simply never arrives, and if you were not watching the participant list you will not know until you go looking for a recording that does not exist.
Two practical responses. On an important client call, glance at the participant list in the first minute and confirm your tool is actually there. And if the client's environment blocks bots as a matter of policy, a capture mode that does not require admission avoids the problem entirely, which is one of the trade-offs covered in bot in the call versus bot-free capture. What changes per platform is covered in Zoom, Google Meet and Teams.
Decide where the recording will live, before it exists
The answer is rarely "one place," and it is worth knowing before you accumulate a year of client conversations.
Most people end up with two copies: the platform's own recording in their organization's storage, and the notetaker's transcript and summary on the vendor's systems. They follow different retention rules and different administrators. Our guide to where your meeting recordings live covers this in full, including the default access permissions that are usually broader than people assume.
The client-specific question on top of that: who inside your company can open a recording of this client's call? On many team plans the answer is more colleagues than were in the meeting. If that would surprise your client, it is worth knowing now.
The related question of whether your meeting content is used to train a model is covered in does your meeting data train the model, and it is a fair thing for a client to ask you.
What happens to it when the engagement ends
Almost nobody plans this, and it is the cleanest thing on the list to get right.
When a client engagement finishes, you are usually left with an archive of their commercial conversations and no reason to keep it. If your agreement requires deletion or return of their confidential material, that archive is in scope, and it is easy to forget because it does not look like a document.
Set a retention period at the start rather than relying on remembering later. Where your tool supports scheduled deletion, use it. Where it does not, put a task in your own system for the end of the engagement. Deleting a folder of recordings at the close of a project takes two minutes and removes an entire category of future problem.
The meetings not to record at all
Some client conversations are worse for being recorded, regardless of permission.
A negotiation where you want candor from both sides. A conversation about a mistake your team made. A discussion involving personal circumstances of anyone at the client. In each case the presence of a recorder changes what gets said, and what gets said is the thing you were there for.
You can also record selectively. A standing arrangement with a client that you record working sessions but not commercial negotiations is easy to explain and shows judgment. And if the client asks you to stop, stop immediately, without negotiating.
Platform behavior, vendor retention settings and access defaults change with updates. Confirm the current details before relying on any specific one here. If you are still choosing a tool for client work, the hub guide on how to choose an AI meeting note taker covers the criteria.
FAQ
Do I need my client's permission to record a call?
As a matter of practice, tell them in advance and get a clear yes, ideally in the calendar invite. Legal requirements vary by location and by contract, so check yours and get advice if a specific situation is unclear.
Could my contract prohibit recording a client call?
It might restrict how their confidential information is handled, stored, or shared with third parties, which is what a recording on a vendor's systems amounts to. Read the clause once, and ask the client if it is ambiguous.
Why did my notetaker fail to record a client's meeting?
Very likely it was never admitted. Per tl;dv's documentation, if the bot cannot join, nothing is recorded, and per Google's support documentation certain Meet access settings deny third-party note taker bots automatically without host action.
Who at my company can see recordings of my client calls?
Often more people than attended. Team workspaces and platform defaults commonly grant access across an organization, so check both layers before assuming it is only you.
What should I do with client recordings when the work ends?
Delete them unless you have a specific reason to keep them, and check whether your agreement requires deletion or return of confidential material. Set a retention period at the start rather than relying on memory.