LinkedIn · 2026-03-25 · 5 min
InMail or Connection Request for B2B Outbound
InMail and connection requests solve different problems and are not interchangeable. Here is when each one earns its place, with the cost and behaviour differences that actually decide it.
The choice between InMail and a connection request gets treated as a matter of personal preference. It is not. The two mechanisms behave differently, cost differently, and suit different situations, and picking the wrong one for the situation you are in quietly caps your results before the message is even written.
What Each One Actually Is
A connection request is an invite to become a first-degree connection, with an optional short note attached. It is free, limited in weekly volume, and once accepted, opens an ordinary message thread that stays open indefinitely.
InMail is a paid credit that lets you message someone directly without being connected, typically included with a Sales Navigator or Recruiter seat, or bought separately. It bypasses the "please connect first" step entirely, but it costs a credit whether or not the person replies, and it sits in a folder that behaves slightly differently to the regular inbox.
Where Connection Requests Win
For most B2B outbound aimed at building a genuine, lasting relationship with a named account, connection requests are the better default, for a few concrete reasons:
- The relationship persists. Once someone accepts, you keep that connection permanently, regardless of whether the current conversation goes anywhere. That connection has ongoing value: they see your posts, you see theirs, and a second attempt six months later starts from a warmer position.
- The commitment is lower for the recipient. Accepting a connection is a small, low-friction decision. Replying to an unsolicited InMail from a stranger is a bigger one, because it looks and feels like being pitched to directly.
- It costs nothing per send, which matters when you are running a sustained, multi-week campaign across a real account list rather than a handful of one-off outreach attempts.
The trade-off is speed. A connection request requires acceptance before the real conversation can start, which adds a step and some delay to every single contact.
Where InMail Earns Its Cost
InMail has a genuine place, mostly in narrower situations:
- Time-sensitive outreach, where waiting for a connection to be accepted is not workable, such as reaching someone about a live, dated opportunity.
- Very senior or hard-to-reach titles who accept few connection requests but occasionally read a well-targeted InMail, because it arrives through a different, less crowded channel.
- One-off, high-value targets where the volume economics of a connection-based campaign do not apply, because you are trying to reach one specific person, not build a list-based motion.
The cost structure matters here. Every InMail spends a credit regardless of outcome, so sending InMail at the same volume as a connection-request campaign gets expensive fast, and the response rate per credit needs to justify that spend specifically.
A Side-by-Side View
| Connection request | InMail | |
|---|---|---|
| Cost | Free, within weekly limits | Costs a credit per send |
| Relationship after send | Persists once accepted | No lasting connection unless they respond and you separately connect |
| Best for | Sustained, list-based campaigns | Time-sensitive or single high-value targets |
| Recipient friction | Low, easy to accept | Higher, feels more like direct sales contact |
| Speed to first reply | Slower, gated by acceptance | Can be faster since there is no acceptance step |
How We Actually Use This
For the bulk of a researched, named-account campaign, connection requests are the primary mechanism, because the goal is a durable relationship with an account over months, not a single message landing once. InMail gets reserved for specific, narrower situations inside the same campaign: a genuinely senior title who has ignored two connection attempts, or a dated opportunity where waiting is not an option.
Mixing the two deliberately, rather than picking one as a blanket policy, is where most of the value sits. A campaign that only ever sends InMail burns budget on volume it was not designed for. A campaign that only ever sends connection requests occasionally misses a narrow window where InMail was genuinely the better tool.
When Neither Is the Answer
If the target audience genuinely is not active on LinkedIn, no combination of these two mechanisms will produce results, and the channel itself is the wrong choice, not the delivery method. That is a different diagnosis and worth ruling out before optimising between InMail and connection requests. You can see how we structure channel selection generally on our how it works page.
Next: audit your last month of sends and check whether InMail was used for genuinely time-sensitive targets or simply as a default, because that gap is usually where the budget is being wasted.