LinkedIn InMail vs Email to Recruiters: Which Actually Works

InMail vs cold email vs connection note — reply-rate reality, cost, and how to pick per recruiter.

You have three channels to reach a recruiter: LinkedIn InMail, a LinkedIn connection request with a note, and cold email. They’re not equivalent — reply rates, cost, and speed vary significantly, and the right choice depends on the recruiter, not your preference.

Reply-rate reality

Cold email (direct to inbox). Typical reply rate 4–10% for well-targeted, personalized outreach. Higher for warm intros. The channel with the most upside if you can find the address.
LinkedIn InMail (paid). Reply rate 10–25% because the recruiter gets a notification and knows you paid to send it. Best per-touch response rate, but capped by monthly credit budget.
Connection request with a note. Accept rate 15–30%; reply rate on the first note ~5–10%. Cheapest but slowest to compound.

When to use LinkedIn InMail

You cannot find the recruiter’s email address anywhere.
The role is time-sensitive (closing soon) and you can’t wait for a connection to accept.
You have a paid LinkedIn Premium / Recruiter Lite subscription with unused credits.
The recruiter is a “LinkedIn open profile” user — InMails to open profiles don’t cost a credit.

When to use cold email

You can find or reasonably guess the recruiter’s work email.
You want to attach a resume PDF — LinkedIn doesn’t let you attach files in InMail.
You’re running any kind of outreach at scale (10+ per week).
You want the exchange to live in your email history, not LinkedIn’s.

When to use a connection request

You have time on your side — accepted connections compound.
You want long-term visibility (posts, comments, activity feed).
You’re out of InMail credits and can’t find the email.

The two-channel move

Sending a cold email and a connection-request note the same day lifts reply rate materially — you become recognizable in two contexts at once. Don’t send an InMail on top; three simultaneous channels reads as spam.

Templates by channel

Cold email template

TemplateSubject: Interested in your {{Role}} req — {{years}} yrs {{skill}} Hi {{First Name}}, I saw {{Company}} is hiring a {{Role}} on {{Team}}. I'm currently a {{Your Title}} at {{Your Company}} with {{years}} yrs of {{skill}} experience. Two relevant results: – {{Concrete result #1}} – {{Concrete result #2}} Resume attached. Happy to do a 15-min intro any afternoon this week or next. Thanks, {{Your Name}} {{Phone}} · {{LinkedIn}}

LinkedIn InMail template

Shorter than email. InMails render in a preview window on mobile — the first 40 words are what get read.

TemplateSubject: {{Role}} on {{Team}} — 30 sec context Hi {{First Name}}, Reaching out about your {{Role}} req on {{Team}}. I'm a {{Your Title}} at {{Your Company}} — {{one line about fit and one concrete result}}. Happy to send a resume and set up a 15-min intro if there's interest. Would this week or next work better? Thanks, {{Your Name}}

Connection-request note

LinkedIn limits connection notes to 300 characters. Use them.

TemplateHi {{First Name}} — saw you're hiring for {{Role}} on {{Team}}. I'm a {{Your Title}} at {{Your Company}} with {{years}} yrs of {{skill}} — happy to send a resume if there's interest. Thanks!

Choosing per recruiter

A rough decision tree:

Can you find the email? → Send email. If no reply after two follow-ups, add a LinkedIn connection request as a second channel.
Can’t find email, InMail credits available? → InMail.
No email, no credits? → Connection request with note. Wait for accept, then message.

What Fwalla does

Fwalla focuses on the email channel — SMTP from your Gmail with conservative pacing and scheduled follow-ups. Use LinkedIn as a complement, not a replacement.

Automate the templates above. Free while you job-search.

Fwalla personalizes templates like these per recruiter, per role, and sends them from your own Gmail on a schedule that protects deliverability. Set it up once, wake up to replies.

Start free with Gmail

Related guides