Use caseRetail banking

Bank fee complaints and disputes

A customer disputes $105 in overdraft fees after a call and an app message went nowhere. Three channels, two deadlines, one missed callback.

The deadlines are set the day the complaint is registeredEvery earlier contact is read before the answerThe specialist decides the remedy and signs

Actions on this complaint
The assistantFee check, September

Three overdraft fees of $35.00 posted on Sep 11. Your fee schedule allows two per day, so the third, $35.00, is over the limit.

source · statement Sept 2026, fee schedule sec. 6
The fee check on the statement

One rule fails · the AI names it, the specialist sets the remedy

01

What gets in the way

In a nutshell

Sep 24, Derek Lawson calls his branch about $105 in overdraft fees, and the banker promises to call back. Sep 29, he writes in the app. Oct 2, he sends a formal complaint by email. Each message reaches a different person, and the answer that finally goes out forgets the promise made on the phone, sometimes after the 60-day deadline. The hard part is getting the facts together before writing.

The complaint becomes a case on its first day. The workflow sets its deadlines, every earlier contact sits in its history, and the AI checks the charges against the fee schedule. The specialist starts from the facts and their sources, and keeps the remedy and the signature.

Complaint RC-26-03114 · HistoryCase management
Three channels, one thread. Every contact Derek made, in date order, with the answer Priya is about to sign in front.
Complaints dashboardCase management
Rachel's view of the region. Every open complaint counted against its next deadline, before any of them slips.

None of these screens is exotic for a complaints team. They help because each one is ready when the next is needed: the clock starts at registration, the history is read before the answer, and the file is ready if the customer goes to the CFPB. The acts below stay with RC-26-03114 until the CFPB response is open.

02

The registration

The email becomes a complaint case, and its two deadlines start the same evening.

Step 1Intake

The email is filed as a complaint case

Derek Lawson writes to customer service on Oct 2. He was charged $105 in overdraft fees on a single day in September and wants them refunded. His email and the attached statement are filed in a new case.

The AI gives each piece its type, links the case to his checking account on the account number in the statement, and proposes a category. Priya Natarajan, complaints specialist, confirms it is a complaint and the case opens.

Category: Fees and chargesProduct: checking accountStatement Sept 2026 attached
Complaint RC-26-03114Case management
The category is a proposal. Priya confirms or changes it, and both stay in the history.
The complaint exists from the first messageNo inbox to sort by hand. The email, its attachment and its account land together, in a case with an owner.
Step 2Workflow

Two deadlines start counting

The workflow sets the two dates your complaints policy follows: an acknowledgment within ten business days, a full answer within 60 days. Each is an SLA timer on the case, visible to Priya and to her team lead.

The assistant drafts the acknowledgment. Priya adds her direct line and sends it on Oct 5.

Complaint RC-26-03114Case management
The dates come from the process, so nobody types them by hand.
The clock is set by the processThe deadlines exist the day the complaint does. An escalation fires before either one is missed.
Step 3Reporting

The queue is sorted by the next deadline

Priya's queue lists every open complaint with its category and its next deadline. Rachel Stone in compliance sees the same view for the whole region, with the complaints closest to their limit on top.

Due this week: 4Past due: 1Acknowledged: 22
Complaints queueCase management
The deadline is a column you can sort and filter on.
Compliance sees the risk before it happensThe complaints near their limit stand out every morning, without anyone keeping a spreadsheet of dates.
03

The answer

Priya needs three things before she writes: what was charged, what the rules allow, what the customer already said.

Step 4AI check

The fees are checked against the fee schedule

The AI reads the September statement and compares it with the fee schedule in force. Three overdraft fees of $35.00 posted on Sep 11, at the posted rate. The schedule allows two per day, so one fee is over the limit.

The result is written on the case: a status, and the reasoning in plain words, each line pointing to the statement and the schedule section.

Statement Sept 2026.pdfViewer
Priya checks the highlighted lines on the statement itself.
The breach is found on the statement linePriya does not count fee lines by hand. She checks a finding and its source.
Step 5Assistant

Read everything the customer already said

Derek also called his branch on Sep 24 and wrote in the app on Sep 29. The branch note and the app message were filed on the same account. Priya asks the assistant for a short account of the earlier contacts.

Complaint RC-26-03114Case management
Each sentence of the answer cites the note or message it comes from.
Pull ten answers your team sent last month. How many forgot something the customer was promised on the phone, and how many of those customers wrote back angrier?
The answer covers what the customer went throughThe missed callback is in front of Priya before she writes, so the answer can own it.
Step 6Workflow

Priya decides the remedy, compliance reviews it

Priya refunds the $35.00 fee above the daily limit and keeps the other two, which follow the account agreement. She adds a goodwill credit of $20.00 for the missed callback and writes the reason for each amount.

Because the answer admits a breach of the daily limit, the process sends it to Rachel Stone for approval. Rachel approves and opens a task for the billing team: check whether the same run charged other accounts.

Complaint RC-26-03114Case management
The remedy and its reasons are fields of the case. The AI did not set them.
A breach never leaves without a second pair of eyesThe approval path is written in the process. Priya does not have to remember which answers need compliance.
Step 7Assistant

A reasoned answer, drafted from the case

