Use Case Scenario
This scenario continues the AUS Bank story told in CRM Use Case Scenario and extended in Campaign Use Case Scenario. Nothing in those scenarios changes here. This page picks up from outbound calling and describes what happened on the inbound side.
Background
Daniel's collections team now phones overdue customers first, and it works. The side effect is that customers phone back. Calls to the Loan Servicing number land on a shared phone system, and whoever happens to be free picks up. The agent does not know who is calling, what the account looks like, or that the same customer was called yesterday and promised to pay on Friday.
"When a customer calls back about a promise to pay, we ask them to repeat everything. They are already uncomfortable, and now they feel like nobody is keeping track. I also cannot tell from the phone system how many callers hung up before anyone answered."
Monica, Loan Servicing Supervisor
Marcus Webb is one of Daniel's collections agents. Before the change he took call backs on a desk phone, wrote a note on paper and typed it into the register at the end of the day, when he remembered.
What Monica and Daniel Asked For
- One phone system and one CRM. Calls handled through the existing phone system should appear in UNICONNECT AI without anyone keying them in.
- Agents who are ready. An agent should be able to choose when they take calls, and nobody should receive calls while on a break.
- The right team for the right call. Loan Servicing callers should reach the Loan Servicing team, with Collections able to take overflow.
- The customer on screen. When a call arrives, the agent should see who is calling.
- A record of every call. Each call should be stored with its recording, its path through the queues and how long the caller waited.
- An outcome for every conversation. At the end of each call the agent picks the result from a short list and sets a follow up when one is promised.
- Help for new agents. Supervisors should be able to listen in, coach quietly and, rarely, take a call over.
- Visibility without chasing. Monica wants to see waiting and abandoned calls during the day and a summary afterward.
- Clear limits. Agents place and take calls. Only supervisors hear recordings and step into calls.
How the Team Met Those Requirements
Working with the UNICONNECT AI implementation team, the requirements were met by connecting the bank's phone system to the platform and then building on top of it. Five decisions shaped the result.
The Connection
The bank's 3CX phone system was connected through the 3CX plugin, and the agents' extensions were synced so each person became a platform user with their own extension. Calls on 3CX now create call records automatically.
The Agents and Their Statuses
Agents begin a shift when they are ready and choose a status. Available keeps them logged into the queue and allows calls. Break statuses take them out of the queue, so nobody receives calls while away.
The Queues
A Loan Servicing queue takes calls to the main number, and a Collections ring group lets the whole collections team pick up overflow. Callers outside business hours are answered by an AI Agent, which can hand them to a person when needed.
- Call arrives: Customer rings the Loan Servicing number
- Route: Queue, ring group or AI Agent
- Agent: Call is answered and the customer appears on screen
- After the call: Outcome recorded and follow up set
The Record and the Outcome
Each call is stored with its recording and call path. At the end of the call Marcus chooses a disposition and, when the customer promises to pay, sets a follow up date and assigns it to himself.
The Access Limits
Agents received the built in User role, which lets them place calls. Monica and Daniel received supervisor roles that add the call log, recordings and the monitoring controls.
Recordings and live call controls act on real customer calls. They were given to supervisors only, and agents were told monitoring is part of the job.
Seeing What Happened
Monica keeps the Inbound Live & Queue Monitor on a wallboard. It shows callers waiting, calls in progress and agents available. The next morning she opens Abandoned Calls and Call Distribution to see how the previous day went, and Activity Summary to see how agents spent their shifts.
"I used to find out about abandoned calls from angry emails. Now I see them building up and I can send someone from Collections before the queue gets long."
Monica, Loan Servicing Supervisor
Outcomes
Measured against the problem Monica first raised, the biggest change was that a returning customer no longer had to start from the beginning.
| Measure | Before | After |
|---|---|---|
| Who answers a call back | Whoever is free, with no context | The right team, customer on screen |
| How a call reaches the register | Typed in later, if at all | Recorded automatically |
| Calls outside business hours | Unanswered | Answered by an AI Agent |
| Who can see abandoned calls | Nobody until a complaint | Monica, during the day |
For AUS Bank, Campaign reached customers first and Telephony made sure that when they called back, someone was ready for them and the conversation was kept.
Where Each Part Is Documented
Each requirement above corresponds to a Telephony documentation page. Configuring the Telephony Use Case shows how the team built it.
| Guide | Covers |
|---|---|
| Campaign Use Case Scenario | The story this extends |
| Configuring the Telephony Use Case | How it was built |
| 3CX Plugin Configuration | One phone system and one CRM |
| Status Management with 3CX | Agents who are ready |
| Group Management with 3CX Queues and Ring Groups | The right team for the right call |
| System Workflows | The customer on screen |
| Call Records | A record of every call |
| Call Dispositions | An outcome for every conversation |
| Live Call Controls | Help for new agents |
| Telephony Reports and Dashboards | Seeing what happened |
| Telephony Permissions | Who does what |