Use caseRetail banking
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
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. 6One rule fails · the AI names it, the specialist sets the remedy
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.
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.
The email becomes a complaint case, and its two deadlines start the same evening.
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.
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.
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.
Priya needs three things before she writes: what was charged, what the rules allow, what the customer already said.
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.
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.
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.
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.
Derek accepts the refund but not the rest. The case keeps its history and carries on, all the way to the CFPB.
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.
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.
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.
Upholding or rejecting the complaint stays with Priya. The AI reads the charges against your fee schedule and reports one of three results.
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.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.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.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.
Counted on Derek Lawson's complaint, one fee dispute that reached the CFPB. Another category or another policy will give other counts.
Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.
The specialist answers the customer, compliance answers the regulator, IT answers for the channels. This page has something for each.
Mornings go into finding what the customer already said, somewhere.
A missed deadline reaches you on the same day it reaches the regulator.
Mailboxes, branch tools and the app each hold part of the complaint, and none of them talk.
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
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.