The Reserve Bank — Integrated Ombudsman Scheme, 2021 (IOS 2021, RBI/CEPD/GSD/2021-22/166, November 12, 2021) consolidated three prior ombudsman schemes — the Banking Ombudsman Scheme, the Ombudsman Scheme for NBFCs, and the Ombudsman Scheme for Digital Transactions — into a single integrated framework. IOS 2021 covers scheduled commercial banks, non-scheduled commercial banks, regional rural banks, urban cooperative banks, state cooperative banks, district central cooperative banks, NBFC-Deposit-taking and NBFC-Non-Deposit-taking (in specified categories), and payment system operators licensed by RBI.
The scope expansion means that AI governance obligations in customer grievance redressal now apply to a population far wider than the banking sector alone. Every NBFC and payment system operator with an AI-mediated complaint handling process must comply with IOS 2021's reasoned written reply, 30-day resolution, and evidence production obligations — not only scheduled commercial banks.
This post maps the specific AI governance obligations that IOS 2021 creates for three AI systems in the grievance redressal chain: complaint response AI (LLMs drafting reasoned written replies), complaint triage AI (classification and routing models), and AI models whose outputs are the subject of the underlying complaint.
LLM Complaint Response: The Reasoned Written Reply Trap
IOS 2021 Clause 9 requires a "reasoned written reply" before ombudsman jurisdiction opens. This is a legal threshold that AI-generated complaint responses must meet — and the legal consequences of failing to meet it are specific to IOS 2021 proceedings.
An LLM-generated complaint response that is factually accurate, cites correct policy provisions, and addresses the specific complaint grounds satisfies Clause 9. The governance risk is not that AI was used — it is that LLM hallucination can produce a reply that appears reasoned but contains factual misrepresentations: citing a policy version that has been superseded, stating an account action was taken on a date different from the actual system date, claiming regulatory compliance for an action that was not compliant.
In ombudsman adjudication, if the bank's reasoned written reply contains factual misrepresentations, the Ombudsman can draw adverse inference — treating the misrepresentation as evidence that the bank's original action was also erroneous. This inference risk is significantly higher for LLM-generated replies, because the LLM has no access to the bank's authoritative system records unless specifically integrated, and template-based LLM responses can produce plausible-sounding but factually wrong statements about specific customer accounts.
The AI governance framework for LLM complaint responses:
- System integration: the LLM must have access to the authoritative customer record (CBS data, not a summary), transaction history, and the specific policy version in effect at the time of the disputed action
- Human-in-the-loop review: a responsible officer must verify factual claims in the draft reply before dispatch — the review must be logged with officer identity and timestamp
- Version and model logging: the model version used to generate the draft, the system prompt, and the draft text before human review must all be retained for 5 years
- Hallucination detection layer: a secondary model or rule-based checker that flags claims in the LLM reply that cannot be verified against the authoritative account record
Complaint Triage AI: The 30-Day Clock
IOS 2021 Clause 8 specifies that the ombudsman accepts jurisdiction only after the regulated entity has had 30 days to resolve the complaint. AI triage models that misroute complaints — classifying an urgent payment failure as a general banking inquiry — delay the start of the 30-day clock in the appropriate resolution pathway. When 30 days expire without resolution, ombudsman jurisdiction opens automatically. The bank cannot undo this by correcting the routing after the fact.
MRMF Clause 4.2 requires pre-deployment validation for models used in material decisions. A complaint classification that triggers a 30-day regulatory timeline is a material decision. The validation requirements for complaint triage AI:
Per-category false-negative validation: The model must be validated for false-negative rates on each complaint category that carries time-sensitive IOS 2021 consequences — unauthorized transactions (Category A under IOS 2021), payment failures, account blockages, and loan-related complaints. Aggregate classification accuracy is insufficient.
Priority routing override: The triage AI must have a deterministic override path — specific trigger words or account conditions that force escalation to a human reviewer regardless of the model's classification, for complaint types where misrouting risk is highest.
Monitoring and drift: Complaint language and complaint categories evolve. Triage AI must be monitored for classification drift — a model trained on 2024 complaint data may not correctly classify complaint language patterns that emerge in 2026 (e.g., new complaint categories related to AI-mediated decisions, DPDP rights requests embedded in complaints). PSI monitoring on the complaint text feature distribution is the minimum.
AI Models as the Subject of Complaints: Evidence Readiness
As AI models make more customer-affecting decisions — credit declines, transaction blocks, KYC rejections — an increasing share of IOS 2021 complaints will challenge AI decisions. IOS 2021 Clause 14 gives the Ombudsman authority to call for documents. AI decision logs are documents.
A bank whose credit decision AI declines a customer's loan application, and whose customer files an IOS 2021 complaint alleging discriminatory or unexplained rejection, will face a request for: the model version used for the decision, the input features processed for the specific customer, the output score, the threshold applied, and the reason codes generated. If the bank cannot produce this documentation — because the AI system does not log at this granularity or the retention period has passed — the bank faces adverse inference in the ombudsman proceeding.
Evidence readiness requirements for AI-mediated customer decisions:
- Decision log: model version, input feature values (not just feature names), output score, threshold, reason codes — logged per decision
- Retention: 5 years minimum (PMLA audit floor); extend to 7 years for decisions subject to IOS 2021 complaints if the complaint was filed within 5 years
- Retrievability: the log must be queryable by customer identifier and decision date — an archived flat-file log that requires days to process is not functionally retrievable for ombudsman proceedings with response deadlines
- Explainability translation: technical model output (feature SHAP values, attention weights) must be translatable into a customer-understandable explanation that the bank's customer service team can communicate — the ombudsman proceeding will require this translation
DPDP Act Complaint Data: The Training Corpus Trap
Customer complaint data is personal data under DPDP Act 2023. Banks that have trained complaint classification, sentiment analysis, or resolution-suggestion models on historical complaint data face a DPDP compliance question: what was the legal basis for secondary processing of complaint data for AI training purposes?
The complaint data was originally collected for complaint resolution (contractual obligation or legal obligation basis). AI model training is a different purpose. Without explicit consent for the training use, or without anonymizing the data beyond DPDP re-identification thresholds, the training constitutes unlawful secondary processing.
The recursive exposure: a DPDP rights complaint about a bank's use of complaint data for AI training is itself an IOS 2021 complaint if the bank is the data fiduciary. DPDP and IOS 2021 obligations intersect for AI governance in ways that no global framework addresses.
IOS 2021 AI Governance Checklist
- ☐ LLM complaint response: system integration to authoritative CBS records; human-in-the-loop review queue with officer ID and timestamp logging; draft versioning; hallucination detection for factual claims
- ☐ MRMF model card: complaint classification AI and LLM response AI in MRMF model inventory as material decision models
- ☐ Triage AI validation: per-category false-negative rate validated for time-sensitive IOS 2021 categories; priority routing override for highest-risk categories
- ☐ 30-day clock monitoring: operational reporting on complaint resolution SLA by routing path; alerts for complaints at 20-day mark that are still in triage or general queues
- ☐ AI decision evidence readiness: decision log per AI-mediated customer decision (model version, inputs, output, threshold, reason codes); 5-year retention minimum; queryable by customer/date
- ☐ Ombudsman document production process: documented workflow for responding to IOS 2021 Clause 14 document production requests that include AI decision records
- ☐ DPDP training data audit: existing complaint AI models audited for DPDP training data legal basis; future training processes require DPDP-compliant data or synthetic data
- ☐ NBFC and PSO coverage: IOS 2021 AI governance framework applied to all regulated entities under the scheme, not only commercial banks
- ☐ PSI monitoring: complaint triage AI monitored for classification drift; complaint language distribution shifts tracked quarterly
- ☐ RBI CEPD examination readiness: IOS 2021 AI governance documentation packaged for RBI Consumer Education and Protection Department examination