Why do candidates ghost recruiters?
Mostly because the employer went quiet first. Of the 956 candidates Selection Lab surveyed in September 2026, 77% of those who stopped replying themselves name a reason that is essentially about speed. The job, the terms and the discomfort of saying no together account for 23%. Candidate ghosting is a response time problem, not an employer branding problem.
Most recruiters have the same reflex when a candidate stops answering. Unreliable, no manners, that generation. The research we published last week turns that reflex around. Ask candidates why they stopped replying the last time and you rarely hear anything about the job. You hear about waiting.
This article is the practical follow-up to that research. The research shows what goes wrong. Below is how you build a process in which a candidate never goes more than a few days without hearing something, even with three hundred applicants in the system at once.
The numbers first. 31% of the candidates who stopped replying name an employer who stopped first as their main reason. 21% name slow or unclear communication. Together that is 52% for whom the employer's silence came before their own. Add the 26% who had accepted another offer in the meantime and you arrive at 77% of reasons that are essentially about speed.
Set that against the reasons that are about you as an employer. 11% lost interest in the role or the company, 10% dropped out over the terms of employment. Five times as many candidates drop out over how you communicate as over what you project.
And the explanation recruiters give most often, that saying no feels awkward and candidates disappear to avoid it, barely shows up. Six candidates in the entire survey named it.
What that means is uncomfortable but useful. The candidate who ghosts you is, in most cases, a candidate who was already waiting for you. Not for a better salary or a nicer job ad, but for a message.
Almost nobody decides to keep a candidate waiting. It happens because the process allows it. Walk through a standard process and you can see where the silence starts.
| Stage | What the candidate hears | Where the silence sits |
|---|---|---|
| Application received | An automatic confirmation | Then nothing, until someone opens the pile |
| Screening | Usually nothing | The recruiter works through the pile when there is time, the candidate does not know whether they are still in the running |
| Interview invitation | An invitation, often after days of emailing about a date | The hiring manager's calendar and the candidate's do not line up |
| After the interview | "We'll get back to you" | Internal alignment, a second candidate still to come, the decision maker on holiday |
| Decision | An offer or a rejection, if it comes | Rejected candidates often hear nothing at all |
The pattern is the same every time. The candidate hears something at the moment you need something from them. Between those moments they hear nothing, and that is exactly where they start to wonder whether they are still in the picture. How short that patience is, we know from the earlier research in this series.
In August 2026 we asked 962 candidates what they consider an acceptable wait for a response to their application. 51.8% say three days or less. 20.1% expect to hear something within 24 hours. And it is not the youngest candidates who are the most impatient, but the forty-somethings. Among 36 to 45 year olds, 65.5% name three days as the limit.
Three days is shorter than most screening rounds take. That is exactly the point. The norm candidates apply no longer fits a process in which the recruiter replies when they get around to it. If you want to stay inside those three days, you have to decouple the response from the availability of people.
You do not need to rebuild your process. You need to add three things that are usually missing from it.
Agree per stage how long a candidate waits at most for a substantive reply, and record it in your ATS. For example, three days after applying a candidate knows whether they are through, two days after the interview they hear what the next step is. When the standard is exceeded, an interim message goes out automatically. The point is not that you always stay inside the standard. The point is that the candidate notices when you exceed it, and so do you.
Most silence in a process is not a decision but a delay. The hiring manager is on holiday, the second candidate is not coming until next week, the decision maker wants to sleep on it. Then send exactly that. A two-sentence message, we are not there yet and you will hear from us by Friday at the latest, removes the doubt without promising anything you cannot deliver. A candidate who knows where they stand waits longer than a candidate who has to guess.
The same goes for the rejection. Whoever sends nothing after a decision is the employer in the research who went quiet first. How to stop ghosting candidates is covered in an earlier article.
The longest wait sits between the application and the first real contact, because that step depends on when a recruiter has time to open the pile. You can remove that dependency. A conversational screening via WhatsApp or web chat, such as SmartChat, asks the first questions at the moment the candidate applies, books an interview straight away if there is a fit and sends a proper rejection if there is not. The candidate hears something substantive within minutes instead of days. The recruiter opens the pile once it has already been sorted.
The first two changes cost no tooling, only agreements. The third does require a tool, and it is also the only one that closes the biggest gap.
The research has a second layer. Of the candidates who stopped replying themselves, 65% had been ghosted before. Those who had never been ghosted stopped replying themselves in 45% of cases. Those who experienced it more than once, in 61%. The behaviour recruiters see as unreliable was, in two thirds of cases, learned at another employer. What candidates do next is in the earlier research on ghosted candidates.
That makes ghosting not an incident between you and one candidate, but a way of working the profession has taught itself. It also means that most candidates who come to you already expect you to go quiet too. Whoever does not, stands out. Not with a better job ad, but with a message on day two.
Want to see what a screening looks like that replies within minutes instead of days? Book a demo and we will walk through your own process at the points where the silence sits.
Mainly because the employer went quiet first or replied too slowly. In Selection Lab research among 956 candidates (September 2026), 31% of candidates who stopped replying name an employer who stopped first, 21% slow or unclear communication and 26% another offer already accepted. Together, 77% of the reasons are about speed.
Within three days. In Selection Lab research among 962 candidates (August 2026), 51.8% name three days or less as an acceptable wait for a response to their application, and 20.1% expect to hear something within 24 hours. Among 36 to 45 year olds, 65.5% put the limit at three days.
By taking the waiting time out of your process. Agree a maximum response time per stage and record it in your ATS, send an interim message as soon as a decision takes longer, and do not let the first contact depend on a recruiter's calendar, for example with a conversational screening via WhatsApp or web chat that replies right after the application.
No. In Selection Lab's response time research, 36 to 45 year olds are the least patient group, not the youngest. And of the candidates who stopped replying themselves, 65% had been ghosted before. The behaviour is learned in earlier application processes, not tied to a generation.
.png)
Why do candidates ghost recruiters?
Mostly because the employer went quiet first. Of the 956 candidates Selection Lab surveyed in September 2026, 77% of those who stopped replying themselves name a reason that is essentially about speed. The job, the terms and the discomfort of saying no together account for 23%. Candidate ghosting is a response time problem, not an employer branding problem.
Most recruiters have the same reflex when a candidate stops answering. Unreliable, no manners, that generation. The research we published last week turns that reflex around. Ask candidates why they stopped replying the last time and you rarely hear anything about the job. You hear about waiting.
This article is the practical follow-up to that research. The research shows what goes wrong. Below is how you build a process in which a candidate never goes more than a few days without hearing something, even with three hundred applicants in the system at once.
The numbers first. 31% of the candidates who stopped replying name an employer who stopped first as their main reason. 21% name slow or unclear communication. Together that is 52% for whom the employer's silence came before their own. Add the 26% who had accepted another offer in the meantime and you arrive at 77% of reasons that are essentially about speed.
Set that against the reasons that are about you as an employer. 11% lost interest in the role or the company, 10% dropped out over the terms of employment. Five times as many candidates drop out over how you communicate as over what you project.
And the explanation recruiters give most often, that saying no feels awkward and candidates disappear to avoid it, barely shows up. Six candidates in the entire survey named it.
What that means is uncomfortable but useful. The candidate who ghosts you is, in most cases, a candidate who was already waiting for you. Not for a better salary or a nicer job ad, but for a message.
Almost nobody decides to keep a candidate waiting. It happens because the process allows it. Walk through a standard process and you can see where the silence starts.
| Stage | What the candidate hears | Where the silence sits |
|---|---|---|
| Application received | An automatic confirmation | Then nothing, until someone opens the pile |
| Screening | Usually nothing | The recruiter works through the pile when there is time, the candidate does not know whether they are still in the running |
| Interview invitation | An invitation, often after days of emailing about a date | The hiring manager's calendar and the candidate's do not line up |
| After the interview | "We'll get back to you" | Internal alignment, a second candidate still to come, the decision maker on holiday |
| Decision | An offer or a rejection, if it comes | Rejected candidates often hear nothing at all |
The pattern is the same every time. The candidate hears something at the moment you need something from them. Between those moments they hear nothing, and that is exactly where they start to wonder whether they are still in the picture. How short that patience is, we know from the earlier research in this series.
In August 2026 we asked 962 candidates what they consider an acceptable wait for a response to their application. 51.8% say three days or less. 20.1% expect to hear something within 24 hours. And it is not the youngest candidates who are the most impatient, but the forty-somethings. Among 36 to 45 year olds, 65.5% name three days as the limit.
Three days is shorter than most screening rounds take. That is exactly the point. The norm candidates apply no longer fits a process in which the recruiter replies when they get around to it. If you want to stay inside those three days, you have to decouple the response from the availability of people.
You do not need to rebuild your process. You need to add three things that are usually missing from it.
Agree per stage how long a candidate waits at most for a substantive reply, and record it in your ATS. For example, three days after applying a candidate knows whether they are through, two days after the interview they hear what the next step is. When the standard is exceeded, an interim message goes out automatically. The point is not that you always stay inside the standard. The point is that the candidate notices when you exceed it, and so do you.
Most silence in a process is not a decision but a delay. The hiring manager is on holiday, the second candidate is not coming until next week, the decision maker wants to sleep on it. Then send exactly that. A two-sentence message, we are not there yet and you will hear from us by Friday at the latest, removes the doubt without promising anything you cannot deliver. A candidate who knows where they stand waits longer than a candidate who has to guess.
The same goes for the rejection. Whoever sends nothing after a decision is the employer in the research who went quiet first. How to stop ghosting candidates is covered in an earlier article.
The longest wait sits between the application and the first real contact, because that step depends on when a recruiter has time to open the pile. You can remove that dependency. A conversational screening via WhatsApp or web chat, such as SmartChat, asks the first questions at the moment the candidate applies, books an interview straight away if there is a fit and sends a proper rejection if there is not. The candidate hears something substantive within minutes instead of days. The recruiter opens the pile once it has already been sorted.
The first two changes cost no tooling, only agreements. The third does require a tool, and it is also the only one that closes the biggest gap.
The research has a second layer. Of the candidates who stopped replying themselves, 65% had been ghosted before. Those who had never been ghosted stopped replying themselves in 45% of cases. Those who experienced it more than once, in 61%. The behaviour recruiters see as unreliable was, in two thirds of cases, learned at another employer. What candidates do next is in the earlier research on ghosted candidates.
That makes ghosting not an incident between you and one candidate, but a way of working the profession has taught itself. It also means that most candidates who come to you already expect you to go quiet too. Whoever does not, stands out. Not with a better job ad, but with a message on day two.
Want to see what a screening looks like that replies within minutes instead of days? Book a demo and we will walk through your own process at the points where the silence sits.
Mainly because the employer went quiet first or replied too slowly. In Selection Lab research among 956 candidates (September 2026), 31% of candidates who stopped replying name an employer who stopped first, 21% slow or unclear communication and 26% another offer already accepted. Together, 77% of the reasons are about speed.
Within three days. In Selection Lab research among 962 candidates (August 2026), 51.8% name three days or less as an acceptable wait for a response to their application, and 20.1% expect to hear something within 24 hours. Among 36 to 45 year olds, 65.5% put the limit at three days.
By taking the waiting time out of your process. Agree a maximum response time per stage and record it in your ATS, send an interim message as soon as a decision takes longer, and do not let the first contact depend on a recruiter's calendar, for example with a conversational screening via WhatsApp or web chat that replies right after the application.
No. In Selection Lab's response time research, 36 to 45 year olds are the least patient group, not the youngest. And of the candidates who stopped replying themselves, 65% had been ghosted before. The behaviour is learned in earlier application processes, not tied to a generation.
