Use case #0003

Resolution SLA: how Dispute Manager AI meets RBI's 30-day resolution requirement

The RBI's 30-day resolution requirement is not a guideline — it is the gate. A dispute unresolved at Day 30 can be taken to the Banking Ombudsman without any further obligation on the borrower's part. The institution loses control of the resolution timeline, the resolution forum, and in many cases the resolution outcome. The Dispute Manager Agent AI treats every dispute as a 30-day clock that started the moment the complaint was filed — not the moment the Nodal Officer got around to reading it. Every day of the clock is tracked. Every milestone is timestamped. Every at-risk case is escalated 7 days before the deadline. And every borrower whose case is approaching resolution receives a proactive communication — not because the institution wants to pre-empt the Ombudsman, but because a borrower who feels heard and kept informed is a borrower who does not need to escalate to feel that justice is being served.

The RBI's 30-day resolution requirement is not a guideline — it is the gate. A dispute unresolved at Day 30 can be taken to the Banking Ombudsman without any further obligation on the borrower's part. The institution loses control of the resolution timeline, the resolution forum, and in many cases the resolution outcome. The Dispute Manager Agent AI treats every dispute as a 30-day clock that started the moment the complaint was filed — not the moment the Nodal Officer got around to reading it. Every day of the clock is tracked. Every milestone is timestamped. Every at-risk case is escalated 7 days before the deadline. And every borrower whose case is approaching resolution receives a proactive communication — not because the institution wants to pre-empt the Ombudsman, but because a borrower who feels heard and kept informed is a borrower who does not need to escalate to feel that justice is being served.

The 30-day resolution timeline — and where cases most commonly stall

The 30-day clock appears straightforward but has specific structural risks. The first is acknowledgement delay: institutions that use a manual complaints inbox may take 3 to 5 working days to acknowledge a dispute — burning 15% of the resolution window before the investigation has begun. The Dispute Manager AI sends the acknowledgement within 2 hours of dispute receipt, automatically, with a case number and a committed resolution timeline. The 5-working-day acknowledgement obligation under the Ombudsman Scheme is met before the Nodal Officer has seen the complaint.

The second structural risk is evidence retrieval delay — the 3 to 4 working days typically spent gathering call logs and payment records, as described in the previous article. With automated evidence retrieval in under 24 hours, the Nodal Officer can begin substantive assessment by Day 2 instead of Day 5 or 6. The 4 to 5 days saved on evidence retrieval are the difference between a 21-day average resolution time and a 27-day average resolution time — and between a portfolio of cases that are comfortably within SLA and one where 15 to 20% of cases are approaching the 30-day limit at risk of Ombudsman escalation.

"The institution that waits 5 days to acknowledge a dispute and 5 more days to gather evidence has used one-third of its resolution window on process overhead before the actual investigation has begun."

The full resolution timeline: from complaint to closed case

D0
Complaint receipt · Within 2 hours

Automated acknowledgement · Case number assigned · Evidence retrieval initiated

Within 2 hours of a complaint being filed — by WhatsApp, email, branch, or app — the Dispute Manager AI sends the borrower a formal acknowledgement with their case reference number (DIS-2025-XXXX), the name of the Nodal Officer responsible for their case, a committed resolution timeline ("We will resolve your complaint by [date]"), and the RBI Ombudsman contact details as required by the Integrated Ombudsman Scheme. The acknowledgement is timestamped and logged. Evidence retrieval from all 8 sources begins simultaneously with the acknowledgement.

→ Obligation: acknowledge within 5 working days · AI achieves: within 2 hours · Regulatory buffer: 4.8 working days created immediately
D1–2
Days 1–2 · Evidence assembled and preliminary assessment generated

Nodal Officer receives complete evidence file with preliminary assessment — within 24–48 hours

By Day 2, the Nodal Officer's case file contains: the borrower's complaint statement, all 8 evidence sources retrieved and cross-referenced, the AI's preliminary assessment of whether the evidence supports or contradicts the claim, the category classification (which of the 6 dispute categories), and the recommended resolution pathway with a draft resolution letter. The Nodal Officer's job is to review the AI's assessment, apply judgement where evidence is ambiguous or incomplete, approve the resolution approach, and sign off the resolution letter. This is the role of an experienced compliance professional — not a data gatherer.

→ Evidence assembled by D1–2 · Preliminary assessment generated · Nodal Officer reviews not retrieves
D3–14
Days 3–14 · Substantive investigation and resolution drafting

The resolution is drafted, any supplementary evidence gathered, and the Nodal Officer's decision documented

