You stop losing candidates between Naukri, email, and LinkedIn by putting every name on one ranked, de-duplicated list per job — and working only from that list. Duplicate screening, no shared ranking, and replies that die in the channel they arrived in are the three leaks. A unified dashboard is the fix; the product walkthrough is in Naukri, LinkedIn, email — one dashboard for scattered sourcing (SafalHires Fixes, Episode 6). This page is the operational why those leaks happen on an Indian staffing desk, and what to change this week even before a full rollout.
The candidate replied. They replied in LinkedIn. Your tracker still says “awaiting Naukri apply.”
You are not losing them to competitors. You are losing them to tabs
The story agencies tell is “someone else offered faster.” Sometimes that is true. More often the person applied on Naukri, mailed a CV to the generic jobs@ inbox, and accepted a LinkedIn InMail from a second recruiter in the same firm. Three records. Two screens. Zero owner. By Thursday nobody knows who owes a reply. The candidate experiences silence and takes the next call that sounds organised.
That is not a motivation problem. It is what happens when sourcing infrastructure is three products and a spreadsheet. How agencies store that mess is a longer data-governance note: how staffing agencies handle candidate data across multiple tools.
Duplicate screening is the tax nobody budgets for
Without a shared identity, the same CV is a new person every time it arrives. Recruiter A reads the Naukri apply at 11 am. Recruiter B reads the PDF at 4 pm. Both log “screened.” Neither logs the other. You have paid twice for a human hour and still do not have a client-ready paragraph. At 10+ open requirements this tax becomes the whole afternoon. Capacity, not talent, is the constraint: how to manage 10+ open requirements without missing candidates.
Naukri apply, emailed CV, LinkedIn reply. If your tools cannot match on email or phone, you will keep paying the second screen.
Each tab has its own order: newest apply, newest mail, newest message. Fit is never the sort key, so the strong late LinkedIn profile waits behind 40 Naukri mismatches.
A “yes, 30 days notice” in Gmail does not update the Naukri status. The desk keeps calling. The candidate stops answering.
Replies die in the channel they arrived in
Indian hiring runs on WhatsApp after the first touch, but the first touch is still split. LinkedIn replies after 9 pm. Naukri mailers go to spam. The jobs@ inbox is a PDF graveyard. If the owner of the req is only watching Applies, the LinkedIn yes is invisible. Episode 6 shows the channels feeding one list. The operational rule here is simpler: the person who owns the JD owns every inbound for that JD, regardless of tab. If that sentence is not true in your agency, you will keep losing people who already said yes.
A sheet works until the intern forgets to paste. It cannot ingest IMAP, cannot de-dupe a LinkedIn URL against a Naukri apply, and cannot rank overnight inbound. Use it as a temporary SLA log, not as the system of record.
One ranked list, not three memory palaces
The desk needs one place where a name appears once, with a match score, a source tag, and a last-touch. Naukri Hot Vacancy inbound, Chrome-extension profiles, LinkedIn, IMAP, uploads, internal pool — same list. That is the SafalHires model, including a 75,000+ database so last quarter’s almost-hire is not a new stranger. You do not need that product name to accept the design: canonical list first, channels as feeds.
Pick two live JDs. Assign one owner. Every Naukri, mail, and LinkedIn touch for those JDs goes into one tracker the same day — even a crude sheet. Count how many names were already in another tab. That count is your leakage. Then decide whether a ranked dashboard is cheaper than continuing to pay it.
| Leak | What the candidate feels | What the desk should do |
|---|---|---|
| Duplicate screen | Two similar calls, no progress | De-dupe on email / phone before a second read |
| No shared rank | Silence while mismatches get called first | Sort by fit, not by tab |
| Reply in the wrong tab | They answered; you still “awaiting” | One owner, one list, last-touch visible |
What not to copy from the product episode
Episode 6 is the tour: Hot Vacancy posting, extension, LinkedIn connect, IMAP, uploads. This page is the leak list. Do not wait for a perfect integration to enforce ownership and de-dupe. Tools make the list automatic. Process makes the list canonical. Agencies that install a dashboard and still let each recruiter keep a private LinkedIn hunt will leak in the same places with nicer UI.
Questions delivery leads ask on Monday
How do we lose people between Naukri, email, and LinkedIn?
Duplicate screens, no shared ranking, replies stuck in the channel they arrived in. The candidate did not vanish. The desk never reconciled the tabs.
What actually stops the loss?
One ranked, de-duplicated list per job. Channels feed it. Recruiters work from it.
Can a spreadsheet fix this?
Only as a stopgap, and only if it is updated. It will not rank inbound or catch a reply nobody pasted. Volume and headcount kill it.
One list per job. Every channel. Ranked.
SafalHires puts Naukri, email, and LinkedIn on a single shortlist so the person who already said yes is not sitting in the other tab.
Free trial