IMPLEMENTATION GUIDE
Use current positions as matching evidence
Read positions marked current rather than choosing the first position in the response. A person may have multiple current employers or advisory roles. Keep the position title, employer name, and matched domain together so an operations teammate can evaluate which association belongs on the contact record.
Resolve account candidates deliberately
Normalize the matched employer domain and look for existing CRM accounts using the same normalization. If several accounts share it, apply your subsidiary or regional account rules. If there is no matched domain, leave the association unresolved instead of guessing from the company name. A company enrichment request can add firmographics separately when needed.
Preserve verified relationships
Compare the proposed association with the existing one before writing. Queue conflicts for review and retain the previous association and evidence in your audit trail. Match completed tasks to contact IDs and make repeated webhook deliveries update the same proposal rather than create duplicate account records.
Connect the workflow
Use the API overview for request and task handling, or the Loop guide for webhook delivery.
People enrichmentSee professional positions and matched employer details.Common questions
Is an employer domain available for every person?
An employer domain is included when matched. Some positions may lack a domain, and a contact can have multiple current positions. Keep those cases available for review.
Does a person lookup return the employer’s full company profile?
People enrichment provides professional details and a matched employer domain when available. Request company enrichment separately to add industry, employee count, and headquarters.