Skip to content
Hiring teams11 min read

How to Stop Ghosting Candidates When Hundreds Apply: A Communication Plan with Message Templates

Hundreds of applicants and no time to reply? A stage-by-stage plan for candidate messages, with timing targets, owners and short templates.

By the HireRabbit.AI team · Published · Last updated

On this page
  1. How big the problem is
  2. Why good teams end up ghosting people
  3. What it costs you
  4. The plan: four stages, four messages
  5. Who owns each message, and how to make it stick
  6. A note on automated screening and silence
  7. A four-week rollout
  8. Common questions

Say you run talent at a 300-person company. Each role gets a few hundred applicants, your two recruiters can't reply to all of them, and candidates have started mentioning the silence in reviews of your company. Nobody on the team decided to ignore people. The silence built up one unanswered application at a time.

This guide is for teams in that spot. It covers why ghosting happens, what the research says it costs, and a communication plan you can put in place this month: four stages, a short template for each, a timing target and a named owner.

How big the problem is

Candidates are hearing back less often than they did two years ago, and the numbers come from several independent surveys.

Criteria's 2026 Candidate Experience Report, based on more than 2,500 job seekers and covered by Fortune in March 2026, found that 53% of job seekers had been ghosted by an employer in the past year. That figure was 48% in 2025 and 38% in 2024, so it has risen for three years in a row.

Ghosting after an interview is common too. Greenhouse's 2024 State of Job Hunting report (December 2024, 2,500 workers in the US, UK and Germany) found that 61% of job seekers had been ghosted after a job interview, up from 52% in April 2024. The rate was higher for underrepresented candidates, at 66%, than for white candidates, at 59%. When Greenhouse asked what candidates wanted improved, 42% named stronger recruiter communication. The post-interview figure is the one that should worry hiring teams most, because those candidates had already spent an hour or more talking to someone at the company.

Why good teams end up ghosting people

Almost nobody ghosts on purpose. The causes are usually some mix of these four.

The first is volume. When a role gets 400 applications, writing to each person by hand is several days of work that nobody has budgeted for. The recruiter answers the candidates who are still in the running, and the rest wait for a reply that never comes.

The second is that no one owns the message. The recruiter assumes the hiring manager will close the loop after the final interview. The hiring manager assumes the recruiter will. The coordinator who scheduled the call has moved on to the next role. Each person has a reasonable belief that someone else sent it.

The third is fear of saying the wrong thing. Many HR teams worry that any reason given in a rejection could be quoted back to them in a complaint, so they say nothing. The worry is understandable, but silence has its own cost: a candidate who writes back angry, or posts about it. A short, neutral message that gives no specific reason ("we've decided to move forward with other candidates") is far kinder than nothing. Have your employment counsel review your templates once, then reuse them.

The fourth is roles that stall. A hiring freeze, a budget review or a reorganization puts a role on hold, and the whole pipeline goes quiet because nobody knows what to tell candidates yet. Weeks pass. By the time the decision comes, writing to people feels awkward, so it doesn't happen.

What it costs you

Ghosting has a cost you can see in your hiring numbers and a cost that shows up later in your brand.

CareerPlug's candidate experience research (February 2025) found that poor experiences, such as a lack of communication or unclear job expectations, led 26% of job seekers to decline offers in 2024. The same research found that 66% of candidates said a positive experience influenced their decision to accept. If you are competing for the same few strong people as three other companies, the one that kept candidates informed has an edge.

The longer-term cost is what the CandE benchmark research calls candidate resentment: the share of candidates who had a poor experience and say they won't engage with that business and brand again. In June 2025 Survale, which runs the CandE benchmark, put the North American resentment rate at 15%. Depending on your business, those people may be customers, future applicants or the friends of future applicants. In a November 2025 analysis of the same research, Survale's Kevin Grossman listed "Poor or No Communication / Ghosting" among the top negative themes candidates raised.

