CRM data quality · one email in, a qualified account out
Inbound lead enrichment: from a form email to a qualified account
The short answer
Inbound lead enrichment completes a lead that arrives with only a work email. Look up the person behind the address, take the company page of their current job, enrich that company, then qualify the lead against your ideal customer profile before anyone reads it. What a lookup cannot answer, such as what the lead needs, stays on the form.
On this page8 sections
- What is inbound lead enrichment?
- What can a work email tell you about a lead?
- How do you qualify an inbound lead from its email?
- Which form fields can you stop asking for?
- What should you do when the lookup finds no one?
- When should inbound lead enrichment run?
- How do you enrich an inbound lead with the API?
- Sources and method
Someone fills in a demo request with a work email and presses submit. At that moment, your CRM knows an address and nothing else. Before the lead can be scored, routed or answered, someone or something has to work out who this is, where they work, and whether that company is one you sell to. Done by hand, it means a rep searching for the person before replying. Done as inbound lead enrichment, it runs the moment the form is submitted, and it is the first place where CRM data quality is won or lost: a lead attached to the right account on arrival starts clean, and only needs re-checking when the person moves.
What is inbound lead enrichment?
Inbound lead enrichment is lead enrichment applied at the moment a lead arrives: the form gives you an email, and enrichment gives you the person and the account behind it.
- Definition Inbound lead enrichment also called inbound enrichment
- Filling in who a new lead is and which company they work for, from the little they typed into a form, before anyone has to look them up by hand.
PreciselyInbound lead enrichment completes a lead that arrives with a work email and little else. A reverse email lookup identifies the person and their current job, the job's company page identifies the account, and a company enrichment returns its industry, size and headquarters. The result feeds lead qualification and lead routing; a lead that cannot be identified stays marked as unknown instead of being guessed.
It runs in three moves, and each one hands its result to the next:
- The person. From the email, find who it belongs to and the job they hold today.
- The account. From that job, take the company page it is attached to, and match it to your accounts.
- The company. From the page, get the firmographics your qualification and routing rules read.
What can a work email tell you about a lead?
More than its domain suggests, once it is resolved to a person. Reverse Email Lookup takes the address and returns the professional behind it: the job held today and when it started, the career before it, and for each job the company page and its ID when the company has one.
The domain on its own is a weak clue. On November 10, 2026, we looked up the address of someone in revenue operations at Datadog. It ends in datadoghq.com: a domain match works only if your account stores that exact domain, and it misses every subsidiary and alias. The lookup settles it without the domain: the current job points to the Datadog company page, ID 1066442.
The same response also says the title is recent. The person took their current title in 2026, after a different one at Datadog. A CRM that saved this contact from an earlier form still shows the old title, and would route and message on it.
How do you qualify an inbound lead from its email?
Look up the person, enrich the company of their current job, and check both against your ideal customer profile. Here is the real lookup, end to end:
- industry
- Software Development
- employees_on_linkedin
- 10,330
- hq
- New York, United States
- Software companySoftware Development
- More than 1,000 employees on LinkedInemployees_on_linkedin 10,330
- Headquarters in NORAM or EMEAhq.region NORAM
- Works in revenue or sales operationsRevenue operations
- Identify the person. The reverse lookup returns the current job: here, a role in revenue operations, under a title the person took in 2026.
- Enrich the account. Company Enrichment takes the page of that job and returns the company profile: industry, a headcount band, the employee count on LinkedIn, headquarters and region.
- Check fit. Compare the company and the job with your ideal customer profile. The example in the diagram asks for a software company with more than 1,000 employees on LinkedIn, headquartered in the NORAM or EMEA region, and someone in revenue or sales operations. Datadog and this lead pass all four checks.
- Hand it on. A qualified lead goes to routing with its account already matched, and a lead that misses a check goes to nurture with the reason written down.
That is how to qualify inbound leads on fit, the same way every time. Lead qualification has a second half that data cannot do. Fit says the company and the person look like your customers. Whether they need something now, and what, only the lead can say.
Enrichment answers fit. Only the lead can answer need.
Which form fields can you stop asking for?
Every field the lookup can answer reliably. A long form asks people to type what is already one call away. Keep the questions only the lead can answer:
- Work email
- What they want help with
- Consent to be contacted
- Companyfrom the current job
- Job titlefrom the current job
- Countryfrom the person and the company
- Company sizefrom the company profile
- Industryfrom the company profile
Some teams keep a company field anyway, to catch the leads the lookup cannot identify. That works, as long as the typed value never overwrites a matched account: a person writes their company name the way they say it, and the account match has already been made on the company page.
What should you do when the lookup finds no one?
Keep the lead and say what is missing. A lookup that returns found: false costs nothing in records and still tells you something: the address may be personal, brand new, or an alias such as a shared inbox.
- Do not create an account from the domain. A personal domain names no company, and several company pages can claim the same company domain.
- Mark the lead as unidentified, so that scoring does not treat an empty profile as a poor fit.
- Ask for a work email in the first reply, then run the lookup again.
The same discipline applies after qualification. The page on lead routing shows where an unidentified or unmatched lead should go, and why a default rep is the wrong answer.
When should inbound lead enrichment run?
On arrival, before routing, and again whenever the same person comes back. On arrival, because routing and scoring read what enrichment writes. On a return visit, because people change jobs and titles between two forms: the Datadog lead above changed title in 2026, and a record saved from a form before the change would carry the old one.
Run it on every form that creates or updates a lead: demo requests, trial sign-ups, content downloads, event lists. A lead enriched in one place and not another ends up with two versions of the same person in the CRM.
For builders
Two calls do the enrichment: one for the person, one for the account. This part shows both on the real lookup, and what to check before you put them behind a form.
How do you enrich an inbound lead with the API?
The form's work email in, the person out, with the current job and the company page it is attached to.
Send
email- The full address the lead submitted.
Read
found, person- The person, or found: false when no one matches. Nothing is counted then.
person.experiences[]- Each job with job_title, company_linkedin_url, company_linkedin_id (null when the company has no page), job_start_date and job_is_current.
The company page of the current job in, the company profile out.
Send
company_linkedin_url- Taken from the current job in the first response.
Read
company.linkedin_id, name- The account key, and the name to show the rep.
company.industry, size, employees_on_linkedin, hq- What fit rules read.
Each person or company found is one record, so a fully enriched lead uses two; plans and rate limits are on the BlitzAPI pricing page.
The real lookup
The first response, on November 10, 2026, trimmed to the current job, without the job title, the date masked to the year:
{
"found": true,
"person": {
"location": { "country_code": "US", "continent": "North America" },
"experiences": [
{
"company_name": "Datadog",
"company_linkedin_url": "https://www.linkedin.com/company/datadog",
"company_linkedin_id": "1066442",
"job_start_date": "2026-••-••",
"job_is_current": true
}
]
}
}The second, for the Datadog page, trimmed to what fit rules read:
{
"found": true,
"company": {
"linkedin_id": 1066442,
"name": "Datadog",
"industry": "Software Development",
"employees_on_linkedin": 10330,
"hq": { "city": "New York", "country_code": "US", "region": "NORAM" }
}
}The response also carries size, a headcount band. The two fields do not measure the same thing: pick one per rule and keep it. This example qualifies on employees_on_linkedin.
Before you put it behind a form
- Call the lookup on submit, before routing and scoring read the lead.
- Qualify on the current job (job_is_current) and its company page, never on the email domain.
- Write the company ID onto the lead, so the account match and routing read the same key.
- Treat found: false as unidentified: keep the lead and ask for a work email.
- Overwriting a matched account with the company name typed in the form.
- Run it again when a known person submits a new form: titles and employers change between visits.
Sources and method
- Written by
- The BlitzAPI team
- Published
- API calls run on
- Reverse Email Lookup, BlitzAPI API reference
- Company Enrichment, BlitzAPI API reference
- Plans, records and rate limits, BlitzAPI documentation
The BlitzAPI team ran the two lookups shown in the first diagram and in the builders section on November 10, 2026, on the work email of someone in revenue operations at Datadog. The page shows the company, the person's function, the country and a title change in 2026; the name, the titles, the address, the dates and the earlier employers are withheld.
The ideal customer profile in the first diagram is an example. The form fields in the second diagram describe a typical demo request, not a measured one.