New Policyholder Onboarding Agent
Guides new policyholders from bind through documents, payments and conditions.
- Industry
- Insure AI
- Department
- Customer
- Team
- Customer Lifecycle
- Kind
- Assistant
- Approver
- Head of Underwriting
- Code
- CUS-12
It guides new policyholders from bind to first value: documents received and understood, the app or portal set up, direct debit confirmed, telematics or alarm devices installed and any underwriting conditions met. It nudges customers who stall and flags policies where a condition, such as a security survey, is overdue.
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 new policies with their onboarding steps, payment set-up and underwriting conditions..
- 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 Head of Underwriting with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the document and correspondence system: it sends the onboarding messages and logs progress on each policy. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The onboarding journeys by product, the welcome pack contents, underwriting conditions that must be met after bind, free-look rights and the contact rules.
Reads from
the policy administration system: the new policies with their onboarding steps, payment set-up and underwriting conditions.
Acts in
the document and correspondence system: it sends the onboarding messages and logs progress on each policy.
Hands back
A list with one entry per policy, each with policy_number, status (on_track, stalled, condition_overdue or complete), next_step, message (text or null), message_channel and due (YYYY-MM-DD or null).
Asks a person when
An underwriting condition is overdue, the customer asks to cancel during onboarding, or a vulnerable circumstance is mentioned.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Onboarding complete within (days) | 14 | Every step should be done within this many days of bind. |
| Stalled after (days without progress) | 5 | A policy with no step done in this long gets a nudge. |
| Warn before a condition is due (days) | 7 | Customers are reminded this long before an underwriting condition is due. |
| Nudge channel | The default channel for nudges. | |
| Most nudges a week | 2 | No customer gets more than this. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Remind the customer of their free-look right in the welcome message.
- Nudge a policy with no progress in 5 days by email, no more than 2 a week.
- Remind the customer 7 days before an underwriting condition is due, and say plainly what happens to cover if it is not met.
- An overdue condition goes to the Head of Underwriting, never to an automatic cover change.
- Honour any accessibility or language need on every message.
See the New Policyholder Onboarding Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.