The result
| Variant | Reply rate | Meeting rate |
|---|---|---|
| Sales Navigator InMail | 3.7% | 0.4% |
| Connection request then message | 37.0% | 5.1% |
Sample
2023, twelve weeks, 4,330 prospects. Companies of 500 to 2,000 employees. CTOs and product leaders. Split at random inside each account.
Why it works
Senior buyers read InMail as advertising, because functionally that is what it is. It carries a label, it arrives without a relationship, and it is the one message type in LinkedIn that a stranger can pay to place in front of you. Everyone who receives them has worked that out.
A connection request is a different object socially. It asks for something small, it is reciprocal, and accepting it is a decision the recipient makes rather than one made for them. By the time you send a message, the person has already said yes to something.
The credit economics make it worse. Because InMail costs money per send, teams treat the send as the valuable thing and write to justify it: longer messages, more product detail, a meeting ask in the first line. Every one of those choices tested badly on its own.
How to apply it
Send a connection request with a short note, then message after acceptance. The note is capped at 300 characters, which sits inside the 240 to 420 band that peaked at 38.6 percent replies in our length test.
If your acceptance rate is low, that is a targeting problem, not an argument for InMail. Fix the list.
Keep InMail for the narrow case it is actually good at: a named individual you cannot reach any other way, where the cost per send is irrelevant because the account is worth it. As a channel for volume it does not work.
What this test does not tell you
One test, one segment: technical and product leaders at 500 to 2,000 employee companies. The effect size is large enough that we are confident about direction elsewhere, but we have not measured InMail against connection requests for every persona. LinkedIn also changes InMail delivery and credit rules regularly, so this reflects 2023 behaviour.
Method
One variable at a time. A test alters a single element; if two things change we learn nothing. Prospects were split at random inside each client account, holding industry, geography, seniority and company size constant on both sides. No test was called below 2,000 prospects per arm, because outbound is noisy at low volume. Reply rate is reported as the leading indicator and meeting rate as the decision, because several variants lifted replies and produced no extra meetings at all, and those were not rolled out.
This test is one of fifteen in a dataset covering 389,890 prospects and 15,018 meetings across 41 client programmes and 17 clients, run between 2018 and 2026. The full set is on the 2026 outbound benchmarks page.
Cite this page as: Prospectio.ai, Test 2: organic connection request against Sales Navigator InMail, from The Prospectio Outbound Evidence Report 2026.