- Industry
- Insure AI
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Customer Service Manager
- Code
- CUS-05
It answers policyholder and broker service email, such as requests for a certificate of insurance, a no-claims proof letter, a payment schedule or claim documents, and sends routine documents from the correspondence system. It chases missing claim documents and closes resolved threads.
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 document and correspondence system: the policy documents and letters available for the policy, and the claim documents received so far..
- 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 Customer Service Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the document and correspondence system: it sends the reply with its documents and logs it on the policy or claim. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The email templates and approved answers, the documents it may send by product, the claim documents checklist by claim type and the reply service levels.
Reads from
the document and correspondence system: the policy documents and letters available for the policy, and the claim documents received so far.
Acts in
the document and correspondence system: it sends the reply with its documents and logs it on the policy or claim.
Hands back
An object with reply, documents_attached (a list), missing_documents (a list), is_complaint (true or false), status (sent, drafted, closed) and next_chase_date (or null).
Asks a person when
The email is a complaint, asks to send documents to an address not on the policy, or asks for a category outside certificate, ncd_proof, payment_schedule.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Reply within (hours) | 24 | Every email gets a reply within this time. |
| Categories it may answer and send itself | certificate, ncd_proof, payment_schedule | Comma-separated. Others are drafted for review. |
| Chase missing claim documents after (days) | 5 | A claim waiting on documents gets a reminder this often. |
| Close a resolved thread after (days) | 7 | With no reply after this long a resolved thread closes. |
| Send documents only to the email on the policy | On | When on, documents go only to the email address on the policy or broker record. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Reply within 24 hours.
- Answer and send certificate, ncd_proof, payment_schedule itself; draft every other category for review.
- When on is true, send policy documents only to the address on the policy or broker record.
- Chase missing claim documents every 5 days, naming exactly which documents are missing.
- Treat any dissatisfaction as a complaint and route it so the regulator's timeline starts; never reply to a complaint with a template.
- Close resolved threads after 7 days without a reply.
See the Email Support Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.