Zoho Recruit stores every candidate a company has reviewed, along with their resume, skills, and application history. Most of that history stays untouched once a role closes. A recruiter starting a new search rarely goes back to check it, even when a strong fit is already stored in the database.
This expert guide covers what tools Zoho Recruit offers for finding candidates already in the database. It also covers their limitations and how an external AI integration addresses those to automate rediscovery, sourcing, and scoring past qualified candidates.
What Is Talent Rediscovery?
Talent rediscovery involves searching and matching candidates in a Zoho Recruit database with newly opened roles. This includes applicants from closed positions, those in a talent pool, and individuals who advanced partway through a hiring process before a role was filled or put on hold.
By automatically checking stored candidates against new openings, rediscovery streamlines sourcing. This reduces reliance on a recruiter’s memory.
Does Zoho Recruit Provide Candidate Rediscovery?
Partially, Zia (Zoho Recruit's AI assistant) generates Candidate Matches by comparing a job's required skills against the entire candidate database, including the passive talent pool. It assigns each candidate a numeric match score.
A candidate who lacks a must-have skill is excluded from that list. Zia also works in reverse by showing which open jobs best fit a specific candidate's profile. Additionally, Zoho Recruit's Advanced Search allows a recruiter to run Boolean, wildcard, and exact-phrase queries across candidate fields and resume attachments.
Both tools require a recruiter to open them for a specific job or candidate. Zia's score reflects skill overlap rather than a defined set of reasons based on resume evidence. It screens out anyone missing a must-have skill instead of showing them with a lower score.
Neither tool considers how long ago a candidate entered the database, nor do they record a hiring manager's decision on a match.
How to Rediscover Candidates in Zoho Recruit
Zia's Candidate Matches already scans the database and returns a numeric score for a specific job. Connecting Skima AI adds stated reasons tied to resume evidence, date-scoped scans, and a hiring manager feedback loop that Zia does not track.
Below is a 5-step workflow that starts with what Zoho Recruit already provides and builds on it:
Step 1: The Native Path, Start With Zia Candidate Matches
Open a job opening inside Zoho Recruit and select Candidate Matches. Zia compares the job's must-have and nice-to-have skills against every candidate in the database, including the passive talent pool, and returns a ranked list with a numeric match score. Candidates missing a must-have skill get excluded from the list.
This step scans the whole database without a manual keyword search. The score reflects skill overlap rather than stated reasons, though, and a candidate close to qualified but missing one listed skill never appears at all. For a version that explains its scoring and tracks what happens next, Skima AI builds on this next.
Step 2: Connect Your Zoho Recruit Account With Skima AI
Create an OAuth client inside Zoho Recruit's API console, scoped for Modules, Tags, Notes, and Attachments. This connection uses Zoho Recruit's own REST API directly, with no middleware required.
- Read access: candidate details, job opening details, job application data, and resume attachments
- Write access: custom fields, tags, and notes
- Pulled data: candidate contact details, resumes, application stage and source, and job opening requirements for scoring context
- Event triggers: candidate created or updated, and job application created or updated, delivered through Zoho Recruit's webhooks
Step 3: Configure Custom Fields and Confirm the Connection
Create the Skima AI match score and reasons custom fields through Zoho Recruit's UI or Field Meta API, or let Skima AI provision them automatically. Configure webhooks for candidate and job application events. If webhooks are not available, Skima AI falls back to a 10 to 15 minute polling interval instead.
Before rolling this out further, test the connection on two or three job openings. Upload a resume, confirm the Match Score and Reasons appear, submit sample hiring manager feedback, and check that it logs to the notes correctly.
Step 4: Launch Talent Rediscovery Against a Live Requisition
Open the job inside Skima AI, from the Jobs list or from within the job itself. Click the three-dot Actions menu and select Rediscover Candidates. A modal opens with options to narrow the scan: select a specific candidate segment, or leave it open to every synced Zoho Recruit record.
Set the candidate created date range next: All time, Last 6 months, Last 1 year, or a custom window, and optionally check the location filter to restrict the scan geographically. Click Apply. A "Performing Rediscovery" notification appears while the scan works in the background, and turns green with a refresh option once it completes.
Step 5: Review, Filter, and Sync Feedback Back to Zoho Recruit
Refresh the page and open the Rediscovered source tab inside View Candidates. Each match carries a Skima AI score and reason bullets, tagged with a Rediscovery source label. Filter by Industry, Work Mode, Experience Level, Notice Period, Location, and Salary Range to narrow the list.
Once the shortlist looks right, generate a secure, no-login link and send it to the hiring manager. They click thumbs up, thumbs down, or maybe on each name, with an optional comment. Skima AI writes that decision back into Zoho Recruit as a note on the candidate record, keeping the feedback on the record without a second login.
What If Your Zoho Recruit Database Is Messy or Duplicated
Zoho Recruit includes two tools for merging duplicate candidate records. Find & Merge Duplicates searches from a specific candidate's profile using up to six matching fields. Deduplicate searches an entire module in bulk based on a chosen unique field.
Both tools allow a recruiter to select a master record and combine the rest into it, carrying over attachments and activity history.
Both tools require the recruiter to start the search manually. They also limit the actual merge to three records at a time, even if Deduplicate shows a longer list of matches. No potential duplicate is flagged on its own. A recruiter only discovers one by running Find & Merge or Deduplicate directly.
Skima AI treats this as ongoing maintenance rather than something a recruiter has to schedule. It first matches on email, phone, or LinkedIn URL, then checks name, location, and company together as a backup signal.
When a match is found, a field comparison modal displays differences across Name, Title, Company, Location, Email, Phone, and LinkedIn, tagging each mismatched field as Differs.
A recruiter can choose which values to keep and merge the records, or add the profile as new if the two genuinely differ. Every resolved case is logged under the Duplicates tab, divided into In Database, From Uploads, and Resolved sub-tabs for later audit.
5 Benefits of Candidate Rediscovery with Skima AI in Zoho Recruit
A documented 30-day pilot with Zoho Recruit reported 5 specific changes once Skima AI starts scoring a company's stored candidate history:
- Faster Time-to-Screen: Rediscovered candidates arrive already matched and scored against the open role, reducing time-to-screen by 58% compared to starting a fresh search.
- Interviews Double From the Shortlist: The same pilot saw interviews booked from the shortlist double compared to the prior process.
- Reasons Behind Every Score: Every rediscovered match carries a 0 to 100 score with reason bullets tied to resume evidence, where Zia's Candidate Matches returns a score alone.
- One Candidate Record, No New Login: Match scores, reasons, and tags write directly to the same candidate fields and notes a recruiter already checks inside Zoho Recruit.
- Manager Feedback That Sticks: Hiring manager satisfaction rose 24 points on NPS in the same pilot, tied to a feedback link that logs every decision instead of a verbal note.
5 Best Practices to Rediscover Talent in Zoho Recruit
A few habits decide whether this connection turns into a steady source of candidates or a one-time setup:
- Start With Zia Candidate Matches: Use Zia's built-in scoring to catch obvious matches for a specific job first. Move to a scoped Skima AI scan when a stated reason, a date-limited pool, or a tracked hiring manager decision matters.
- Automate Rediscovery on Job Creation: Skima AI's setting under Preferences and General starts a database scan the instant a new job gets created inside the connected account, so no requisition goes live without a first look at existing history.
- Reverse Search Across Client Requisitions: A staffing agency running several client requisitions at once often has a candidate who did not fit one client's role but suits another. Reverse Search starts from that candidate's profile and returns every open job they match, ranked by score.
- Segment Scans by Candidate Created Date: Choose a 6-month or 1-year window when a role calls for someone recently active. Widen to all time for a niche or hard-to-fill role where the applicant pool has stayed thin for years.
- Review the Duplicates Tab Instead of Waiting to Deduplicate: Since Zoho Recruit's own merge tools only run when a recruiter starts them, checking the In Database sub-tab on a set schedule catches overlap that would otherwise sit unresolved.
Pilot Candidate Rediscovery in Zoho Recruit Now
For a company with a multi-year history in Zoho Recruit, piloting Skima AI can deliver a strong ROI. Begin with two or three live requisitions, preferably roles with a history of multiple fills to create a robust scoring pool.
Next, connect Skima AI to Zoho Recruit, set up the Match Score and Reasons fields, and test the connection on the selected job openings. Skima AI's integration recommends starting small: test initially, then go live on pilot roles while monitoring progress through weekly dashboards along with 15-day and 30-day performance reports.
Observe how many rediscovered candidates reach interviews and gather feedback from hiring managers on the shortlist link. Skima AI's documented pilot revealed a 58% reduction in time-to-screen, a doubling of interviews from the shortlist, and a 24-point increase in hiring manager satisfaction on NPS. Expanding to additional requisitions can then be confidently based on these results.
Frequently Asked Questions
1. Does Zoho Recruit have a built-in talent rediscovery feature?
Partially, Zia's Candidate Matches scans the entire database, including the passive talent pool, and scores candidates against a job's required skills, but it excludes anyone missing a must-have skill and gives no stated reason for its score.
2. How do I rediscover candidates in Zoho Recruit?
Start with Zia's Candidate Matches for a scored list tied to one job. For an explainable, auditable version, connect Skima AI through Zoho Recruit's API, configure custom fields for Match Score and Reasons, then launch Talent Rediscovery on a live requisition.
3. What are the benefits of candidate rediscovery in Zoho Recruit?
Based on a documented 30-day pilot, rediscovered candidates cut time-to-screen by 58% and doubled interviews from the top-10 shortlist. Matches carry a score with stated reasons, and hiring manager satisfaction rose 24 points on NPS.
4. Is Skima AI safe to integrate with Zoho Recruit for talent rediscovery?
Yes. Skima AI scores candidates using resume-based evidence only, with no automatic rejections, and logs every hiring manager decision and shortlist action for audit. Data stays encrypted in transit and at rest, backed by a signed Data Processing Agreement.
5. Is candidate rediscovery useful for Zoho Recruit's typical customers?
Yes, especially for staffing agencies juggling several client requisitions at once, where a candidate who does not fit one client's role often suits another. The value grows with the size of the closed-role history behind the account.
