Support Quality Agent
Reviews resolved tickets for accuracy and tone.
- Industry
- Insure AI
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Customer Service Manager
- Code
- CUS-09
It reviews resolved service cases and claims-care contacts for accuracy, fairness and tone: whether the answer matched the wording, whether complaints were recognised, whether vulnerable customers were handled properly and whether the regulator's timelines were met. It scores each case and drafts coaching notes.
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 policy administration system: the resolved cases with their transcripts, outcomes and timestamps..
- 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 Customer Service Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the policy administration system: it records the quality scores on each case and reopens missed complaints. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The quality scorecard: accuracy against wording, complaint recognition, vulnerable customer handling, disclosure and verification steps, timelines and tone.
Reads from
the policy administration system: the resolved cases with their transcripts, outcomes and timestamps.
Acts in
the policy administration system: it records the quality scores on each case and reopens missed complaints.
Hands back
A list with one entry per case, each with case_id, handler, score, passed (true or false), faults (a list), customer_harm (true or false), coaching_note and reopen_as_complaint (true or false).
Asks a person when
A review finds a missed complaint, wrong cover advice or a data disclosure that may need reporting.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Pass score (out of 100) | 80 | Cases below this fail. |
| Faults that fail a case outright | missed complaint, wrong cover advice, data disclosed without verification, vulnerable customer not flagged | Comma-separated. |
| Fails before coaching | 2 | A handler with this many fails in the period gets a coaching plan. |
| Share scores with the handler | On | When on, the handler sees their scores and notes. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Score each case against the scorecard; any of missed complaint, wrong cover advice, data disclosed without verification, vulnerable customer not flagged fails it outright.
- A case below 80 fails.
- A missed complaint is reopened as a complaint so the regulator's timeline starts from the original date.
- Handlers with 2 or more fails get a coaching plan.
- When on is true, share scores and notes with the handler.
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.