The offer was signed. The start date was set. You announced the team. And then the new hire never showed, doesn't answer calls, and blocks your number. It feels like betrayal; recruiters see it often enough that it has a name — ghosting after acceptance — and a pattern with predictable causes. The pattern is also preventable.
How often it happens
Numbers vary by industry and study, but a consistent finding across recruiter surveys: a meaningful slice of accepted offers (commonly cited in the 10–25% range for hourly and high-volume roles; lower for senior) end in no-show or pre-start withdrawal. The cost is total — you've paid the sourcing, the interviews, the offer negotiation, and now you're back to zero with a two-week delay and a vacancy that people inside the company already heard was filled.
The four causes that actually matter
1. The silence window. The biggest single driver is nothing dramatic: it's the dead air between acceptance and day one. Two, four, six weeks where the employer says nothing while the candidate's old job keeps them warm, a counteroffer appears, or anxiety about the unknown does its work. Ghosting is usually a fade-out that starts with silence.
2. The counteroffer. A manager who fights to keep the person the day they resign is offering certainty against your unknown. Counteroffers succeed disproportionately because, at that moment, the candidate has more information about their current job than about yours.
3. Stacked competing offers. Acceptance isn't exclusive in practice. Many candidates — especially mid-salary, high-demand roles — accept one offer while continuing to interview. Whichever start date, comp, or commute wins the final week wins the person.
4. Bad-process residue. Slow interviews, dropped calls during the process, a vague start date, last-minute changes — every inconsistency accumulates trust debt. The candidate who already half-regrets the process reads the silence as confirmation.
The anti-ghosting sequence
This is pre-start engagement, and it's a calendar problem, not a personality one:
- Same-day confirmation: signed offer, start date, first-day logistics — time, parking, who to ask for — in writing.
- A weekly touch for the whole gap. Nothing operational required; "excited for the 3rd, here's who you'll work with" messages outperform silence dramatically. For hourly roles with short gaps, the same-day plus day-before confirmation covers it.
- Pre-work, delivered warmly: paperwork, any required screening or credential checks, a first-week read. A candidate doing admin for you is psychologically in, and completed verification prevents a week-one cancellation.
- A named human who answers the phone when they call. Uncertainty without a contact resolves as abandonment.
- Watch the pre-start flake risk the way you watch funnel numbers elsewhere: if more than a couple of acceptances are dying silently per month, the problem is the sequence, not the candidates.
- When someone vanishes: one follow-up with a deadline ("we'll hold your offer through Friday"). Sometimes there's an emergency and the door should stay open; sometimes the silence is the answer, and the deadline at least gives you certainty to restart.
The structural point: engagement isn't a nicety bolted onto hiring, it's the retention layer before retention. Tracking which touchpoints actually correlate with start-day attendance turns this from a ritual into a managed stage of the pipeline — and it belongs in the same system that holds your candidate records, not a founder's memory. That's a talent CRM problem: the pipeline doesn't end at accept; day one is where it ends.
Bottom line
Candidates ghost after accepting because of the silence between offer and start, counteroffers they can evaluate more easily than your unknown, competing offers they're still weighing, and process debt that made the silence feel expected. Fix it with a weekly touch calendar, same-day logistics, warm pre-work, one named human, and a deadline for the vanishing — and treat the pre-start window as a managed stage in your CRM, because it is.