You Have 5,000 Candidates On File. How Many Have Heard From You This Year?

Active applicants are the small half of the talent pool

Any talent team that has been hiring for a couple of years is sitting on a large database and using a small fraction of it. The people who applied this week get attention because an ATS puts them in a queue. Everyone else — the applicant from last March, the referral who was not ready to move, the candidate who reached the final round and lost to someone marginally stronger, the person who filled in a form at a campus event — is technically in the system and practically invisible.

Nurture is what converts a database into a pipeline

Candidate relationship management is the practice of treating that dormant majority as a relationship rather than a record. It is a monthly touch that is worth opening, a job alert that matches what somebody actually said they wanted, and an outreach message that references the conversation you had eleven months ago rather than opening cold. None of that is possible in a system whose data model starts at "applied".

The payoff is measured in time-to-shortlist. A team that has kept its pool warm can answer a new requirement from people who already know the company, already replied to a recruiter once, and do not need three days of persuasion before a first call.

The reply happens where the candidate already is

Recruiting email in India competes with a full inbox and loses. WhatsApp does not have that problem: the message is read the same day, and replying costs a candidate one thumb rather than a laptop and a spare twenty minutes. For a passive candidate who is mildly curious but not job-hunting, that difference in friction is the whole conversion.

Consent is what keeps the channel usable

A channel this effective stops working the moment it is abused, which is why the consent model matters as much as the send. HelloGrowthCRM runs candidate outreach on approved WhatsApp Business API templates, records how each candidate entered the database and what they agreed to, and enforces opt-out at the segment level. A candidate who leaves a list is excluded from the next broadcast because the segment excludes them, not because a recruiter remembers to.

Under the DPDPA, a talent pool is personal data held for a stated purpose. Having the consent state, the source and the message history on the record is what turns a data-principal request from a week of inbox archaeology into a lookup.

The internal shortlist comes first

Most requirements are opened with a purchase: job-board credits, a database subscription, a sourcing tool. That spend is often buying access to people who are already in the company's own database, entered there by a previous campaign that nobody indexed against this role.

What scoring actually does

AI candidate scoring runs the job description against every profile in the pool and returns a ranked list with a reason attached to each score. It catches the two cases keyword search reliably gets wrong: the candidate who has done exactly this work for four years but described it in different vocabulary, and the candidate whose CV contains the keyword once, inside a list of tools they once installed.

The output is a ranking aid, not a decision. A recruiter still reads the shortlist and still makes the call — the difference is that the reading starts from a list of thirty ranked profiles rather than four hundred unsorted ones, and that the external sourcing budget is spent on the genuine gap instead of on re-acquiring people the company already had.

What Beamery, Gem and Avature sell

The category was defined by enterprise talent-CRM vendors, and they are good at it. They also share a commercial shape: pricing is quoted rather than published, the product is bought with an implementation project attached, and the outreach model was designed around email and LinkedIn because that is what works in the markets they were built for. For a large global talent function with a dedicated operations team, that is a reasonable trade.

What an India-first talent team needs instead

An eight-person talent team in Pune or Gurugram is making a different set of trades. They need a published price they can put in a budget line, a start date measured in minutes rather than weeks, no seat minimum that forces them to buy licences for people who will not log in, and outreach on the channel their candidates read. HelloGrowthCRM is ₹899 per user per month, has a free plan that carries a real candidate database rather than a trial countdown, and puts WhatsApp at the centre of candidate communication rather than at the edge.

It is not the same product as an enterprise talent CRM and does not pretend to be. It is the version of the category that an India-priced, WhatsApp-first talent team can actually run.

Alongside the ATS, not instead of it

If you are running Naukri RMS, Zoho Recruit, Keka or an in-house applicant tracker, keep it. The formal hiring process — the application, the interview record, the offer — has a home and does not need moving. What has no home today is everything that happens before an application exists and everything that happens after a rejection. That is the layer this page is about.

Alongside agency recruitment, if you run both

Teams that also work with staffing partners, or agencies reading this from the other side, will want CRM for recruitment agencies, which covers the second pipeline an agency runs: job orders per client, shortlist turnaround, and placement-fee collection. The candidate-side features described here are shared between the two; the client-side pipeline is not.