Use case #0003

Ombudsman escalation: what triggers automatic RBI escalation in Grievance AI

The RBI's Integrated Ombudsman Scheme gives borrowers the right to escalate an unresolved complaint to the RBI Ombudsman if the institution does not resolve it within 30 days. An institution that waits for the borrower to discover and exercise this right is managing a compliance exposure. An institution whose Grievance AI proactively notifies the borrower of the escalation right at exactly day 30, and — where warranted — prepares the Ombudsman filing on the institution's behalf, is managing a relationship.

The RBI's Integrated Ombudsman Scheme gives borrowers the right to escalate an unresolved complaint to the RBI Ombudsman if the institution does not resolve it within 30 days. An institution that waits for the borrower to discover and exercise this right is managing a compliance exposure. An institution whose Grievance AI proactively notifies the borrower of the escalation right at exactly day 30, and — where warranted — prepares the Ombudsman filing on the institution's behalf, is managing a relationship.

The Integrated Ombudsman Scheme — what the institution is obligated to do

The RBI's Integrated Ombudsman Scheme (IOS), introduced in November 2021 and extended to NBFCs, creates a three-tier complaint resolution architecture: the institution (30-day resolution SLA), the Ombudsman (if the institution fails), and the Appellate Authority (if the borrower is unsatisfied with the Ombudsman's decision). The institution's obligations under the IOS are: to resolve complaints within 30 days; to notify the borrower of the escalation right if the complaint is not resolved within 30 days; to cooperate with the Ombudsman in any investigation; and to implement Ombudsman awards within the specified time.

An institution that allows a complaint to cross the 30-day resolution threshold without notifying the borrower of the escalation right has violated the IOS. An institution that does not cooperate with the Ombudsman's investigation — by providing requested documents late or withholding the complaint file — creates an adverse finding risk that is worse than the original complaint.

The Grievance AI monitors every open complaint against its 30-day resolution clock, sends the required escalation notification proactively on day 28 (not day 31 after the breach), and — for complaints where the institution has determined it cannot resolve in the borrower's favour — prepares the Ombudsman escalation package including the complaint history, the institution's position, and the relevant supporting documents.

"An institution that notifies the borrower of the Ombudsman right only after the 30-day deadline has passed is notifying the borrower of a breach, not of a right. The Grievance AI sends the notification on day 28."

The six automatic escalation triggers

Trigger 1
30-day
clock breach
Unresolved complaint approaching 30-day SLA — proactive notification triggered at day 28

Borrower notified of Ombudsman escalation right 2 days before the 30-day deadline

When an open complaint reaches day 28 without resolution, the Grievance AI sends the borrower a notification: "Your complaint (ref: GRV-XXXX) has been open for 28 days without a final resolution. We are continuing to work on it. If we do not resolve it by [day 30 date], you have the right to escalate to the RBI Integrated Ombudsman at cms.rbi.org.in using your complaint reference number." This notification satisfies the IOS requirement proactively — before the breach, not after.

→ Trigger: Day 28 without resolution · Notification auto-sent · Internal escalation to GRO · Resolution attempt intensified
Trigger 2
Tier 1
conduct
pattern
Three or more Cat B (collection conduct) complaints involving the same agent or team in 30 days

Pattern of collection conduct complaints triggers automatic escalation to senior management and regulatory notification preparation

A single collection conduct complaint may be a misunderstanding or a borrower error. Three complaints about the same agent or the same team within a 30-day window is a pattern — and a pattern of FPC violations is a regulatory risk beyond the individual complaint. The Grievance AI detects the pattern, escalates immediately to the Collections Head and CCO, suspends the agent pending investigation, and prepares a voluntary self-disclosure brief for the RBI if the pattern is confirmed.

→ Trigger: 3+ Cat B complaints, same agent or team, 30 days · Agent suspended · CCO briefed · Voluntary disclosure prepared
Trigger 3
Borrower
requests
escalation
Borrower explicitly requests Ombudsman escalation — institution must facilitate, not obstruct

When the borrower explicitly asks to escalate to the Ombudsman, the Grievance AI facilitates the filing — not the borrower

A borrower who says "I want to take this to the RBI Ombudsman" is exercising a legal right. The Grievance AI does not attempt to retain the complaint at the institution level — it provides the borrower with the Ombudsman filing portal link (cms.rbi.org.in), confirms that their complaint reference number is valid for Ombudsman filing, and generates a complete complaint dossier that the borrower can attach to their Ombudsman submission — including the institution's position and the supporting documents.

→ Trigger: Borrower explicitly requests escalation · Dossier generated · Portal link provided · Institution does not obstruct
Trigger 4
Unauthorised
debit
pattern
Two or more Cat A (unauthorised debit) complaints in 14 days — potential systemic error

Multiple unauthorised debit complaints suggest a system error — proactive investigation and potential self-report

