- Industry
- Retail
- Department
- Customer
- Team
- Support Operations
- Kind
- Decision-maker
- Approver
- Customer Service Manager
- Code
- CUS-02
It reads each incoming case from email, chat, phone notes, store referrals and marketplace messages, categorises it (delivery, collection, return, product, loyalty, payment, safety), sets its priority and routes it to the right queue. It puts product safety reports, injuries and card fraud at the front and groups cases about the same failed delivery route or store.
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 order management system's customer service case: the open cases, the order and delivery status for each order named, and the open incidents..
- 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 order management system's customer service case: it updates each case with its category, priority, queue and incident link. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The triage guide: the case categories and queues, priority definitions, the service levels by channel and loyalty tier, the safety and fraud indicators, and the known-incident list for delivery routes and the site.
Reads from
the order management system's customer service case: the open cases, the order and delivery status for each order named, and the open incidents.
Acts in
the order management system's customer service case: it updates each case with its category, priority, queue and incident link.
Hands back
A list with one entry per case, each with case_id, category, priority (1 to 4), queue, due_by (YYYY-MM-DDTHH:MM), incident_id (or null), category_confidence and reason.
Asks a person when
It opens a new incident cluster, or a safety case cannot be routed because the product cannot be identified.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Words that mark a safety case | injury, burn, choking, fire, smoke, allergic, broke and cut, sharp | Comma-separated. A case with any of these goes to product safety at the highest priority. |
| Raise priority for top-tier members | On | When on, cases from the top loyalty tier go up one priority level. |
| Marketplace reply deadline (hours) | 24 | Marketplace messages must be answered within this, or the seller rating suffers. |
| Cases that make an incident cluster | 10 | This many cases about the same route, store or SKU in an hour are linked to one incident. |
| Route to a person below this confidence | 0.7 | A case it cannot categorise with this confidence goes to the general queue for a person. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A case mentioning any of injury, burn, choking, fire, smoke, allergic, broke and cut, sharp, or a possible injury, is priority 1 and goes to product safety, whatever else it is about.
- Suspected card fraud or account takeover is priority 1 and goes to the payments and fraud queue.
- Marketplace messages are due within 24 hours and are prioritised against that deadline.
- When on is true, top-tier loyalty members' cases go up one priority level.
- Link 10 or more cases about the same delivery route, store or SKU in an hour to one incident.
- A case categorised below 0.7 confidence goes to the general queue for a person.
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.