Service Request Triage Agent
Categorises, prioritises and routes policy and claims service requests.
- Industry
- Insure AI
- Department
- Customer
- Team
- Support Operations
- Kind
- Decision-maker
- Approver
- Customer Service Manager
- Code
- CUS-02
It categorises incoming service requests and claims contacts, such as new FNOL, claim chasers, endorsements, cancellations, complaints and broker queries, sets priority and routes each to the right queue. It fast-tracks urgent losses such as an uninhabitable home or a stranded traveller and groups mass contacts after a catastrophe event.
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 policy administration system: the policies named with their line, segment and open service cases, and any open claim on them..
- 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 policy administration system: it updates each service case with its category, priority, queue and event tag. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The routing matrix: request categories, queues by line and channel, priority rules, regulatory complaint definitions and the catastrophe surge protocol.
Reads from
the policy administration system: the policies named with their line, segment and open service cases, and any open claim on them.
Acts in
the policy administration system: it updates each service case with its category, priority, queue and event tag.
Hands back
A list with one entry per request, each with request_id, category (fnol, claim_chaser, endorsement, cancellation, renewal, complaint, broker_query, billing or spam), priority (P1 to P4), queue, merged_into (or null), event_tag (or null) and reason.
Asks a person when
It opens a catastrophe queue, re-prioritises more than a queue's daily capacity, or routes a request to the special investigations unit.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Words that mark an urgent loss | uninhabitable, flooded, fire, stranded, hospitalised, injured, theft of vehicle | Comma-separated. A request with any of these is P1. |
| P1 response target (minutes) | 30 | P1 requests are routed for contact within this time. |
| Segments that get priority | high_net_worth, corporate | Comma-separated customer segments routed to dedicated handlers. |
| Merge repeat contacts within (hours) | 48 | Repeat contacts about the same policy or claim within this window are merged. |
| Contacts that trigger a catastrophe queue | 50 | This many contacts naming the same event in a day open a catastrophe queue. |
| Close obvious spam itself | On | When on, spam with no policy reference is closed without review. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A request with any of uninhabitable, flooded, fire, stranded, hospitalised, injured, theft of vehicle, or a vulnerable customer, is P1 and is routed for contact within 30 minutes.
- Any expression of dissatisfaction is tagged as a complaint and routed to the complaints queue so the regulator's timeline starts.
- Route high_net_worth, corporate to their dedicated handlers and broker queries to the broker service desk.
- Merge repeat contacts on the same policy or claim within 48 hours.
- When 50 or more contacts name the same event in a day, open a catastrophe queue and tag them to the event.
- A request mentioning possible fraud goes to the special investigations unit queue, never back to the customer.
- When on is true, close spam with no policy reference.
See the Service Request 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.