Do Indian sales teams need consent to record sales calls under DPDPA?
November 22, 2026
November 22, 2026
Yes, in almost every case. A recorded sales call is digital personal data under the Digital Personal Data Protection Act, 2023, so you need a Section 5 notice and Section 6 consent, a clear “yes” rather than silence, before you record, transcribe or score it. Consent must be as easy to withdraw as to give, and you must be able to prove it. These duties apply from 13 May 2027.
Most Indian sales floors record every call. Diallers do it by default, CRMs attach the audio to the lead, and an AI layer turns the recording into a transcript, a sentiment tag and a lead score. Until now the only rule anyone checked was TRAI’s: are we allowed to make this call? From 13 May 2027 a second question applies to every recording under the Digital Personal Data Protection Act, 2023 (DPDPA): did the person on the line agree to what we are doing with their voice and words?
In this guide we explain why a recording is personal data, why “this call may be recorded” is not consent, how TRAI’s 18 September 2026 amendments sit alongside DPDPA, and what sales operations should change before May 2027.
DPDPA applies to digital personal data, and a call recording is exactly that: an audio file that identifies a person by voice, name and number, stored on a server. The transcript is personal data. So are the CRM notes, the sentiment tag and the “likely to buy” score that your AI dialler derives from the conversation. Each of these is processing, and under Section 4 processing is lawful only with consent under Section 6 or for one of the legitimate uses listed in Section 7.
Section 7(a) helps with inbound calls: when a prospect voluntarily gives you their details for a specified purpose, such as asking for a quotation, you may use them for that purpose without separate consent, as long as they have not objected. It does not stretch to recording the call for training, feeding an AI model or pitching a different product. Those are separate purposes and need separate consent.
No. That sentence is a notice, and an incomplete one. Section 6(1) requires consent that is free, specific, informed, unconditional and unambiguous, given by a clear affirmative action. A prospect who stays on the line has not acted; they have simply not hung up, and the Act says consent cannot be inferred from inaction. Section 6(3) also requires the request to be in clear, plain language, with the option to receive it in English or any of the 22 languages in the Eighth Schedule, and to carry the contact details of the person who answers data questions for your company.
Section 6(10) adds the part most sales leaders miss: if a complaint reaches the Data Protection Board, the burden of proving that notice was given and consent obtained sits with you, the Data Fiduciary. A dialler log that says “call connected” proves nothing. You need the notice version, the words the prospect used to agree, the timestamp and the purposes they agreed to, kept for at least the one year that Rule 6(1)(e) requires for processing logs.
It does not. The Telecom Commercial Communications Customer Preference Regulations, 2018 (TCCCPR) govern the right to place a commercial call: DLT registration, the 140 series for promotional calls, the 1600 and 1601 series for service and transactional calls, and DND preferences. DPDPA governs what you do with the personal data the call creates. The Third Amendment to TCCCPR, notified by TRAI on 18 September 2026, makes the overlap sharper for sales teams.
| Question | TRAI TCCCPR 2018 (as amended Sept 2026) | DPDPA 2023 and DPDP Rules 2025 |
|---|---|---|
| May we dial this number? | Yes, if DND preferences and DLT consent allow it; a written or digital customer inquiry permits follow-up for seven days | Not TRAI’s question, but the inquiry is a Section 7(a) purpose you must stay within |
| May we use a robocall or autodialler? | Only after pre-declaring the A2P calls and numbers to your telecom provider; undeclared A2P calls are treated as spam and attract a termination charge of up to 5 paise a minute | The recording and transcript still need Section 5 notice and Section 6 consent |
| May we record and transcribe the call? | Silent on recording | Consent for recording; separate consent for AI analysis, scoring or training |
| May we keep legacy consents? | Yes, if obtained through verifiable means and registered on the telecom provider’s digital platform | Only if they meet Section 6(1); otherwise a Section 5(2) notice and fresh consent |
| How does the customer withdraw? | DND registration or a complaint to 1909; appeal within 15 days | As easily as consent was given (Section 6(4)); processing must stop within a reasonable time (Section 6(6)) |
| What is the exposure? | Header or template suspension within six hours; telemarketer resources disconnected for a year | Up to ₹50 crore for consent breaches; up to ₹250 crore for failing to secure the recordings |
The two regimes run in parallel, and clearing one does not clear the other. We covered the messaging side of this in our guide to WhatsApp and SMS marketing under DPDPA.
A compliant opening is shorter than most legal teams fear. It needs five elements, delivered before recording begins.
If the prospect says no, the call can continue without recording, or the agent takes notes by hand for the Section 7(a) purpose only. What you cannot do is record anyway. For calls to people under 18 the parent must consent, so B2C teams selling coaching or education products need an age check in the script.
Section 6(4) gives every Data Principal the right to withdraw consent at any time, with the ease of doing so comparable to the ease with which it was given. A consent given by one spoken word cannot require an email to a legal department to undo. Section 6(6) then requires you, within a reasonable time, to cease processing and to cause your Data Processors to cease as well, and Section 8(7) requires erasure once consent is withdrawn or the purpose is served, unless another law requires you to keep the data. We explained the processor side of this in what your CRM vendor contract must include.
In a sales stack the withdrawal has to travel. The recording sits in the dialler, the transcript in the CRM, the lead score in the analytics tool and a copy in the backup. A withdrawal that stops the next call but leaves the audio in four systems is not compliance. Make the CRM the single place where consent status changes and is pushed outward.
We built QQCRM, our AI CRM accelerator, so that consent status, purpose and retention travel with each contact record and reach every connected tool, and DAPro (Data Adhikaar) to manage notices in 22 languages, consent and withdrawal requests, with a tamper-evident Evidence Vault and 25+ connectors to the diallers, CRMs and analytics systems where your recordings already live. If you would like us to review your call scripts and consent flow, book a 30-minute call with our team.
Recording itself is not prohibited by a dedicated statute, but a recording of an identifiable person is digital personal data under DPDPA. From 13 May 2027 you will need a Section 5 notice and valid Section 6 consent before recording, transcribing or analysing a sales call, unless a legitimate use under Section 7 applies to that specific purpose.
No. It is a notice, and usually an incomplete one. Section 6(1) requires consent given by a clear affirmative action, so the prospect must actually say yes after hearing what will be recorded, why, for how long and how to withdraw. Staying on the line is inaction, which the Act does not treat as consent.
No. TRAI’s TCCCPR regulations decide whether you may place a commercial call, including the 18 September 2026 rules on pre-declaring robocalls and autodiallers. DPDPA decides what you may do with the recording, transcript and derived data. A call can be fully TRAI-compliant and still breach DPDPA if the recording was made without valid consent.
Yes, if the consent covers it. Transcription, sentiment tagging and lead scoring are separate processing purposes, so the notice should name them and the consent should extend to them. Consent captured only for recording does not stretch to AI analysis, and using recordings to train a model is a further purpose that needs its own consent.
Withdrawal must be as easy as giving consent, and once received you must stop processing within a reasonable time and make your processors stop too. Section 8(7) then requires erasure of the recording, transcript and derived data unless another law requires retention. Keep a dated record of the withdrawal and the deletion as evidence.
This article is for general information and is not legal advice. Confirm obligations against the official texts of the DPDP Act 2023, the DPDP Rules 2025 and the TRAI Telecom Commercial Communications Customer Preference Regulations, 2018 (as amended), and consult qualified counsel for your situation.
Monthly insights on AI, VR and DPDPA compliance — straight from our team to your inbox.
Free 30-minute consultation with our team — or see our products in action.