- Industry
- IT Company
- Department
- Customer
- Team
- Support Operations
- Kind
- Decision-maker
- Approver
- Head of Service Delivery
- Code
- CUS-02
It reads each incoming ticket and sets its category, P1 to P4 priority and resolver group from the triage matrix, the client's contracted SLA tier and the affected service, merging duplicates and linking tickets that point to one major incident. It sets those fields in the service management system and starts the SLA clock on the contracted target.
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 ticketing and service management system: the account's contract SLA tier, open tickets and any active major incidents for the services named..
- 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 Service Delivery with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the ticketing and service management system: it sets category, priority, resolver group and SLA target on each ticket, merging and linking as decided. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The triage matrix: categories, the P1 to P4 priority definitions by impact and urgency, resolver groups by service, contracted SLA targets per tier and the major-incident criteria.
Reads from
the ticketing and service management system: the account's contract SLA tier, open tickets and any active major incidents for the services named.
Acts in
the ticketing and service management system: it sets category, priority, resolver group and SLA target on each ticket, merging and linking as decided.
Hands back
A list with one entry per ticket, each with ticket_id, category, priority (P1 to P4), resolver_group, sla_target_minutes, merged_into (or null), major_incident_id (or null) and reason.
Asks a person when
A ticket is P1, a major incident is declared, or a client-set priority is lowered.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Signals that suggest P1 | production down, cannot log in, data loss, security breach, ransomware, all users affected | Comma-separated phrases that make a ticket a P1 candidate when the environment is production. |
| P1 response target (minutes) | 15 | The default P1 response target when the contract states none. |
| Contract tiers with priority handling | Enterprise, Managed Premium | Comma-separated SLA tiers whose tickets are raised one priority when impact is equal. |
| Merge duplicates within (hours) | 12 | Tickets from the same account about the same issue within this window are merged. |
| Tickets that make a major incident | 5 | This many accounts reporting the same service within an hour links them to one major incident. |
| May close spam and auto-replies | On | When on, out-of-office replies and spam are closed without a person. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Set priority from impact and urgency on the matrix; a production ticket matching production down, cannot log in, data loss, security breach, ransomware, all users affected is P1 and its response target is the contract's P1 target or 15 minutes.
- Raise priority by one level for tiers in Enterprise, Managed Premium when impact is otherwise equal.
- Merge tickets from the same account on the same issue within 12 hours.
- When 5 or more accounts report the same service within an hour, link them to one major incident and page the Head of Service Delivery.
- Never lower a priority the client set on a P1 without the Head of Service Delivery.
- Close spam and auto-replies only when on is true.
See the Ticket 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.