What enrichment is
Enrichment adds what is missing to a record you already hold, from a source you can name. Two other jobs are often confused with it, and a record may need all three.
- Enrich: add what is missing.
- Cleanse: fix or remove what is wrong.
- Verify: check that what is there still holds.
Why a large database is not a large opportunity
A record passes through four states before it is worth a person’s time. It is stored, because it sits in a system you hold. It may be contacted, if the way it was collected allows a follow-up on that channel. It is usable, if it is not a duplicate, has not opted out and holds enough to say who the customer is. And it is worth a conversation, if there is an honest reason to get in touch now.
Each state holds fewer records than the one before. That is why the audit comes first, and why records are sorted green, amber or red before any is used. The sorting is an operating starting point, not legal advice, and the basis for each record group is recorded with you before anything is sent.
How every record is handled
We agree one record group with you first: where it comes from, which fields matter and who will follow it up. Every record in it is then handled by the same eight rules.
- The record is matched to the right company or existing account before anything is added.
- One source is ranked first for each field; the others fill only what is still empty.
- A value your team entered is never overwritten; a different value is shown beside it for a person to accept.
- An empty result never clears a field.
- Every added value carries its source, its capture date and who approved the field; an AI reading is labelled as a reading.
- A record set aside keeps its reason (duplicate, opt-out, unclear source, out of segment) and stays visible.
- A published route is checked again before anyone uses it.
- Details about private individuals are added on the basis that you hold the permissions the person gave you, and are processed the way you choose.
What stays with your team
Your named person decides who is contacted, and keeps pricing, objections, complaints and anything sensitive. You approve the record group, the sources, the channel, the message, how often it goes and when it stops. A score only sets the order of the list. It is not a judgement about the people on it.
How we start
We start with the audit on one set of records. You export the fields you can authorise, and we map them, count what is usable and look at what your current tools already do before proposing anything on top.
You then receive a recommendation, and it will be one of three: run a small pilot, repair the data first, or stop. If your existing tools already fill the gaps and score the records, we say so. If you hold only an old, finite database, the honest product is a one-off pilot, not a subscription.
A pilot is a finite queue worked by a person, with an outcome log, so the result is measured in your own system.