Skip to content
Fair Housing NoticeSaved
RealtyLT

Enrichment · Append + Verify

Half a name becomes a full profile

A bare address or partial contact is enriched into phone, email, and property detail through BatchData and public-record sources, deduped and validated, with what came back marked as what came back rather than merged silently into what you already knew.

  • BatchData + public records
  • phone + email checks
  • property detail append
  • dedupe + validate
Talk to us about thisSee it running on the AI page
What a pass does to a row, illustrated
The record you haveThe record you can work

  1. A first name and an email, from a sign-in sheet

    filled
    • Full name
    • a mobile appended
    • source and date recorded

  2. A mailing address with no property behind it

    partial
    • The parcel
    • when it last changed hands
    • no contact found

  3. A contact whose number you already had

    needs a decision
    • The file disagrees
    • both values kept
    • sent to a person

An illustration rather than a real record: no client, no address and no telephone number here belongs to anybody. What it is showing is the third row. When an outside file disagrees with something you already knew, the honest behaviour is to keep both and ask, and the common default is to overwrite without telling anybody.

Why it matters

20

separate sources of consumers' contact information that one data broker reported to the Federal Trade Commission

FTC, Data Brokers: A Call for Transparency and Accountability, May 2014

You can't work a lead you can't reach. Enrichment fills the gaps in records you already own, and writes down where each value came from and when, so the row tells you how much to trust it.

What it is

Data Enrichment, in plain terms

It is the pass that makes the records you already own usable. Most CRMs are full of half-leads: a first name and an email, an address with no phone, a duplicate of a contact that already exists, a number that stopped working two years ago.

Enrichment resolves them through BatchData and public-record sources into a phone number, an email, and the property detail behind the address, then dedupes and validates so the list you hand to a caller is one they can actually work. What validation establishes is that a number is well formed, in service and not a duplicate, which is a useful check and is not the same as establishing that it reaches that person.

How it works

What happens, in order

  1. Append what is missing

    A phone number for the email-only contact, an email for the phone-only one, and the property detail behind the address.

  2. Verify what is there

    Numbers are checked rather than assumed. Dialling time spent on numbers that no longer connect is a real cost and it is one almost nobody counts, which is why the checking happens before the list is handed over rather than after.

  3. Dedupe and flag

    Duplicates merge with their history intact, and records that came back thin are flagged as thin rather than padded out to look complete.

  4. Source, date, and what happens on a disagreement

    Every enriched value records where it came from and when it was written. Where an outside file disagrees with something the record already held, the rule is agreed with you at the start rather than inherited from a default, and both values can be kept so a person can settle it.

Use cases

Where it earns its keep

  • The CRM you cannot call

    Thousands of contacts and no numbers against most of them. A pass over the part of it you would actually work turns an archive into something you can pick up and use.

  • Open-house sign-ins

    A first name and a scrawled email become a fuller record, with the property they already own attached and a note saying where the rest of it came from.

  • Before you spend on outreach

    Checking first means the campaign is not spending on rows that were never going to reach anybody, and it is cheap to do on a sample before it is done on everything.

Limits

What it does not do

Every other section on this page is selling you something. This is the one that says where it stops. If a vendor cannot tell you this about their own product, you have learned something anyway.

  • It does not invent a contact. A record that will not resolve comes back flagged as thin or unreachable, because a dead number that looks live costs you more than a blank field.
  • It does not guarantee a match. How much resolves depends on the area and on how much public record sits behind the address, and no honest provider quotes a rate before seeing the list.
  • It does not tell you how old a value is unless the provider passes that through. Freshness is the most useful thing an appended field could carry and it is the one most often missing from the response, so it is worth asking for by name.
  • It does not know which answer is right when two sources disagree. That is a decision about your business and it gets made once. Worth knowing which way the tooling leans: on HubSpot, keeping a value you already hold is a per-property checkbox you select at import time rather than the resting state.
  • It does not make a list callable in the legal sense. Do-not-call registrations and consent rules apply to an enriched record exactly as they do to any other.
  • It does not tell you anybody is interested. Enrichment makes a record reachable. Whether that person wants to hear from you is a different question.

See it live

Easier to understand when you can touch it

Everything on this page is a node on the RealtyLT AI page: a galaxy that reshapes into a brain, with every service hanging off the core. Open the Data Enrichment node to read the same thing in its own habitat, and talk to the chat assistant while you are there, because that one is genuinely live.

Open it on the AI pageStart at the galaxy
Data Enrichmentone node on the hub

Questions

Asked and answered

The questions people actually ask about Data Enrichment, answered the way we would answer them on the phone. If yours is not here, ask us and we will add it.

What is data enrichment?

It is filling in what a contact record is missing and checking what it already has: appending a phone number or an email, adding the property detail behind an address, confirming that a number is in service, and collapsing duplicates. What arrives is an assertion from an outside file rather than something you observed, which is why the source and the date matter as much as the value.

How is enrichment different from skip tracing?

Skip tracing starts from a property and finds the owner. Enrichment starts from a contact you already have and completes it. They use the same underlying sources, and in practice most pipelines need both. The legal weight sits with skip tracing, because there is no prior relationship behind it.

Will enrichment overwrite the data I already have?

Only if the pass is configured that way, so establish which way rather than assuming. Decide it deliberately: fill blanks only, keep both values in separate fields, or send disagreements to a person. Whichever you choose, the previous value, the source and the date should be written to the record, because without them there is no way back from a bad pass.

How fast does contact data go stale?

There is no published rate worth quoting. The figures that circulate for contact data run from twenty to thirty percent a year, with up to seventy quoted for email addresses on their own, and they trace back to press releases and vendor pages rather than to a study with a stated sample. What is knowable is the mechanism: a field stops being true when something happens to a person, so the rate belongs to the people in your database rather than to the data, and it is different for a first-time buyer and a couple downsizing.

What happens to records that cannot be enriched?

They come back flagged as thin or unreachable rather than padded out with a guess. A dead number that looks like a live one is worse than a blank field, because you pay for it in dial time.

Read more

Written up in more detail

  • August 25, 2026

    The Empty Fields Got Filled. So Did the Ones That Were Already Right.

    Most of the blanks came back full, which is what you paid for. In one record the number a client gave you herself had been replaced, and nothing in the row said what was there before, where the new one came from, or when either was true. What an appended field actually asserts, why no honest decay rate exists, and the two columns that make all of it manageable.

  • August 25, 2026

    It Read the Date Correctly. The Date Was Not the Deadline.

    The rider arrived as a photograph taken over a kitchen table, with two handwritten changes and a date among them. Everything was read correctly and the answer was still wrong, because what a deadline counts from is not printed on the page. What was actually measured on real scanned forms, what a person scores on the same task, and the phrase one regulation defines twice.

  • August 25, 2026

    You Have Her Number. She Never Gave It to You.

    She picked up, she was polite, and she asked the one question nobody in this trade can answer: where did you get this number? Two federal statutes ask it too, and they ask it of you rather than of the tool. What skip tracing actually is, what the law permits, and the four questions to put to a provider in writing.

Want Data Enrichment running in your business?

Tell us what you do today and we will tell you honestly whether this is the right place to start. If it is not, we will say which one is.

Levan Tsiklauri

Builds these. Answers the phone himself.

(917) 905-7923

Also built

The rest of the machine

All AI services