Lapse Prediction Agent
Flags policies at risk of lapsing or not renewing and why.
- Industry
- Insure AI
- Department
- Customer
- Team
- Customer Lifecycle
- Kind
- Investigator
- Approver
- Head of Distribution
- Code
- CUS-14
It predicts which policies are likely to lapse or not renew, from premium increases at renewal, missed payments, recent claims experience, quote activity elsewhere and channel, and explains the drivers for each. It proposes retention actions for policies above the risk threshold, leaving any premium change to underwriting. **The problem it solves:** Why the policies named are likely to lapse or not renew: renewal price change, payments, claims experience, tenure and channel, and which drivers weigh most.
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 policies' renewal terms, premium changes, payment history and tenure, and quotes issued for the same customers..
- 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
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Head of Distribution with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the policy administration system: it flags the at-risk renewals and creates the retention tasks. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The lapse model: drivers and their weights by line, renewal price change bands, the retention playbook and the fair pricing rules that forbid penalising loyal customers.
Reads from
the policy administration system: the policies' renewal terms, premium changes, payment history and tenure, and quotes issued for the same customers.
Acts in
the policy administration system: it flags the at-risk renewals and creates the retention tasks.
Hands back
A list with one entry per policy, each with policy_number, risk_percent, drivers (a ranked list, each with driver, weight and evidence), premium_at_stake and retention_action.
Asks a person when
A retention action involves a premium change, or a whole segment's lapse risk rises sharply.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Lapse risk that triggers action (%) | 40 | Policies at or above this risk get a retention action. |
| Predict lapses within (days) | 60 | The window predicted. |
| Renewal increase that counts as a price shock (%) | 15 | An increase at or above this is a strong driver. |
| Annual premium that gets a retention call (USD) | 1500 | Policies below this get an email, above it a call. |
| Ignore policies younger than (days) | 90 | Too new to predict. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Predict lapse within 60 days; ignore policies younger than 90 days.
- Act on policies at or above 40 percent risk, ranked by premium at stake.
- Treat a renewal increase of 15 percent or more as a price shock and say so as a driver.
- Retention actions never offer a price below what a new customer would pay for the same risk, and any premium change goes to underwriting.
- Policies above 1500 get a retention call, others an email.
See the Lapse Prediction Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.