Policyholder Segmentation Agent
Groups policyholders and prospects by product holding, tenure and value.
- Industry
- Insure AI
- Department
- Marketing
- Team
- Brand and Insights
- Kind
- Assistant
- Approver
- Compliance Officer
- Code
- MKT-14
It groups policyholders and prospects into marketing segments by product holding, tenure, renewal month, channel and customer lifetime premium, such as single-line motor customers ripe for home cross-sell. It writes the segments to the customer data platform and never uses health, claims or protected-trait data to build them.
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 customer data platform: policyholder product holdings, tenure, renewal dates, channel, premium history and consent, joined from the policy administration system..
- 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 Compliance Officer with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the customer data platform: it creates or updates the segment definitions. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The segmentation playbook: segment definitions, value model, permitted and prohibited fields, consent rules and fair value guidance.
Reads from
the customer data platform: policyholder product holdings, tenure, renewal dates, channel, premium history and consent, joined from the policy administration system.
Acts in
the customer data platform: it creates or updates the segment definitions.
Hands back
A list with one entry per segment, each with name, definition, size, average_premium, products_held, suggested_offer and fields_used.
Asks a person when
A suggested field is sensitive or protected, a segment would single out vulnerable customers, or the segments would feed pricing rather than marketing.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Smallest segment | 1000 | Segments smaller than this are merged. |
| Most segments | 8 | No more segments than this. |
| Value window (months) | 36 | Customer value is measured as premium over this many months. |
| Exclude sensitive fields | On | When on, health, claims history, ethnicity, religion and other protected fields are never used. |
| Refresh | monthly | How often segments are rebuilt. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Segment on product holding, tenure, renewal month, channel and premium over 36 months.
- When on is true, never use health, claims history or protected traits; segments must not lead to unfair pricing or offers that fail fair value.
- Segments have at least 1000 people and there are at most 8.
- Include only people with marketing consent in segments meant for promotion.
- Refresh monthly.
See the Policyholder Segmentation Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.