A recruiter outreach email is a first-contact message to a candidate who has not applied, describing one role in two lines, saying why this person specifically, and asking for a short conversation. Unlike the other templates in this set it is often sent to a personal address, which changes the legal basis, the tone and the list rules. Recruiters report 8 to 15% positive replies when the email names something specific from the candidate's work, and under 3% for the "I came across your profile" version.
A work address with a role-relevant message can rest on legitimate interest in the UK and EU. A personal address is a consumer contact: be transparent about where you found it, make opting out one reply, and keep nothing beyond the conversation. The laws guide covers the detail.
Freemail addresses on B2B-style lists ran 17.6% invalid in 2026 corpus data, higher than business addresses. Old personal addresses from CVs and old profiles are the main reason. Verify before the send.
The candidate is not buying; they are deciding whether to spend an hour of their evening. Specific, respectful, no urgency language, no "exciting opportunity".
They may be employed. Never send to a work address a message that could be read by a manager. Personal address or LinkedIn for employed candidates; work address only for roles they publicly recruit for.
The first is why them. Not their title; a thing they built, wrote, shipped or spoke about. One sentence that could not be sent to anyone else. Recruiters who do this report replies three to five times higher than the profile-browsing version.
The second is the role in two lines: what the team does, what this person would own, and the one fact candidates actually want up front, usually location or remote policy and the salary range. Hiding the range lowers replies; most candidates now treat its absence as a signal.
Everything else, the company history, the benefits list, the culture paragraph, waits for the conversation. The ask is 20 minutes at a time they choose.
Subject: {role_title} at {hiring_company}: {specific_hook}
Hi {first_name},
Your {specific_work} is the reason I am writing; it is close to what this role does day to day.
{hiring_company} is hiring a {role_title} to {role_in_one_line}. {location_or_remote}, {salary_range}. The team is {team_size} people, reporting to {manager_title}.
If that is worth 20 minutes, pick a time that suits you, evenings included. If it is not the right moment, a one-word reply closes it and I will not keep your details.
{recruiter_name}
{recruiter_firm}, on behalf of {hiring_company}
If this is not relevant, reply "no" and I will not write again.
{specific_work} A project, talk, repo, article or product they made{role_in_one_line} What the role owns, not the job title{salary_range} State it; its absence lowers repliesSubject: A quiet question
{first_name},
I will keep this short because you are probably not looking. {hiring_company} is building {thing_being_built}, and your work on {specific_work} is the closest match I have seen.
The role is {role_title}, {location_or_remote}, {salary_range}. No process yet, just a conversation if you are curious. If not, no follow-up from me.
{recruiter_name}
If this is not relevant, reply "no" and I will not write again.
{thing_being_built} What the team is building, in plain wordsSubject: Your application to {other_role}
Hi {first_name},
You applied for the {other_role} role at {hiring_company} in {month}. That one went to someone else, but a {role_title} opening just came up that matches your {specific_work} more closely.
{role_in_one_line}; {location_or_remote}, {salary_range}. Would you like the details, or should I close your file?
{recruiter_name}
If this is not relevant, reply "no" and I will not write again.
{other_role} The role they applied for{month} When they applied| Rule or metric | Standard | Why |
|---|---|---|
| Source of address | Candidate profile, CV with consent, referral, or a finder on a public work address | Scraped personal addresses are the complaint risk |
| Verification | Every address, before the send | Old CV addresses bounce; freemail invalid share 17.6% |
| Sending domain | The agency's real domain for warm or referred candidates; a secondary for cold volume | Candidates search the sender; a bare domain loses them |
| Positive replies | 8 to 15% per 100 delivered (industry) | Below that, the "why them" line is generic |
| "Not now" replies | 5 to 10% | Keep with consent and a date; re-engage then |
| Complaints or removal requests | Under 0.3%; honour within a day | Personal addresses are consumer contacts |
Subject: Senior Backend Engineer at Harbourline: your queue-replay write-up Hi Kemi, Your write-up on replaying a failed job queue without double-processing is the reason I am writing; it is close to what this role does day to day. Harbourline is hiring a Senior Backend Engineer to own the ingestion pipeline. Remote in UK or EU hours, 85,000 to 100,000 GBP. The team is six people, reporting to the Head of Platform. If that is worth 20 minutes, pick a time that suits you, evenings included. If it is not the right moment, a one-word reply closes it and I will not keep your details. Tom Walsh Northbridge Search, on behalf of Harbourline If this is not relevant, reply "no" and I will not write again.
It could be sent to anyone, and candidates know it. Name a thing they made.
Its absence is read as a signal and lowers replies.
Employed candidates get personal address or LinkedIn. A manager may read the work inbox.
Personal addresses are consumer contacts. A no means delete.
The full set
Client-side outreach for agencies
The two-channel version for employed candidates
Finding a candidate's address, and the legal line
Consent, personal data and opt-outs
Freemail invalid rates by provider
Often, if you are transparent about the source, the message is relevant to their work, opting out takes one reply, and you keep nothing beyond the conversation. Rules differ by country; the UK and EU treat personal addresses as consumer contacts. Work addresses with a role-relevant message are the safer route.
Why this person specifically, in one sentence about their work; the role in two lines with location or remote policy and the salary range; and a 20-minute ask at a time they choose. Company history, benefits and culture wait for the call.
Yes. Its absence is now read as a signal and lowers replies. State the range plainly in the second paragraph; it also filters out conversations that would end at the range anyway.
Addresses from old CVs and profiles are stale, and freemail addresses on list-style data ran 17.6% invalid in 2026. Verify every address before the send and send to confirmed-valid addresses only.
Recruiters report 8 to 15% positive replies when the first line names something specific the candidate made, plus 5 to 10% "not now" replies worth keeping with a date. The "came across your profile" version runs under 3%.
Stale CV addresses out, confirmed-valid in, and the message reaches a person. 100 free checks a month, unknowns refunded.
Ayoub built BounceZero's 5-stage validation pipeline, its dedicated BGP-announced IP infrastructure, and the Patroni HA PostgreSQL cluster behind every verification. Previously built high-volume email delivery infrastructure. Trained at 1337 Benguerir (École 42 network, 2019). Open-source: bgp_analyzer.
Templates by trigger and stage, each with the deliverability rules that apply
A partnership outreach email template for integration, co-marketing and referral partnerships
An agency pitch email template that beats the hundred identical pitches a prospect gets each week
A SaaS trial nudge email template for signups who stopped
A LinkedIn connection request note plus the email that follows three days later
Four SDR cold email templates under 80 words each
A consultant cold email template for selling judgement rather than a product
Continue through related topics