A rep-entered profile URL beats a vendor's perfect-score match
Enrichment can return a different person even when name and company scores are perfect.
SymptomAn enriched contact shows another person's profile or title even though the CRM already held the right profile URL.
The standard enrichment flow trusts a vendor match whenever its name and company scores are high, treating a perfect score like proof.
A perfect score can still be a different person. Name and company are what the vendor matched on, so two people with one name at one company can both score perfectly.
Profile slugs also change when people rename their public profile URL, so an old URL in the CRM and a new one from the vendor can be the same person.
So let the human-entered URL win, because someone chose it on purpose. The vendor should fill only the gaps, with every disagreement logged and reviewed on a schedule. Adopt a new slug only when the vendor supplies a stable id that ties both URLs to the same person. Otherwise the CRM's URL stays.
In a synthetic test set of contacts with rep-entered profile URLs, letting a perfect-score vendor match win overwrote the correct URL on 5 of 10 namesake contacts; keeping the rep-entered URL overwrote none and logged 5 disagreements for review. The set shows the mechanism, not how common it is.
List contacts that hold a profile URL both in a rep-entered CRM field and from enrichment. Count the contacts where the 2 URLs differ. Any difference where the enriched URL is the one in use is a possible wrong person.
Passes ifWherever the rep-entered and enriched profile URLs differ, the rep-entered one is the URL your jobs and agents read.
Access needed:crm-read
- 01Treat a profile URL entered in the CRM as the identity anchor. Let enrichment fill only empty fields.
- 02Log every case where the vendor's profile differs from the CRM's, instead of choosing silently. Review logged disagreements on a schedule.
- 03Adopt a new profile slug only when a stable id from the vendor ties both URLs to the same person. Otherwise, log the disagreement. Then keep the CRM's URL.
- 04Never let a match score override a human-entered identifier, however high the score.