CRM Use Case Scenario
1. Background
AUS Bank operates a centralized contact center of twenty five agents supporting retail banking customers across card disputes, fraud alerts, loan servicing, and account access issues. Each of these service lines grew up independently inside the bank over the years, and each still runs on its own tracking method: card disputes are logged in a spreadsheet maintained by the card operations team, fraud alerts are tracked through email threads, and loan servicing requests live in a ticketing tool the lending department purchased on its own. An agent fielding a call that touches more than one of these areas has no single place to see the full picture of what a customer has already reported.
The risk of that fragmentation became concrete during a routine regulatory review.
Monica, Contact Center Director
"The examiner asked us to show resolution times for every card dispute over the past quarter, and we could not produce a single, reliable report. The data existed, but it was split across three systems that never talked to each other, and reconciling them by hand took our compliance team the better part of a week. That is a regulatory exposure we cannot carry forward."
Following that review, AUS Bank's leadership set a requirement: every customer service case, regardless of which banking service line it belonged to, needed to be logged, assigned, and tracked in one system, with resolution times that could be reported on demand. The contact center selected UNICONNECT AI to build that capability.
2. Establishing a Case Register
Working with her UNICONNECT AI implementation team, Monica scoped out a single, dedicated register covering every service line the contact center handles, rather than building a separate tracker for each department the way the bank had done in the past. The register needed to hold a card dispute and a fraud alert side by side, under one consistent structure, so a resolution-time report could be produced across all of them without reconciling separate systems afterward.
The result was a new, purpose built space named Service Cases, standing alongside the contact center's existing customer and contact records.
3. Describing Each Case
With Service Cases established but empty, Monica's team defined exactly what a case record needed to capture, working from the requirement that a single report had to cover every service line consistently. Three pieces of information were identified as essential for every case:
- Case Type, a broad classification such as Card Dispute, Fraud Alert, Loan Servicing, or Account Access, selected from a fixed list.
- Case Reason, a narrower classification beneath it, such as Unauthorized Transaction or Billing Error under Card Dispute, and Suspected Identity Theft or Suspicious Login under Fraud Alert.
- Assigned Agent, the AUS Bank employee responsible for resolving that case, drawn from the same contact records used elsewhere in the business rather than typed in separately.
Using the same three fields across every service line, rather than letting each department define its own structure, was the deliberate point: it is what makes a single resolution-time report possible across card disputes, fraud alerts, loan servicing, and account access all at once.
4. Designing the Case Screens
A well defined field is only useful once the right person sees it at the right moment, and a contact center agent is often reading a case screen while a customer is actively describing their problem over the phone. Monica's team designed four distinct screens around that reality: a complete record for a single case, a sortable queue of every open case, a short intake form an agent completes while still on the call, and a condensed summary surfaced directly on the customer's own account so any agent who answers next sees prior cases immediately.
The complete case record groups Case Type and Case Reason together near the top, since a supervisor checks both in the same glance when reviewing the queue, and gives Assigned Agent its own clearly labeled section further down, next to a compact summary of that agent's own contact details. The case queue surfaces Case Type as a sortable column so supervisors can see where volume is concentrated across service lines at a glance. The intake form walks through the three fields in the order an agent naturally works through them while still on the call: type, then reason, then who it is assigned to.
5. Keeping Fields in Sync With Each Other
Within the first week of real use, a data quality risk became apparent: selecting Card Dispute as the Case Type still left every Case Reason in the system selectable, including combinations, such as Card Dispute paired with Suspicious Login, that describe no case an agent would actually log. Left unaddressed, this was exactly the kind of inconsistency that had made the old department-by-department tracking unreliable. Monica's team configured a rule so that selecting a Case Type immediately narrows Case Reason to only the values that genuinely belong beneath it, Unauthorized Transaction and Billing Error under Card Dispute, Suspected Identity Theft and Suspicious Login under Fraud Alert.
A second rule applies the same discipline to Assigned Agent: once a case is tagged to a specific service line, the Assigned Agent selection narrows itself to only the agents certified to handle that line, removing the possibility of a fraud alert being handed, by mistake, to an agent trained only in loan servicing.
"Agents were never expected to memorize which case reasons belong under which type, especially across four different service lines," Monica observes. "Now the form simply does not offer the incorrect combinations in the first place."
6. Bringing In Existing Data
Roughly six hundred open cases, split across the card operations spreadsheet, the fraud team's email threads, and the lending department's separate ticketing tool, needed to be brought into a single register before it could be considered the system of record. Rather than treating that backlog as unrecoverable, the contact center ran a bulk import from each source in turn, mapping their respective columns to Case Type, Case Reason, and Assigned Agent. The import surfaced close to eighty cases with no agent recorded at all, mostly from the fraud team's email based tracking, which supervisors corrected using filtered views before the register was considered complete. With the backlog cleared, a filtered export now goes to the compliance team every week in place of the quarter-end scramble that originally triggered the project.
7. Controlling Who Can Do What
A case register spanning fraud, disputes, and lending is only as trustworthy as the controls around who can change it, a point the regulatory review had made clear. Monica's team defined two distinct roles before extending access across the full contact center floor.
| Role | What that person can do |
|---|---|
Contact Center Supervisor | Full access to every case, including logging new ones, editing any field, and changing how the case screens themselves are arranged. Assigned only to Monica and the three service line leads. |
Service Agent | Can view every case and update the ones assigned to them, but cannot create, delete, or modify a case assigned to a different agent, and cannot change screens or add new fields. |
A disputed amount field, added at the request of the compliance team, received a narrower rule still: both roles can view it on screen, but only Contact Center Supervisor can edit it, since an incorrect figure directly affects the bank's regulatory reporting. That restriction applies to the single field alone, leaving what either role can do with Case Type, Case Reason, or Assigned Agent untouched.
8. Connecting an Outside System
Several months into the rollout, a new requirement arrived from the card operations team. A customer's account balance, recent transactions, and card status already lived inside AUS Bank's core banking platform, the system of record for every account the bank holds and one that was never going to be replaced or duplicated. Recreating that data by hand inside the case register was never a realistic option: it would have meant two systems tracking the same balances, with no guarantee either stayed accurate for long, and banking regulation requires that account data have exactly one authoritative source.
Carlos, Card Operations Lead
"Our core banking platform is not something we are permitted to duplicate elsewhere, it is the authoritative record for every account and transaction we hold. What agents actually need is to see a customer's recent transactions the moment they open a card dispute, without logging into a second system mid-call."
Instead of duplicating that data, Monica's team had UNICONNECT AI connect to the core banking platform directly, so account balance, recent transactions, and card status appear alongside a case the moment it is opened, without anyone at AUS Bank re-entering a single figure. The core banking platform remains the sole authoritative source for that data; it simply becomes visible from inside the case register as well. Should AUS Bank ever change core banking providers in the future, that one connection is what would need to be updated, not the case register itself.
9. Outcomes
Measured against the regulatory review that started the project, the impact was immediate and continued to compound as every service line came onto the register.
| Measure | Before | After |
|---|---|---|
| Cases with no record of assignment | ~80 at import | 0 ongoing |
| Time to produce a quarterly resolution-time report | ~1 week, manual | Same day, filtered export |
| Time for an agent to view account activity on a dispute | 2 systems, ~90 seconds | 1 screen, instant |
| Systems of record for open service cases | 3 separate systems | 1 register |
For AUS Bank, the case register closed a genuine regulatory exposure and gave supervisors a single, reportable view across every service line the contact center handles, with room to extend the same approach to additional service lines as the bank's needs evolve.
10. Where Each Part Is Documented
Every stage of this scenario corresponds to one or more of the configuration guides already written for the Service Cases module. 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.
| Guide | Relates to |
|---|---|
| CRM Module Overview | Background |
| CRM Getting Started | Background |
| Default CRM Modules | Background |
| Internal Modules | Establishing a Case Register |
| External Modules | Connecting an Outside System |
| Configuring a CRM Module | Establishing a Case Register |
| Configuring CRM Fields | Describing Each Case |
| Managing CRM Modules | Establishing a Case Register |
| Configuring CRM Layouts | Designing the Screens |
| Configuring CRM Dependencies | Keeping Fields in Sync |
| Records Management | Bringing In Existing Data |
| Configuring CRM Permissions | Controlling Access |