Every recruiter hits the same wall on a busy week. You have 40 people sitting in the screened stage, a hiring manager who wants interviews booked by Friday, and no time to write 40 messages by hand. So you reach for bulk send, and the result reads like a utility bill. Candidates can tell. Reply rates drop, and the ones who do reply sound guarded. The fix is not to stop sending in bulk. The fix is to write the message the way you would write it to one person, then let the software handle the repetition.
Start with the stage, not the list
A good bulk message is scoped to a moment in the pipeline. Everyone in the screened stage shares a context: they applied, someone looked at their resume, and they are waiting to hear what happens next. That shared context is what lets you write one message that fits all of them. If you find yourself adding caveats like 'if you have already spoken with us, ignore this', your list is too broad. Filter tighter first.
- Applied but not screened: a short acknowledgement with a realistic timeline.
- Screened, moving forward: an invitation with a scheduling link.
- Screened, not moving forward: a clear, kind close with the door left open.
- Interviewed, waiting on a decision: a status update, even if the update is 'no news yet'.
Write the first sentence like a text to a friend
The opening line does most of the work. 'Dear Candidate, thank you for your interest in the position' announces that a machine is talking. 'Hi Priya, I read through your application this morning' does not. Use a first-name merge field and put a real detail in the first sentence: the role title, the location, the day you reviewed applications. Merge fields are not the problem. Generic sentences are the problem.
Keep the whole message under 60 words for SMS and under 120 for email. One idea, one ask, one link. If you need to explain the interview format, the parking situation and the dress code, that belongs in the confirmation message after they book, not in the invitation.
Leave room for a reply, and then actually reply
The difference between a robot and a person is that the person answers. If you bulk send from a no-reply address, you have told candidates the conversation is one way. Send from a channel that lands in a shared inbox so whoever is on duty can pick up the thread. In Apex ATS the bulk send goes out from the applicant record, and every reply drops into the team inbox as a chat thread tied to that candidate, so nobody has to dig through a personal mailbox to find out that Marcus asked whether Thursday at 4 is still open.
- 01Send the batch in the morning, not at 9 pm.
- 02Watch the inbox for the next two hours. Most replies come fast.
- 03Answer short questions in one line. Do not template the follow-up.
- 04Anyone who replies with a question gets a person, not another bulk message.
Templates are for structure, not for voice
Saved templates save time when they capture the parts that should not change: the scheduling link, the stage name, the compliance line if your industry needs one. They hurt when they lock in a tone that nobody on your team actually uses. A practical test: read the template out loud. If you would be embarrassed to say it to a candidate on the phone, rewrite it. Keep three or four templates per stage at most, and review them every quarter. Language that felt fresh in January reads stale by July.
Illustrative numbers from teams we have worked with: a stage-scoped SMS with a first-name opener and a single scheduling link tends to see reply rates in the 40 to 55 percent range within 24 hours. A generic 'Dear Applicant' email to the same group often lands closer to 10 to 15 percent. The candidates are the same. The words are different.
Bulk messaging is not a shortcut around treating people like people. It is a way to make sure everyone at the same point in your process hears from you promptly, in words a human would use. Scope the stage, write to one person, send from somewhere replies can land, and then show up in the thread. That is the whole trick.