Support Quality Agent
Reviews resolved tickets for accuracy and tone.
- Industry
- IT Company
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Service Desk Lead
- Code
- CUS-09
It reviews resolved tickets against the service desk quality scorecard, marking technical accuracy, SLA adherence, root cause captured, tone and whether the client had to repeat themselves, each mark quoting the reply it rests on. It records the scores and coaching notes and flags any ticket where a credential, client data or another client's information was exposed.
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 ticketing and service management system: the resolved tickets, their SLA timers, closure codes and replies..
- 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 Service Desk Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the ticketing and service management system: it records the quality scores and coaching notes against each ticket and resolver. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The service desk quality scorecard: criteria and weights, auto-fail conditions, SLA rules, closure-code standards and the coaching guide.
Reads from
the ticketing and service management system: the resolved tickets, their SLA timers, closure codes and replies.
Acts in
the ticketing and service management system: it records the quality scores and coaching notes against each ticket and resolver.
Hands back
A list with one entry per ticket, each with ticket_id, score, passed (true or false), auto_fail (or null), marks (a list of criterion, score and quote) and coaching_note.
Asks a person when
A ticket shows credential or client-data exposure, or a resolver is flagged for coaching.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Pass score | 80 | A ticket scoring below this fails review. |
| Auto-fail on | wrong technical answer, credential exposed, another client's data shared, SLA breached without notice, closed without root cause on P1/P2 | Comma-separated conditions that fail a ticket whatever its score. |
| Coaching after fails in 30 days | 2 | A resolver failing this many reviews in 30 days gets a coaching session. |
| Share scores with the resolver | On | When on, each resolver sees their scores and notes. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Score every criterion on the scorecard and quote the reply each mark rests on.
- A ticket matching any of wrong technical answer, credential exposed, another client's data shared, SLA breached without notice, closed without root cause on P1/P2 fails whatever its score.
- A ticket below 80 fails.
- Flag a resolver for coaching after 2 fails in 30 days.
- A ticket where a credential or client data was exposed goes to the Service Desk Lead and security as a possible data incident.
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.