---
title: "AI Voice Agents for Debt Collection in India | Vobiz"
description: "AI voice agent for debt collection in India: RBI calling hours, recovery agent rules, DPDP recording duties, 1600-series numbers and the guardrails to build."
canonical: https://www.vobiz.ai/resources/blogs/compliance/ai-voice-agents-debt-collection-india/
---
[Blogs](https://www.vobiz.ai/resources/blogs/)Compliance

# AI Voice Agent for Debt Collection in India: RBI Rules and Setup (2026)

What RBI, DPDP and TRAI rules mean for AI loan and EMI reminder calls, which conversations need a human, and the guardrails to build in.

![AI Voice Agent for Debt Collection in India: RBI Rules and Setup (2026)](https://www.vobiz.ai/blog-thumbs/ai-voice-agents-debt-collection-india.jpg)

![Team Vobiz](https://www.vobiz.ai/favicon-192.png)Team Vobiz

10 min read19 November 2026

Share this article

On this page

Subscribe

For newsletter and updates

An AI voice agent can make loan and EMI reminder calls in India and handle part of the collections conversation, but the lender answers for every call it places. The RBI's recovery rules apply: contact only between 8:00 a.m. and 7:00 p.m., no harassment or excessive calling, and, from 1 January 2027, calls recorded and kept for six months. Add DPDP Act duties for the recordings and TRAI's 1600-series rule for the calling numbers, and you have the frame this guide walks through.

_This is not legal advice. Regulations change and apply differently by entity type; confirm your position with your compliance team or counsel before going live._

## Which RBI rules apply to recovery calls?

There are three layers, and the dates matter because the rules change on 1 January 2027.

**1\. The August 2022 circular (in force now).** RBI circular [RBI/2022-23/108](https://www.rbi.org.in/scripts/NotificationUser.aspx?Id=12378&Mode=0), dated 12 August 2022, applies to commercial banks (excluding payments banks), AIFIs, all NBFCs and HFCs, co-operative banks and ARCs. It bars intimidation and harassment by lenders and their agents, naming: calling before 8:00 a.m. or after 7:00 p.m. for recovery of overdue loans, threatening or anonymous calls, persistent calling, inappropriate messages, and false or misleading representations. The lender keeps ultimate responsibility for what it outsources. Microfinance loans are excluded.

**2\. The Fair Practices Code in the 2025 consolidated directions.** For NBFCs, the [Reserve Bank of India (NBFC – Responsible Business Conduct) Directions, 2025](https://www.rbi.org.in/scripts/BS_ViewMasDirections.aspx?id=12942) carry the Fair Practices Code. Communications must be in a language the borrower understands (para 10), and NBFCs must not persistently bother borrowers at odd hours (para 20). Para 100 repeats the 8 a.m. to 7 p.m. rule; for **microfinance loans**, para 91(2) treats calls before 9:00 a.m. or after 6:00 p.m. as harsh.

**3\. The August 2026 amendment directions (from 1 January 2027).** On 6 August 2026 the RBI [issued amendment directions](https://www.rbi.org.in/Scripts/BS_PressReleaseDisplay.aspx?prid=63305) on "Conduct of Regulated Entities in Recovery of Loans and Engagement of Recovery Agents" for nine categories of lender, from commercial banks to NBFCs, HFCs and co-operative banks, all effective 1 January 2027. The commercial bank version ([RBI/2026-27/223](https://taxguru.in/rbi/rbi-issues-comprehensive-commercial-bank-recovery-agent-loan-recovery-conduct-directions-january-2027.html)) is the one we read in full, and its relevant paragraphs are:

| Provision (commercial bank text) | What it says | What it means for an AI agent |
| --- | --- | --- |
| Para 454A | Applies to recovery from borrowers in default, and "mutatis mutandis" to collection of dues in the normal course | Pre-due EMI reminders are in scope, not just overdue recovery |
| Para 454Y(4) | Contact only between 08:00 and 19:00, unless the borrower has expressly asked or authorised otherwise | The calling window must be enforced per borrower, with a record of any opt-in to other times |
| Para 454Y(1) | Recovery matters discussed only with the borrower or guarantor | The agent must verify who it is speaking to before discussing dues |
| Para 454Z | Harsh practices include abusive language, threatening or anonymous calls, calling outside hours, excessive calls or messages, harassing relatives or co-workers, false or misleading statements about the debt | Prompt and guardrail design, plus frequency caps |
| Para 454P | Record the time and number of calls; record call content and keep it for six months (longer if sub judice); take precautions such as telling the borrower the call is recorded | Recording on by default, a recording notice, and a retention policy |
| Para 454AA | A dedicated grievance mechanism; recovery communications must include the grievance officer's name, email, phone and address | The agent needs to be able to give these details on request |
| Para 454AB | Comply with other rules, including the RBI's outsourcing directions and TRAI's TCCCPR, 2018 | Your calling numbers and consent sit under TRAI rules too |

Check the parallel text issued for your entity type; details differ.

For digital loans, the [Digital Lending Directions, 2025](https://www.rbi.org.in/Scripts/BS_ViewMasDirections.aspx?id=12848) (para 8(v)) add that when a recovery agent is assigned or changed after default, its particulars must reach the borrower by email or SMS before the agent makes contact.

## Is an AI voice agent a "recovery agent" under RBI rules?

The directions do not mention AI or automated calls. They define a recovery agency as an entity or individual, other than the bank's own employees, engaged by the bank to assist in recovery. If a vendor runs the agent and calls on your behalf, plan for it to be treated as an outsourced recovery arrangement, with due diligence, code of conduct and grievance obligations attached. If you run it in-house, the conduct rules still bind you as the lender. Some provisions, such as the IIBF certificate for recovery agents (para 454I), do not map cleanly onto software; take that to your compliance team.

The RBI's [FREE-AI committee report](https://www.khaitanco.com/sites/default/files/2025-08/Ergo%20-%20FREE%20AI%20Framework%20-%2028%20Augusut%202025.pdf) of 13 August 2025 is not binding regulation, but one of its seven "sutras" is disclosure of AI use with individuals keeping final authority to override AI systems. Announcing an automated agent acting for the lender, and offering a human, follows that line.

## DPDP Act: call recordings, consent and retention

A recovery call captures personal data, often including reasons for non-payment that reveal health or job loss. Under the [Digital Personal Data Protection Act, 2023](https://www.dpdpa.com/dpdpa2023/chapter-2/section8.html), the lender is the data fiduciary and your telephony and AI vendors are data processors. The [DPDP Rules, 2025](https://static.pib.gov.in/WriteReadData/specificdocs/documents/2025/nov/doc20251117695301.pdf), notified in November 2025, phase in obligations over eighteen months, so most of them bite from mid-2027.

-   **Notice and consent.** The Rules require a separate, plain-language consent notice stating the specific purpose. Your onboarding notice should name reminder and recovery calls, recording and AI processing.
-   **Security safeguards.** Section 8(5) makes the fiduciary responsible for reasonable safeguards, including for data held by processors. Failure to maintain them carries the Act's highest penalty, up to ₹250 crore.
-   **Erasure.** Section 8(7) requires erasure once the purpose is served or consent is withdrawn, unless a law requires retention. The RBI's six-month recording rule is that kind of law.
-   **Processing logs.** Rule 8(3) separately requires a fiduciary to retain personal data, associated traffic data and processing logs for at least one year for specified purposes.

So you keep recordings for a defined period while minimising what is in them: redact PII from recordings and transcripts so retained audio proves conduct without carrying account, card or Aadhaar numbers. We covered that tension in detail in [PII redaction for BFSI voice agents](https://www.vobiz.ai/resources/blogs/compliance/pii-redaction-bfsi-voice-agents/). How the six-month and one-year periods interact for your data is a question for counsel.

## TRAI and DLT: which numbers can you call from?

Under TRAI's [direction of 19 November 2025](https://www.trai.gov.in/direction-regarding-phase-wise-implementation-mandatory-adoption-1600-series-numbers-rbi-sebi-and), RBI-regulated entities had to move service and transactional calls to the **1600 series**: commercial banks by 1 January 2026, large NBFCs, payments banks and small finance banks by [1 February 2026](https://www.theweek.in/wire-updates/business/2025/11/19/del27-biz-trai-bfsi.html), and remaining NBFCs, co-operative banks and RRBs by 1 March 2026. TRAI's [July 2026 clarification](https://www.scconline.com/blog/post/2026/07/18/trai-clarifies-1600-and-140-series-number-framework/) confirms that 1600-series calls cannot be tagged, blocked or filtered under the TCCCPR, while the **140 series** is for promotional calls.

EMI reminders and recovery calls are service or transactional calls, so they belong on 1600-series numbers. Keep cross-sell offers out of them; a top-up pitch makes the call promotional.

## What should the AI handle, and what needs a human?

Short, factual, well-documented calls suit an AI agent. Conversations that need judgement, empathy or authority belong with people.

| Use case | AI agent | Why |
| --- | --- | --- |
| Pre-due EMI reminders (T-3, T-1) | Good fit | Short, scripted, high volume, low emotional load |
| Bounce or missed-debit notification | Good fit | Factual: amount, date, how to pay |
| Sending a UPI or payment link during the call | Good fit | Agent triggers an SMS or WhatsApp link from your backend |
| Promise-to-pay capture | Good fit, with limits | Capture date and amount; write to the LMS; no negotiation beyond preset options |
| Updating contact details, callback scheduling | Good fit | Structured data capture |
| Financial hardship, job loss, medical emergency, bereavement | Human | The directions ask lenders to avoid contact around occasions such as bereavement or medical emergencies; restructuring needs authority |
| Disputes about the amount or charges | Human | A "false or misleading representation" risk if the agent guesses |
| Settlement or waiver negotiation | Human | Needs policy discretion and documented approval |
| Borrower asks for a person, or becomes distressed or abusive | Human (immediately) | Escalation is a guardrail, not a fallback |
| Third-party pickup (relative, colleague) | End politely | Dues can only be discussed with the borrower or guarantor |

## Guardrails to build in before the first call

Each of these should live in code or configuration, not only in a prompt.

1.  **Identity and disclosure in the first sentence.** "This is an automated assistant calling on behalf of \[Lender\] about your loan account. This call is recorded." An unnamed caller looks like the anonymous calling the rules prohibit.
2.  **Verify before discussing dues.** Confirm the borrower or guarantor using data you hold (date of birth, last digits of the loan account) before mentioning amounts. If it fails, end politely.
3.  **Calling window enforced at dial time.** Check every dial against 08:00 to 19:00 IST (09:00 to 18:00 for microfinance loans under the NBFC directions), and stop dialling with a buffer before the close so calls don't run past it. Store any borrower request for other times as an explicit, timestamped record.
4.  **Frequency caps across channels.** Count AI, human and agency calls and messages against one per-borrower limit. Para 454P requires you to document call times and counts anyway.
5.  **Do-not-call and avoid-times.** Honour requests to avoid particular times, as para 454Y(4) expects, and suppress calls around known bereavement or medical events.
6.  **Escalation paths.** Intents such as "dispute", "lost my job", "hospital", "talk to a person", or signs of distress trigger a warm transfer or a scheduled human callback.
7.  **Hard limits on what the agent can say.** No unapproved statements about legal action, police, credit scores or family. Amounts and dates come from the loan system, never the model.
8.  **Language.** Use the borrower's preferred language from your records, since the Fair Practices Code requires communication in a language the borrower understands.
9.  **Grievance details on request.** The agent should be able to give the grievance officer's name, email, phone and address, and log that it did.
10.  **Recording retention and redaction.** Retain for the required period, redact PII, restrict access, delete on schedule.

A minimal window check looks like this:

```python
from datetime import datetime, time
from zoneinfo import ZoneInfo

IST = ZoneInfo("Asia/Kolkata")

def can_dial(borrower, now=None):
    now = now or datetime.now(IST)
    start, end = (time(9, 0), time(18, 0)) if borrower.is_microfinance else (time(8, 0), time(19, 0))
    end_buffered = time(end.hour - 1, 45)  # stop new dials 15 min before close
    if borrower.has_time_authorisation(now):
        return True
    if not (start <= now.time() < end_buffered):
        return False
    if borrower.calls_today() >= borrower.daily_cap:
        return False
    return not borrower.in_avoid_period(now)
```

## The architecture

A compliant setup has five parts: the **loan management system** (dues, due dates, language, contact preferences), an **orchestrator** (who to call, window, caps, suppression lists, audit log), **telephony** (1600-series numbers, answering machine detection, recording, transfer to humans), the **voice agent** (speech-to-text, a model with a narrow tool set: fetch dues, send payment link, log promise-to-pay, request transfer, and text-to-speech, on Vapi, Retell AI, ElevenLabs, LiveKit, Pipecat or your own stack), and a **compliance store** (redacted recordings and transcripts, call counts, disclosures, escalations, retention jobs).

The flow: the orchestrator checks the window and dials from a 1600-series number, AMD screens out voicemail, the agent discloses and verifies, tools read dues and send the payment link, and anything outside its remit is transferred. After hangup, the recording is redacted and stored and the outcome written back.

## How to run this on Vobiz

Vobiz is the telephony layer in that setup:

-   **1600-series numbers** for service and transactional calls (plus 140-series, 92-series mobile, toll-free and local), ₹1,000/month for 1400, 1600 and 92-series, with hosted KYC in minutes and DLT compliance support.
-   **SIP trunks connected to Airtel, Jio and VIL**, or bring your own carrier. See [SIP trunking](https://www.vobiz.ai/products/sip-trunking/).
-   **₹0.42/min** inbound and outbound, billed in INR with a GST invoice, no setup fee or minimum commitment. See [pricing](https://www.vobiz.ai/pricing/).
-   **Campaigns with a daily calling window**: the Campaign Manager API takes a timezone such as `Asia/Kolkata`, window start and end times, and retry limits. Use it as a second check behind your own orchestrator.
-   **Answering machine detection, recording (with a delete API) and call transfer** through the [Voice API](https://www.vobiz.ai/products/voice-api/), plus **PII redaction for BFSI calls** configured on the trunk and **43-field CDRs** for the call-count record.
-   **Native integrations** with Vapi, Retell AI, ElevenLabs, LiveKit, Pipecat, Bolna, Ultravox and OpenAI Realtime, or WebSocket audio streaming for your own agent.

If you run on Plivo today, the Vobiz API is close to 1:1, so migration is mostly a client and base URL swap plus new numbers. If most of your collections calling is outside India, a global CPaaS may fit better; Vobiz is built around Indian carrier connectivity and INR billing.

Start with the [docs](https://www.vobiz.ai/docs/introduction) or [sign up on the console](https://console.vobiz.ai/); a first test call is typically live in about ten minutes.

## FAQ

### What are the RBI calling hours for loan recovery calls?

8:00 a.m. to 7:00 p.m., under both the 2022 circular and the amendment directions effective 1 January 2027, unless the borrower has expressly authorised other times. For NBFC microfinance loans the window is 9:00 a.m. to 6:00 p.m.

### Do the RBI rules apply to EMI reminder calls before the due date?

From 1 January 2027 the recovery conduct provisions apply "mutatis mutandis" to collection of dues in the normal course, so treat pre-due reminders as in scope.

### Does an AI collections agent have to say it is an AI?

The recovery directions do not mention AI, but the RBI's FREE-AI report favours disclosure and anonymous calls are prohibited. Say it is an automated assistant calling for the named lender.

### How long must recovery call recordings be kept?

Six months from the call date under the new directions, longer if the matter is sub judice. DPDP Rule 8(3) separately sets a one-year minimum for processing logs. Redact PII from what you keep.

### Which number series should a bank or NBFC use for collection calls?

The 1600 series, which TRAI made mandatory for RBI-regulated entities' service and transactional calls by 1 March 2026. The 140 series is for promotional calls.

### Can an AI agent negotiate settlements or handle hardship cases?

It should not. Use it for reminders, payment links and promise-to-pay capture, and route hardship, disputes and settlement requests to trained staff.

## More Related Articles

[![The Call You Have to Keep, and the Data You Can't Store](https://www.vobiz.ai/piiredactionthumbnail.png) Compliance7 min read ### The Call You Have to Keep, and the Data You Can't Store How do you keep a call recording DPDP forces you to delete but RBI forces you to retain? Vobiz redacts PII in BFSI voice calls, live at GFF Booth K25. Read full article ![Piyush Sahoo](https://www.vobiz.ai/blogpromotion/piyush.png)Piyush Sahoo 3 September 2026](https://www.vobiz.ai/resources/blogs/compliance/pii-redaction-bfsi-voice-agents/)[![Verified in Seconds, Compliant by May 2027](https://www.vobiz.ai/ekycthumbnail.png) Compliance6 min read ### Verified in Seconds, Compliant by May 2027 Vobiz verifies Indian businesses and individuals in under 30 seconds via Aadhaar, PAN and GST, no documents stored. See TRAI compliance live at GFF Booth K25. Read full article ![Piyush Sahoo](https://www.vobiz.ai/blogpromotion/piyush.png)Piyush Sahoo 2 September 2026](https://www.vobiz.ai/resources/blogs/compliance/ekyc-trai-dpdp-compliance-gff-2026/)[![Twilio Alternatives in 2026: Best Voice APIs for India and Voice AI](https://www.vobiz.ai/blog-thumbs/best-twilio-alternatives-india.jpg) Buyer's Guide10 min read ### Twilio Alternatives in 2026: Best Voice APIs for India and Voice AI Twilio alternatives for voice in 2026: Indian numbers, INR billing and AI voice agents. Compare Vobiz, Plivo, Exotel, Telnyx and more, plus a migration guide. Read full article ![Team Vobiz](https://www.vobiz.ai/favicon-192.png)Team Vobiz 19 November 2026](https://www.vobiz.ai/resources/blogs/buyers-guide/best-twilio-alternatives-india/)
