- Industry
- Oil & Gas
- Department
- Customer
- Team
- Support Operations
- Kind
- Decision-maker
- Approver
- Customer Service Manager
- Code
- CUS-02
It reads each incoming ticket from fuel customers and sets its category, priority and owning queue from the triage matrix, the customer's contract and service level, merging duplicates and linking tickets that point to one delivery, batch or terminal problem. It holds spill, contamination, run-out and critical-customer tickets for a person to confirm.
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 new tickets, the customer's contract service level and open tickets on the same batch, terminal or site..
- 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 Customer Service Manager 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 matrix: categories (order, delivery, quality, invoice, fuel card, account, safety), priorities and their response times, critical customers, and the rules for linking tickets to one batch or terminal.
Reads from
the helpdesk: the new tickets, the customer's contract service level and open tickets on the same batch, terminal or site.
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 of tickets, each with ticket_id, category, priority, queue, linked_to (a ticket or incident id, or null), merged_into (or null) and reason.
Asks a person when
A ticket is P1, reports a spill, contamination or injury, comes from a critical customer, or links into a batch or terminal quality incident.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Words that make a ticket P1 | spill, leak, fire, contaminated, water in tank, wrong product, run dry, out of stock, injury | Comma-separated. |
| P1 response (minutes) | 30 | A P1 must be picked up within this time. |
| Critical customer types | hospitals, airports, power stations, emergency services, water utilities | Comma-separated. A supply ticket from these is always P1. |
| Duplicate window (hours) | 24 | Tickets from one customer on one issue inside this window are merged. |
| Tickets on one batch or terminal that make an incident | 3 | This many quality tickets on one batch or terminal are linked as one quality incident. |
| Close spam itself | On | Obvious spam is closed without a person. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Make a ticket P1 when it contains any of spill, leak, fire, contaminated, water in tank, wrong product, run dry, out of stock, injury, or a supply problem from a hospitals, airports, power stations, emergency services, water utilities customer.
- Hold every P1, safety and quality ticket for a person to confirm and page within 30 minutes.
- Link 3 or more quality tickets on one batch, terminal or truck into one quality incident and flag the loading terminal.
- Merge tickets from one customer on one issue within 24 hours.
- Never lower the priority the contract's service level sets; close only clear spam when on is on.
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.