Use Case Scenario
This scenario continues directly from CRM Use Case Scenario, where AUS Bank brought every service line into a single Service Cases register, with Case Type, Case Reason, and Assigned Agent captured the same way on every case. Nothing in that scenario changes here. This page picks up right where its Outcomes left off.
Background
The two Automations workflows closed the gap Monica's team found after the Service Cases register went live: a case no longer sat silently until someone happened to notice it. An agent was emailed the moment a case landed in their queue, and anything left unresolved past its SLA window escalated itself to the right supervisor, without anyone having to watch for it.
What the workflows could not do was answer a standing question rather than a one off event. Escalation emails told Monica's team about one case at a time, as it crossed its threshold. Nobody could yet answer, on demand and without digging, how many cases were open right now, how they broke down across service lines, or whether the escalation workflow was firing often or rarely in a given week.
"The escalation emails solved the cases that were already slipping through. What they do not give me is the view I actually need walking into a Monday leadership meeting: how many cases are open right now, which service line is carrying the load, and whether that number is getting better or worse. Right now the honest answer is that I would have to ask three different supervisors and wait for them to check."
Monica, Contact Center Director
The case data itself was never the problem. It had been sitting in Service Cases, complete and current, since the CRM scenario first stood it up. The problem was that nobody had a reportable view of it that did not involve asking someone to go look.
The New Ask
Monica brought the requirement back to her UNICONNECT AI implementation team in concrete terms, split across two different people with two different working patterns.
"I'm on the floor all day, moving between calls and coaching agents. I don't have time to run a report. I need something I can glance at on my second monitor that tells me, right now, how many cases are open and whether one service line is piling up faster than the others."
Priya, Contact Center Supervisor
"I'm the opposite. I don't need it live, I need it portable. Once a week I want a document I can pull up in a leadership meeting and forward afterward, without anyone needing a login to see it."
Monica, Contact Center Director
Those two working patterns, a supervisor who wants something always on and glanceable, and a director who wants something she can export and hand off, are what shaped the two things Monica's team built: a dashboard for Priya, and a report for Monica herself.
A View the Supervisor Can Glance At
For Priya, the requirement was a page she could leave open on a second monitor without thinking about it again: a single number for how many cases are currently open, a breakdown of where those cases sit by service line and status, and a sense of which specific reasons are driving the volume. Nothing in that requirement called for a file to download or a report to run on a schedule. It needed to update itself continuously, against whatever the floor's current caseload actually was, and stay legible at a glance between calls.
That requirement is what a dashboard is for: a live page, not a static document, built once and then simply left open.
A View the Director Can Carry Into a Meeting
For Monica, the requirement pointed the opposite direction. A live page is exactly the wrong fit for someone who does not log in daily and wants something to forward by email before a meeting she may not even be dialed into live. What she needed instead was the same underlying Service Cases data, grouped the same way, but produced as a document: something she could generate on demand, attach to an agenda, and hand to someone outside the contact center entirely without granting them system access.
That requirement is what a report is for: the same data as the dashboard, but built to be exported, shared, and read later, rather than watched live.
Priya and Monica were never asking for two different data sets. Both requirements trace back to the same Service Cases fields the CRM and Automations scenarios already established, Case Type, Case Reason, Case Status, Assigned Agent. The distinction Monica's team designed around was entirely about how each person needed to consume that data, live and glanceable versus exportable and portable, not what the data itself needed to contain.
Controlling Who Can See and Build What
A dashboard left open on a supervisor's monitor and a report forwarded outside the contact center both raise the same question the CRM scenario had already answered for the case register itself: who is allowed to see this, and separately, who is allowed to build or change it. Monica's team did not invent a new access model for either one. The same Contact Center Supervisor role already trusted to edit any Service Case was the role given permission to build and modify dashboards and reports. Service Agents were left able to view whatever was explicitly shared with them, but not to create or edit a dashboard or report themselves.
Sharing the finished dashboard and report was handled per item rather than by role: Priya was added directly so the dashboard stayed visible to her specifically, and the report's audience was expanded as needed each time it was forwarded, without touching who could edit the underlying workflows or the case register.
Outcomes
Measured against the quieter gap the Automations workflows had left behind, standing visibility closed it within the same week the dashboard and report went live.
| Measure | Before | After |
|---|---|---|
| Time for a supervisor to see current open case count | Ask a colleague, wait | Glance at a screen |
| Preparation time for the weekly leadership meeting | Compiled by hand | One export, minutes |
| People who could answer "how many cases are open" | Whichever supervisor you could reach | Anyone with the dashboard open |
| Systems holding the reportable view of Service Cases | None, data existed but no view did | 1 dashboard, 1 report |
For AUS Bank, the dashboard and report did not change what Service Cases tracked or how a case moved through escalation. They closed the last gap in the chain the CRM and Automations scenarios had already built: the data was correct and the workflows were watching it, but until now, nobody had a reportable view of either one without asking someone else to go look.
Where Each Part Is Documented
Every stage of this scenario corresponds to one or more of the configuration guides already written for Reporting & Dashboard. This page serves as the map between the narrative and the reference material. The pages below are where each capability is explained in complete, step by step detail, including How to Configure the Use Case in Uniconnect AI, which rebuilds both the dashboard and the report from this scenario from scratch.
| Guide | Used in |
|---|---|
| Reporting & Dashboard Overview | Background |
| Reporting & Dashboard: Getting Started | Background |
| Built-in Dashboards | A View the Supervisor Can Glance At |
| Creating a Dashboard | A View the Supervisor Can Glance At |
| Widget Types | A View the Supervisor Can Glance At |
| Filters | A View the Supervisor Can Glance At |
| Built-in Reports | A View the Director Can Carry Into a Meeting |
| Creating a Report | A View the Director Can Carry Into a Meeting |
| Exporting & Sharing Reports | A View the Director Can Carry Into a Meeting |
| Sharing, Duplicating & Publishing Dashboards | Controlling Who Can See and Build What |
| Reporting & Dashboard Permissions | Controlling Who Can See and Build What |
| How to Configure the Use Case in Uniconnect AI | Both the Dashboard and the Report |