The same research points at what works. Grossman reported that the highest rated CandE winners give 44% more candidates feedback than all employers, and have 40% fewer candidates still waiting to hear about next steps two months or more after they applied. Survale's January 2026 summary of the 2025 benchmark found that when employers gave candidates specific feedback, the candidates' willingness to refer others (measured as an NPS rating) rose 69%.

The plan: four stages, four messages

The fix is four messages, a timing target for each, and one name next to each message. Here is the whole plan in one table.

StageMessageTiming targetOwner
Application receivedConfirmation with what happens next and whenImmediately (automated)Recruiter sets it up once per role
Not moving forward after screeningShort, neutral declineWithin 10 business days of applyingRecruiter
After an interview, not moving forwardPersonal decline, with optional brief feedbackWithin 5 business days of the last interviewHiring manager writes or approves; recruiter sends
Role closed or on holdStatus update to everyone still in the pipelineWithin 5 business days of the decisionRecruiter, with hiring manager sign-off

The timing targets are ours. Pick numbers your team can actually hit and write them into the job kickoff notes. Survale's January 2026 summary reported that 69% of employers in the CandE research were focused on timely dispositions within one to two weeks, so a 10 business day target for early-stage declines sits inside that range.

The templates below are deliberately short. They avoid giving reasons at the early stages and don't promise things you can't control. They are a starting point; they are not legal advice, so ask your counsel to review the wording before you use it.

Stage 1: application received

Most applicant tracking systems can send this automatically. The part teams skip is the second sentence, which tells the candidate when to expect an answer. That one sentence prevents a lot of follow-up emails.

Hi [first name],

Thanks for applying for the [role] position at [company]. We've received your application and our team is reviewing it now.

We aim to let every applicant know where they stand within two weeks. If you're selected for an interview, you'll hear from [recruiter name] directly.

Thanks, [Recruiter name], [company]

Only promise two weeks if you can meet it. If your process is slower, say three weeks and hit it.

Stage 2: not moving forward after screening

This message goes to the largest number of people, so it is the one most likely to slip. Send it in batches. A recruiter who clears declines every Friday afternoon will stay ahead of the queue on most roles.

Hi [first name],

Thank you for your interest in the [role] role at [company]. We've reviewed your application, and we won't be moving forward with it for this position.

We had a large number of applicants and had to make some difficult choices. We'd be glad to see your application for future roles that match your experience.

Best wishes with your search, [Recruiter name], [company]

Keep it that short. With hundreds of applicants, a specific reason for each one is more wording for counsel to worry about, and it usually invites debate without helping the candidate much.

Stage 3: after an interview, not moving forward

This message deserves more care. The candidate has given you time, possibly taken a day off work, and prepared for a conversation with your team. A form email a month later reads as disrespect, and silence is worse: remember that 61% of job seekers in the Greenhouse survey had been ghosted after an interview.

Three things improve this message. Send it within a week of the final interview. Have the person the candidate actually met (the hiring manager or the recruiter who ran the process) put their name on it. And when you can do so safely, offer one or two lines of feedback tied to the job's requirements.

Hi [first name],

Thank you for taking the time to interview for the [role] role and for talking with [interviewer names]. We enjoyed learning about your work on [specific topic from the interview].

After a lot of discussion, we've decided to offer the role to another candidate whose experience with [job requirement] was a closer fit for what the team needs right now.

This was a close decision. If you're open to it, we'd like to keep in touch about future openings on the team.

Thank you again, [Hiring manager name], [company]

A few notes on feedback. Tie it to the job's stated requirements, never to anything personal. Keep it to what your interview notes actually support. If a candidate replies asking for more detail, a 15-minute call with the recruiter is often better than a long email, and your counsel can tell you what your company is comfortable putting in writing. If you can't give feedback at all, remove that clause and keep the rest.

