---
title: "Enrichment starts with the right entity."
description: "Company and people enrichment adds evidence to a known record. Identity resolution, contact discovery and verification answer different questions."
canonical: "https://altss.com/console/enrichment"
last-updated: "2026-11-17"
---

# Enrichment starts with the right entity.

Company and people enrichment adds evidence to a known record. Identity resolution, contact discovery and verification answer different questions.

Last modified: 2026-11-17

## Resolve identity before adding fields

A prospecting team often has incomplete names, old job titles and duplicate organizations. Adding more attributes to the wrong entity makes the record harder to trust. Start with exact legal identity, official domain, geography and the relationship between a parent, subsidiary and brand. Keep conflicting evidence visible until the match is resolved.

## Company enrichment

Define the organization using its official domain and legal identifiers where available. Request only fields needed for the job: operating activity, location, ownership evidence or public transaction context. Each field should retain its source and date; an operating office is not automatically a headquarters and a financing announcement is not a complete funding history.

## People enrichment

Use the person’s name, organization and role context to distinguish similar identities. Record whether a role is current, historical or undated. Public employment evidence and licensed professional contact data have separate source and use conditions; a match on a name alone is insufficient.

## Contact discovery

Define the relevant professional contact and the allowed delivery use. Availability varies by record and by the provider or dataset permissions that apply. A professional email address does not by itself establish consent for a particular outreach campaign. Keep the contact field’s origin, verification context and permitted use with the result.

## Verification

Email verification describes a checking process, not a guaranteed delivery rate. Delivery also depends on sending practices, recipient policy and the current mailbox state.

Verification should answer a named question: does a domain resolve, is a person associated with this organization, or what mailbox check was performed and when? Those checks are not interchangeable. Record the method, date and result, and retain unknown or inconclusive outcomes.

## Entity resolution

Organization identity and relationship evidence are separate. Shared names or domains can suggest a relationship; they do not establish that two organizations are the same.

Resolve a match through identifiers and primary evidence. Preserve separate records for a parent, operating subsidiary, pension fund and foundation, even when names or addresses overlap. Return match evidence and unresolved alternatives so a human can inspect the decision.

## What a useful enrichment result preserves

| Field | Review context |
| --- | --- |
| Organization | Legal name, official domain and identifiers used for the match |
| Person and role | Exact organization, source, observed date and current/historical status |
| Contact | Field origin, check method, verification date and applicable use limits |
| Uncertainty | Conflicting sources, missing values and alternatives requiring review |


## Choose the available capability before funding

The separate Altss Console publishes authenticated REST and MCP interfaces and a catalog for bounded SEC financial research using public issuer filings. Follow its connection guide and current tool catalog for account eligibility, credential setup, scope, quotes and funding requirements. This does not grant private-company dossiers, contact enrichment or unrestricted graph access.

[Read the current Console catalog](https://console.altss.com/tools.json)

[Check Console pricing](https://console.altss.com/pricing)

## Choose the delivery path

- [Discuss an enrichment requirement](https://altss.com/contact)
- [People Intelligence](https://altss.com/intelligence/people)
- [Security, permissions and result use](https://altss.com/console/security-and-permissions)

[Discuss your workflow](https://altss.com/contact)

[Explore capabilities](https://altss.com/console/capabilities)

## Give your agents a defined job.

Start with the capability, its evidence requirements and the decision your team needs to make. Confirm the available tool and permitted use before execution.

[Read the connection guide](https://console.altss.com/connect)

[Discuss a requirement](https://altss.com/contact)

Canonical URL: https://altss.com/console/enrichment

