- Industry
- Oil & Gas
- Department
- Customer
- Team
- Support Operations
- Kind
- Decision-maker
- Approver
- Customer Service Manager
- Code
- CUS-07
It decides who should own a complex customer case by matching its type (quality, delivery, credit, contract or safety), severity, the account's annual volume and history to the escalation matrix and the on-call rota. It reassigns the ticket with a case brief and pages the on-call owner when supply to a customer is at risk or a safety or quality incident is involved.
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 case history, the account, the escalation matrix and owners' open cases..
- 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 reassigns the ticket to the chosen owner and tier with the case brief, and raises the page when one is needed. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The escalation matrix: owners by case type (product quality lab, terminal operations, credit control, key account manager, HSE), severity definitions, the on-call rota and owners' capacity.
Reads from
the helpdesk: the case history, the account, the escalation matrix and owners' open cases.
Acts in
the helpdesk: it reassigns the ticket to the chosen owner and tier with the case brief, and raises the page when one is needed.
Hands back
An object with owner, tier, page (true or false), case_brief and reason.
Asks a person when
The case involves safety, an environmental release, a contract dispute or an account above 5000000 USD, or the chosen owner differs from the one requested.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Tier 2 after (hours) | 24 | Unresolved at tier 1 for this long, the case moves up. |
| Reopens that escalate | 2 | A case reopened this often goes to the account owner. |
| High-value account (USD per year) | 5000000 | Accounts above this go to their key account manager. |
| Page on call for | spill, injury, contamination, stock-out at a critical customer | Comma-separated. |
| Most open cases per owner | 12 | Owners at this load are skipped. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Route by case type to the matrix owner: quality to the product quality lab, safety to HSE, supply to terminal operations, credit to credit control.
- Page the on-call owner for spill, injury, contamination, stock-out at a critical customer.
- Send accounts above 5000000 USD a year to their key account manager.
- Move a case up after 24 hours at tier 1 or 2 reopens.
- Skip owners with 12 open cases and write a brief so the customer never repeats themselves.
See the Escalation Routing Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.