Skip to content
Hiring teams6 min read

How to Stop Ghosting Candidates

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

Piles of unanswered resumes turn into a clear pipeline that sends update messages back to candidates
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

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 unanswered applications piled up one at a time.

This guide covers why ghosting happens, what 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

Criteria's 2026 Candidate Experience Report, based on more than 2,500 job seekers, found that 53% had been ghosted by an employer in the past year. That figure was 48% in 2025 and 38% in 2024.

Greenhouse's December 2024 State of Job Hunting report found that 61% of job seekers had been ghosted after a job interview, up from 52% in April 2024. 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. It usually comes from four causes.

The first is volume. When a role gets 400 applications, writing to each person by hand is several days of work nobody has budgeted for. Slow first reviews make it worse, which is why reducing time to hire and fixing silence usually go together.

The second is that no one owns the message. The recruiter assumes the hiring manager will close the loop after the final interview, and the hiring manager assumes the recruiter will.

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, so they say nothing. A short, neutral message with no specific reason 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 or budget review puts a role on hold, the pipeline goes quiet because nobody knows what to tell candidates, and by the time the decision comes, writing to people feels awkward.

A letter rack with one slot for each of the four messages in the plan below. In a team that only sends the automated confirmation, the other three slots stay empty: the screening decline, the decline after an interview and the update when a role closes. Point at a slot to lift out its message, or the one nobody wrote.

What it costs you

CareerPlug's February 2025 research found that poor experiences, such as a lack of communication, led 26% of job seekers to decline offers in 2024. In the same research, 66% said a positive experience influenced their decision to accept.

The longer-term cost is what the CandE benchmark calls candidate resentment: candidates who had a poor experience and won't engage with that business again. In June 2025 Survale, which runs the benchmark, put the North American resentment rate at 15%.

The better employers show the upside. Survale's Kevin Grossman reported that the highest rated CandE winners give 44% more candidates feedback than all employers. When employers gave candidates specific feedback, their willingness to refer others rose 69%.

The plan: four stages, four messages

Each message has a timing target and one person's name next to it.

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, so pick numbers your team can hit. Survale reported that 69% of employers in the CandE research were focused on timely dispositions within one to two weeks, and a 10 business day target sits inside that range.

One pad per stage, one sheet per business day the plan allows before the message goes out: 0 for the automated confirmation, 10 for a decline after screening, 5 after an interview and 5 when a role closes or goes on hold. Point at a pad to fan out its days.

The templates below are short on purpose. 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 telling the candidate when to expect an answer.

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.

Stage 2: not moving forward after screening

This message goes to the most 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'd be glad to see your application for future roles that match your experience.

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

Stage 3: after an interview, not moving forward

This message needs more care, because the candidate has given you time and prepared for a conversation with your team. Send it within a week of the final interview, signed by the person the candidate met, and offer a line of feedback tied to the job's requirements when you safely can.

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].

We've decided to offer the role to another candidate whose experience with [job requirement] was a closer fit for the team right now.

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]

Keep the feedback line to the job's stated requirements and what your interview notes support. If you can't give feedback at all, remove that clause and keep the rest.

Stage 4: role closed or on hold

When a role is paused or canceled, everyone still in the pipeline needs to hear about it, including people you had not reviewed yet.

For a role on hold:

Hi [first name],

The [role] position at [company] 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.

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, so put it in the recruiter's calendar.

Who owns each message, and how to make it stick

Write ownership 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, even if the recruiter sends it.

Then build these habits:

  1. Block 30 minutes every Friday in the recruiter's calendar to clear declines.
  2. Add "candidates to close" as a standing line in the weekly hiring sync.
  3. Don't archive a closed job until every candidate on it has a final status and a message sent.
  4. Track one metric: the number of candidates with no status change for more than 14 days. If it grows, someone has dropped a stage.
A card file for one example role, one card per candidate, placed by the days since their status last changed. The 3 cards past the 14-day tab are the number to track. Point along the file to let days pass with nobody clearing it and watch more cards cross the tab.

A note on automated screening and silence

Automated screening can make ghosting worse. The tool moves hundreds of people out of the pipeline in a minute, yet nothing reaches the candidate unless you set it up to.

In HireRabbit.AI, moving a candidate to Shortlisted, Selected or Rejected sends the candidate an email. Auto-reject, which only runs on a cut-off score you set and a batch you confirm, sends no email, so you still owe those candidates the Stage 2 message. You can see how those stages work on the product page.

A four-week rollout

In week one, draft the five templates in your own voice, send them to counsel and agree on timing targets. In week two, set up the Stage 1 confirmation for every open role and check whether each bulk action and stage change emails the candidate.

In week three, clear the backlog: message every candidate with no status change for more than 14 days. In week four, add "candidates to close" to your hiring syncs and start tracking the 14-day number.

Put this into practice.

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