What is call recording consent?

Why it matters

A recording of a call in which people can be identified is personal data under the GDPR. That has two practical consequences for a sales team. First, you need a lawful basis to record (Article 6): consent is one, legitimate interest is another, and which one fits depends on your situation. Second, you must tell the people on the call that you record, why, how long you keep it and what their rights are (Article 13). Some countries add their own rules on recording conversations.

There is a trust side too. A prospect who discovers afterwards that a call was recorded rarely trusts the rest of the deal. Saying it clearly at the start costs ten seconds.

This page is general information, not legal advice. Check your own situation with your data protection officer or legal counsel.

Example

A video call starts at 00:00. The meeting bot joins and announces that the call is recorded. At 00:15 the prospect asks: “What do you do with the recording, and how long do you keep it?” The rep answers in two sentences and offers to send the privacy notice. The prospect agrees, and the call continues. For an in-person meeting, the rep asks the same question at the start, on the recording.

How Drummer handles it

Drummer’s meeting bot announces the recording when it joins Google Meet, Microsoft Teams, Zoom or Webex. In the phone app, the rep asks at the start of the meeting and Drummer notes from the recording that the customer agreed.

Recordings and transcripts stay in the EU (AWS Frankfurt, EU transcription, EU-hosted models), are never used to train models, and follow your retention settings. Roles keep calls visible to the right people only, audit trails show who did what, and a DPA is available on request. See security and how to record sales calls under GDPR.