Inbound lead enrichment: fill the gaps without guessing who signed up

An inbound lead enrichment workflow starts with information a person chose to submit. Its job is to add useful context without replacing that information with a more confident-looking guess.

A work domain can suggest an organization. It does not prove the person's role, purchasing authority or employer. A personal email domain tells you even less. Treat enrichment as a set of proposed annotations, not permission to rewrite the signup record.

Keep submitted and inferred fields separate

Store the original form submission first. Then create an enrichment job linked to its stable ID. A provider timeout should not lose the signup or make the form ask the visitor to submit again.

For an update, preserve these layers:

Use an idempotency key based on the submission and enrichment version. Retries should update the same job rather than creating duplicate CRM contacts.

Use company enrichment before expanding personal data

Hunter's API reference documents company, person and combined enrichment operations. Those are different requests with different input and output requirements. Start with the least data needed to answer the actual routing question.

If all you need is the company's category or public website, do not fetch every available phone number or personal profile. If the submitted domain is a common email provider, leave the company unresolved unless the person supplied additional context.

People Data Labs Company Enrichment is another candidate for resolving an approved company input. Check the match and preserve uncertainty. A domain associated with a parent company may not identify the product team or subsidiary the visitor represents.

Normalize results without hiding their origin

An application-owned annotation might look like this:

{
  "submission_id": "internal-reference",
  "company_match": {
    "state": "unresolved",
    "provider": null,
    "provider_record_id": null,
    "observed_at": null
  },
  "proposed_fields": {},
  "human_review_required": true
}

This is a schema example, not a provider response. Keep raw provider fields in appropriately restricted storage if your agreement allows it. Do not put personal enrichment results into browser analytics or public report artifacts.

Separate no match, invalid input, a processing restriction and an account error. They require different actions. None should turn into an invented company so that a routing rule can keep running.

Route conservatively

Use explicit, reviewable business rules. An enterprise-domain match can help suggest an account owner, but it should not automatically deny access, downgrade support or classify a person as unimportant.

A personal email address is not evidence of low value. An incomplete vendor record is not evidence that the organization is small. Send uncertain cases to a general review queue instead of burying them.

Keep contact permission separate from data availability. A person asking for a specific report has not necessarily asked to join every sequence your sales tools support.

Give the agent a bounded enrichment job

Implement asynchronous enrichment for approved inbound submissions.
Persist the original submission before calling a provider.
Use the minimum approved fields and server-side credentials.
Keep self-reported, provider and human-corrected data separate.
Do not infer an employer from a common personal-email domain.
Use idempotent retries and preserve no-match, restricted and error states.
Propose CRM updates for review; do not enroll anyone in outreach.
Report match coverage, conflicts, latency and per-job usage without PII.

Measure downstream usefulness

Count correct company matches on a reviewed sample, not just populated fields. Track how often a correction is needed and whether the enrichment reduces preparation time for the requested conversation.

Test a duplicate submission, a personal email, a parent/subsidiary conflict, a provider outage and an explicit removal request. Verify that a human correction survives the next scheduled refresh.

Use the company-research guide when the matched account needs a deeper brief. For a separate outbound workflow, the outreach pipeline starts from an approved prospecting scope rather than assuming every inbound record belongs in a campaign.