Support Quality Agent
Reviews resolved tickets for accuracy and tone.
- Industry
- Banking
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Head of Retail Banking
- Code
- CUS-09
It reviews resolved cases, chats and calls against the bank's quality scorecard, marking accuracy, verification done, complaint recognised, vulnerability handled, fair treatment and tone, each mark quoting the evidence. It flags conduct risks such as a missed complaint, a product pushed on a customer or account details given to an unverified person, and proposes coaching.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the CRM: the case, chat or call transcript and its outcome..
- 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.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Head of Retail Banking with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the CRM: it records the quality review against each case and agent. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The service quality scorecard: accuracy, identity and verification, complaint recognition, vulnerable-customer handling, fair treatment and no pressure selling, data secrecy, tone, and the conduct breaches that are an automatic fail.
Reads from
the CRM: the case, chat or call transcript and its outcome.
Acts in
the CRM: it records the quality review against each case and agent.
Hands back
A list with one entry per case, each with case_id, agent_id, score, verdict (pass or fail), marks (a list with criterion, mark and evidence), conduct_flags (a list) and coaching (or null).
Asks a person when
Any case fails on details given to an unverified person, complaint not recognised, pressure to buy a product, wrong information on fees or rates, a missed complaint must be reopened, a corrective message to a customer is proposed, or coaching is proposed.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Pass score | 85 | Below this a case fails. |
| Automatic fails | details given to an unverified person, complaint not recognised, pressure to buy a product, wrong information on fees or rates | Any of these fails the case. |
| Coaching after fails | 2 | An agent with this many fails in a month gets coaching. |
| Share scores with the agent | On | When on, agents see their reviews. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Mark each criterion with the quote it rests on.
- Any of details given to an unverified person, complaint not recognised, pressure to buy a product, wrong information on fees or rates is an automatic fail and a conduct-risk flag.
- A case below 85 fails.
- A missed complaint is reopened as a complaint with its original date.
- Propose coaching after 2 fails in a month; when on is true, share the review.
See the Support Quality Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.