Cold email software for recruiters

Two audiences, two campaigns

Candidates and clients respond to different messages and produce different complaint risks. A candidate who receives three irrelevant role emails complains faster than a client who receives one relevant note. Keep them on separate mailboxes and separate sequences so the signals stay readable.

For candidates the useful fact is the role and why it fits them. For clients it is a specific hiring problem and a shortlist. Neither needs a paragraph about your agency.

• Candidate campaign: role, location, one reason it fits.
• Client campaign: the hiring problem, the evidence you can help.
• Separate mailboxes so a complaint does not cross audiences.

Timing around a candidate's day

Candidates read email early and late; clients read during working hours. That is a scheduling choice, not a trick. Sending a role at 6am local time is more likely to be seen before the day starts, and it looks like a person who works early rather than a system that fired at midnight.

Keep follow-ups two to four business days apart and stop on reply. A second message to someone who already answered “not looking” is the fastest way to be reported as spam.

The interval and stop rules are in follow-up sequence.

Reply handling is the product

In recruitment, a reply is the start of a conversation that needs a human within hours. A setup that sends well but routes replies to an unread inbox wastes the only outcome that matters. Route replies to a shared inbox with an owner and a response-time expectation.

Track three outcomes per campaign: interested, not now, wrong role. The third tells you the list is off; the second tells you the timing is off; the first tells you the message works.

• Shared inbox with a named owner.
• Response target measured in hours, not days.
• Outcome tags that inform the next list.

If you want campaigns and replies in one place, cold email campaigns with reply handling covers that workflow.

Compliance and consent, settled first

Recruitment outreach touches personal data, and rules differ by country. Before the first campaign, decide what lawful basis you rely on, what you will do with a deletion request, and how long you keep candidate data. None of that is solved by software.

Worked example: a desk sending to candidates in three countries kept one list and one message. After a complaint, they split the list by jurisdiction, added a one-line explanation of how they found the candidate, and removed anyone who asked. The campaigns got smaller and the complaints stopped.

If list quality is the weak point, verified contact data supplies checked business contacts.

Measuring a desk without vanity metrics

Recruitment outreach has three outcomes that matter: a candidate who is interested, a client who will take a call, and a role that needs a different audience. Everything else, including opens and clicks, is a proxy that can move without changing any of the three.

Track time-to-first-reply as well as reply counts. A desk that gets twelve replies in three days is in a different position from one that gets twelve replies over three weeks, even though the rate looks the same. Reply speed is also the best predictor of whether a candidate is still available.

Review the numbers weekly with the people who answer replies. They will tell you which roles produced wrong-role responses, and that is the input for the next list rather than a dashboard.

• Interested candidate, client call, wrong audience.
• Time-to-first-reply alongside reply count.
• Weekly review with the people handling replies.
• Keep candidate and client suppression lists separate as well as the campaigns. A candidate who asked not to be contacted about one role may still be a client contact, and treating them as the same record creates a compliance problem.
• Ask candidates how they prefer to be contacted and record it. A desk that knows one candidate wants a message rather than an email can send fewer messages and get better answers, and the preference survives the campaign, which a reply rate does not.
• Keep a single shared inbox per client or desk and one rule for who answers. When two people reply to the same candidate from different addresses, the thread fragments and the candidate receives conflicting information, which is worse than a slow answer from one owner.
• Record why a candidate said no. Salary, location, timing and role shape are four different answers, and each changes the next list you build. A desk that only records "not interested" learns nothing and rebuilds the same audience next quarter with the same result.

Recruitment campaign types and the signal to watch

Re-engagement lists are the highest complaint risk; treat opt-outs as permanent.

Frequently asked questions