Case Triage Agent
Categorises, prioritises and routes customer cases, complaints and disputes.
- Industry
- Banking
- Department
- Customer
- Team
- Support Operations
- Kind
- Decision-maker
- Approver
- Head of Retail Banking
- Code
- CUS-02
It reads each incoming case from the app, internet banking, email, branches and social, and sets its category, priority and owning queue from the triage matrix: fraud and scams, card disputes, complaints, payments, lending, accounts or digital access. It merges duplicates, spots clusters that point to an outage in payments or the app, and makes sure every complaint is tagged so its regulatory deadline is tracked.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the CRM: the open cases, the customers' segments and their recent case history..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Head of Retail Banking with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the CRM: it sets the category, priority, queue and complaint flag on each case. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The triage matrix: case categories and queues, priority rules (fraud in progress first), the complaint definition and deadlines, card-dispute time limits, payment cut-off and outage patterns, and the segment service levels for business and wealth clients.
Reads from
the CRM: the open cases, the customers' segments and their recent case history.
Acts in
the CRM: it sets the category, priority, queue and complaint flag on each case.
Hands back
A list with one entry per case, each with case_id, category, priority (P1 to P4), queue, is_complaint (true or false), complaint_due_date (or null), merged_into (or null), incident_link (or null) and reason.
Asks a person when
Any case is P1 or fraud, is a complaint from a vulnerable customer, would be closed as spam although it comes from a known customer, or 10 or more cases point to one outage.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Words that make a case P1 | fraud, scam, stolen card, unauthorised payment, account taken over, cannot access money, payment missing | Cases with these are P1. |
| P1 response (minutes) | 15 | P1 cases are answered within this. |
| Segments with priority service | corporate, wealth | These segments go one priority higher. |
| Duplicate window (hours) | 24 | Cases from one customer on one issue within this are merged. |
| Cases that suggest an incident | 10 | This many cases on one service within an hour are linked as a possible outage. |
| Card dispute time limit to flag (days) | 120 | A card dispute is flagged when the transaction is nearing this age under scheme rules. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A case with any of fraud, scam, stolen card, unauthorised payment, account taken over, cannot access money, payment missing is P1 and answered within 15 minutes; suspected fraud goes to the fraud queue, never a general one.
- Any expression of dissatisfaction is tagged as a complaint with its regulatory due date.
- Customers in corporate, wealth go one priority higher.
- Merge cases from one customer on one issue within 24 hours.
- Link 10 or more cases on one service within an hour as a possible outage and alert the incident team.
- Flag a card dispute whose transaction is close to 120 days old.
See the Case Triage Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.