Cold Email for Recruiters: Reaching Passive Candidates

Recruiting outreach has one structural difference from sales outreach: the people you contact are not potential buyers, and the data you hold about them is often personal rather than corporate. That makes context the thing that earns a reply — and opt-out handling the thing you cannot get wrong.

Why do generic recruiting emails get ignored?

Candidates pattern-match just as well as buyers. A message that could have been sent to anyone reads as a mass mailing, and passive candidates — who already have a job — have no reason to engage with one. What earns a reply is evidence that you looked at their actual situation.

How does a candidate profile map onto Mailor?

The same mechanism that infers a buyer profile infers a candidate profile: roles, industry, company size and skill signals, stored as a project’s ICP and editable before any search runs.

Recruiting needHow it maps
Target role and senioritytarget_roles on the project
Industry and skillstarget_keywords and inferred industry with a confidence signal
Locationtarget_geo
Fit rankingEach lead is scored against the profile, so the strongest matches surface first

What personalization actually works in recruiting?

Specificity about the person, not flattery. Reference something factual from their public professional context — a role transition, a specialism, a product they worked on — and connect it to one concrete reason this opportunity is worth a look. Vague praise reads as automated; a specific observation does not.

What are the data-protection duties for candidate outreach?

Candidate data is usually personal data, which puts it in a stricter category than corporate contact data. Two obligations follow and neither is optional: honour opt-outs permanently, and be able to say where the data came from. Mailor enforces the unsubscribe mechanism at the account level — an unsubscribed contact cannot be re-enrolled — but the lawful basis for contacting a candidate, and your retention policy for their data, remain your responsibility.

How does Mailor fit a recruiting workflow?

Create a project for the role, describe the candidate profile, review and adjust the inferred targeting, generate the contact list scored against it, then draft per candidate from their public context. Follow-up sequences are opt-in and stop on reply, and the AI disclosure page states plainly what is generated by a model and what is not.

Frequently asked questions

Is cold email to candidates legal?

It depends on jurisdiction and on your lawful basis for processing personal data. Business-contact rules, which often permit unsolicited B2B email with a working opt-out, are not the same as personal-data rules, which may require a lawful basis such as legitimate interest and give individuals stronger rights. Take advice for your market; what Mailor guarantees is the mechanical side — a working unsubscribe and permanent suppression.

How do I reach passive candidates without being spammy?

Reference their actual professional context and offer one concrete reason to respond. Specificity is the difference between outreach and spam in recruiting more than in any other use case, because the recipient has nothing to gain from a generic message.

Should I personalize with details from social profiles?

Use public professional information and keep it relevant to the role — a specialism, a transition, a product they shipped. Avoid anything that reads as surveillance, and be able to say where each fact came from if asked.

How many candidates should I contact per role?

Fewer, better-matched contacts outperform a wide list here. Each lead is scored against the candidate profile, so work down the ranking and stop when reply quality drops rather than when the list ends.

Related reading