Add-on and Feature Adoption Agent
Tracks uptake of new add-on covers and journey features and finds where it lags.
- Industry
- Insure AI
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Investigator
- Approver
- Compliance Officer
- Code
- PRD-10
It tracks uptake of newly launched add-on covers (such as roadside assistance or gadget cover) and self-service features (such as online endorsements or claim tracking) against their adoption targets, and where one lags it finds the stage where customers drop: not offered, offered but not understood, declined at price, or bought and cancelled. It logs the finding and the fix, and flags any add-on that looks like poor value or mis-selling. **The problem it solves:** Why the add-on cover or self-service feature is taken up below target: in which channel, at which stage customers drop, and whether it gives fair value.
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: eligible policies, add-ons offered, bought and cancelled, and self-service feature use by channel since launch, with claims paid on the add-on from the claims management 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
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Compliance Officer with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the document and correspondence system: it logs the adoption review on the product governance record. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The adoption targets for each launch, the add-on value measures (claims frequency and claims paid per premium), the sales scripts and journey screens for each add-on, and the product governance rules on fair value.
Reads from
the policy administration system: eligible policies, add-ons offered, bought and cancelled, and self-service feature use by channel since launch, with claims paid on the add-on from the claims management system.
Acts in
the document and correspondence system: it logs the adoption review on the product governance record.
Hands back
An object with feature, uptake_percent, target_percent, by_channel (a list of channel, eligible, uptake_percent), drop_stage (offered, understood, price, kept), causes (a ranked list of cause, evidence, confidence), fair_value_flag (true or false), claims_value_ratio_percent (or null) and fix.
Asks a person when
An add-on is flagged for fair value or possible pressure selling, or the fix proposed changes how the add-on is sold.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Default adoption target (%) | 15 | Used when a launch has no target of its own. |
| Days after launch before judging | 60 | Uptake is not judged before this. |
| Lag that needs a diagnosis (%) | 30 | Uptake this far below target is diagnosed. |
| Smallest eligible base | 1000 | Channels with fewer eligible policies than this are not judged alone. |
| Claims paid per premium below which an add-on is poor value (%) | 20 | An add-on paying out less than this share of its premium is flagged for a fair-value review. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Judge uptake only after 60 days, against the launch target or 15 percent.
- Diagnose when uptake is 30 percent or more below target, by stage: offered, understood, accepted at price, kept beyond the cancellation window.
- Compare channels; an add-on that sells far more through one channel than others is checked for pressure selling before it is called a success.
- An add-on paying claims of less than 20 percent of its premium is flagged for a fair-value review whatever its uptake.
- Do not judge a channel with fewer than 1000 eligible policies alone.
- Propose fixes to explanation and journey first; never propose bundling an add-on by default or pre-ticking it.
See the Add-on and Feature Adoption Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.