Everyone asking me whether they should use InMail or connection requests is really asking a simpler question: which one will get more replies? The answer is almost always connection requests — but context matters. Here is how I think about it.
What's the actual difference?
LinkedIn InMail is a paid message you can send to anyone on LinkedIn, regardless of whether you are connected. It lands directly in their inbox without requiring them to accept a connection first. It is available on Sales Navigator, Recruiter, and most premium plans — and it costs credits, which are allocated monthly based on your subscription tier.
Connection requests work the other way round. You send a request (with or without a personalised note), wait for the person to accept, and then send your message once you are connected. It is entirely free, and there is no hard limit on the number of connections you can have — though LinkedIn does cap how many requests you can send per day and per week, especially on newer or unwarmed accounts.
The mechanic sounds small, but it completely changes the psychology. With a connection request, the prospect makes an active decision to let you in before you even say anything substantive. That one step filters for people who are at least curious. With InMail, you skip that gate — which sounds better but often is not.
Reply rates: what the data says
The numbers I see across Flow AI customers and my own outreach are broadly consistent with what I hear from operators across the industry. Connection request acceptance rates run 15–25% for reasonably targeted lists, and of the people who accept, 30–40% reply to the follow-up message. That gives you a net reply rate of roughly 5–10% across the full list — and those are warm, self-selected conversations.
InMail reply rates sit at 10–25% depending heavily on seniority, industry, and message quality. At first glance that looks competitive. But the InMail number is already the net rate — there is no acceptance step — and it includes a lot more friction from people who never opted in to hear from you. Above 20% on InMail is genuinely strong; below 10% usually means the targeting or message needs work.
The other thing worth saying plainly: reply rate is not the whole story. A 25% InMail reply rate from the wrong audience produces nothing. A 12% connection reply rate from a precisely targeted list of decision-makers at companies in your ICP can fill a pipeline. Channel selection is maybe the third or fourth lever. Targeting and message quality are first and second.
Cost and quota reality
Connection requests are free. InMail is not. On Sales Navigator, you get roughly 50 InMail credits per month on the individual plan. On sponsored InMail campaigns, you can pay roughly $10 or more per send at scale — and that cost multiplies fast when you are running volume outreach.
For context, a single SDR running a disciplined connection-first cadence can send 300–400 personalised connection requests per month through a warmed account, follow up with accepted connections, and keep a healthy pipeline without touching InMail at all. The cost difference is not a rounding error; it is the difference between a tool that scales and one that caps out at 50 sends a month unless you pay more.
When to use connection requests
The honest answer is: most of the time. Connection requests are the right default for almost every B2B use case. That includes SDRs and AEs prospecting into accounts, agencies running outreach on behalf of clients, founders doing personal outreach, and anyone whose target audience is already reachable at 2nd degree.
The personalised connection note is your first impression. Keep it under 200 characters, make it about them, and do not pitch on the first touch. If your message makes them curious enough to accept, you have earned the conversation — and the follow-up message lands in a different psychological frame than an InMail from a stranger.
Flow AI automates this whole cadence: connection request, timed follow-ups once accepted, and a clean handoff to your inbox when a conversation starts. The key is pacing it to stay inside LinkedIn's daily limits, which is exactly what the Auto-pilot feature in Flow AI is designed to manage.
When to use InMail
InMail earns its cost in a narrow set of situations. The clearest one is executive-level cold contacts who are 3rd-degree or beyond — people your network cannot reach via a shared connection, and whose attention is worth paying for. C-suite and VP targets at enterprise companies sometimes fall into this bucket, especially if you are selling something with a high ACV.
It also makes sense in recruiter workflows where LinkedIn Recruiter already includes InMail credits and the target is genuinely a passive candidate who has not engaged with any other touch. And for event follow-ups — reaching people you met at a conference but who have not connected with you yet — InMail can feel less strange than a cold request with no context.
What InMail is not: a shortcut around bad targeting, a substitute for a compelling message, or a volume play. If you are sending 50 InMails a month and getting a 5% reply rate, the problem is not the channel.
Combining both channels
The approach I recommend to most people is a simple sequenced cadence: attempt the connection request first, and if there is no acceptance within 7 days, follow up with InMail. This lets you make the most of the free, higher-converting channel while still reaching genuine outliers who are worth the credit spend.
In practice, you will find that the majority of your meaningful replies come from the connection side. The InMail follow-up catches a small number of people who were interested but slow to act — and occasionally surfaces a conversation you would have missed entirely.
Flow AI tracks acceptance on every connection request, so you know exactly who accepted and who did not. That gives you a clean signal for when it makes sense to spend a credit rather than guessing.
The bottom line: start with connection requests, get your targeting and messaging sharp, and treat InMail as a precision tool for genuinely hard-to-reach prospects — not a volume channel. If you want to see how this plays out in practice, try Flow AI free and run a list through the connection-first cadence.
