A complaint is both an individual customer's concern and a potential signal about a wider process. Resolving it well requires understanding what happened, deciding whether the response is fair and confirming that any promised remedy occurred. Learning from it requires a second step: identifying whether other customers could face the same problem.
Banks and NBFCs often receive complaints through branches, email, contact centres, digital channels and external escalation routes. Fragmented intake can make one customer's experience appear as several unrelated tickets. It can also hide the first date on which the institution knew about the issue.
A dependable complaint process therefore combines complete intake, clear ownership, evidence-based investigation and meaningful closure. Root-cause analysis then connects recurring concerns to changes in products, systems and staff instructions.
Make complaint intake accessible and complete
Customers should be able to raise concerns through the channels the institution makes available. The process should not depend on the customer using legal terminology or selecting the perfect category. Staff need guidance for recognising a complaint even when it arrives as a general service message.
Create a consistent record containing the customer's concern, relevant product, date received, channel and requested outcome. Preserve the original wording where appropriate. An internal summary can be useful, but it should not erase an important part of the allegation.
Link duplicate contacts without losing their history. A customer who repeatedly follows up may be experiencing delay or unclear communication. Treating every follow-up as a new complaint can inflate volumes while concealing the age of the underlying issue.
Separate urgency from ordinary queue order
Some complaints require prompt attention because the potential harm is continuing. Examples can include an unresolved payment issue, an incorrect restriction or a concern about ongoing collection activity. The appropriate response depends on the facts and applicable requirements.
Define triage criteria and escalation authority. Staff should know when they can resolve a straightforward issue and when specialist review is required. Avoid routing every difficult complaint through several teams without assigning a single accountable owner.
Record immediate protective or corrective actions separately from the final decision. A temporary operational adjustment may reduce harm while facts are checked, but it should not be presented as the complete resolution if substantive issues remain.
Investigate the customer's actual concern
Begin by identifying the questions that need answers. What does the customer say happened? Which records could confirm or challenge that account? What terms, communications and operational events are relevant? A focused investigation is more useful than collecting every available document.
Obtain evidence from the systems and teams involved. Compare dates, amounts, instructions and messages. If records conflict, explain how the conflict was resolved. Do not assume that an internal system is correct simply because it is the institution's official source.
Keep a neutral account of the evidence. A complaint may be partly justified even if one element is mistaken. The response should address each material concern rather than rejecting the entire case because a single detail could not be substantiated.
Distinguish internal review from external escalation
RBI's 2026 internal-ombudsman directions separately address commercial banks and NBFCs. [1] [2] Their applicability and procedural requirements need to be assessed for the institution. The internal-ombudsman mechanism is not simply another name for the customer-service team.
Where the framework requires review before a proposed rejection or partial resolution, design the workflow to identify the relevant cases and preserve that review. Do not rely on individual staff remembering to forward them manually.
External escalation rights and the institution's communications about them must follow the applicable scheme and requirements. An internal status of “closed” should not imply that the customer has accepted the outcome or that every external avenue has ended.
A worked example: a payment credited late
Suppose a hypothetical customer complains that a timely payment was credited late and led to an additional charge. The loan system shows the later posting date, while the customer provides a bank reference indicating an earlier transfer.
The investigator checks the actual receipt, matching process, allocation rules and charge calculation. The issue may arise from a delayed file, an incorrect identifier or a misunderstanding about the relevant payment method. The final response should explain the supported facts and the resulting treatment.
If the institution identifies a processing defect, it should verify that the charge is corrected and consider whether other customers were affected by the same file or process. A courteous apology without an executed correction would not complete the remedy.
Define closure by the outcome promised
A response letter and a completed remedy are different milestones. If the institution promises a refund, record the actual payment. If it promises a record correction, verify the corrected record and any relevant downstream update. If it rejects the complaint, retain the evidence and required review supporting that decision.
Communicate in language the customer can understand. Explain what was examined, the conclusion and the actions taken or still planned. Avoid a long template response that fails to address the specific concern.
Keep the customer's reaction distinct from the institution's completion status. A customer may remain dissatisfied even after the institution has completed its approved process. Conversely, a customer may stop responding while promised corrective work remains unfinished.
Classify causes beyond the visible symptom
A useful taxonomy separates the complaint topic from its root cause. “Incorrect charge” describes a symptom. The cause could be an outdated product configuration, a missing waiver, an allocation defect or an inaccurate staff explanation. These require different remedies.
Use a structured questioning process. Ask why the error occurred, why the existing control did not prevent or detect it and why the issue reached the customer. Stop when the analysis identifies a cause that can be acted on, rather than assigning blame to an individual without examining the process.
Avoid forcing uncertain cases into a confident category. Record provisional causes and update them as evidence develops. Poor cause data can misdirect management attention as easily as poor transaction data.
Assess whether the problem affects a wider population
Once a process defect is identified, define the potentially affected population. Consider product versions, channels, dates, system releases and customer segments. The boundary should follow the cause, not simply the list of customers who complained.
Test whether the defect occurred elsewhere and estimate its effect. Where remediation is needed, assign an owner and track execution independently of the original complaint. A large population review may continue after the individual customer's case is resolved.
Retain the method used to identify affected customers and the evidence of corrective action. This allows independent reviewers to assess whether the institution addressed the whole problem or only the cases that became visible through complaints.
Use management information carefully
Complaint volumes need context. Compare them with customer numbers, transaction volumes and relevant business changes. A growing product can show more complaints even if the complaint rate falls; a stable volume can conceal worsening service if activity declines.
Monitor ageing, repeat contacts, reopened cases, overturned decisions and delays in executing remedies. Segment by product, channel and root cause. These measures reveal different weaknesses and should not be collapsed into a single satisfaction score.
RBI's consumer-protection reporting provides useful background on the importance of grievance redress and systemic learning. [3] The institution's own reports should help management decide which process changes require attention, funding or independent assurance.
Use reopening as diagnostic evidence
A reopened complaint can mean the original explanation was unclear, the promised remedy failed or new information changed the assessment. Record the reason instead of treating reopening automatically as a service-team failure. Different causes require different improvements.
Link the reopened record to the original concern and preserve the earlier response. This allows reviewers to see whether the institution's understanding changed and whether the customer had to repeat information unnecessarily.
Repeated reopening after a supposedly completed correction is particularly useful evidence. It suggests that the closure test may be too weak or that downstream systems did not receive the change. Investigate that pattern before asking staff simply to close cases faster.
Verify that improvements change later outcomes
An action labelled “staff sensitised” is difficult to evaluate unless it specifies what behaviour should change and how that will be tested. Prefer actions with observable outcomes: a corrected rule, a clearer disclosure, a revised allocation process or a tested escalation route.
Review later cases to see whether the same cause recurs. If it does, examine whether the action was incomplete, poorly implemented or based on an incorrect diagnosis. Closing an action after issuing an instruction does not establish that the underlying problem has disappeared.
A mature complaint process respects both the individual and the wider evidence. It gives each customer a reasoned response, confirms actual redress and uses recurring concerns to improve the institution's operations. That is how complaint handling becomes a source of control insight rather than only a queue to clear.
PRIMARY REFERENCES
Sources & further reading
Primary-source references checked on 12 October 2026. Follow the relevant authority’s current text for applicability, amendments and commencement dates. International standards provide context and are not automatically identical to domestic requirements.