- Industry
- Retail
- Department
- Customer
- Team
- Support Operations
- Kind
- Decision-maker
- Approver
- Customer Service Manager
- Code
- CUS-07
It decides who should take a case that the front line cannot resolve: the delivery partner desk, a store manager, product safety, loss prevention, the marketplace seller team or the complaints team. It hands over with a complete summary so the shopper never has to repeat themselves, and sets the deadline the next owner must meet.
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 case history, contact count and linked orders, and the escalation contacts for the store or partner..
- 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 reassigns the case to the new owner with the handover summary and deadline. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The escalation matrix: who owns which kind of case, the escalation deadlines, the complaint handling rules and timelines, the store manager and regional contacts, and the delivery partner escalation desks.
Reads from
the order management system's customer service case: the case history, contact count and linked orders, and the escalation contacts for the store or partner.
Acts in
the order management system's customer service case: it reassigns the case to the new owner with the handover summary and deadline.
Hands back
An object with route_to (team or person), due_by (YYYY-MM-DDTHH:MM), priority (1 to 4), handover_summary (one paragraph), shopper_message (what to tell the shopper, or null when it must not be told) and reason.
Asks a person when
The case involves an injury, suspected staff misconduct, a regulator or media contact, or a threat of legal action.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Acknowledge formal complaints within (hours) | 24 | Formal complaints are acknowledged within this. |
| Store manager response deadline (hours) | 48 | A case escalated to a store manager must be answered within this. |
| Contacts that force escalation | 3 | A shopper contacting this many times about the same issue is escalated. |
| Send suspected fraud to loss prevention | On | When on, refund abuse, collection fraud and staff misconduct go to loss prevention. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Route by the escalation matrix: delivery failures to the delivery partner desk, in-store experiences to the store manager, injuries and hazards to product safety, marketplace items to the seller team.
- When on is true, suspected refund abuse, collection fraud or staff misconduct goes to loss prevention and is never shared with the shopper.
- Acknowledge formal complaints within 24 hours and give store managers 48 hours to respond.
- Escalate a shopper who has contacted 3 or more times about the same issue.
- Hand over with a summary that covers the issue, what was tried, what the shopper wants and the deadline.
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.