Case study · Compliance
The odd use case that saved a client from an $82K lawsuit
It wasn't a sales call. It was a six-minute request to move a payment date, the kind of call most QA programs never review. Here's how The Scorecard and an analyst caught a serious compliance issue and got it resolved before it became an $82,000 problem.
- Client
- National debt settlement company
- Team
- 60+ agents across sales and service
- Outcome
- Lawsuit avoided, customer retained
Service call · Draft date change
- Legal action mentioned02:51
- Outcome assured to customer03:28
Escalated to compliance
- $82K
- potential exposure avoided
- 6 min
- length of the call that mattered
- 19 hrs
- from call to resolution
The call nobody was listening to
The client brought The Scorecard in to score its sales calls. During onboarding they chose to send every recorded call, including their customer service lines, mostly so they could see volume across the whole floor. Service calls had never been part of their QA. A team lead spot-checked maybe one in two hundred.
On a Tuesday afternoon, a long-time program customer called to move her monthly draft date. Partway through the call she mentioned that she had just received court papers from one of her creditors. The agent, trying to be reassuring, told her not to worry, that the program would take care of it, and that she didn't need to do anything about the papers.
Why it mattered
A debt settlement program can't stop a creditor from filing suit. A customer who ignores a summons can end up with a default judgment, wage garnishment, and legal fees added to the balance. Telling her not to respond was harmful advice, and it misrepresented what the program does. That's the kind of statement that turns a single account into a deceptive-practices claim.
The client's counsel later put the combined exposure, including the balance at risk of a default judgment, refunded program fees, and the cost of defending a claim, at roughly $82,000.
How it was caught
The Scorecard engine checks every call for a set of high-risk situations regardless of call type, including any mention of lawsuits, summons, or garnishment, and any assurance about an outcome. This call triggered both within forty seconds of each other.
On its own, the automated score ranked the call as low priority, because service calls carry less weight than enrollments. That's where the analyst made the difference. The analyst assigned to the account reviewed the flagged moments, confirmed the customer had an active court deadline, and escalated it straight to the client's compliance lead that same afternoon, with timestamps and a written summary.
What happened next
The compliance lead called the customer the next morning, corrected the guidance, explained her options in writing, and connected her with the program's attorney network. A response to the summons was filed ahead of the deadline, the creditor agreed to settle the account within the program, and the customer stayed enrolled. No complaint was ever filed.
The agent was coached that week. Nothing punitive, just a clear, approved way to respond whenever a customer mentions legal action.
What changed
The client added a legal-mention rule to the scorecard for every agent, sales and service alike, and The Scorecard now routes any mention of a lawsuit or summons to compliance the same day. Three more of these calls have been caught since, and every one was resolved within 24 hours.
The riskiest call in a given week often isn't a sales call. Reviewing every call, and having a person who understands the context look at what the system flags, is what made the difference here.
Client details have been changed to protect confidentiality.