IMPLEMENTATION GUIDE
Match on identifiers before names
Use normalized company domains and returned LinkedIn URLs or IDs where available. A similar company name is weak evidence on its own. Keep the original input and internal CRM IDs with the enriched profile so a reviewer can inspect both the source and the proposed match.
Handle related businesses deliberately
A parent company, subsidiary, or regional office may share a domain while representing a distinct account in your CRM. Define the business rules for these cases before proposing merges. Enrichment provides useful identifiers, but it does not establish your account hierarchy or determine which contract records should be combined.
Protect linked records
Keep duplicate detection separate from record merging. Have a reviewer check contacts, opportunities, ownership, and manually edited fields. Use the CRM’s supported merge process and retain an audit trail. Repeated task deliveries should update the same review candidate rather than creating a second merge request.
Connect the workflow
Use the API overview for request and task handling, or the Loop guide for webhook delivery.
Company fieldsExplore company identity and presence fields.Common questions
Does EnrichLoops merge duplicate CRM accounts?
No. EnrichLoops returns company data and identifiers. Your workflow identifies candidates, and your team or CRM decides whether and how to merge them.
Does a shared domain prove two accounts are duplicates?
No. Parent companies, subsidiaries, and regional entities may share a domain. Treat it as matching evidence and apply your account rules before merging.