> For the complete documentation index, see [llms.txt](https://docs.kernel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kernel.ai/integrations/salesforce-integration/lead-enrichment.md).

# Lead enrichment

Identify the company behind a Salesforce Lead and add company data to the Lead record.

Kernel identifies the company behind a Salesforce Lead and writes company data back to the Lead. You can enrich a Lead before creating an Account in Salesforce.

### Before you start

Confirm which Leads your workflow selects, which company inputs it reads and which Lead fields it updates. Lead enrichment uses its configured selection and field mappings. Use [Inbound](https://docs.kernel.ai/developer/inbound-api) for scheduled and API-triggered enrichment, and the [Salesforce Integration User Permission Matrix](https://docs.kernel.ai/integrations/salesforce-integration/salesforce-integration-user-permission-matrix) to check access to the selected objects and fields.

### How it works

Kernel reads the company details available on the Lead, such as its company name, website, email domain, LinkedIn URL, and address. It uses these details to resolve the company's identity and return a [KERN ID](/concepts/kern-id.md).

A KERN ID identifies the company the Lead belongs to. It is separate from the Salesforce Lead ID and Account ID.

Kernel then enriches the company and writes the configured fields back to the original Lead. Your setup determines which Leads are selected, how often they are checked, and which fields are updated.

## What gets enriched

Available company data includes:

* Legal and trading name, website, and LinkedIn URL.
* Headcount and revenue.
* Industry classification and custom verticals.
* Headquarters address and company phone number.
* Company identity confidence and supporting reasoning.

The fields returned depend on your enrichment setup and the information available for the company. Lead enrichment focuses on the company, rather than the individual person's profile.

See the [Data dictionary](/data/data-dictionary.md) for field definitions.

## Matching Leads to Accounts

If a Lead and an Account resolve to the same company, they can share a KERN ID. Your Salesforce team can use that ID in its own matching, routing, or reporting rules. Both records need a KERN ID for this comparison.

For example, a Lead entered as "Acme UK" and an Account named "Acme UK Limited" may resolve to the same entity. Their shared KERN ID gives your rules a way to match them even though the names differ.

Kernel's Lead enrichment does not automatically populate an Account lookup on the Lead. Linking the Salesforce records requires a separate rule or workflow.

A parent company and its subsidiary have different KERN IDs. Comparing KERN IDs matches the same entity, not every company in its corporate family.

## Lead conversion

Kernel does not convert Leads into Accounts, Contacts, or Opportunities. Your team continues to use its Salesforce conversion process.

Lead enrichment writes to the Lead record. It does not automatically switch to the Account when a Lead is converted.