Hire: Feature Requests

Find Potential Duplicates Hub for Candidate Cleanup
===== THE PROBLEM As our database grows through bulk imports, migrations, and manual sourcing, duplicate profiles are inevitable. Currently, finding and fixing these is a manual, one-by-one process. We have to search for a name, open two profiles, and manually merge them. This leads to fragmented communication logs, inaccurate reporting, and "dirty" data. Crucially, many candidates apply using alternate emails (personal vs. school), so relying on "Exact Email Match" as the sole field for linking candidates is not enough. ===== PROPOSED FEATURE Add a "Find Potential Duplicates" button or hub in the Candidates area (or under an Admin/Tools section) that scans the database and surfaces likely duplicate candidate profiles in a review queue. This would be especially useful immediately after bulk imports or large hiring campaigns, when the risk of duplicates is highest. ===== HOW IT WOULD WORK The system should automatically flag potential duplicates using a combination of: -- Exact and Fuzzy matches on Candidate Name -- Exact and Fuzzy matches on Email and Phone -- (Optional) Resume-based matching (e.g., similar work history, education, or location) The feature would show groups of "Potential Duplicates." Each group should display key details (Name, Email, Phone, Current Pipeline Stage, Source, Last Activity, Last Updated, etc.) in a side-by-side comparison view to help us confirm if they are the same person. ===== ACTIONS AND SAFETY For each potential duplicate group, an Admin or Recruiter needs the ability to: -- MERGE: Combine selected candidates into a single primary profile. We need to choose which values to keep when data conflicts (e.g., which phone number) and automatically combine notes, messages, scorecards, resumes, and history into the merged record. -- DISMISS: A way to ignore a group if the records are not actually the same person. -- SAFETY: Controls like an "Undo" or "Rollback" window for recent merges, and an Activity Log showing who merged which candidates and when. ===== FILTERS & MAIN USE CASES The hub should include filters (Job, Pipeline, Created Date Range, Source) so teams can target cleanup on specific data sets—for example, filtering only for "Bulk Import" sources. Primary Use Cases: -- Post-migration cleanup -- Post-bulk-import cleanup -- Ongoing monthly/quarterly database hygiene to ensure accurate analytics and recruiting details.
4
Load More