This FAQ answers the questions HR teams and candidates ask most about candidate ghosting: why it happens, how to stop it, whether automated rejections are acceptable, how fast to respond, who owns communication, and what causes background-check limbo. Every answer ties back to Stop Ghosting Candidates: the HR communication playbook.

• Why do employers ghost candidates?
• How do you stop ghosting candidates?
• Is it rude to send an automated rejection?
• How fast should employers respond to applicants?
• Who is responsible for candidate communication?
• What causes background-check limbo?

Why do employers ghost candidates?

Employers ghost candidates because the work of communicating has no owner and no deadline.

Under a real req load, any message that depends on a human remembering gets dropped. The candidate reaches a stage, the next message waits on someone finding ten spare minutes, and those minutes never arrive. Silence becomes the default. The fix is structural: assign owners and deadlines, then automate. See the full definition of candidate ghosting.

How do you stop ghosting candidates?

Assign an owner and a response-time SLA to every stage, then automate the messages so closure fires on a trigger.

Start by mapping the funnel and finding the stages where nobody owns the next message. Set a candidate communication SLA for each, then build automated rejection emails through your ATS so dispositions close the loop instantly. Automation makes the baseline reliable; the recruiter’s time goes to judgment.

Is it rude to send an automated rejection?

No. A timely automated rejection is far kinder than indefinite silence.

Candidates are explicit: they want the automated message, not the ghosting. The rudeness comes from automation used badly — generic, late, or fired at 2 a.m. A warm, stage-aware rejection sent in business hours is the respectful choice. The rejection email tactics that respect applicants guide shows how.

How fast should employers respond to applicants?

Acknowledge immediately, decide screening within five business days, send post-interview status within forty-eight hours, and finalize within a fixed window after the last interview.

The exact numbers matter less than writing them down and enforcing them through ATS timers. What candidates need is not instant yeses but freedom from silence.

Who is responsible for candidate communication?

The recruiter and the hiring manager, each at different stages.

The recruiter owns acknowledgments, updates, and rejections; the hiring manager owns the decision and feedback. Ghosting thrives in the handoff, so name the owner at every stage and gate requisition closure on the manager logging a decision.

What causes background-check limbo?

A gap between the ATS, HCM, and background-check vendor that nobody owns.

When a check stalls and no escalation rule fires, the candidate sits in silence after already accepting. The fix is integration plus a no-silence escalation path extended into the post-offer stage so a vendor delay produces a message, not a void.

Expert Insight: The thread running through every one of these answers is the same — ghosting is a missing system, not a missing virtue. Stop asking whether your recruiters care enough and start asking whether your process has an owner and a deadline at every stage. Automate the reliable baseline, then let people and AI handle the judgment. That single reframe fixes more ghosting than any amount of communication training.