In short: For most recruiters, a personalised connection request produces more conversations per month than InMail, because you get far more of them. InMail reaches candidates at a slightly higher rate per message, but one Sales Navigator seat gives you roughly 50 InMail credits and around 350 connection requests over the same period - so volume wins on pipeline, not per-message quality.
Connection requests vs InMail is one of those debates that sounds like a quality question but is really a maths question.
That said, InMail isn't useless. There are specific scenarios where spending a credit makes sense, and knowing the difference saves you money and your LinkedIn standing.
What is the difference between InMail and a connection request?
LinkedIn InMail is a paid direct message you can send to anyone on LinkedIn without being connected. It arrives in the recipient's LinkedIn inbox and, on some account types, triggers a notification to their external email. You need a Premium or Sales Navigator subscription to send InMails, and each account gets a fixed monthly credit allowance - typically 50 credits on Sales Navigator Core. If the recipient responds, you get the credit back.
A connection request is free. You send a request to connect, optionally with a note of up to 300 characters, and the recipient sees it as an invitation. If they accept, you're connected and can message freely. If they ignore or withdraw it, the request disappears. LinkedIn caps the number of connection requests you can send (around 100 per week on most accounts, though LinkedIn adjusts this based on your acceptance rate), so there's a ceiling - but it's a far higher ceiling than InMail credits give you.
The structural difference matters for recruiters: InMail reaches people who haven't opted in to hearing from you. A connection request asks permission first, and when someone accepts, they've signalled at least mild interest - which is a warmer start to a conversation.
Which gets a higher response rate: InMail or connection requests?
Per message sent, InMail wins on response rate.
But that framing obscures the real number: conversations per month per seat. With 50 InMail credits, even a strong response rate gives you a modest number of conversations. With 350 connection requests (a reasonable monthly send on a healthy account), a personalised note gives you a meaningfully higher number - before you factor in that accepted connections then receive free follow-up messages.
Stack those two steps and the total conversation rate per request sent sits comfortably above what most InMail sends deliver.
The honest caveat: both numbers depend heavily on the quality of your message and how well-targeted your list is. A generic InMail and a generic connection request both get ignored.
When does InMail make more sense for recruiters?
InMail earns its credit in specific circumstances.
The person has their profile set to "Open to InMail" and isn't actively connecting. Some senior candidates and hiring managers keep their profile heads-down. They won't accept a random connection request but will read an InMail because it feels more deliberate.
You're reaching out to a 3rd-degree connection with no shared network. A cold request from someone with no mutual connections and no visible reason to connect has a low acceptance rate. An InMail with a clear subject line at least gets read.
You have a very short candidate list and need a high-touch approach. If you're running a retained search with eight target candidates, spending eight credits to reach all of them directly is a reasonable call. The economics flip when your list is 200 people.
The role is senior and the candidate is passive. An InMail to a FTSE 250 CFO carries a different tone to a connection request. For very senior placements, the formality lands better.
Outside those scenarios, a well-crafted connection request note does the same job for free.
When do connection requests work better?
Connection requests win on volume and warmth for the vast majority of recruiter outreach.
Candidate sourcing at scale. If you're filling a mid-market role and working a longlist, a personalised connection request is cost-free and scalable. InMail credits run out fast.
Client development. A hiring manager who accepts your connection request has taken a small, voluntary action in your direction. That acceptance is a warmer base for a follow-up message than cold InMail delivery. Understanding how the LinkedIn algorithm works for recruiters matters here too - your posts will start appearing in their feed once you're connected, which compounds the relationship over time without you doing anything extra.
Building a warm pipeline over time. Connecting first, then nurturing through your content and occasional messages, produces relationships that convert when the timing is right. InMail is a one-shot message. A connection is an ongoing channel.
When your acceptance rate is strong. If your profile is optimised, your headline is relevant and your content shows up in their feed, your connection acceptance rate is higher - which means your conversation rate per request sent goes up too.
Your headline is the first thing a visitor reads, so it's worth testing a few with the LinkedIn headline generator.
InMail vs connection request: quick comparison
| InMail | Connection request | |
|---|---|---|
| Cost | Paid credits (Sales Navigator from ~£79/mo) | Free |
| Monthly volume | ~50 credits (Sales Navigator Core) | ~400 requests (LinkedIn-dependent) |
| Response rate per message | Higher per message | Lower per message, but far higher volume |
| Acceptance step | No - lands directly in inbox | Yes - recipient must accept first |
| Requires Premium? | Yes | No |
| Credit returned if recipient responds? | Yes | N/A |
| Best pipeline use | Senior/passive candidates, 3rd-degree outreach, short high-value lists | Candidate sourcing at scale, client development, warm pipeline building |
| Warmth of follow-up channel | One-shot message | Ongoing - posts, messages, comments |
Response rate figures sourced from outflo.io and getfuzzy.ai, 2026. Re-verify before use; these are practitioner-reported, not LinkedIn's own published figures.
How to write a connection request note that gets accepted
The note is 300 characters. That's one sentence of context and one of reason. Recruiters who treat it as a cover letter get ignored; recruiters who treat it as a warm introduction get accepted.
A few things that work:
- Name the shared context. "I work with fintech scale-ups hiring AEs - your profile came up while I was researching the space." It's specific, it's relevant, it doesn't ask for anything yet.
- Don't pitch the role in the note. The ask comes after acceptance, in a direct message. The note's job is to get accepted, not to close.
- Write for this person, not for a list. "I'd love to connect and explore synergies" is automatic decline territory. A note that feels personal gets accepted; a template gets ignored.
- Check your character count. 300 characters is short. Write it in a notes app first.
How to write an InMail that doesn't waste a credit
InMail has a subject line - use it. The subject line is what determines whether the message gets opened. "Opportunity at [Company]" gets deleted. Something like "CFO search - your name came up" is more likely to get opened because it's specific and it implies a referral.
Inside the message:
- Lead with why this specific person, not why this specific role.
- Keep it short. Three short paragraphs is plenty. If you need more, you're pitching too hard.
- Make the ask easy. "Would a 15-minute call this week make sense?" is a lower commitment than "Are you open to a new opportunity?"
- Never attach a job description. That signals you're fishing, not headhunting.
The credit-return mechanic is worth remembering: if the recipient responds (even to decline), you get the credit back. A polite, specific InMail that gets a "not for me right now" response still costs you nothing.
Does content on LinkedIn affect how InMail and connection requests land?
Yes, and this is the part most recruiters miss.
If a hiring manager has seen your posts in their feed before your connection request arrives, your acceptance rate is meaningfully higher. You're a recognisable presence in their feed instead of a cold name. The same effect applies to InMail: a prospect who's engaged with your content in the past is far more likely to read and respond to your message.
This is why treating LinkedIn outreach (InMail or connection requests) as separate from your LinkedIn content is a mistake - outreach and content belong in the same system rather than separate workflows.
Content that converts for recruiters tends to fall into four types: posts that start conversations (questions, opinions, observations that prompt comments), posts that deliver value to a specific reader (your ideal client or your ideal candidate, not both at once), personal posts that make you recognisable as a person, and success stories that demonstrate what you do. Understanding which type to post when, and for which reader, is a strategy question.
If you're looking for inspiration on what to post, there are specific post ideas for data recruiters and IT recruiters that follow the same pillar logic.
Stuck on what to post? The free LinkedIn post idea generator spins up one angle per content pillar in a few seconds.
Should recruiters combine InMail and connection requests?
Yes, when it makes sense to sequence them. A common approach that practitioners report working well:
- Connect first (with a personalised note).
- If the request is ignored after about a week, send an InMail.
- Follow up the InMail once, briefly, a few days later if no response.
- Move on.
This approach uses your free channel first and spends a credit only when the free approach has already been tried. Evaboot's analysis of InMail vs connection requests covers the sequencing logic in more detail.
The mistake is spending InMail credits on people who would've accepted a connection request anyway. Save InMail for the list where connection requests aren't landing.
A third option: LinkedIn content that brings conversations to you
InMail and connection requests are outbound. You go to the person. Content is inbound - the person comes to you, or at least arrives warm when you do reach out.
For recruiters who want LinkedIn to generate client and candidate conversations without spending hours on outreach, a consistent content strategy compounds over time in a way that outreach alone doesn't. One good post that reaches a hiring manager's feed is doing outreach to dozens of people simultaneously, at no credit cost.
This is what MyCopyPal is built for. It's a LinkedIn content tool built by a recruiter and copywriter, for recruiters, focused on posts that start client and candidate conversations rather than vanity metrics. Every post is written for one named reader - your ideal client or your ideal candidate by design.
The strategy layer (on the Pro plan at £35/month) gives you a 30-minute intake, then a content calendar that tells you which pillar to post, for which audience, on which day - across four pillars: Conversation starters, Valuable posts, Personal posts and Success stories. The AI is trained to avoid the generic phrasing that makes LinkedIn posts sound the same, and it learns from your edits so posts sound like you over time. Performance tracking is weighted to conversations, not impressions, because a comment or DM signals real pipeline intent in a way that an impression alone doesn't.
How to decide: a quick framework for recruiters
Ask yourself these questions before you choose a channel.
1. How long is my list?
If you're reaching 200+ people for a role, connection requests are the only scalable answer. If it's 10-15 senior targets, InMail makes more sense.
2. Do I have a shared context or mutual connection?
A connection request with a specific reason to connect gets accepted far more often than a cold one. If you have no context, an InMail with a strong subject line might perform better.
3. Has this person seen my content before?
If they follow you or have engaged with a post, a connection request from you isn't cold. Send it.
4. How senior is the target?
Mid-market candidates: connection requests. C-suite or board-level passive candidates: InMail, and invest time in the message.
5. What's my monthly credit situation?
If you're sitting on unused InMail credits with three days to go in the month, use them. They don't roll over on most plans.
6. Am I using LinkedIn content to warm my outreach list?
If not, that's the most impactful change you can make before optimising which outreach channel to use.
What is the difference between LinkedIn InMail and a connection request?
Which has a higher response rate: InMail or connection requests?
How many InMail credits do you get on LinkedIn?
Do you need Sales Navigator to send InMail?
Is it worth paying for Sales Navigator if you mostly use connection requests?
Can you send a connection request without a note?
Does LinkedIn penalise you for low connection request acceptance rates?
What is the character limit for a LinkedIn connection request note?
Do InMail credits get refunded if someone responds?
How does LinkedIn content affect InMail and connection request success rates?
Bottom line: which should recruiters use?
For most recruiters, most of the time, a personalised connection request beats InMail on pipeline produced per month because the volume advantage overwhelms the small per-message response rate gap. Spend InMail credits on short lists of senior or passive targets where a cold request is unlikely to land. On everything else, invest the time in a better note instead of a paid channel.
MyCopyPal is a LinkedIn content tool for recruiters who want to write posts that generate inbound leads. MyCopyPal builds you a personalised content strategy, tells you what to write each day, and writes posts in your voice. Want to try it out? You can write your first 3 posts for £5.
