How to stop ghosting candidates (and why it matters)
Ghosting a candidate is almost never deliberate — it's an organisation problem. Here's how to fix it.
Ghosting is an organisation problem, not unkindness
The story is always the same: an application lands on a busy day, slips to the bottom of the pile, and three weeks later the candidate is still waiting. No one decided to ignore them — the system let them slip.
What it really costs
A ghosted candidate talks about it. To friends, sometimes online. Your employer brand is built as much on the candidates you reject as on those you hire.
And the pipeline dries up: a strong candidate treated poorly will not re-apply, and will warn others off.
The method: make the wait visible
You cannot reply to what you cannot see. Step one is to know, for each application, how long it has waited since the last exchange, with an alert past a threshold.
A weekly "who is waiting for an answer?" review removes 90% of ghosting.
Fast replies without spending your evenings
Email templates (rejection, invitation, follow-up) with the candidate's variables let you reply in seconds while staying personal. Replying fast does not mean replying at length.
How aiKip helps
aiKip shows, on every application and pipeline card, how long it has been waiting, flags those stalling past the threshold, and sends a weekly digest of candidates awaiting a reply. With reusable email templates, replying to everyone becomes sustainable again.
Frequently asked questions
What is ghosting in recruiting?
It is going silent on a candidate after one or more exchanges, with no reply or explanation.
Should you reply to every candidate?
Ideally yes, at least with a respectful rejection. It is cheap with templates and decisive for your employer brand.
How do you reply fast without spending hours?
With reusable email templates and alerts on waiting applications, as aiKip offers — a reply becomes a matter of seconds.
aiKip is the sovereign, compliant ATS that makes all of this simple.
Start the 30-day free trial →