Every recruiter has a story about the candidate who was keen on Tuesday, confirmed the interview on Wednesday, and vanished on Thursday. It is tempting to blame the candidate. Sometimes that is fair. More often, the ghosting started with us: a reply that took two days, an interview request that sat in a queue, a question that never got answered. This post looks at why candidates go quiet and why the fix is less about clever messaging and more about being fast.
Ghosting is usually a competition you lost
An active candidate is rarely talking only to you. A warehouse associate might apply to six roles in an afternoon. A software engineer might have three processes running. Whoever responds first sets the tone, and whoever responds first with a concrete next step usually wins the candidate's attention.
Look at it from their side. They apply at 9:40 in the morning. One employer texts back at 9:52 asking two quick screening questions. Another emails a form acknowledgement. A third says nothing for four days. By the time the third employer reaches out, the candidate has already had a phone screen with the first one and mentally moved on. They are not being rude when they do not reply. They are just busy with the process that felt real.
What the timing looks like in practice
The numbers below are illustrative, drawn from patterns we see across teams rather than a formal study, but they line up with what most recruiters will recognise from their own pipelines.
- Reply within 5 minutes of an application or inbound message: roughly 70 to 80 percent of candidates respond and stay engaged through the next step.
- Reply within the same business day: engagement drops to somewhere around 50 percent.
- Reply the next day: closer to 30 percent.
- Reply after 3 or more days: you are effectively cold-outreaching someone who already applied to you, and response rates look like cold outreach, often under 15 percent.
The curve is steep at the front. That is the whole point. The difference between five minutes and five hours is bigger than the difference between five hours and five days. Speed in the first window is what keeps the candidate treating your process as live.
Why teams are slow even when they care
Almost nobody is slow on purpose. The delay comes from how the work is arranged.
- Applications land in a job board dashboard that gets checked once a day.
- Candidate messages go to one recruiter's personal inbox, and that recruiter is in interviews all afternoon.
- Replying means opening the resume, finding the phone number, switching to a phone or a separate texting tool, and typing from scratch.
- Nobody knows whether a colleague already responded, so people wait rather than double up.
Each of these adds friction, and friction turns into hours. The fix is not asking people to try harder. It is removing the steps between seeing a message and answering it.
Building the five-minute reply
Here is what works for teams that get their first-response time down to minutes.
- 01Put messaging in the candidate record. If you can text or email from the same screen where you see the resume, you will actually do it. This is the core of how messaging works in Apex ATS: the SMS and email thread sits on the applicant record, and the whole team sees it as one chat-style conversation in a shared inbox.
- 02Use templates for the first touch. A good first reply is short and asks one thing: confirm interest and ask a screening question, or offer a scheduling link. Write it once, save it, and send it in two clicks.
- 03Share the inbox. When any recruiter can see and answer any candidate message, and can see that a colleague already has, the queue clears faster and nobody double-replies.
- 04Automate the acknowledgement, but not the conversation. An instant, human-sounding text that says thanks, here is what happens next, buys you time. Then a real person follows within the day.
- 05Batch the routine. If 40 applications arrive overnight, a bulk send of the screening question at 8:30 gets 40 conversations started before the first coffee.
We used to lose about a third of confirmed interviews to no-shows. Once we started confirming by text the day before and replying to anything they sent within a few minutes, that dropped to roughly one in ten. Same jobs, same candidates. Just faster.
Operations recruiter, regional healthcare staffing team (illustrative)
Speed is not the same as pressure
A fast reply does not mean a pushy one. Nobody wants four texts in an hour. The goal is that when a candidate reaches out, the response arrives while the question is still in their head, and it moves things one concrete step forward. Confirm, ask, offer a slot. Then leave them alone until the next real update.
Ghosting will never go to zero. People change their minds, take other offers, or stop looking. But a large share of it is simply the natural result of being slow, and that share is under your control. Get the first reply down to minutes and watch how many of your ghosts turn back into candidates.