Candidate communication: why silence costs you good people, and what to do insteadSkip to content

Candidate communication: why silence costs you good people, and what to do instead

Candidates don't treat silence as 'no news yet'. They treat it as an answer, and act on it. Here's how to keep every candidate informed without it becoming a full-time job.

Dhruv Sanjay Rao, Head of Product6 min read

Most recruiters don’t go quiet on candidates on purpose. The decision is waiting on a hiring manager who’s travelling, the panel hasn’t met, and there’s nothing new to say, so nothing gets said. It feels neutral. You’ll write when there’s news.

To the candidate it isn’t neutral at all. A week of silence after an interview reads as a no, or as a company that doesn’t have its act together. Either way, they act on it. They take the other interview more seriously, say yes to the other offer, and when your email finally arrives, the person you wanted has moved on.

Every message a candidate gets should answer three things: where do I stand, what happens next, and when will I hear from you. Most of good candidate communication comes down to that, and to keeping the date you gave.

Silence is an answer

Candidates remember being left hanging. In a LiveCareer survey of more than 1,000 US workers, reported by HR Reporter, 48% said they wouldn’t reapply to an employer that had ghosted them, and 37% said they’d tell other people about it. It’s not rare, either. Greenhouse’s 2024 research found that 61% of job seekers had been ghosted after an interview.

The cost isn’t spread evenly. Strong candidates are usually running more than one process, so they’re the ones with somewhere else to go. A weaker candidate will wait for your reply. A strong one takes the offer from the company that kept them informed.

Give a date, and keep it

“We’ll be in touch soon” is the most common line in recruiting, and almost useless. Soon to you means after the panel meets. Soon to the candidate means tomorrow, and by Thursday they’ve decided you’ve lost interest.

A date changes this. “You’ll hear from me by Tuesday, either way” gives the candidate something to plan around. More importantly, it gives you something to be accountable to. Tell candidates the shape of the process at the start, how many rounds and roughly how long, and a long process stops being alarming. A candidate who knows there are three rounds over two weeks doesn’t panic on day four.

When a date is going to slip, and some will, write before it passes, not after. “No decision yet, the panel meets on Monday, I’ll write by Tuesday” takes thirty seconds and keeps a candidate in your process. Missing a date you gave is how ghosting starts. Nobody decides to ignore a candidate. A deadline goes by, it becomes awkward to write late, and then it’s easier not to write at all.

Write where they’ll actually read it

A message only counts if the candidate sees it. In India that’s often WhatsApp rather than email, which many candidates check once a day at most. Elsewhere it might be email or text. Use the channel your candidates answer, not the one that’s most convenient to send from.

Make replying easy, too, especially when the answer is no. A candidate who can withdraw or ask to reschedule with a one-line reply will usually tell you. One who has to write a formal email to a stranger often won’t. Making it easy to say no is one of the most effective ways to stop candidates disappearing on you.

Say no clearly, and properly

Nobody enjoys sending rejections, so they’re the messages most likely to be delayed, softened into something vague, or never sent. Each of those is worse for the candidate than a clear no.

Match the effort to how far the candidate got. Someone screened out at the résumé stage needs a short, polite answer, and they need it reasonably quickly, not six weeks later. Someone who sat three rounds has given you several hours of their life. A short phone call, then a written note, is the respectful minimum.

Say the decision plainly in the first line or two. Then thank them for something specific, and leave the door open to the company if you mean it. Don’t write “we’ll keep your CV on file” unless someone will actually look at it, because a vague no keeps people waiting for a yes.

Feedback that helps and doesn’t backfire

Candidates who reached the interviews often ask for feedback, and giving it well builds a lot of goodwill. Giving it carelessly can come across as bias, or simply hurt more than it helps.

Good feedback is tied to the job, not the person. “The role needs hands-on experience leading migrations, and your examples were mostly from feature work” is useful and fair. “Not quite the right fit” tells the candidate nothing, and employment lawyers warn that vague phrases like that can be read as cover for discrimination. One strength and one thing to work on is plenty. Agree it with the panel first, so the candidate doesn’t hear something different from each interviewer.

This is where a structured interview scorecard pays off twice. If every interviewer wrote down evidence against the job’s requirements, the feedback is already there, specific and defensible. Avoid anything about age, health, family, background or how someone came across, and comparisons with the person you hired. It’s worth checking your local employment law before putting feedback in writing; this isn’t legal advice.

The quiet weeks between yes and day one

In India, the riskiest stretch of the whole process comes after the offer is accepted. Experienced candidates often serve notice periods of 60 to 90 days, and People Matters describes the gap between acceptance and joining as the “most fragile” period, with recruiter contact dropping off after the offer as one of the main reasons people don’t join.

It makes sense from the candidate’s side. They’ve said yes to you, their current employer is making a counter-offer, and another company is still interviewing them. If the only sign of you in two months is a joining-date email, the other conversations feel more real.

So stay in touch through the notice period, and make the contact mean something: an introduction to their manager, a call with the team, joining details well before they’re needed. Ask, without judgement, whether they’re weighing other offers. You can’t stop parallel processes, but you can be the company that’s clearly expecting them.

Why it slips when you’re doing it by hand

None of this is difficult. Each message is short. The difficulty is that there are hundreds of them, and each one depends on a person remembering.

Dates live in a recruiter’s head or a spreadsheet column. Updates go out from a personal phone, and when that recruiter is on leave, nobody else knows who was promised what. Rejections pile up in drafts because they’re unpleasant to send. In a busy hiring month, the candidate who’s quietly waiting is always the easiest thing to put off, so they get put off. Nobody is ignoring candidates. There’s simply no system that notices when a promise is about to be broken.

That’s the honest case for running candidate communication from a system: not that software writes better messages, but that it sends the routine ones on time, every time, and shows you who’s been waiting too long.

How Arexis helps

In Arexis, the routine messages go out on their own: booking links, confirmations, reminders before each interview, reschedules and coding-test invites, on WhatsApp with email as the fallback, and you can see whether each one was delivered. Stalled candidates are flagged, so the person waiting on a decision doesn’t get forgotten, and your recruiters’ time goes on the calls and conversations that need a person. See how pipeline operations work.

Found this useful? Pass it on.

See it on your own roles.

Screening, scheduling, interviews and proctored coding tests in one workspace. 30 days free, no card.