Priya asks the assistant for a draft grounded in the case. It explains the limit, the refund, the fees that stay and the credit, and it tells the customer how to escalate, as your policy requires for every final answer.

She rewrites the opening in her own words, checks each amount against the case and signs it on Oct 14.

Complaint RC-26-03114Case management
The values taken from the case are highlighted in the draft, so each one is checked.
Every line can be defendedEach amount points to a statement line or a schedule section, which is what the CFPB reads first if it goes further.
04

The disagreement

Derek accepts the refund but not the rest. The case keeps its history and carries on, all the way to the CFPB.

Step 8AI check

A reply comes in with a new argument

On Oct 21 Derek writes back. He says his income is low and that the bank's hardship fee waiver should apply. The reply is linked to the same case on its content, and the status moves to Disagreement.

The AI checks the hardship criteria of the bank's written policy against the statements on file. Priya reads the result and the payroll deposits herself, then confirms the position in a final answer on Oct 28.

Hardship checkAI console
Each criterion shows the statement lines it was checked on.
The new argument gets a real checkPriya answers on the criteria of the policy, read on the statements, and can overrule with a reason.
Step 9Workflow

The CFPB response opens from the complaint

Derek files a complaint with the CFPB on Nov 3, and the CFPB forwards it to the bank. From the complaint, Priya launches a CFPB response case: the exchanges, the documents checked and both answers are transferred to it instead of being copied.

The branch call note carries an internal comment about the banker. Priya redacts it in the viewer: the CFPB response carries the distributable version, the full note stays inside.

CFPB response CF-26-0412Case management
The response case carries everything the complaint holds, linked to it.
The CFPB response is ready in two daysNobody hunts for the letters across three mailboxes. The file was being built from the first email.
Step 10History

The complaint waits for the CFPB to close it, with its trail

The bank has 15 days to respond through the CFPB portal and 60 days to close the case. Both dates are SLA timers on the response case. The complaint stays open until the CFPB case closes, and its history keeps every message, analysis and decision, dated and attributed.

Complaint RC-26-03114 · HistoryCase management
The trail is part of the case, readable by the auditor or the regulator.
Audit questions are answered from the caseWhich deadline was met, who approved the breach, what the customer was told: the regulator can read it straight off the case.
05

The verdicts

Upholding or rejecting the complaint stays with Priya. The AI reads the charges against your fee schedule and reports one of three results.

Compliant

Every charge follows the rules

Amounts, caps and notices match the fee schedule, and the case says so in one sourced line.

Then: the specialist explains it in the answer and decides any goodwill credit.
Facts missing

A document is needed first

A statement for the right month, an account agreement version. The check says which piece it could not find.

Then: the specialist asks for it; the check runs again when it is filed.
Rule breached

A rule fails, and you know which

The AI lists what is fine first, then names the rule that fails and the lines behind it.

Then: the specialist sets the remedy, compliance approves, the answer goes out signed.
Where the AI stops

It refunds nobody. It upholds nothing. It sends no answer on its own. Across the ten steps on this page, the remedy and the signature belong to the specialist, and the approval to compliance.

The AI classifies, checks, summarizes and drafts. The control is in how the process is written, with its deadlines and its approval path.

06

The gains

Counted on Derek Lawson's complaint, one fee dispute that reached the CFPB. Another category or another policy will give other counts.

2 datesset on the case the day it is registered, with an escalation before each one.
4 contactsread in one history before the answer: branch call, app message, email, reply.
1 actionto open the CFPB response with every exchange and document attached.

Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.

Why these numbers hold

Zero missed deadlinesProcess reliabilityThe clock starts with the case, and the queue sorts on it.
Zero forgotten contactsAnswer qualityEvery message on the account sits in the history the specialist reads first.
Decision supportA person decidesChecks and drafts cite their sources. The remedy and the signature stay with the specialist.
07

Who uses it

The specialist answers the customer, compliance answers the regulator, IT answers for the channels. This page has something for each.

Business operations

Complaint specialists

Mornings go into finding what the customer already said, somewhere.

  • The complaint arrives as a case with its category proposed.
  • The earlier calls and messages are summarized with their sources.
  • The fee check points to the statement line.
  • The answer is drafted with the escalation details already in it.
Risk and compliance

Compliance officers

A missed deadline reaches you on the same day it reaches the regulator.

  • Every complaint carries its two deadlines from day one.
  • Answers that admit a breach come to you before they go out.
  • Each analysis and decision stays in the history, dated.
  • The rules checked are yours, written in plain language.
IT and architecture

CIOs and architects

Mailboxes, branch tools and the app each hold part of the complaint, and none of them talk.

  • Messages from each channel are filed on the same case.
  • The AI check is a step in the process, called by API.
  • The CFPB response is a process you launch from the complaint.
  • Hosted where your bank decides: your data center or your cloud.

How to begin

With one category. Take the complaints about fees, where the rule is written and the statement holds the proof, and run them as cases with their clock.

Your mailbox, your branch notes and your app stay as they are. The complaint case collects what each one receives.

Your move

See it on your own complaints

Bring a few anonymized complaints and your complaints policy. We will set the clock on one with you, then draft the answer from its history.

The screens on this page are drawn to show one step at a time, with example data.

Uxopian Software helps organizations put AI to work across the systems they already run, without giving up control of their data, their infrastructure or their critical processes.