Call Recording and Voice AI Under DPDP: How to Choose a Consent Management Solution for Contact Centres
Call recording under DPDP: a guide for contact centres on consent, announcements, voice AI, retention and choosing a consent management platform in India.

When a contact centre records a call, transcribes it or hands it to an AI voice agent, it processes personal data under the Digital Personal Data Protection Act, 2023 (DPDP Act). A caller's voice, phone number and account details are personal data, and the business that decides why and how it uses them is the Data Fiduciary.
Call recording under the DPDP Act raises five practical questions: when consent is needed, what the announcement covers, how AI voice agents and speech analytics are treated, how long recordings can be kept and what a consent management solution should offer. Each activity has its own purpose, and the Act asks for a ground for processing that matches each one. Recording a service call, scoring it for quality and training an AI model on it are three separate questions.
What Does DPDP Compliance Cover in a Single Contact Centre Call?
The interactive voice response (IVR), the automated menu callers hear first, plays the announcement and routes the call. Once a human agent or an AI voice agent takes over, a recording platform stores the audio, a transcription engine converts it to text, speech analytics scores the call and the CRM logs the outcome.
The Act covers personal data in digital form at each of these stages, while the announcement covers the first stage only. A map of your call journey, with a named purpose and owner for each stage, gives you the working basis for DPDP compliance in a contact centre. It also shows which vendors act as Data Processors, meaning they handle personal data on your behalf. You remain responsible for them, and the Act allows you to engage them only under a valid contract.
Do You Need Customer Consent to Record Calls Under DPDP?
Not always. The Act allows processing on two grounds: the customer's consent, or certain legitimate uses listed in it. One legitimate use covers personal data that the customer voluntarily provided for a specified purpose, provided the customer has not indicated that consent is refused for that use. A caller who shares account details on a service line to resolve a query may come within it for that purpose, though later uses of the call need their own ground.
Recording, quality monitoring, training, analytics and marketing are separate purposes, and each needs the ground that suits its own circumstances. For your contact centre, a separate consent request arises only where consent is the ground chosen for that purpose.
Where consent is the ground, a notice must precede or accompany the request, and the consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action. As the Data Fiduciary, you carry the burden of proving both notice and consent, and customers can withdraw consent with comparable ease.
Promotional calls follow TRAI's Telecom Commercial Communications Customer Preference Regulations (TCCCPR), amended on 12 February 2025, which govern consent, preferences and number series for commercial calls. Agreement to receive offers covers that purpose alone, and AI analysis of the same call needs its own ground.
Read more on outbound calling in DPDPA for Telemarketing: What Section 6 Means for Your Outbound Calling Operations
What Should a Call Recording Announcement Say Under DPDP?
Three elements work together. The announcement is the short spoken message, the notice is the fuller document that Rule 3 describes, and the consent action is the caller's affirmative response, needed only where consent is the ground.
Rule 3, which applies from 13 May 2027, asks for a notice that is understandable on its own, in plain language, with an itemised description of the personal data and the specified purpose. It must give the specific link to the business website or app and describe other means for withdrawing consent, exercising rights and complaining to the Data Protection Board of India (the Board). The notice needs more than a web link, and customers can read it in English or any Eighth Schedule language.
The points that follow are recommended practice. Your announcement tells callers that recording takes place, names the purposes and points to the notice. Where consent is the ground, the keypad response and a timestamp tied to the notice version form the record, and a call that carries on after silence gives weaker proof.
A single announcement plays across call types, so its wording and choices should match the ground chosen for each purpose, and it belongs at the IVR before recording starts. A transfer to an AI voice agent, a callback or a new purpose such as a marketing offer should prompt a check on whether the notice covers it, and an updated notice or a new consent request may follow, depending on the ground.
A brief spoken line can state the purposes and offer a choice, with the full notice sent by SMS or web address in customers' languages. Callers who decline need a defined route, such as an unrecorded line or a callback, because the legitimate use applies only while the customer has not indicated non-consent. Counsel should confirm the position for calls that another law requires to be recorded.
How Does DPDP Apply to AI Voice Agents and Speech Analytics?
AI involvement leaves the Act's general duties in place, and the purpose of processing still decides the ground. Consent for voice bots in India follows the same logic as any other call. Four layers show where each ground applies.
Service delivery. An AI voice agent handling a refund query uses the caller's voice and history to fulfil the customer's own request, which is closest to the legitimate use described above.
Analytics and quality. Transcripts are a second copy of the conversation, and sentiment scores produced by speech analytics are personal data about an identifiable customer. When a score shapes a decision that affects the customer, such as call priority, the Act asks the business to make reasonable efforts to keep the data complete, accurate and consistent.
Model development. Reusing conversations to train AI models is a separate purpose. Consent must be specific and unconditional, so avoid making service depend on agreement to training use.
Vendor access. Vendors with access to recordings are processors. Contracts should state permitted uses, including model improvement, and Rule 6 expects the processor contract to carry security safeguards.
You should also tell callers when they are speaking to an automated agent. This is recommended practice that supports informed consent, and your counsel can confirm whether any sector or telecom rule adds a disclosure duty.
How Long Can Contact Centres Keep Call Recordings Under DPDP?
The legal position. The Act and the Rules fix no single retention period for call recordings. The Act requires erasure when the customer withdraws consent or when it is reasonable to assume the specified purpose is no longer served, whichever is earlier, unless another law requires retention. Processors must erase too, and you must meet a customer's erasure request unless retention is necessary for the specified purpose or for compliance with law.
Two Rules mention one year, and they apply to different things. Rule 6 asks for logs and personal data to be kept for one year so that the business can detect and investigate unauthorised access, unless another law says otherwise. Rule 8(3) sets a minimum of one year for specified personal data, traffic data and logs for Seventh Schedule purposes. Both serve their own stated purposes and set no general period for call recordings. The Third Schedule's three year erasure after inactivity applies only to large e-commerce, social media and online gaming platforms, for all purposes except a few listed ones such as user account access.
Recommended practice. For your contact centre, the practical question is how long each purpose needs a recording, so a call recording retention policy starts from purpose.
Recording purpose | What starts and ends the clock | Who signs off |
|---|---|---|
Customer service | Query closure, plus any period another law requires | Business owner, legal |
Complaint resolution | Complaint closure, plus record keeping duties | Grievance owner, legal |
Quality monitoring | End of the evaluation cycle | Quality team |
Agent training | End of the training use | Training team and legal |
AI model training | Own purpose, ground and vendor terms settled first | Privacy lead, legal, IT |
Deletion has to reach the recording, transcript, scores, CRM notes, backups and vendor storage, and a customer identifier carried across these systems helps you find each copy.
What Should a Consent Management Solution for Contact Centres Offer?
Consent information becomes hard to track once recording, IVR, CRM and analytics tools each hold part of it. A consent management solution keeps one record of what each customer agreed to and what changed afterwards, and contact centres need five capabilities from it.
Purpose-level capture. Service, quality, training and marketing each get a separate record for every customer.
Evidence trail. Timestamp, channel, notice version and call reference let you show notice and consent, and a searchable history is the core of audit trail software for DPDP Act compliance.
Withdrawal enforcement. A withdrawal made on a call, on the web or in an app reaches the dialer, CRM and analytics tools.
Integrations. APIs connect the consent record to your IVR and CRM, which is where DPDP Act compliance for CRM data begins.
Reporting. Privacy and operations teams can see consent status by purpose.
How to Evaluate a Consent Management Platform for Your Contact Centre
Your recording, IVR and analytics tools are already in place, so test how a consent management platform for DPDP Act compliance works with them. Ask each vendor to demonstrate the following on your own call journey.
Assessment area | What to ask for |
|---|---|
Integration feasibility | Documented APIs, a named route to IVR and CRM, and IT effort |
Evidence quality | A live search from one customer record to its timestamp, notice version and withdrawal |
Scalability | Behaviour across brands, channels and call volumes |
Security | Access controls, access logs and hosting details |
Implementation | Timeline, team roles and your own workload |
Vendor accountability | Support terms, sub-processor disclosure and written responsibilities |
One test carries the most weight: change a customer preference in one live system and watch it arrive in another. Treat a promise of automatic compliance with caution, since software supports the work and legal judgement stays with the business.
A consent management platform is software a business uses to run its own consent records. A Consent Manager is a separate regulated entity, which the Act defines as a person registered with the Board through whom a customer can give, manage, review or withdraw consent; the Rules allow registration from 13 November 2026.
How OneConsent Works Alongside Your Telephony and Analytics Stack
OneConsent is enterprise consent management software for businesses with many customer systems, and it works alongside telephony, IVR and analytics tools. Its Consent and Preference Management module works as a preference management platform for DPDP Act requirements across the consent lifecycle: purpose-specific capture, tracking, withdrawal and enforcement through preferences kept in sync across connected applications. The consent audit trail supports searching consent history and tracing notice versions.
OneConsent does not record calls, run IVR menus, perform speech analytics or manage audio storage, deletion and retention, which stay with your recording platform and policy. Integration scope depends on your systems, so a demonstration on your own call journey confirms it.
How Can Contact Centres Prepare for DPDP Before 13 May 2027?
These five activities turn the recommendations above into a work plan.
Customer interaction mapping. Record every system, vendor and purpose from announcement to archive.
Notice and consent review. Check announcements and notices against Rule 3 and the ground chosen for each purpose.
AI and vendor processing. List model training and vendor access, with the contract terms.
Retention and deletion governance. Set retention by purpose and confirm that deletion reaches every copy.
Withdrawal and audit testing. Change one customer's preference and confirm it reaches connected systems with an evidence trail.
Review Your Call Journey With the OneConsent Team
The OneConsent team reviews your call journey and shares personalised findings on purposes, consent evidence and withdrawal handling as part of its DPDP compliance consulting services. To prepare your call recording practice for the DPDP Act, explore OneConsent consent management or book a OneConsent demo with your IVR and CRM setup to see purpose-based consent records and audit trails.
Rohit Sharma is a Marketing Manager at OneConsent with over 7 years of experience across digital marketing, and digital transformation. His work spans content research, planning, and marketing, with a focus on DPDP compliance, data protection, privacy, AI, and emerging technologies. At OneConsent, he focuses on researching and writing about data privacy, consent management, and the DPDP Act, making complex topics clear, practical, and relevant for businesses while helping audiences understand how privacy and technology are shaping the future of digital experiences.
See all articles by Rohit SharmaFrequently Asked Questions
Have more questions?
Search our full DPDP knowledge base for more answers.