Complaint Closure Quality: Why Banks Close Complaints Without Resolving Them, and How to Stop It

A customer writes to their bank about a charge they never agreed to. Four days later an SMS arrives saying the complaint is closed. The charge is still on the statement, and nobody has explained why.
On the bank’s dashboard, this is a win: the case was closed within the turnaround time (TAT). For the customer, nothing has changed. This is a complaint closure quality problem, and it usually ends with a second complaint, a social media post or a case before the RBI Ombudsman.
This article explains what complaint closure quality means, why closures go wrong, what RBI’s 2026 rules say about reviewing complaints before they are rejected, and how banks and NBFCs can fix the process. It also shows how reopened complaints, resolution quality checks and a regular grievance audit tell you where closures are failing.
What is complaint closure quality?
Complaint closure quality tells you whether a closed complaint was actually resolved. It looks past the “Closed” status in the system and asks a plain question: did the customer’s problem get fixed, or, where the bank cannot give them what they asked for, was the decision explained properly and reviewed fairly?
A good closure has three things:
Action: the refund, correction or reversal was completed and recorded, not just promised.
A clear reply: the customer is told what was checked, what was found, what was done and what happens next.
A way forward: if the customer disagrees, the reply says how to escalate, and that route works.
Most banks measure closure speed because it is easy to count. Speed matters, and RBI prescribes timelines for it. But a case closed in two days with the problem intact is a fast failure, not a success.
What RBI’s current rules mean for complaint closure
Two RBI frameworks shape how closures should work in 2026. One operates inside the bank, before a complaint is rejected. The other operates after the bank’s reply. Whether they apply to you depends on your type of regulated entity, so check the directions for your category.
Inside the bank: the Internal Ombudsman Directions, 2026
On 14 January 2026, RBI issued Internal Ombudsman (IO) Directions, with separate versions for commercial banks, small finance banks, payments banks and other regulated entities. For commercial banks, they apply to banks with 10 or more banking outlets as on 31 March 2025. News reports on the release say eligible NBFCs are covered too, based on deposit-taking status, branch count and asset size.
These are the parts that matter most for closure quality, taken from the commercial banks’ text:
Complaints that are partially resolved or wholly rejected by the bank’s internal mechanism must be auto-escalated to the IO’s office for review, through a fully automated complaint management system.
Where RBI, NPCI or card network rules set a resolution timeline, the case must reach the IO early enough to leave at least 10 days for review. In all other cases, it must reach the IO within 20 days of receipt.
Before escalation, the bank can record only three outcomes: Fully Resolved, Partially Resolved or Wholly Rejected.
The same branch, unit or touchpoint should not close the complaint. A rejected or partially resolved complaint needs review at a fairly senior level before it goes to the IO.
The final decision must reach the customer within 30 days of the bank receiving the complaint.
The IO records a reasoned decision. If the IO upholds a rejection, the reply must say the complaint was reviewed by the IO and must tell the customer about the RBI Ombudsman, with the CMS portal URL and the CRPC address.
The bank’s internal audit must review implementation of these Directions every year, including whether auto-escalation happens within the timelines.
The IO’s office analyses complaint patterns every quarter and suggests fixes for repeat complaints.
The clauses on outcome categories and on closure by a different unit had a compliance deadline of 30 June 2026, so they should be live in covered banks by now.
After the bank’s reply: RB-IOS, 2026
The RBI Ombudsman Scheme has also changed. The Reserve Bank – Integrated Ombudsman Scheme, 2026 came into force on 1 July 2026 and replaced the 2021 scheme. Complaints received before that date continue under the 2021 scheme.
A customer can approach the RBI Ombudsman if the bank has not replied within 30 days (or the longer period set by RBI, NPCI or card network rules), or if the customer is not satisfied with the reply or resolution. The complaint should be filed within 90 days of that timeline expiring or of the bank’s last communication, whichever is later. The Ombudsman can award compensation of up to ₹30 lakh for consequential loss, and up to ₹3 lakh for loss of time, expenses and harassment.
One practical warning: many bank web pages and older articles still quote the 2021 scheme’s one-year window. If your customer-facing pages or reply templates do, update them.
What is mandatory and what is good practice
Practice | Where it comes from |
|---|---|
Auto-escalate partially resolved and wholly rejected complaints to the IO within the timelines | RBI Internal Ombudsman Directions, 2026 (binding on covered entities) |
Record only the three outcome categories | Same Directions |
Do not let the same branch or unit close the complaint | Same Directions |
Communicate the final decision within 30 days | Same Directions |
Annual internal audit of the IO framework | Same Directions |
Ask the customer to confirm the issue is resolved | Best practice. It is not a condition of closure in the RBI texts reviewed for this article |
Sample “fully resolved” closures every month | Practical recommendation |
Track reopen rate and repeat complaints | Practical recommendation. RBI sets no benchmark |
Why complaints get closed without resolution
Few poor closures come from bad intent. They come from how the process is measured and built.
TAT is the only number anyone reviews. When teams are judged mainly on turnaround time, closing the ticket stops the clock. Some staff close a case planning to deal with it if the customer comes back.
The complaint is tagged as a query. Queries follow looser rules, so a quick answer closes them. But the IO Directions define a complaint as any representation alleging deficiency in service, with or without a specific relief sought. If the customer is saying the bank got something wrong, it is a complaint, whatever the tag says.
The reply explains nothing. “As per policy” may be correct. It still tells the customer nothing about what was checked.
Nobody checks whether the customer accepted the answer. In many systems, sending a response is the closing event, and silence is read as satisfaction.
The case spans teams and partners. A card dispute may need the card team, operations and a network or processing partner. If the first team replies and marks it closed, the pending action disappears from view.
The same unit decides and closes. When the team that handled a complaint also rejects it and closes it, nobody independent has looked at the decision. The IO Directions now address this directly for covered entities.
Reopened complaints are logged as new ones. If a repeat complaint gets a fresh ticket with no link to the first, the earlier closure never counts as a failure and the reopen rate looks healthy.
What poor closure costs a bank
Closing a case without solving it rarely makes the problem go away. It usually returns in a bigger form.
Repeat handling: the same issue is investigated twice, often by a more senior person the second time.
Escalation to the RBI Ombudsman: this route is free for the customer, the bank has to respond, and the Ombudsman can award compensation.
Board-level visibility: under the IO Directions, cases where the Competent Authority overrules the IO go to the board’s Customer Service Committee. So does a quarterly report of complaints the RBI Ombudsman resolved in the complainant’s favour, with analysis of at least the top five categories.
Supervisory attention: customer grievance redress is part of RBI’s supervisory review, and RBI’s consumer protection department may review cases where a customer reaches the Ombudsman after the bank did not accept the IO’s decision.
Lost trust: a customer who feels ignored is more likely to move their account than to file a third complaint.
How to improve complaint closure quality
You do not need a full overhaul. These six changes cover most of the gap.
1. Define “resolved” for each complaint type
Write a closure rule per complaint type, so staff cannot close a case without meeting it. An illustrative starting point:
Complaint type | Treat as resolved only when | Keep on record |
|---|---|---|
Wrong or disputed charge | The charge is reversed, or its basis is explained with the fee clause and the date it was disclosed | Statement entry, fee schedule reference, reply sent |
Failed or delayed transaction | Money is back in the account and any compensation due under the applicable RBI, NPCI or network timeline is paid | Transaction reference, credit date, customer notification |
Loan or account statement dispute | The correction is made, or a reconciled ledger is shared with the customer | Before and after statements, approval note |
Service delay (card, cheque book, closure request) | The service is delivered, or a dated commitment is given and tracked | Delivery proof or tracking reference |
2. Separate who handles from who closes
For covered entities this is now an RBI direction. Even where it is not, it is sound design: the person or unit that handled the complaint should not be the only one deciding it is finished. Rejections and partial resolutions need a senior reviewer before anything is sent.
3. Treat classification as a control
Use the complaint-or-query test: is the customer saying the bank fell short? Then it is a complaint. Keep the query category for genuine requests for information, and sample it during audits.
4. Confirm with the customer before final closure
This is best practice, not an RBI requirement. After sending the reply, ask the customer a simple yes or no: is the issue solved? Keep the case open for a short window (seven days is a common starting point) and reopen it automatically if the answer is no. If there is no response, close it with a separate reason such as “closed, no response from customer”, not “customer satisfied”. Always link the reopened case to the original complaint ID, so your reopen rate is real.
5. Write replies that can be checked
A reviewer, an auditor or the RBI Ombudsman should be able to read the reply and see what was done. Compare these two replies in a case where the bank finds the charge valid:
Weak: “The charge is as per bank policy. Your complaint is closed.”
Better: “We checked your account for [month] and found a charge of ₹[amount] for [fee name]. It was applied under [clause] of the schedule of charges shared with you on [date and channel], so we have not reversed it. [For covered banks: This complaint was reviewed by our Internal Ombudsman.] If you disagree, reply to this message or call [number] within [period] and we will reopen the case. You can also approach the RBI Ombudsman at https://cms.rbi.org.in.”
The second reply costs a few more minutes to write and prevents many repeat contacts.
6. Send root causes back to product and operations
If the same complaint keeps arriving, better replies will not fix it. A confusing fee disclosure or a failing process will. Share complaint trends with product and operations teams every month, and use the IO’s quarterly pattern analysis as an input where your bank has one.
Using a grievance audit to check closure quality
A grievance audit is a structured review of how complaints were handled and closed. It shows whether your process works in practice, not just on paper.
Two different audits are in play here. The annual internal audit of the IO framework is required by RBI for covered entities. A monthly closure-quality audit is a practical recommendation that goes further, because the IO safety net has a gap: it only reviews complaints the bank itself classifies as partially resolved or wholly rejected. A complaint wrongly closed as “fully resolved”, or tagged as a query, never reaches the IO. Your audit should look exactly there.
Sample bucket | Why sample it | What to check |
|---|---|---|
Closed as “Fully Resolved” | The IO review does not cover these | Was the relief actually delivered and recorded? Does the reply match the complaint? |
Wholly rejected or partially resolved | These should have gone through senior review and the IO | Escalated within timelines? Reasoned decision? Closed by a different unit? |
Tagged as query or request | By definition, a complaint may be hiding here | Did the customer allege a deficiency in service? |
Reopened and repeat complaints | The first closure failed | Why did it fail, and which team or product is behind it? |
Cases that reached the RBI Ombudsman or where the IO was overruled | Highest stakes | Where did the internal process miss? |
Sample size depends on your volume. What matters is that every bucket is represented each month. For each sampled case, ask:
Is the customer’s actual problem addressed in the reply, not just the topic?
Was the promised action completed, and is there proof on record?
Is the explanation in plain language, with specifics?
Was the escalation route stated correctly, with current RBI Ombudsman details?
Was closure approved by someone independent of the handling unit?
Was the customer’s response, or the attempt to get one, recorded?
Here is a hypothetical example of how this plays out. A bank’s monthly sample shows that many charge-reversal complaints are closed with a policy reply, even where the customer’s disclosure argument was valid. The audit team updates the guideline, trains the team, and adds a second-level check on rejections. The next audit shows whether those cases are coming back less often. The value is in the loop: sample, find the cause, fix, sample again.
Reopened complaints as an early signal
A rising number of reopened complaints is usually the first sign that cases are closing before customers are satisfied. Track these alongside it:
Reopen rate within 30 days of closure
Repeat complaints from the same customer on the same issue
Share of rejected complaints reversed on review
Share of closures with customer confirmation or a documented attempt
Audit pass rate by team and product
RBI sets no benchmark for these, so record a baseline for two or three months before setting targets.
Where technology helps, and where Webnyay fits
Spreadsheets and email threads cannot enforce closure rules at volume. A complaint management system can, if it is configured to. Look for a system that can:
Require a recorded outcome category and block closure without it
Stop the same user or unit from reviewing their own rejection
Run escalation timers tied to the applicable timeline
Link reopened cases to the original complaint
Require key fields in the reply, such as what was checked and how to escalate
Keep a full audit trail and report by product, team and root cause
AI can help flag replies with missing details, but the final decision should stay with an officer.
Webnyay’s grievance redressal software is described as an AI-powered platform for omni-channel complaint intake, tracking, workflows and escalations with audit trails, and its listed use cases include banks and NBFCs. It also works well with a clear escalation design; our guide on the grievance escalation matrix covers ownership and audit trails in more detail. If you are looking at speed alongside quality, read how to reduce complaint resolution time in banks, NBFCs and insurers and what to look for in a complaint tracking system for banks.
Some complaints are really disputes, such as a loan disagreement that a reply cannot settle. For those, Webnyay’s online dispute resolution offering provides online conciliation, with secure chatrooms, document exchange and video sessions, and online arbitration if conciliation does not work. How a specific closure rule or Internal Ombudsman review workflow would be set up in your environment is best confirmed in a demo, against your own complaint policy.
Next step
If your team still decides closure by status and TAT alone, with reopened cases, rejected complaints and query tags sitting in spreadsheets or separate systems, you will not see poor closures until a customer or the RBI Ombudsman points them out. Webnyay can help you move that work into a structured digital process. Explore Webnyay’s Compliance and Grievance Redressal solution or book a demo, and bring one real closed complaint from your own queue. Ask to see how outcome categories, independent review, escalations and audit trails would be configured for it.
This article is for general information. It is not legal advice, and Webnyay is not a law firm. RBI directions differ by type of regulated entity and change over time, so check the current text that applies to you.
FAQs
What is the difference between closing a complaint and resolving it?
Closing is a status change in the system. Resolving means the customer’s problem was fixed, or, where it could not be, the decision was explained and reviewed. A complaint can be closed without being resolved, and that gap is what closure quality measures.
Does RBI require banks to get customer confirmation before closing a complaint?
Not in the Internal Ombudsman Directions or RB-IOS 2026 texts reviewed for this article. Even so, an unconfirmed closure carries risk, because a dissatisfied customer can escalate to the RBI Ombudsman. A confirm-or-reopen step is good practice, and your own board-approved policy may require more.
Which complaints go to the Internal Ombudsman?
Complaints that the bank has partially resolved or wholly rejected. Customers cannot approach the IO directly, and the IO’s contact details are not public. Some matters are outside the IO’s purview, such as corporate frauds that do not affect the customer, internal HR matters, and cases already decided by or pending before courts, consumer commissions or arbitration. Note that service deficiencies inside commercial decisions are still valid for the IO.
What can a customer do if they are not satisfied with a closed complaint?
They must first have complained to the bank in writing. If the bank did not reply within 30 days (or the longer applicable timeline), or the customer is unhappy with the reply, they can file with the RBI Ombudsman through cms.rbi.org.in, by email to the CRPC or by post. The window is 90 days from the timeline expiring or the bank’s last communication, whichever is later.
What is a good reopen rate?
There is no standard benchmark. Compare against your own baseline by product and team, and look at why cases reopen. A very low rate can also be a warning if customers have no easy way to reopen.
Do these rules apply to NBFCs and fintechs?
RB-IOS 2026 covers banks, certain NBFCs, non-bank prepaid payment instrument issuers and credit information companies, each with eligibility conditions. The IO framework applies to eligible NBFCs as well, under thresholds in RBI’s directions for them. A fintech that is not itself a regulated entity under the scheme is not covered directly. If you operate through a bank or NBFC partner, confirm with them who owns the customer complaint.