The moment a customer disputes a debt, the agent marks the account as disputed and stops collection activity on it. It then sorts the claim, pulls the agreement, statements and payment history, checks for payments that were missed or misapplied, and prepares an evidence pack. A named disputes handler decides whether the debt stands, and only they can restart collection.
What is a debt dispute, and who owns the process?
A debt dispute is a customer's challenge to whether they owe a balance, or how much. It takes several forms, and each needs different evidence:
- Not my debt: the customer has never had the account, which often points to identity fraud.
- Already paid: a payment was made but not credited, or credited to the wrong account.
- Wrong amount: charges, interest or fees the customer believes were applied in error.
- Settled or closed: the customer says an earlier agreement ended the debt.
- Too old: the customer believes the debt can no longer be pursued.
The head of collections owns the process; compliance owns the rules on pausing activity; fraud owns "not my debt" claims. A named disputes handler owns each case. Our guide to AI agents in banking covers the wider limits.
What does the agent prepare, and what does a person approve?
- Agent, depth 3: flags the account as disputed and pauses collection. Reminders, calls, fee application and onward referral stop for the disputed balance. This is a protective action and should never wait. Evidence: flag time against the customer's first statement of dispute.
- Agent, depth 1: classifies the claim into one of the forms above, quoting the customer's words. "Not my debt" claims go to fraud. Evidence: classification and quote.
- Agent, depth 1: assembles the account evidence. The signed agreement, statements, payment history, any earlier arrangements, and correspondence. Evidence: an index of documents with sources.
- Agent, depth 1: tests the claim against the evidence. For "already paid", it searches incoming payments around the date and amount the customer gives, including unallocated payments. For "wrong amount", it recalculates charges against the agreement's terms. Evidence: workings.
- Agent, depth 2: drafts the evidence pack and a recommendation. What the evidence shows, what is missing, and a draft reply for each possible outcome. Evidence: the pack.
- Person, disputes handler: decides. Uphold in full, uphold in part, or reject. Evidence: decision and reasons.
- Agent, depth 3 after approval: applies the outcome. Balance corrections, credit file correction requests, and the reply to the customer, all as approved. Evidence: changes linked to the decision.
- Person, disputes handler: lifts the dispute flag. Collection resumes only after this, and only on the balance that stands. Evidence: flag removal by a named person.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Pause | Flags the account, stops collection | 3 | Nothing; pausing never waits |
| Classify | Sorts the claim, routes fraud | 1 | Fraud team for "not my debt" |
| Evidence | Pulls agreement, statements, payments | 1 | Nothing |
| Test | Searches payments, recalculates charges | 1 | Nothing |
| Pack | Drafts findings and replies | 2 | Nothing yet |
| Decide | Nothing | none | Disputes handler decides |
| Apply | Makes approved corrections, sends reply | 3 | Handler approves the content |
| Resume | Nothing | none | Handler lifts the flag |
Which controls matter, and what evidence do they leave?
Pause is immediate and automatic. The agent cannot be argued out of it, and other agents and systems see the flag. Evidence: suppressed contacts and fees logged.
Only a person lifts the flag. Evidence: refused verdicts on any agent attempt.
Missing evidence counts against the debt, not for it. If the agreement cannot be found, the pack says so plainly. The handler decides what that means. Evidence: "missing" entries in the index.
No onward referral while disputed. A disputed debt is not passed to an agency or sold. Whether an agent should ever make that referral is covered in whether an AI agent can pass a debt to a collection agency. Evidence: refused verdicts on referral attempts.
Settlement is not a resolution. Offering a discount to make a dispute go away does not answer whether the debt is owed. Settlement is a separate decision; see whether an AI agent can negotiate a settlement on a debt. Evidence: settlement capability absent from dispute cases.
Complaint rules may apply too. A dispute is often also a complaint, with its own handling time limits. Evidence: complaint flag where applicable.
What should you measure?
- Time from dispute to pause. Should be close to zero.
- Collection contacts after a dispute flag. Target zero.
- Disputes upheld, by type. Many upheld "already paid" disputes point to a payment allocation problem.
- Time to decision.
- Credit file corrections requested and confirmed.
Where does it usually go wrong?
Collection carries on. The dispute is logged in one system and the reminder engine in another never hears about it.
The agent argues. Asked "why do you say I owe this?", it recites the balance and terms as if that settled the matter. Its job is to gather and present, not to defend.
Unallocated payments are missed. The customer's payment sits in a suspense account. Search there first.
"Not my debt" is handled as a billing question. If the customer never opened the account, it is a fraud case. The same split appears in handling unauthorised transaction claims.
The credit file is left wrong. The balance is corrected internally, but nobody asks for the reported data to be fixed.
Questions people ask
Can the agent tell the customer the dispute has been accepted?
Only after the handler decides, and in the approved wording. Before that, it confirms the dispute is logged, collection is paused, and when to expect an answer.
What if the customer disputes only part of the balance?
Pause collection on the disputed part. Whether the undisputed part can still be collected depends on your policy and local rules; that is a handler decision.
Should the agent ask the customer for evidence?
Yes, where the claim depends on it, such as proof of a payment. It drafts the request; the customer is not required to prove a negative such as "I never had this account".