WhatsApp for Recruitment Agencies: Screening Without Phone Tag

Every recruiter I have spoken to in the last year already works on WhatsApp. Candidates answer a message in four minutes and let a call ring out for four days. The messages are happening. What is missing is a system: the conversations sit on three different personal phones, and when a recruiter leaves, the candidates leave with them.

This is the setup I would put in place for a small agency, in the order that actually fixes things.

Where WhatsApp earns its place on a recruitment desk

Not everywhere. Recruitment has a few message types that repeat hundreds of times a month, and those are the ones worth moving onto a business number:

• First response to an application, so nobody waits two days to hear anything.
• Interview invites, confirmations and reminders.
• Document collection: ID, certificates, signed offer letters, bank details.
• Offer and joining-date follow-ups, where the silence between "accepted" and "joined" is exactly where candidates disappear.
• Post-placement check-ins at 30 and 90 days.

What does not belong there: salary negotiation, client contracts, and anything you would not want forwarded. Keep those on a call or email.

What breaks when each recruiter uses their own phone

This is the expensive part, and it does not show up until it does.

The candidate list belongs to whoever typed the number. A recruiter resigns, and the shortlist for three open roles goes with them. You cannot audit it, export it, or prove it was worked properly.

Nobody can cover. If the only person who has the candidate on WhatsApp is on leave, the interview confirmation does not go out and the candidate does not show up. That is a placement lost to an out-of-office.

There is no record. Two recruiters message the same candidate from two numbers, or a client asks when a candidate was told about the interview and nobody can say. A shared inbox fixes this by design.

Personal numbers carry ban risk. A personal number sending a few hundred messages a week to people who did not save it is exactly the pattern WhatsApp treats as spam. A business number with proper opt-in and template approval is the safer route, and it is the only route if you want to keep the number when the person leaves. If you are still choosing between the app and the platform, WhatsApp Business API vs the Business app covers that decision.

Opt-in has to be collected at the same moment as the application

Meta's policy requires the person's consent before you message them, and consent collected two steps later does not exist. Put it where the application happens:

• On the application form, a checkbox: "Contact me about this application on WhatsApp at the number above." Unticked by default.
• On the job page, a WhatsApp button that opens a chat which the candidate starts. A candidate messaging you first is consent you can point at.
• On the intake call, one line in the notes: "Candidate agreed to WhatsApp for updates, 20 Oct."

Store the source and the date next to the number. When a candidate says they never agreed, you want to be able to show the form submission rather than guess.

The four messages that carry most of the work

These are utility messages, not marketing. Utility templates are for updates about a transaction the person already started, which is what every one of these is:

Two things bite here. First, templates need approval before you can send them outside an open conversation, and a vague template gets rejected. The patterns that pass are in why WhatsApp templates get rejected and the full process is in the template approval guide. Second, a template that says "Dear Candidate" reads like a bulk SMS. Put the role name in it and people reply.

Screening questions that fit in a chat

The mistake I see is a fifteen-question form dropped into WhatsApp. People abandon it. Four questions get answered:

1. Notice period, in weeks.
2. Current and expected range, as a band rather than a number.
3. Location, and whether they will travel or relocate.
4. Work authorisation, if the role needs it.

That is enough to decide whether a call is worth booking, and it takes a candidate ninety seconds. Everything else belongs on the call. If you are weighing how much of this to automate, chatbots vs human agents is the decision framework: automate the first response and the scheduling, keep a human on anything that affects whether someone takes the job.

Scheduling, and the no-show problem

Interview no-shows are usually not disinterest. They are a candidate who agreed to a slot three days ago on a screen they have since closed. One utility reminder 24 hours before, with a confirm and a reschedule option, does most of the work. Clinics learned this earlier than recruiters; the mechanics are the same as appointment reminders.

The 24-hour window, and what happens after it

WhatsApp gives you 24 hours from the candidate's last message to reply freely. Inside that window you can write anything. Outside it, you need an approved template to reopen the conversation.

For a recruitment desk this is fine, because your follow-ups are scheduled around events: application, interview, offer, joining. Design the messages to fire at those moments and you rarely need to reach into a cold conversation. If you do, say what it is about in the template, or it reads as spam and gets blocked.

What I would set up first in a three-person agency

1. One business number, owned by the company, on the WhatsApp Business Platform. Not a recruiter's handset.
2. A shared inbox so all three recruiters see every conversation, with assignment.
3. The four utility templates above, submitted for approval before launch week.
4. The opt-in checkbox on the application form, with the source stored against the number.
5. A rule: candidates are contacted only from the business number. No exceptions, including the founder.
6. A weekly export, so the candidate database lives in your system rather than in WhatsApp.

That is roughly a week of setup. Done in that order, the first thing you notice is that nobody asks "did you message them?" any more, because the answer is visible.

Where BNex fits

BNex is the WhatsApp Business Platform product I build. It puts the business number and the shared inbox in one place, so a candidate thread is visible to the whole desk and stays with the company when someone moves on.

It does not shortcut Meta's processes. Template approval, display name review and opt-in rules apply the same way, and that is deliberate, because an account built on shortcuts is an account you lose at the worst moment. If your problem is not the tool but the rollout, what to check when comparing shared inbox software and the shared inbox guide are the two reads that save a wrong purchase.

If you are running an agency and cannot tell whether a candidate was ever contacted, message me on WhatsApp at +91 73587 22745 and describe the setup you have. I will tell you what I would change first, and it is usually the number ownership.

Related Reading

• WhatsApp chatbots vs human agents: when to use which
• Connect WhatsApp to your CRM with API webhooks
• Shared inbox software: 7 questions to ask before you buy