Example processfintechCFPB

Complaints handling automation software

An example of complaints handling as a governed process: agents do the 8 steps, and a person signs the gate before anything irreversible happens. Download it, import it into your workspace, and adapt it to your systems.

Download example · JSONImport into Minctrl →

minctrl.process/v1 · hash af24dd60f161…c74b

The graph8 agent steps1 human gatesigns: Complaints manager (DISP-accountable)

Complaints handling & redress autopilot

Banks and insurers field 50K-500K+ complaints a year, each demanding manual classification, evidence-gathering, a DISP-compliant final-response letter and a hand-built redress calculation under a regulatory clock. The work is repetitive and costly, yet a wrong redress figure, a missed vulnerability flag, or a blown deadline turns into ombudsman case fees, uphold rates and conduct findings. Routine complaints are auto-classified, investigated against policy and timeline, with the redress computed and the final-response letter drafted straight-through. Only the financial concession and fair-treatment judgment — plus any vulnerability-flagged case — reaches a complaints manager, who signs every redress/goodwill payment and the letter before money moves or it is sent.

The governed flow · branches, parallel work & a human on the irreversible step
vulnerability flag — mandatory human handlingno vulnerability flagroutine / not upheld / no redressredress owed or contested fair-treatment callsent back — more evidence neededapproved with redressapproved, no payment
Start
agent · low risk
Pull the complaint and the customer record from the case-management and core banking systems, classify the root cause and detect any vulnerability flags
decision
Vulnerability flag present?
parallel · fan-out / join
Open parallel investigation work-streams
agent · low risk
Test the complaint against product terms and DISP rules and the regulatory timeline
agent · low risk
Gather transaction and interaction evidence from the ledger and the communications archive
agent · medium risk
Compute the redress/refund (interest, fees, consequential loss) and draft the final-response letter with the proposed outcome; merges the two parallel investigation streams
decision
Routine, in-policy, no redress owed?
agent · low risk
Record the not-upheld / no-redress disposition and standard final response as a reversible draft on the case, log it for the SLA clock and route into monitoring — no money moves and no customer-facing send on this branch
gate · human sign-off
A complaints manager reviews fair treatment, approves the goodwill/redress figure and signs the final-response letter; vulnerability cases are decided here, and a case can be sent back for more evidencesigns: Complaints manager (DISP-accountable)
decision
Manager decision?
agent · high riskirreversible
Disburse the approved redress/goodwill payment via the payment rails and post it to the ledger
agent · high riskirreversible
Send the signed final-response letter to the customer and record DISP-compliant delivery
agent · low risk
Track the 8-week/regulatory SLA, log the audit trail, and route any referral to the Financial Ombudsman Service
Done
low riskmedium riskhigh riskbranch / reworkgate · human sign-off
Use this example
01

Download the file

A minctrl.process/v1 document: the graph and the hash of the process it becomes.

02

Import it in Processes

Import into Minctrl opens this example in your workspace; one click stores it as your first version. Import JSON does the same with the file, and a file changed after download is refused.

03

Connect your systems

Every connector starts in shadow: steps run, nothing leaves Minctrl until you configure a connector and switch it live.

04

Adapt it

Change signers, time limits and steps on the canvas. Each save is a new version; a running case stays on the version it started with.

Questions
How do I automate complaints handling with Minctrl?

Start from this example. Import the file in Processes, connect your own systems, and adapt the steps on the canvas. Agents run the reversible steps; every irreversible step waits at a gate for the role you choose. The example has 8 steps and 1 gate; you can change any of them.

Is complaints handling in Minctrl auditable?

Every run start, signature and change to the process is written to a hash-chained audit log your auditor can verify and export. The example is modelled on CFPB; whether your process meets it is a decision for your compliance team.

Does the AI decide everything?

No. Minctrl will not make a process runnable while an irreversible step can be reached without a human gate, and one person cannot sign two gates of the same run.

More examples