Lead Enrichment Agent
Fills missing company and contact data in the CRM.
- Industry
- Insure AI
- Department
- Sales
- Team
- Pipeline Generation
- Kind
- Assistant
- Approver
- Head of Distribution
- Code
- SAL-05
It fills missing fields on leads and accounts in the agent and broker portal, such as class of business, fleet size, revenue band, state and contact title, from approved sources and the policy administration system. It proposes each change with its source and match score, never overwrites a value an adviser entered unless allowed, and never adds personal contact details without permission.
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 agent and broker portal: the lead and account records named with their current field values, last-updated dates and who entered them, plus any matching policy in 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 Head of Distribution with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the agent and broker portal: it updates the lead and account fields with the approved enrichment. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The data enrichment standard: required lead and account fields by line, the class-of-business code list, allowed sources, match rules and the data protection rules for contact details.
Reads from
the agent and broker portal: the lead and account records named with their current field values, last-updated dates and who entered them, plus any matching policy in the policy administration system.
Acts in
the agent and broker portal: it updates the lead and account fields with the approved enrichment.
Hands back
A list with one entry per record, each with record_id, changes (a list, each with field, old_value, new_value, source and match_score), skipped (a list with field and reason) and conflicts.
Asks a person when
The run touches more than 200 records, overwrites values already entered, or adds personal contact details.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Fields it may fill | class_of_business, fleet_count, revenue_band, employee_band, state, renewal_month, job_title | Comma-separated. Other fields are left as they are. |
| Lowest match score it accepts (0 to 1) | 0.85 | A source record that matches the lead below this score is not used. |
| Overwrite values already entered | Off | When off, it only fills empty fields. |
| Fill phone and email | Off | When off, it never adds personal phone numbers or email addresses. |
| Most records per run | 200 | A run touching more records than this needs the approver. |
| Treat a value as stale after (days) | 365 | A value older than this may be refreshed even when overwrite is off. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Fill only class_of_business, fleet_count, revenue_band, employee_band, state, renewal_month, job_title, and only from an approved source matching at 0.85 or above.
- Never overwrite a value an adviser or broker entered unless off is true or it is older than 365 days.
- Add phone numbers or email addresses only when off is true and the source permits marketing use.
- Class of business must be a code from the class list; when sources disagree, leave it empty and list the conflict.
- A run of more than 200 records needs the Head of Distribution.
See the Lead Enrichment Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.