Key takeaway: The connection-request-then-message path beats InMail by roughly 6x on replies. In twelve months of measured LinkedIn recruiting activity (Noon AI platform data, ending July 2026), candidates who accepted a connection request replied to the follow-up message 34.2% of the time, while InMails drew replies just 5.5% of the time.
InMail is LinkedIn's paid shortcut: message anyone, no acceptance needed. The connection request is the slow path: ask first, message after. Recruiters overwhelmingly assume the paid shortcut performs better. The data says the slow path wins, and it isn't close.
The head-to-head numbers
| Path | Volume measured | Reply rate |
|---|---|---|
| Connection request → accepted → message | 76,507 requests / 14,821 accepts | 34.2% of accepts reply |
| InMail | 2,920 InMails | 5.5% reply |
Even accounting for the acceptance gate — 19.4% of requests are accepted — the end-to-end connection path converts about 6.6% of all requests into replies, still ahead of InMail's 5.5%, and every accepted connection stays in your network for future roles either way.
Why does InMail underperform?
- It signals mass outreach. Candidates know InMail costs credits and arrives from recruiters they've never seen. The format itself has been trained into "promotional" territory by a decade of volume.
- No micro-commitment. An accepted connection is a yes before the pitch. InMail asks for the reply and the relationship in one step.
- No compounding. An ignored InMail is a spent credit. An accepted connection is a permanent warm contact — the candidate sees your posts, your profile, your next role.
InMail still has a place: candidates who leave a request pending for weeks, or high-urgency searches where the acceptance delay is unaffordable. It is a fallback, not a default.
What should a LinkedIn recruiting sequence look like?
Based on the measured funnel:
- Connection request with a short, role-specific note.
- On acceptance: a specific message about the role — this is the 34.2% conversion moment; don't waste it on a generic pitch.
- No acceptance after ~1 week: continue via email touches, which carry the bulk of sequence volume, and consider InMail as the last resort.
- Keep the sequence alive two weeks — 90% of replies arrive within 14 days, and 65% arrive after the first message.
Running this manually across hundreds of candidates is the hard part — the timing windows, acceptance triggers, and channel switches are exactly the work that leaks. At Noon, the outreach agent executes this sequence natively: connection requests, acceptance-triggered messages, email fallbacks, and instant reply handling, tuned on the same dataset this report is drawn from.
All channel benchmarks in one place: the 2026 recruiting outreach benchmark report.
FAQ
What is the average InMail reply rate for recruiters? 5.5% in our measured 2025–2026 dataset (Noon AI platform data). Vendor-reported InMail response averages are often higher but based on self-reported or selectively-sampled data.
Do connection requests work better than InMail for recruiting? Yes — candidates who accept a connection request reply to the follow-up message 34.2% of the time, roughly 6x the InMail rate, and the end-to-end path converts more of the total audience too.
Should recruiters ever use InMail? As a fallback: for candidates who leave connection requests pending, or when acceptance delay is unaffordable. Default to the connection-then-message path.
