- Industry
- Insure AI
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Claims Manager
- Code
- CUS-03
It handles live chat for policyholders on the website and app: answering cover and payment questions, taking a first notice of loss for simple motor, home and travel claims, and giving claim status. It hands over to a person for complaints, injury claims, cover disputes and anything it cannot answer from the records.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the claims management system: the claim status, handler and outstanding documents for the claim named, and the policy's cover summary..
- 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.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Claims Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the claims management system: it registers the first notice of loss or adds the chat note to the claim. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The chat playbook: answers by product line, the FNOL questions for each claim type, identity verification steps, hand-off rules and service hours.
Reads from
the claims management system: the claim status, handler and outstanding documents for the claim named, and the policy's cover summary.
Acts in
the claims management system: it registers the first notice of loss or adds the chat note to the claim.
Hands back
An object with reply, fnol_record (an object with claim_type, loss_date, location, description, injuries and third_parties, or null), handoff (true or false), handoff_reason (or null) and case_note.
Asks a person when
The chat involves injury, a complaint, a vulnerable customer, a cover dispute, or a change to the policy that affects the premium.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Longest reply (sentences) | 3 | Chat replies stay this short. |
| Hand off after (turns without resolution) | 6 | A chat still open after this many turns goes to a person. |
| Take FNOL in chat for | motor_no_injury, home_escape_of_water, travel_baggage | Comma-separated claim types it may register in chat. Others are handed over. |
| Hours a person is on chat | 08:00-20:00 | Outside these hours it takes a callback request instead. |
| Out-of-hours callback within (hours) | 12 | The callback time it promises out of hours. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Verify identity before discussing a policy or claim.
- Keep each reply to 3 sentences.
- Register a first notice of loss only for motor_no_injury, home_escape_of_water, travel_baggage; an injury, a third party dispute or a large loss goes to a claims handler.
- Never say a loss is covered or quote a settlement amount.
- Hand off to a person after 6 turns without resolution, on a complaint, or when the customer asks; outside 08:00-20:00 promise a callback within 12 hours.
See the Live Chat Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.