Use Case Scenario
This scenario extends the AUS Bank story told in CRM Use Case Scenario, where every service case was brought into one register. Nothing in that scenario changes here. This page picks up from the register and describes a new requirement that arrived afterward.
Background
AUS Bank's contact center now logs every customer case in one place. The Fraud Alert, Card Dispute, Loan Servicing and Account Access lines all feed the same register, and Monica's supervisors can see the whole picture at any moment. Loan Servicing, however, stayed the quietest line, and not because it carried the least volume. It only ever got loud after the fact. A case appeared the moment a customer called in angry about a missed payment notice, or after a payment had lapsed long enough to trigger an automatic flag. By then the customer was usually a week or two past due and annoyed that nobody had reached out first.
"The register tells us what has already gone wrong, and Monica's escalation rules make sure nothing sits unattended once a case exists. My problem comes earlier than that. I do not want to wait for an angry call. I want my team to be the ones making the first call, while the account is only a few days late and the customer can still sort it out easily."
Daniel, Collections Manager
Daniel's team already phones customers about overdue loans, but they do it from a printed list pulled from the lending system every Monday. By Wednesday the list is out of date, because some customers have paid, some have disputed the charge, and some have asked not to be called. Nobody can say afterward which customers were reached, or what each one said.
What Daniel's Team Asked For
Daniel described what his team needed in his own terms, as a short list of requirements rather than a list of features.
- A call list that stays current. Every morning the list should contain only the accounts that are genuinely overdue that day, without anyone rebuilding it by hand.
- Agents who are prepared. An agent should see the customer's account history on screen before the call is placed, not while the customer is already waiting on the line.
- A record of what the customer said. At the end of each call the agent should pick the outcome from a short, fixed set rather than typing a note: the customer promised to pay, has already paid, disputes the charge, or is unable to pay.
- Hard cases go straight to the register. A customer who says they genuinely cannot pay needs a person looking at the account. That call should become a Loan Servicing case on its own, without anyone copying details across.
- Respect for people who opt out. A customer who disputes a charge, files a complaint, or asks not to be called again must never be dialed again, starting the same day.
- Visibility without chasing. Daniel wants to see how many calls ended in each outcome each day, and to look closely at one specific call when something looks wrong.
- Clear limits on who changes what. Collections agents should work the calls assigned to them and see their own results. They should not change how the outreach is run or edit the list of customers who must not be called.
How the Team Met Those Requirements
Working with the UNICONNECT AI implementation team, Daniel's requirements were turned into a single outbound calling program named Overdue Payment Outreach, built on the same customer data the Loan Servicing line already used. The team made five decisions along the way.
The Calling Program
The call list is drawn from the overdue accounts and narrowed to the ones worth calling that day, so it refreshes itself each time the program runs. Agents work through it with the customer's account history in front of them before each call is placed. The program is treated as a servicing contact about an existing account, not a marketing offer, which also decides which opt out entries apply to it.
The Outcomes
The four outcomes Daniel asked for, Payment Promised, Payment Completed, Dispute Raised and Unable to Pay, are the ones collections teams use across the industry. Agents choose one at the end of every call, so every conversation ends in a structured record instead of a free text note.
The Hand Off
One rule connects the calling program to the case register. When an agent records Unable to Pay, a new Loan Servicing case is opened automatically, exactly as if the customer had phoned in. Monica's existing alert and escalation rules take it from there with no further setup. A Payment Promised outcome instead sends the customer a short confirmation message.
- Call ends: Agent records the outcome
- Check: Is the outcome "Unable to Pay"?
- Result: A Loan Servicing case is opened automatically
The Do Not Call List
A customer who disputes a charge, files a complaint, or asks not to be called again is added to the bank's do not call list the same day, for voice calls and for servicing contacts. From then on the program skips that number.
The Access Limits
Collections agents were given the ability to run the calls assigned to them and see their own results. Changing the program itself and editing the do not call list were reserved for Daniel and his supervisors.
Adding a number to the do not call list does not remove it from a call list that was already prepared. It only stops that number from being included or dialed again afterward.
Seeing What Happened
Daniel opens one shared dashboard each morning. It shows how many calls the previous day ended as Payment Promised versus Unable to Pay, and how the program is progressing, without opening anything call by call. When a specific outcome needs explaining, he opens a detailed report for one customer, which shows the call result and the note the agent left.
"That was the part that made this worth building. I did not want a second, separate escalation process for cases that started as an outbound call. I wanted my hardest calls to land in the same queue Monica's supervisors already watch, and I wanted to see the trend without asking anyone for a spreadsheet."
Daniel, Collections Manager
Outcomes
Measured against the problem Daniel first raised, the change was not only how quickly a case was escalated. It was when a Loan Servicing case came into existence at all.
| Measure | Before | After |
|---|---|---|
| How a Loan Servicing case usually started | Customer called in, or automatic flag | Agent call, recorded on the spot |
| Unable to Pay calls reaching the case register | Manual follow up, if any | Automatic, same day |
| Numbers excluded after a complaint or opt out | Tracked by memory | Enforced by the do not call list |
| Who could see outcome trends | Nobody, no view existed | Daniel, every morning |
For AUS Bank, the case register answered what had already gone wrong, and the escalation rules answered what needed attention right now. The outreach program adds the step before both: reaching the customer first, recording what they said, and letting the customers who could not pay flow into the queue Monica's team was already watching.
Where Each Part Is Documented
Each requirement above corresponds to a Campaign documentation page. Configuring the Campaign Use Case shows how the team built it.
| Guide | Covers |
|---|---|
| CRM Use Case Scenario | The story this extends |
| Configuring the Campaign Use Case | How it was built |
| Campaign Overview | The call list and the program |
| Campaign Filters | A call list that stays current |
| Dispositions | A record of what the customer said |
| DNC Management | Respect for people who opt out |
| Campaign Reports and Dashboards | Seeing what happened |
| Campaign Permissions | Who changes what |