Candidate Ghosting Is a Response-Time Problem
They didn't lose interest. They took another offer while your submission sat waiting on client feedback, and nobody told them what was happening.
A recruiter finds a strong candidate on Monday. Screens them Tuesday. Submits Wednesday.
The client goes quiet. On the following Thursday the client wants to interview. The recruiter calls the candidate and gets voicemail. Then a text with no reply. Then nothing.
The recruiter writes "ghosted" in the notes and moves on.
The candidate did not ghost. They accepted an offer on Friday from a firm that kept talking to them, and they felt too awkward to say so to someone who had gone silent for eight days.
The asymmetry nobody accounts for
A candidate in an active search is talking to four or five firms. From their side, silence is the default experience of recruitment — applications vanish, recruiters stop replying, and the whole process teaches them that nobody owes them an update.
So when your process goes quiet for a week, it does not read as "the client is deliberating." It reads as the same thing every other agency did. They stop expecting you and start expecting somebody else.
The recruiter, meanwhile, is waiting on client feedback and has nothing to report. Which feels like a good reason not to call.
That is the whole mechanism. Both sides are being reasonable and the placement dies anyway.
Silence is the cause, not the symptom
The fix is the same one that works everywhere else in this business: contact does not require news.
Hi Priya — no decision yet on the Verta role, they're still working through submissions. I'll chase Thursday and let you know either way. Anything change on your end?
Ninety seconds. It keeps the candidate warm, it surfaces the "actually I have another offer" conversation while you can still do something about it, and it makes you the recruiter who talks to people.
That last question matters more than the update. "Anything change on your end?" is how you find out about the competing offer on day three instead of day nine.
Where the process leaks
Submission to client feedback. The longest silence in the process and the one you least control. It is also where most candidates are lost. Manage it by managing the candidate, not by waiting on the client.
After a first interview. The candidate walks out with an opinion and no information. Twenty-four hours of silence here is where enthusiasm cools.
Offer to start date. The most expensive place to lose someone, and the one agencies relax in. A candidate with a signed offer and three weeks of notice is being counter-offered by their current employer and courted by whoever else they were talking to. Weekly contact through notice is not paranoia.
Contractors between assignments. A contractor who rolls off and hears nothing for a month is on somebody else's book. This is the cheapest redeployment there is and it is routinely dropped.
What the system has to do
Ghosting reduction is mostly a set of prompts, which means it lives or dies on whether the software surfaces them.
- Days-since-contact on every active candidate, visible as a sorted list rather than a report someone runs
- A stage-based cadence — submitted candidates get contacted every 3 days, offer-stage every week, and the system flags anything that breaches it
- Automatic acknowledgement on application, because the first silence starts before a human is involved
- A shared record, so a candidate who has already been contacted by one recruiter is not chased by another the same afternoon
- Redeployment prompts firing 30 days before an assignment ends, not after
None of that is exotic. It is why agencies with a properly configured system place more from the same pipeline than agencies working out of an inbox.
What to measure
- Median hours from submission to candidate update. The number most directly tied to candidates going cold.
- Drop-off by stage. Where in your process people disappear. It is rarely where recruiters assume.
- Candidates with no contact in 7 days, as a working list.
- Fall-off rate between offer and start. If this is above a few percent, your post-offer contact is too thin.
The honest caveat
Some candidates genuinely do disappear. People change their minds, take counter-offers, decide to stay put, and some of them will not tell you regardless of how well you communicate. That is the job.
But "ghosted" is doing a lot of work in most agencies' notes, and it hides a process problem behind a candidate-behaviour explanation. The test is simple: before you write it, check when you last contacted them. If the answer is more than a week, that was not ghosting. That was mutual silence, and you started it.
We build the candidate and client pipelines, contact cadences and redeployment prompts behind this for US recruiting and staffing agencies. See how it fits together, or tell us how your desks run.