- Industry
- Insure AI
- Department
- Customer
- Team
- Support Operations
- Kind
- Decision-maker
- Approver
- Claims Manager
- Code
- CUS-07
It hands complex servicing and claims-care cases to the right person: senior claims handlers for large or disputed losses, the complaints team, the vulnerable customer team, the broker account manager or the special investigations unit. It weighs loss size, complaint age against the regulator's deadline and reopen history.
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 claims management system: the claim's reserve, handler, authority level, reopen history and any complaint on it..
- 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 Claims Manager with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the claims management system: it reassigns the case to the chosen owner with the handover note and deadline. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The escalation matrix: teams and owners by line, claim authority limits, complaint deadlines, vulnerable customer and bereavement handling, and the SIU referral criteria.
Reads from
the claims management system: the claim's reserve, handler, authority level, reopen history and any complaint on it.
Acts in
the claims management system: it reassigns the case to the chosen owner with the handover note and deadline.
Hands back
An object with case_id, route_to (team and owner), reason, deadline (YYYY-MM-DD or null), flags_kept (a list) and handover_note.
Asks a person when
The case goes to the special investigations unit, involves legal action, media or the regulator, or a complaint is close to its final response deadline.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Loss that goes to a senior handler (USD) | 50000 | Claims at or above this go to a senior claims handler. |
| Escalate a complaint after (days) | 28 | Complaints open this long go to the complaints manager ahead of the regulator's final response deadline. |
| Reopens that trigger escalation | 2 | A case reopened this often goes to a team lead. |
| Flags that escalate at once | legal_action, media, regulator_contact, bereavement | Comma-separated. |
| Most open escalations per owner | 25 | An owner at this load is skipped for the next in line. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Send claims at or above 50000 to a senior claims handler within their authority.
- Escalate complaints open 28 days to the complaints manager so the final response meets the regulator's deadline.
- Escalate at once on legal_action, media, regulator_contact, bereavement; a fraud indicator goes to the special investigations unit and is never mentioned to the customer.
- Cases reopened 2 or more times go to a team lead.
- Vulnerable customers go to the vulnerable customer team with the flag kept on the record.
- Skip owners holding 25 open escalations.
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.