Service Desk Triage Agent
Categorizes, prioritizes and routes tickets.
- Industry
- Procure AI
- Department
- Customer
- Team
- Support Operations
- Kind
- Decision-maker
- Approver
- Client Engagement Lead
- Code
- CUS-02
It reads each incoming ticket from client procurement teams, requisitioners and suppliers and sets its category (requisition, PO, receipt, invoice match, supplier onboarding, catalogue, platform access or payment query), priority and owning queue from the triage matrix and the client's contracted service level. It merges duplicates, links tickets that point to one platform or integration incident, and holds security, sanctions, payment-fraud and P1 tickets for a person.
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 helpdesk: the open tickets and incidents for the clients named, each client's contracted service level and next payment-run date..
- 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 Client Engagement Lead with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the helpdesk: it updates each ticket's category, priority, queue and links, and merges duplicates into the open ticket. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The triage policy: ticket categories, the impact and urgency matrix, queue ownership (client service, AP operations, supplier enablement, platform support), service levels per client contract, month-end and payment-run windows and the open known incidents.
Reads from
the helpdesk: the open tickets and incidents for the clients named, each client's contracted service level and next payment-run date.
Acts in
the helpdesk: it updates each ticket's category, priority, queue and links, and merges duplicates into the open ticket.
Hands back
A list with one entry per ticket, each with ticket_id, category, priority (P1 to P4), queue, fraud_check (true or false), duplicate_of (a ticket id or null), incident_link (an incident id or null), first_response_due (an ISO time) and reason.
Asks a person when
Any ticket is set to P1, is a security, data-exposure, sanctions or bank-detail change report, would be closed as spam although it comes from a known client or supplier, or 5 or more tickets point to one incident.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Words that make a ticket a P1 candidate | cannot raise POs, payment run failed, invoices not loading, bank details changed, login down, data exposed | Comma-separated. A ticket that names one of these is assessed for P1. |
| P1 first response target (minutes) | 30 | The first response time a P1 commits the queue to. |
| Raise invoice and payment tickets this close to a payment run (hours) | 48 | Invoice-match and payment tickets within this many hours of the client's payment run go up one level. |
| Merge duplicates within (hours) | 24 | A ticket on the same document number from the same client within this window is merged. |
| Tickets in an hour that make an incident | 5 | This many tickets on the same symptom within an hour are linked to one platform incident and a person is told. |
| Close spam and auto-replies itself | On | When on, tickets it classifies as spam or out-of-office replies are closed without a person. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Give every ticket exactly one category and one queue from the triage policy; a ticket that fits none goes to client service with the reason.
- Set priority from the impact and urgency matrix; a ticket naming any of cannot raise POs, payment run failed, invoices not loading, bank details changed, login down, data exposed is assessed for P1, with a first response due within 30 minutes.
- Raise invoice-match and payment tickets one level when they fall within 48 hours of the client's payment run, never above P1.
- A supplier asking to change bank details or chasing an unusual payment goes to AP operations with a fraud check flag, never to self-service.
- Merge a ticket into an open one on the same document from the same client within 24 hours.
- When 5 or more tickets report the same symptom within an hour, link them to one incident and tell the Client Engagement Lead.
- Close spam and auto-replies only when on is true, and never close a ticket from a known client user or registered supplier as spam.
See the Service Desk 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.