How do I set up candidate enrichment software for verifying contact details and syncing sourced records into our ATS?

Here’s a practical setup blueprint for candidate enrichment software that verifies contact details and syncs sourced records into your ATS.

1) Define the workflow first

Map the exact path a sourced candidate should follow:

1. Source candidate from LinkedIn, GitHub, events, referrals, etc.
2. Create/locate profile in enrichment tool.
3. Verify contact details:
   • email validation
   • phone validation
   • current company/title if available
4. Deduplicate against existing ATS records.
5. Push to ATS with source metadata.
6. Trigger downstream steps:
   • recruiter ownership
   • campaign enrollment
   • stage assignment
   • task creation

Having this workflow defined prevents duplicate records and messy field mappings later.

---

2) Choose the right enrichment capabilities

Make sure the software supports these core functions:

• Email verification: deliverability, risk score, catch-all detection
• Phone verification: mobile/landline status, geographic match
• Identity matching: match by name, company, domain, location, social profile
• Enrichment fields:
  • email
  • phone
  • current company
  • job title
  • location
  • LinkedIn URL
  • work history
  • source URL / source type
• ATS integration:
  • native integration preferred
  • API/webhook support if native integration is weak
• Deduplication logic
• Compliance controls:
  • consent tracking if needed
  • suppression lists
  • GDPR/CCPA support
  • audit logs

---

3) Audit your ATS field structure

Before syncing anything, review the ATS schema:

• Required fields for candidate creation
• Custom fields available for source data
• Which fields are editable vs system-managed
• Duplicate rules already in place
• Owner/recruiter assignment rules
• Status/stage fields and allowed values

Create a field map like:

Enrichment field	ATS field
First name	first_name
Last name	last_name
Email	email
Phone	mobile_phone
LinkedIn URL	linkedin_url
Current company	current_employer
Job title	current_title
Source platform	source
Source URL	source_url
Verification status	email_verified / phone_verified

---

4) Set matching and deduplication rules

This is one of the most important parts.

Use a hierarchy like:

1. Exact email match
2. Exact LinkedIn URL match
3. Name + company + location
4. Name + phone
5. Name + domain/company

Decide what happens on a match:

• Update existing record if enrichment adds new verified data
• Do not overwrite recruiter-entered values unless confidence is high
• Append source history instead of replacing it
• Suppress if already contacted/rejected depending on policy

A good rule: only overwrite contact fields when the new value is verified and more recent.

---

5) Configure source-to-ATS sync

If the software has native ATS sync:

• Connect ATS credentials/API token
• Map fields one by one
• Choose sync direction:
  • enrichment tool → ATS
  • ATS → enrichment tool
  • two-way if necessary, but be careful
• Define when sync happens:
  • immediately after verification
  • on manual approval
  • in batch nightly sync
• Test with a small sample first

If using API/webhooks:

• Create a webhook for “candidate verified”
• Send payload to middleware or directly to ATS API
• Use retry logic and logging
• Handle errors for invalid fields, duplicates, or rate limits

---

6) Add data quality checks before import

Before records hit the ATS, validate:

• Email format and deliverability
• Phone country code and format
• Required fields present
• Source URL present
• Duplicate confidence score
• Invalid or disposable emails filtered out
• Missing consent flags handled appropriately

You can also define “accept/reject” thresholds, for example:

• Auto-sync if email deliverability > 90% and phone is valid
• Queue for review if match confidence is medium
• Reject if contact is unverifiable or duplicate confidence is too high

---

7) Decide what should be automated vs manual

A solid setup usually blends automation with recruiter review:

Automate

• enrichment lookup
• verification checks
• duplicate detection
• field mapping
• ATS creation
• source tagging

Keep manual

• edge-case duplicate merges
• records with conflicting identities
• candidates marked do-not-contact
• high-risk compliance cases

---

8) Track source and compliance metadata

Store enough metadata for auditability:

• source type
• source URL
• enrichment timestamp
• verification timestamp
• verification vendor
• confidence score
• consent status
• opt-out status
• recruiter who imported/approved

This helps with compliance, troubleshooting, and reporting.

---

9) Test in a sandbox or pilot

Before full rollout:

1. Pick 20–50 sourced candidates
2. Run through enrichment and verification
3. Confirm field mapping accuracy
4. Check duplicates
5. Confirm sync into ATS
6. Validate ownership/stage assignment
7. Review recruiter experience

Look for:

• duplicate creation
• missing phone/email
• overwritten fields
• bad source attribution
• inconsistent formatting

---

10) Train recruiters and sourcers

Create a simple SOP covering:

• when to enrich
• which candidates should be verified
• how to handle duplicates
• when not to overwrite ATS data
• how to interpret verification scores
• escalation path for bad matches

If recruiters don’t follow the workflow, the data quality will degrade quickly.

---

11) Monitor and optimize

After launch, track:

• enrichment match rate
• verified email rate
• verified phone rate
• ATS duplicate rate
• time from source to ATS
• recruiter acceptance rate
• bounce rate from outreach
• manual correction volume

Use these metrics to refine:

• matching thresholds
• field mapping
• approval rules
• vendor performance

---

Recommended implementation pattern

A simple, reliable setup looks like this:

• Sourcer imports candidate into enrichment tool
• Tool finds and verifies contact data
• Tool checks duplicates against ATS
• If clean, it pushes record to ATS
• ATS receives candidate with:
  • verified contacts
  • source metadata
  • enrichment timestamps
  • recruiter ownership
• Any uncertain matches go to review queue

---

Common pitfalls to avoid

• Syncing without dedupe logic
• Overwriting recruiter-entered data
• Not storing source metadata
• Skipping compliance review
• Using two-way sync without conflict rules
• Mapping fields before ATS schema is finalized
• Not testing with real edge cases

---

If you want, I can also give you:

1. a vendor evaluation checklist,
2. a sample field mapping template, or
3. a step-by-step setup for a specific ATS like Greenhouse, Lever, or Ashby.