Workforce Use Case Scenario
Use Cases
The AUS Bank case register tells everyone who owns a case. Workforce Management tells them whether that person is at their desk.
Info: This scenario continues the story in CRM Use Case Scenario. AUS Bank already has its Service Cases register, and every case has an Assigned Agent. Read that page first if the names Monica, Hannah and the Service Cases register are new.
The Situation
Some months after the Service Cases register went live, Monica, the Contact Center Director, noticed a gap that the register could not close by itself. Every case has an owner and the resolution time report is reliable, but a case waits when its owner is on a long break, or has signed in without starting a shift.
The gap is clearest in Loan Servicing, where a Collections team of eight agents works overdue accounts. The floor is grouped like the register, in Loan Servicing, Card Disputes and Fraud Alerts. Hannah Cole, one of the three service line leads, supervises that floor and holds the Contact Center Supervisor role. Marcus Webb, extension 1018, is one of her agents. Calls arrive in the Collections Queue, and everyone works in shifts.
What Was Going Wrong
- Uneven breaks. Several agents took lunch at the same time, and the queue backed up.
- Slow help. Agents who needed a decision had to leave their desks or message Hannah.
- Forgotten shifts. Agents signed in but did not start a shift, so calls did not reach them.
- No clear record. When a customer complained that a loan servicing case had sat untouched, the register showed who owned it, but nobody could say whether that agent was on a break, and for how long.
What the Team Needs
| Requirement | Meaning |
|---|---|
| Fair breaks | Long statuses are approved and have a time limit. |
| Quick help | Agents can ask for help without leaving the call. |
| Reliable shifts | Hannah can start a shift for an agent who is ready to work. |
| One view | A screen that shows every agent's shift, status and team. |
| A record | Reports that show how each shift was spent, so that case delays can be explained. |
How Workforce Management Solves It
| Requirement | Feature | Documentation |
|---|---|---|
| Fair breaks | Allowed time and Request Approval on statuses, and Break Requests | Custom Status Configuration, Break Requests |
| Quick help | Raise Hand | Raise Hand |
| Reliable shifts | Force Shift Start and Force Status Change | Force Shift Start, Force Status Change |
| One view | Workforce Monitor and its filters | Monitoring Agents, Workforce Filters |
| A record | Activity Logs and the three reports | Activity Logs, Activity Summary Report |
How to set this up is in How to Configure the Workforce Use Case in UNICONNECT AI. The cases themselves stay in the register described in CRM Use Case Scenario.
A Day After the Change
- 8:00. Hannah opens the Workforce Monitor and filters by Loan Servicing. Seven of eight agents are on shift. She uses Start Shift on the eighth agent's row, who signed in but could not start it.
- 11:30. Marcus asks for Lunch. Lunch has Request Approval on, and the queue is quiet, so Hannah approves it from the Requests filter.
- 12:20. Marcus has been in Lunch for 50 minutes against a 45 minute limit. He appears under Breeches, and Hannah calls his extension. He has two loan servicing cases open in the register, so she asks him to confirm that they are covered while he is away.
- 14:00. Another agent raises a hand over a payment plan. Hannah answers from the Requests filter and dismisses it.
- 17:30. Hannah runs the Activity Summary Report for the day and keeps a copy. If a customer questions a delay on a case, she can show where the assigned agent was.
The Outcome
- Even breaks. Approval spreads lunches across the day.
- Faster help. Raised hands are answered within minutes.
- Full coverage. No agent stays signed in without a shift.
- Evidence. The reports settle questions about who was where, which completes the picture that the case register began.