A single unauthorised debit complaint may be a dispute over agreed terms. Two or more within 14 days suggests a systemic error — a batch processing error, an NACH instruction applied to wrong accounts, or an undisclosed fee being charged at scale. The Grievance AI escalates immediately to the CFO and the Operations Head, initiates a full review of the relevant debit batch, and prepares a voluntary self-disclosure to the RBI if the systemic error is confirmed — rather than waiting for the Ombudsman to discover it.

→ Trigger: 2+ Cat A in 14 days · CFO + Ops Head alerted · Batch review initiated · Voluntary disclosure prepared
Trigger 5
Bureau
misreport
confirmed
Institution confirms it reported incorrect data to CIBIL — correction submission + borrower compensation

A confirmed bureau misreport triggers a correction submission, a written apology, and compensation assessment

When the Grievance AI's investigation of a Cat F complaint (bureau reporting error) confirms that the institution incorrectly reported data to CIBIL — a DPD that did not occur, or a loan as active after closure — the consequence chain is automatic: CIBIL correction submitted within 48 hours, written apology issued to the borrower, compensation assessed under the RBI's compensation policy for regulatory errors, and the incident logged in the FPC quarterly report. If the incorrect data caused the borrower to be declined by another institution, the compensation assessment must include that consequential harm. → Trigger: Bureau misreport confirmed · CIBIL correction in 48hrs · Written apology · Compensation assessed · FPC report

Trigger 6
Ombudsman
award
received
RBI Ombudsman issues an award against the institution — implementation within 30 days, no appeal without grounds

When the Ombudsman issues an award, implementation is mandatory — Grievance AI tracks implementation and compliance

If a complaint reaches the Ombudsman and the Ombudsman issues an award — requiring the institution to refund a charge, correct a record, pay compensation, or modify a practice — implementation is mandatory within 30 days unless the institution appeals to the Appellate Authority on valid grounds. The Grievance AI tracks the award, assigns implementation responsibility, monitors the 30-day implementation clock, and reports completion to the Ombudsman as required. An Ombudsman award not implemented within 30 days is a serious regulatory breach.

→ Trigger: Ombudsman award received · Implementation assigned · 30-day clock monitored · Completion reported to Ombudsman

An Ombudsman escalation package: what the Grievance AI prepares

Ombudsman Escalation Package — GRV-2025-40218 · Complaint: Lakshmi Devi · Collection Conduct
Prepared by Grievance AI · Day 28 trigger · Oct 12, 2025 · Institutional reference confirmed
Complaint referenceGRV-2025-40218
Date of complaintSep 12, 2025
CategoryCat B — Collection conduct
Days open30 days (as of today)
Institution's positionComplaint partially upheld
Resolution offeredApology letter + agent reassigned
Borrower's acceptanceNot accepted — seeking compensation
Documents enclosed8 documents (call logs, complaint history, agent records)
Institution's narrative (for Ombudsman)
Ms Lakshmi Devi filed a complaint on September 12, 2025 regarding collection calls received outside permitted hours. The institution investigated and confirmed that the collection agent (Agent ID: CA-48821) made 3 calls between 7:30 PM and 7:50 PM on September 10 and September 11 — marginally outside the 7:00 PM permitted hour. The institution has acknowledged the FPC violation, issued a written apology to Ms Lakshmi Devi, and reassigned the agent. Ms Lakshmi Devi has requested financial compensation of ₹10,000 for mental distress. The institution has assessed this claim and offered ₹3,000 as goodwill compensation, which Ms Lakshmi Devi has not accepted. The institution respects Ms Lakshmi Devi's right to Ombudsman review on the compensation quantum and will cooperate fully with the Ombudsman's investigation.
Package status
Ready for borrower
Ombudsman portal
cms.rbi.org.in
Institution will cooperate
Confirmed
● All 8 documents attached · Institution's position stated clearly · Cooperation commitment made · Borrower-ready package
Day 28Proactive Ombudsman notification — 2 days before the 30-day breach · Not after the deadline
6Automatic escalation triggers — from 30-day clock to Ombudsman award implementation
VoluntarySelf-disclosure prepared for pattern violations — institution self-reports before Ombudsman discovers the pattern
FacilitateThe institution facilitates Ombudsman escalation — it does not obstruct it. The package is prepared for the borrower.

An institution that facilitates Ombudsman escalation is not conceding — it is demonstrating confidence

An institution that obstructs, delays, or discourages a borrower from escalating to the Ombudsman signals that it is not confident in its own conduct. An institution that proactively prepares the escalation package, provides the portal link, and cooperates fully with the Ombudsman's investigation signals that its conduct can withstand scrutiny. The difference in regulatory relationship is significant: an institution with a track record of proactive compliance and full Ombudsman cooperation is treated differently by the RBI than one that resists every escalation and contests every award. The Grievance AI treats Ombudsman escalation not as a failure to be avoided but as a process to be managed well — because an escalation handled properly is a compliance demonstration, not a compliance failure.

← Back to Grievance Redressal Agent AI