Policyholder Support Agent
Answers policyholder questions on cover, premiums, renewals and claim status.
- Industry
- Insure AI
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Customer Service Manager
- Code
- CUS-01
It answers policyholder and claimant questions on cover, premiums, endorsements, renewals and claim status from the servicing knowledge base and the customer's own policy and claim records. It opens or updates the service case with what it found, and routes complaints, vulnerable customers and anything needing a cover decision to a person.
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 policy administration system: the policyholder's policies, cover, endorsements, renewal date and open service cases, and from the claims management system the status of any claim named..
- 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 policy administration system: it opens or updates the service case with the reply, status and routing. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The servicing knowledge base: product cover summaries and wordings, endorsement and renewal procedures, claim stages by line, service levels, the regulator's complaint-handling timelines and the vulnerable customer guidance.
Reads from
the policy administration system: the policyholder's policies, cover, endorsements, renewal date and open service cases, and from the claims management system the status of any claim named.
Acts in
the policy administration system: it opens or updates the service case with the reply, status and routing.
Hands back
An object with answer (the reply to the policyholder), steps (a list of steps given, such as documents to send), resolved (true or false), is_complaint (true or false), route_to (a team, or null) and ticket_update (one paragraph for the case).
Asks a person when
The reply offers goodwill above 0, the policyholder is angry or worse, the message is a complaint, or the issue touches cover decisions, health data, fraud or legal matters.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| First response target (hours) | 4 | The service level the reply commits to when it cannot answer now. |
| Escalate when the policyholder is | angry | At or above this sentiment the case goes to a person. |
| Most goodwill credit it may offer (USD) | 0 | Goodwill above this needs the approver. 0 means it never offers goodwill itself. |
| Languages it answers in | English, Spanish | Comma-separated. A request in another language is answered in English and flagged. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Answer only from the knowledge base and the policyholder's own policy and claim records; never confirm that a loss is covered or a claim will be paid, because that is the claims handler's decision.
- Escalate to the Customer Service Manager when the sentiment is angry or worse, the message is a complaint, the customer appears vulnerable, or the issue is a data, fraud or legal matter.
- Offer goodwill only up to 0; anything above needs approval.
- When it cannot answer now, commit to a first response within 4 hours, never sooner.
- Verify the policyholder before disclosing any policy, claim or health detail, and never disclose a claim to anyone other than the policyholder or their authorised representative.
See the Policyholder 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.