Consider a phone call for final-round candidates in senior roles or internal applicants. A five-minute call followed by a short email costs you very little.

Stage 4: role closed or on hold

When a role is paused or cancelled, everyone still in the pipeline needs to hear about it, including people you had not reviewed yet. This message is easy to forget, because nobody made a decision about any individual candidate.

For a role on hold:

Hi [first name],

We wanted to give you an update on the [role] position at [company]. The role has been put on hold while we review our hiring plans, and we don't expect to make a decision before [month].

We'll write to you again by [date] either way. If you'd prefer to withdraw in the meantime, just reply to this email and we'll update your application.

Thanks for your patience, [Recruiter name], [company]

For a role that has been closed:

Hi [first name],

Thank you for applying for the [role] role at [company]. We've decided not to fill this position at this time, so we've closed the search.

This decision was about the role and was not a reflection of your application. We'd be glad to hear from you if a future opening fits your experience.

Best wishes, [Recruiter name], [company]

If you send the "on hold" note, the date you give becomes a new commitment. Put it in the recruiter's calendar the day you send it.

Who owns each message, and how to make it stick

Ownership is where these plans usually fall apart, so write it down for each role during the kickoff meeting. A simple rule: the recruiter owns every message before the first interview and every status update, and the hiring manager owns the decision message after interviews. The recruiter can still send it, but the hiring manager approves the wording and the timing.

Then build these habits.

  1. Block a weekly slot in the recruiter's calendar to clear declines. Thirty minutes on Friday is enough for most roles once the templates exist.
  2. Add "candidates to close" as a standing line in the weekly hiring sync. The hiring manager sees how many people are waiting, and the number tends to go down once it's visible.
  3. Track one metric: the number of candidates with no status change for more than 14 days. If it grows, someone has dropped a stage.
  4. When a role closes, don't archive the job until every candidate on it has a final status and a message sent.

A note on automated screening and silence

Automated screening can make ghosting worse if you are not careful. The tool moves hundreds of people out of the pipeline in a minute, and it feels like the work is done. But nothing has been sent to the candidate unless you configured it.

This is worth checking in whatever system you use. In HireRabbit.AI, for example, moving a candidate to Shortlisted, Selected or Rejected sends the candidate an email, but auto-reject (which only runs on a cut-off score you set and a batch you confirm, and can be undone) sends no email at all. That means you still owe those candidates a message, and the Stage 2 template above is a good fit. You can see how those stages work on the product page.

A four-week rollout

In week one, draft the five templates from this guide in your own voice and send them to counsel for review. Agree on the timing targets with your recruiters and hiring managers, and write them down.

In week two, set up the Stage 1 confirmation in your applicant tracking system for every open role. Then go through each bulk action and stage change in the system and write down whether it emails the candidate. You may find more silent paths than you expected.

In week three, clear the backlog. Pull every candidate across open and recently closed roles who has had no status change for more than 14 days, and send them the right message. It can be a few hundred people and takes one or two afternoons with templates.

In week four, add the "candidates to close" line to your hiring syncs and start tracking the 14-day number every week. After a month you'll know whether the plan is holding.

Common questions

Do we really have to reply to every applicant?

In our view, yes, at least once with a final answer. The Stage 1 and Stage 2 messages can be mostly automated or batched, so the cost per candidate is small. The candidates you are most likely to lose are the strong ones who hear from a competitor first.

Should we give feedback to everyone we reject?

Not at the application stage, where the volume is too high and the risk of a poorly worded reason is real. After interviews, brief feedback tied to the job's requirements is worth offering when your counsel is comfortable with it. The CandE research above suggests it pays off in referrals.

What if a candidate argues with the decision?

Thank them, restate that the decision is final for this role, and invite them to apply for future openings. Keep the reply short and neutral, and loop in HR or counsel if the message raises a complaint.

Sources

Put this into practice.

Free during invite-only early access. All you need is a work email, and a person reviews every request.