5 minutes
/
Why candidates actually finish the interview when WhatsApp comes first
Abhimanyu Roat
Co-founder & CEO
Why candidates actually finish the interview when WhatsApp comes first
Recruit Bud is an AI voice screening system that calls and interviews job candidates on a hiring team's behalf. In our pilots, when the call is paired with a WhatsApp message sent first, candidates complete the interview at roughly twice the rate of candidates who only get a cold call. No change to the script, no extra dials, just a candidate who knows what the call is about before the phone rings.
The reason is straightforward: a candidate who picks up a call from an unrecognized number with no prior context has no basis to trust it, and most don't stay on the line long enough to find out.
In short:
A ringing phone gives a candidate no way to tell a real job from a scam call, so most unknown numbers get ignored on reflex
A WhatsApp message lets the candidate see the role, location, and pay in writing first, and decide for themselves whether to engage
Interview completion rates have run roughly 2x higher in pilots where WhatsApp is paired with the call, versus voice alone
The default flow informs candidates with the job details first, then calls, no reply required
If a call goes unanswered, a follow-up WhatsApp message goes out and a second call is scheduled
Once a candidate replies, the bot can hold a real conversation and answer their questions, not just send a template
Why do candidates ignore calls from recruiters?
A phone call carries no information before it's answered. There's no name, no company, no stated reason for the call.
Most candidates in India receive multiple unknown-number calls a day, the majority of them spam or scams, so unfamiliar numbers get declined by default. A recruiter's cold call isn't competing against other job openings for attention. It's competing against every spam call the candidate has already learned to reject on sight.
Candidates who do answer are often guarded rather than engaged: short answers, hesitant tone, an early hang-up if the recruiter doesn't establish legitimacy fast. The call underperforms not because of what's said, but because the candidate has no basis to trust it before it starts. (For a closer look at the spam-call problem specifically, see why candidates pick up WhatsApp messages and ignore recruitment calls.)
Why does sending a WhatsApp message first change that?
It gives the candidate the information a phone call withholds, before any call happens. A WhatsApp message states the job title, location, and pay range in writing. The candidate reads it on their own time and decides whether to engage, instead of having a call arrive with no context and no option to prepare.
It also arrives on a channel the candidate already uses and trusts, not an unfamiliar phone number. A message from a named sender, with a real job description attached, reads as legitimate in a way an anonymous call cannot.
The mechanism is direct: a candidate who has already seen the role in writing recognizes the call that follows as the one they were expecting, and answers it accordingly. That's what produces the completion-rate difference.
[IMAGE: Screenshot of a candidate's WhatsApp screening message next to the follow-up voice call log in the Recruit Bud dashboard]
How does the WhatsApp-and-call flow actually work?
Here's the default sequence, and it's simpler than it sounds:
The candidate gets informed first. A WhatsApp message goes out with the job description, role, location, and pay range.
The call happens next. This isn't gated behind a reply. If the candidate picks up, they already have context, and the conversation starts from a warmer place.
If the candidate doesn't answer, a follow-up message goes out. A short WhatsApp nudge, then a second call attempt later.
Once the candidate replies at any point, the bot can hold a real conversation. Not a static template. It answers questions about the role, the process, timing, whatever the candidate actually wants to know, in their own language.
This is the flow one of our pilot customers specifically asked us to build, based on how their own recruiters already worked a lead: inform first, then call, follow up if there's no answer, and keep the conversation open on WhatsApp the whole way through.
What are the practical benefits of this flow for a hiring team?
Combining WhatsApp and voice into one system removes work that recruiters were doing manually, and gives a hiring team a single record of every candidate interaction instead of scattered ones. The completion-rate gain is the headline number, but the operational changes matter just as much day to day.
Benefit | What changes for the hiring team |
|---|---|
Fewer repetitive candidate queries reach a recruiter | The bot answers routine questions on WhatsApp, shift timing, location, pay, remote or on-site, so recruiters aren't fielding the same five questions on every open role |
One view per candidate, not scattered logs | Every WhatsApp message and every call for a candidate sits under that candidate's record, so a recruiter isn't checking a phone log in one place and a chat app in another to reconstruct what happened. This is the same gap that shows up at the team level for remote staffing agencies that can't see where recruiter effort is going |
No candidate falls through on a missed follow-up | The retry and follow-up message go out automatically when a call isn't answered, instead of depending on a recruiter remembering to circle back later in the day |
Consistent answers across every candidate | The bot gives the same role details and process information every time, so there's no drift between what one candidate hears on call five and what another hears on call fifty |
Recruiter time shifts toward judgment calls | With routine status questions and follow-ups handled automatically, recruiters spend more of their day on the candidates and decisions that actually need a person, not on repeating logistics |
Do you have to use WhatsApp before every call?
No. This isn't a fixed rule your campaigns get forced into. Some lists are small and warm enough that a direct call works fine on its own. Others, especially large lists sourced cold from job boards, benefit from WhatsApp doing the introduction first.
You decide, campaign by campaign, which shape fits the role you're hiring for. The flow described above is simply the one that's performed best across the pilots we've run so far, agencies and in-house hiring teams alike.
Can candidates actually talk to the bot on WhatsApp, or is it just a template?
It's a real conversation, not a one-way blast. Most WhatsApp tools in this space in India send a message and stop there, a template with a role and a link, nothing more.
Our research into what else is out there turned up the same pattern everywhere: one-way messaging, no real dialogue. That held whether we looked at a general-purpose voice AI vendor offering WhatsApp as a bolt-on channel, or an India-focused screening tool that treats WhatsApp as a notification layer rather than a conversation.
That's the gap. A candidate replying "what's the shift timing?" or "is this remote?" shouldn't hit a dead end or force a wait for a human.
The bot answers directly, in the candidate's language, and keeps that thread open independent of whether the voice call has happened yet. The call handles the structured screening. WhatsApp handles everything a candidate wants clarified along the way, before, during the wait, or after.
What should you actually expect if you switch to this flow?
Fewer wasted calls and a candidate on the other end who already knows why you're calling. That's the practical shift: not a nicer-looking message, but a candidate who picked up expecting your call instead of screening it as spam.
The completion-rate gap we've seen across pilots, informed candidates finishing at roughly twice the rate of cold-called ones, comes directly from that difference.
If you want to see the completion-rate difference on your own candidates, send Recruit Bud one role and a candidate list. You'll get the WhatsApp threads and call recordings back to compare against your usual cold-call numbers.
Frequently Asked Questions
Why do candidates ignore calls from recruiters more than other calls?
A ringing phone doesn't tell a candidate anything about who's calling or why. With no name, no context, and years of unknown numbers turning out to be spam or scams, most people let unfamiliar calls go by reflex. A recruiter's cold call is competing with every spam call the candidate has already learned to ignore, not with other job offers.
Does WhatsApp really improve interview completion rates?
Across our pilots, candidates who received a WhatsApp message alongside a screening call completed the interview at roughly twice the rate of candidates who only got a cold call. A candidate who already knows the role, the location, and the salary before the phone rings is far more likely to stay on the line and finish, instead of hanging up on an unfamiliar number.
Do candidates have to reply on WhatsApp before Recruit Bud calls them?
No. The default flow informs the candidate with the job details and then calls them, whether or not they reply first. If the call isn't picked up, a follow-up WhatsApp message goes out and a second call is attempted later. Whether WhatsApp gates the call or simply runs alongside it is something your team configures per campaign.
Can candidates ask questions on WhatsApp instead of just receiving a template message?
Yes. Once a candidate replies, the bot can hold a real conversation, not just fire off a fixed message. It answers questions about the role, the salary band, the location, or the process, in the candidate's own language, before or after the voice call happens.
Share this post