For most cases, the resolution is straightforward by Day 3: the evidence either supports or contradicts the claim, and the appropriate remedy is clear. For cases where the evidence is incomplete (call recording not yet retrieved, bank statement not received from borrower), the investigation continues until Day 14 — with automated follow-ups sent to any external party whose evidence is pending. The borrower receives a mid-case update on Day 7 if the case is not yet resolved: "Your case is under active investigation. We aim to resolve by [date]. If you have any additional information to share, reply to this message." The Day 7 update prevents the borrower from feeling forgotten and reduces the probability that they escalate out of frustration before the resolution is ready.

→ D7 mid-case update to borrower if unresolved · External evidence follow-up automated · No cases left idle
D15–21
Days 15–21 · Target resolution and communication

Target resolution window — most cases resolved in this band · Resolution letter issued and borrower response received

The target resolution for all dispute categories is Day 21 — leaving a 9-day buffer before the 30-day limit. A resolution letter is issued that states the institution's findings clearly, the decision taken, any remediation offered (charge reversal, apology, correction), and the borrower's right to escalate to the Ombudsman if they disagree with the resolution. The resolution is not a win-lose communication — it is a transparent account of what the evidence showed and what the institution is doing in response. A borrower who receives a clear, evidence-based resolution at Day 21 — even if the resolution is partially against them — is less likely to escalate than a borrower who receives a generic "your complaint has been noted" at Day 29.

→ Target: Day 21 resolution · 9-day buffer before 30-day limit · Resolution includes borrower's Ombudsman rights per RBI requirement
D23
Day 23 · SLA risk alert — 7 days before limit

Any unresolved case at Day 23 triggers escalation to the Head of Grievances and the MD

A case that has not been resolved by Day 23 is flagged as SLA-at-risk. The alert goes to: the Nodal Officer (with a specific action demand), the Head of Grievances, and the MD (awareness only). The specific reason for the delay is included: evidence pending from third party, borrower not responding, legal review required. The escalation is not punitive — it is a structural reminder that 7 days remain and the case needs a resolution pathway, not just an investigation status. For cases where resolution requires a senior decision (e.g., a large charge waiver or a policy exception), the Day 23 alert escalates the decision to the appropriate authority.

→ D23 alert: Nodal Officer + Head of Grievances + MD · Specific delay reason identified · Resolution pathway required, not just status
D30
Day 30 · Hard deadline · Ombudsman Scheme gate

Unresolved case at Day 30: borrower automatically informed of Ombudsman escalation right — institution's position fully documented

If a case reaches Day 30 unresolved — which is rare when the sequence above is operating — the Dispute Manager AI sends the borrower a message acknowledging that the 30-day resolution window has elapsed, confirming the institution is still working on resolution, and providing the Ombudsman contact details with the specific language required by the IOS 2021. Internally, the full case record is marked as a 30-day breach event — reported to the Board Risk Committee in the monthly compliance briefing. Every element of the institution's investigation, evidence, and communication is documented and ready for the Ombudsman if the borrower chooses to escalate. The institution's position is always defensible — because the Dispute Manager AI has been building the case file from Day 0.

→ Day 30 breach: rare · Full case documentation ready for Ombudsman if escalated · Board Risk Committee notified in monthly compliance report
2 hrsAcknowledgement sent — vs 5 working days statutory limit · 4.8 working days of regulatory buffer created immediately · Borrower gets case number and Nodal Officer name
D21Target resolution — 9-day buffer before 30-day Ombudsman gate · Nov month-to-date average resolution: 17.4 days · Well within window
D23SLA risk alert — 7 days before the 30-day limit · MD notified for awareness · Nodal Officer given specific delay reason and resolution pathway requirement
17.4 daysAverage resolution time (Nov month-to-date) — vs 27.2 days before Dispute Manager AI · 9.8-day improvement · Zero 30-day breaches this month

The borrower who receives a resolution on Day 17 — with a clear explanation of the evidence, the decision, and the remedy — almost never escalates to the Ombudsman, regardless of whether the decision went in their favour

The Banking Ombudsman's annual report consistently shows that the majority of escalations come not from cases where the institution's decision was wrong, but from cases where the borrower felt unheard, uninformed, or stonewalled. The institution that acknowledges within 2 hours, updates on Day 7, and resolves on Day 17 with a clear, evidence-based letter has done the communication work that prevents escalation — independent of the merits. The institution that acknowledges on Day 5, sends no updates, and resolves on Day 28 with a terse "your complaint has been reviewed" letter has produced a borrower who feels that the Ombudsman is their only remaining option to be taken seriously. The Dispute Manager Agent AI does not resolve disputes faster by cutting corners on investigation — it resolves them faster by removing the 8 to 10 days of process overhead between complaint receipt and substantive investigation, giving the Nodal Officer the same 30 days but with 10 more of them available for actual thinking.

← Back to Dispute Manager Agent AI