Staffing agencies in India usually handle candidate data by spreading it: Naukri (and sometimes Shine or Foundit) for applies, email and Google Drive for zips, Excel for the tracker, WhatsApp for CTC and scheduling, and an ATS only after someone is “serious.” The working fix is not another export. It is one person record and one ranked queue per job, with status that follows the human — not the file.
Every CSV you dump into a new sheet is a new copy of someone’s phone number that you may not be able to update or delete later.
| Tool | What it actually holds | Typical failure |
|---|---|---|
| Naukri / boards | Applies, search downloads | Separate from email pile |
| Email + Drive | PDFs, client forwards | No score, no status |
| Excel / Sheets | Names, numbers, “status” | Stale, duplicate rows |
| Real answers, real numbers | Locked in a chat thread | |
| Unified queue | One record, ranked, gated | Work happens here |
The Excel + Naukri + WhatsApp + Drive stack
This stack exists because each tool is good at one moment. Naukri is where volume arrives. Drive is where a client dumps 80 files. WhatsApp is where candidates actually reply. Excel is where a lead asks for a tracker by 6 p.m. None of those tools was designed to be the others. Recruiters become the integration layer, which is why 4–6 hours a day disappear into triage and re-keying rather than judgment.
On a desk with 10+ open requirements, the same person can exist as a Naukri apply, a Drive PDF, and a WhatsApp thread — three memories, zero shared rank.
Duplicates and stale numbers as an operations problem
Duplicates waste call time and hide fit. A recruiter who already rejected a profile on Naukri will still open the emailed CV if the names differ by a middle initial. Stale numbers waste the other half: the 40% of calls that die is not only CTC mismatch; it is also “number does not exist” because the sheet was last cleaned last quarter. WhatsApp delivery failure should update the record the same hour, not wait for a Friday hygiene ritual.
If the key is Resume_Rahul_final2.pdf, you cannot dedupe. Key on mobile and email, then attach files to that person.
“Already spoken / not interested / notice 60” trapped in chat is invisible to the next consultant on the same req.
If only interview-stage people are entered, the ATS never sees the leak. Shortlisting data has to live where the first pass happens.
DPDP makes scattered data a risk, not just a mess
India’s Digital Personal Data Protection Act affects how agencies collect, store, and share candidate personal data. This section is operational context, not a compliance opinion. Use counsel for your facts.
When the same CV sits in a personal Drive, a WhatsApp backup, and three Excel versions, you cannot answer basic questions: where is this person’s data, who can access it, and can you stop using it if they ask? Unification is not only productivity. It is the difference between one system you can govern and a trail of copies you cannot.
Unify the working queue vs export spaghetti
Export spaghetti is the habit of downloading Naukri, dumping to Excel, mailing a subset to a client, then uploading survivors into an ATS. Each hop is a fork. Unify instead: inbound from boards, email, and LinkedIn land in one ranked list; the recruiter works that list; only then does a chosen shortlist move into the system of record. SafalHires is built as that ranking and sourcing layer — it does not need to replace payroll ATS, and it should not become yet another CSV generator that nobody re-imports.
Pick one live req. Ask: can two recruiters see the same people, the same match order, and the same last WhatsApp outcome without opening four apps? If not, you do not have a database. You have a pile with extra steps.
Questions agencies ask
Where do staffing agencies typically store candidate data?
In practice: Naukri (and other boards), a shared inbox or Drive folder of CVs, Excel or Google Sheets for trackers, and WhatsApp for screening and scheduling. The ATS, if it exists, often only sees people who already reached interview.
What goes wrong when candidate data lives in many tools?
Duplicates, stale phone numbers, and no single status. A recruiter can call someone already rejected on another channel, or miss a match sitting in a zip file. Under India’s DPDP Act, scattered personal data is also harder to govern.
Should we unify data or keep exporting CSVs?
Unify the working queue — one ranked list per job with a single person record. CSV exports between Naukri, Excel, and the ATS create spaghetti: every export is a new stale copy. Export for backup or client reports, not as the system of work.
One queue. One record. Then your ATS.
SafalHires ranks Naukri, email, and LinkedIn into a working shortlist so candidate data is not trapped in Drive zips and chat threads.
See how SafalHires works