Messaging Use Case Scenario
Messaging
How AUS Bank extended its Service Cases register so that customers hear about their case on the channel they prefer.
Info: This scenario extends the AUS Bank story told in CRM Use Case Scenario. Nothing in that scenario changes here.
Background
AUS Bank runs a centralized contact center of twenty five agents for retail banking customers. After a regulatory review, the bank moved every card dispute, fraud alert, loan servicing request and account access issue into one Service Cases register in UNICONNECT AI. Each case records a Case Type, a Case Reason and an Assigned Agent, and supervisors can now report on resolution times from a single place.
The register solved the bank's internal problem. Within a few weeks, a second problem became visible on the telephone lines.
The Gap After Logging a Case
An agent would log a card dispute while the customer was on the line, and the call would end with a spoken promise that someone would follow up. The customer then had nothing in writing. Many rang back the next day to ask whether the case existed, who owned it and when to expect news. Supervisors counted these repeat calls and found that a large share of them asked for nothing more than confirmation.
Monica, Contact Center Director
The requirement was simple. As soon as a case is logged, the customer should receive a written confirmation containing the case reference, the type of case and the name of the agent who owns it. Later updates should follow on the same channel, and every message should be visible to the next agent who opens the case.
Choosing the Channels
Monica's team looked at how customers actually reach the bank and settled on three channels, each with a distinct job.
| Channel | Used for | Provider |
|---|---|---|
| The full confirmation with the case details, and later statements and documents. | Mailgun | |
| SMS | A short notice with the case reference, for customers who are away from a computer. | Dialog E–SMS |
| Conversational updates for customers who prefer to reply in a chat. | WhatsApp Meta API |
The platform administrator connected the three providers once. Carlos, Card Operations Lead, asked for one rule at the start: the card operations team would use the same sender names on every message, so customers learned to recognize them.
Writing One Message Per Channel
Rather than letting each agent write their own wording, Monica's team wrote a Case Received template for each channel and tied each one to the Service Cases module. Each template pulls values straight from the case, so the customer's name, the case reference, the Case Type and the Assigned Agent appear without anyone typing them.
- Email. A designed message with the bank's name, a table of the case details and a line saying what happens next.
- SMS. A single short text with the reference and the case type.
- WhatsApp. An approved template with the same details and a Quick Reply button for the customer to confirm they received it.
Compliance reviewed the wording once. After that, no one could change it without the permission to manage templates.
Sending From the Case
With the templates in place, the agent's routine changed in one small way. After saving the case record, the agent picks the customer's preferred channel and sends the Case Received message from the same screen. Because the record already holds the email address and the mobile number, no detail is typed again. The agent reads the preview, confirms that every value has filled in, and sends.
Keeping the Replies Together
Customers began to reply, mostly with a short thanks and sometimes with a missing detail, such as a transaction date. Those replies arrive in Conversations under the same customer, labeled Service Cases and the channel. The next agent who opens the case, or the supervisor reviewing the queue, sees the whole exchange without asking the customer to repeat it.
Controlling Who Can Send
The two roles from the original rollout carried over, with one addition for messaging.
| Role | Messaging access |
|---|---|
| Contact Center Supervisor | Can send messages, view sent messages for every group, and manage email and message templates. Assigned only to Monica and the three service line leads. |
| Service Agent | Can send messages and view the messages they sent. Cannot change a template. |
Outcomes
After two months, the contact center compared the new process with the old one.
| Measure | Before | After |
|---|---|---|
| Customers who received written confirmation of a new case | None | Every case |
| Repeat calls asking whether a case was logged | High | Rare |
| Time to confirm a case to the customer | Next day, by phone | Within a minute, in writing |
| Places an agent looks for what the customer was told | Notes, email and memory | One conversation |
For AUS Bank, messaging turned the Service Cases register from an internal record into a conversation with the customer, using the same data the register already held.
Where Each Part Is Documented
Every stage of this scenario matches a guide in the Messaging set. The configuration steps are in Configuring the Messaging Use Case.
| Guide | Part of the scenario |
|---|---|
| Overview | Background |
| Channel Configuration | Choosing the Channels |
| Message Templates | Writing One Message Per Channel |
| Sending Messages | Sending From the Case |
| Conversations | Keeping the Replies Together |
| Permissions | Controlling Who Can Send |