Skip to main content
Human guide: work with your agent → Enrich one company and inspect which fields the selected Play actually found. This task ends with a reviewed company profile, not an automatic CRM update.

​
Before you start

Use a company domain or name. Preserve the original identifier alongside the result. A similar company name does not establish the same business entity. The maintained company-to-info Play uses People Data Labs company enrichment. It does not automatically merge three providers or promise every field will be populated. Its typed result contains nullable fields and explicit misses.

​
1. Inspect the Play

Read the current input, output, access, and pricing information. Checking the Play does not run enrichment.

​
2. Query one known company

Use a domain you are authorized to research. This example starts provider work:
Save the returned run ID. Inspect the same run:

​
3. Separate identity from field availability

Check company_found and miss_reason first. Compare company_name and company_domain with the intended company. Then inspect the required business fields. Examples include headcount, industry, hq_country, and total_funding_usd. A null field is missing evidence. It is not automatically zero or an empty business fact.
Keep the result only when its identity fits your input. Preserve null fields and miss reasons instead of filling unsupported values.
If you need several sources, author their selection and precedence rules in a custom Play. Do not assume that a natural-language request changes the maintained Play’s implementation.

​
4. Expand to a file after review

Inspect prebuilt/company-to-info-batch. Map its actual CSV input contract, then use Batch CSV enrichment for a representative pilot. Keep company identity and unknown fields in the export. Ask your agent to explain an identity mismatch before replacing your CRM data. See account enrichment for a field-level workflow.