When using the AI Recruiter across multiple communication modes (chat, email, SMS), new lead records will be generated and changed over time. These updates are sent back to Slate on a daily basis. However, without proper deduplication logic, your system may interpret these updates as new records instead of appending data to an existing one.
Why is deduping necessary?
Slate doesn’t automatically know whether an incoming record from CollegeVine is new or existing. Without proper deduplication rules and information in place, your CRM may treat updated or re-synced leads as new entries, leading duplicate records. Here's why implementing deduplication is essential:
Recommended deduplication practices
To prevent duplicates, follow these guidelines when configuring your source format settings in Slate.
Turn on deduplication settings
Ensure your dedupe settings in your source format are set to:
Dedupe on:
first+last+email+dob
Include Slate ID for precise matching
Slate will automatically attempt to match records entering Slate if a Slate ID field is included in the import. To ensure this is working:
Include the Slate ID as part of your query data when sending data to CollegeVine
Then, map this field in the CollegeVine UI
Finally, ensure this field is mapped back to your Slate ID field within your Source Format
Test with a small batch
We recommend sending a small number of leads in your first import to CollegeVine. This allows you to:
Validate your deduplication rules
Identify any misconfigurations early
Minimize the volume of consolidation your team needs to take on
For more assistance, please reach out to your CollegeVine partnerships team.