What Person Enrichment does
Person Enrichment supplements a known record with fields supported by the current contract. It does not infer sensitive personal information.
Complete supported person fields
Person Enrichment keeps missing fields explicit
Use existing person identifiers to request supported professional fields. Returned fields retain confidence, freshness, and safe provenance.
Supported input and returned output
Supported inputs
- Existing person identifierUse a supported email, profile URL, or record identifier.
- Company contextAdd a known company or domain when permitted.
- Requested fieldsAsk only for fields allowed by the current contract.
Returned outputs
- Professional fieldsReceive supported name, role, company, or related business context.
- Field outcomesKeep found, partial, not-found, and unavailable states separate.
- Evidence metadataReview field-level confidence, freshness, and provenance.
Typical workflow
-
Identify the record
Submit an existing supported person identifier.
-
Request fields
Select only approved professional fields.
-
Normalize results
Map returned evidence into the stable field contract.
-
Review gaps
Keep missing and uncertain fields visible.
Primary use cases
Record completion
Complete supported professional context on an existing contact.
Data review
Compare newly returned fields with current workspace data.
CSV preparation
Map known identifiers for a controlled field completion workflow.
Data confidence and field provenance
Field-level confidence
Confidence applies to each supported match or field and does not turn missing data into a positive result.
Field-level provenance
Each returned field can show safe source context and observation time.
Use through Workspace, CSV, or API
Workspace
Review field changes before saving them to a permitted record.
CSV
Map existing identifiers and requested professional fields when batch execution is approved.
API
Use a scoped enrichment contract only when execution is enabled.
Product maturity
Person Enrichment
BlockedBackend mappings exist, but a unified live execution contract remains blocked.
Not included or not currently available
- No sensitive inferenceUnsupported personal attributes are not guessed.
- No silent field fillAbsent evidence remains not found or unavailable.
- No live executionThe public page does not enable a blocked runtime path.
Trust and controls
Requested-field control
Only approved fields enter the enrichment request.
Safe provenance
Protected raw responses remain inaccessible.
Permission checks
Workspace use remains scoped to authorized records.
Frequently asked questions
It remains not found, unavailable, or partial according to the supported outcome.
No. It is limited to supported professional data fields.
No. The unified live execution contract remains blocked.
Related products
Preserve field evidence
Review the Person Enrichment contract
Create a workspace to inspect permitted fields, or log in to continue.