Built by Patched
Reliable AI for Regulated Risk & Fraud Operations

Same analysts.
A queue that stops growing.

We work the post-complaint queue for Indian banks. Your analyst gets a worked case and one decision to make.

Scope a 2-4 week pilot See how a case runs

Everything runs in draft. Nothing is submitted until your team approves it.

Case Operations live
I4C portal complaint, fresh case
ACK 3147…9821
Working
Complaint read and classifiedFresh case, three disputed transactions
Evidence collected from five systemsAccount, transactions, hold register, KYC, service desk
Checks run against your rulesEncumbrance and FIFO validated, no exception raised
Response drafted with its reasoningSubmission values, and why each one was chosen
Waiting on your analystApprove, send back for more information, or escalate
Evidence sources
0%
backlog reduction
0
complaints closed
98%+
within 72-hour SLA
<1 hr
case turnaround
0x
operational return
0k
workflow runs

Production outcomes at a leading Indian payments bank. SLA and turnaround from Patched fraud, risk and compliance operations.

Read the case studies
The actual bottleneck

Filing the complaint was never the slow part.

A complaint lands in minutes. Working it takes hours, and almost none of that time is spent deciding. It is spent finding.

Reading

One case, five systems

Account data, transactions, hold status and KYC all sit in different places. The analyst opens every one before forming a view.

Rework

The rules keep moving

Formats and regulatory expectations keep changing. Each change lands as rework on a queue already behind.

Proof

Closed is not defensible

Months later somebody asks what was checked, and when. If nobody captured it, the case gets worked twice.

What changes on Monday
Judgement,
not retrieval. Every source,
timestamped. Reconstruct it
months later.

The reading and the first draft are done before anyone opens the case. What is left is the judgement you hired an analyst for. No one is replaced.

What was checked, and when, sits on the case itself. No one reopens five tabs to answer a question about last quarter.

Inputs, checks, decisions and exception reasons stay on the record, so a reviewer never has to call the analyst who worked it.

Analysts today
With CaseLEA
Read every email and complaint
Review a recommendation
Search five systems by hand
Evidence already collected
Write the response from scratch
Approve, amend or send back
Update internal records afterwards
Audit trail written as it runs
The case lifecycle

One case. Four stages. Most tools touch one.

IntakeFour channels, four shapes, all at once.
EvidenceFive systems, read before anyone forms a view.
DecisionWhich scenario is this, and what follows from it.
ProofWritten while the work happens, not after.
Four channels, one queue
NCRP via API I4C portal LEA email Grievances
Collected read-only, all at once
Core banking
Transaction history
Lien and hold register
KYC document store
Service desk history
Checked against your rules
16,736
scenarios mapped from live operations
One outcome, or a routed exception
Written while the work happens
ACK 3147…9821audit record
Inputs recorded
Checks and their results
Exception reason, where one applied
Approver and submitted values
Sealed & reviewable
Coverage

Seven workflows, one operating model.

Start with whichever is under the most pressure. We bring the operating logic and fit it to your data, policies and thresholds.

01

NCRP complaints via API

Straightforward complaints handled in real time, with bank-specific validation and routing.

High volume
02

I4C portal complaints

Complex fresh, reassign and response-received cases worked through to a submitted outcome.

60-87% resolved
03

LEA information requests

Notices interpreted, statements and KYC documents collected, fixed-format responses prepared.

84% less effort
04

Money restoration

Funds verified, FIFO and encumbrance rules applied, service requests raised and tracked to closure.

MRM
05

Grievance redressal

Grievances validated, evidence gathered, submissions raised, LEA responses followed to resolution.

GRM
06

Customer and merchant coordination

Missing evidence requested, counterparties chased, internal service records kept in step.

Email and desk
07

Post-complaint risk profiling

Reported transactions turned into account, velocity and pattern analysis feeding preventive controls.

Risk feedback
next

Start with one

Pick the workflow under the most pressure and prove it on your own cases before widening the scope.

Scope a pilot
Security and control

Designed for data that cannot leave the boundary.

Each deployment is isolated for the institution. We read approved sources read-only, work the case inside the boundary, and keep only the minimum metadata needed to operate and audit it.

Dedicated VPC in MumbaiAWS or GCP deployment aligned to Indian data residency requirements.
No customer data used for trainingTransaction and PII data does not flow back into shared models or Patched systems.
Review and approval by policyOperate draft-first, maker-checker or autonomous by approved scenario.
Audit evidence for every caseInputs, checks, decisions, timestamps, outputs and exception reasons remain reviewable.
Least-privilege, read-only retrievalEncrypted in transit and at rest. Deployment and retention controls finalized with your security team.
SOC 2 Type I and IIRBI SAR certified deployment and CERT-In empanelled penetration testing.
Institution-specific deployment
your boundary
LEA channelsI4C, NCRP, MRM, GRM and email
CaseLEA executionCase data processed inside the boundary
Bank systemsAPIs, warehouse, SFTP, KYC and service desk
Rules and evidenceDeterministic checks, exception routing and audit

Encrypted in transit and at rest. Least-privilege access. Read-only data retrieval. Deployment and retention controls finalized with your security team.

Production case study

From a 15,000-case backlog to a current operation.

We built CaseLEA inside a live operation, edge case by edge case. That is what keeps it working after the rules change, rather than a cleanup that decays.

Results reported across one active deployment

Read the case studies
Cases closed, cumulative 95% backlog reduction
backlog at startcurrent operation
0
new transaction complaints closed
0
reassign complaints closed
0
response-received complaints closed
0
workflow improvements deployed

Start with the cases your process cannot absorb.

Pick one or two workflows, a set of real cases and a number you want moved. We set up around your approved data sources and run in draft until you are ready.

  1. Agree the workflow and the success metric
  2. Connect approved data sources and templates
  3. Run representative cases for 2-4 weeks
  4. Review accuracy, effort saved and exceptions
Scope a pilot on your own cases