Use Case Scenario
A platform administrator at AUS Bank prepares for a campaign launch, and checks it as it runs.
This scenario continues the story in CRM Use Case Scenario. The Service Cases register closed the regulatory gap that Monica faced. Monitoring is how the platform behind that register is kept ready and explainable.
The Situation
The regulatory review that started the Service Cases project left AUS Bank with one lasting rule: anything that touches a customer must be explainable afterwards. Daniel Brooks is the platform administrator for the contact center. Monica is the Contact Center Director. Hannah Cole leads the Loan Servicing floor, and Marcus Webb is one of her agents.
This week AUS Bank launches Overdue Payment Outreach, a Collections campaign for 354 overdue loan accounts. Daniel must be sure that the platform is ready before the campaign starts, and he must be able to explain what happened if an examiner, or Monica, asks a question afterwards.
What Daniel Needs
| Need | Meaning |
|---|---|
| A ready platform | Services are running and resources are not near their limits. |
| Enough seats | The license has room for the agents who will work the campaign. |
| Loaded data | The overdue accounts finished importing before the launch. |
| Working automations | The disposition routing workflow runs for every call. |
| Proof of the result | A record of how many contacts the campaign reached. |
| An audit trail | A way to see who changed a setting, if a question comes up. |
How Monitoring Meets It
| Need | Page |
|---|---|
| A ready platform | System Health Overview and Health Tabs |
| Enough seats | License Details |
| Loaded data | CRM Imports |
| Working automations | Automation Execution Monitor and Task Queues |
| Proof of the result | Campaign Execution |
| An audit trail | Audit Logs |
The setup is in How to Configure the Use Case in UNICONNECT AI.
Launch Day
- 7:30. Daniel opens System Information. System Status reads Operational, all 8 containers are running, and Memory and CPU have room.
- 7:40. He opens License Details. Seven of ten users are in use, so three seats remain for late joiners.
- 8:00. He opens CRM Imports to confirm that the account list finished loading, as the case backlog did when the register was first filled. No import is active.
- 9:00. The campaign starts. Daniel opens Campaign Execution and watches Total and Success rise together.
- 11:00. Monica asks who created the Loan Servicing group and when the Lunch limit became 45 minutes, the kind of question an examiner could ask about how the floor is run. Daniel opens Audit Logs, searches Lunch, and shows the entry with his name, the date and the time. This is the kind of answer the review asked AUS Bank to be able to give.
- 17:00. He opens Automation Execution Monitor and confirms that Collections Disposition Routing completed for the day's calls.
The Outcome
- No surprises at launch.
- A clear record of the campaign.
- Fast answers.