InMail vs Connection Requests: When to Use Each in 2026

InMail or connection request? It sounds like a budget question — InMails cost credits, connection requests are free — but the real tradeoff isn't money. It's attention, audience, and what each channel signals about how you found the prospect.

Used well, InMails are a scalpel and connection requests are a shovel. Used badly, they're both a hammer. Here is how experienced teams choose between them in 2026.

1. The 30-Second Version

If you take nothing else from this post:

• Default to connection requests with a personal note. Free, higher response, builds a long-term network.
• Use InMail when you need speed, when the prospect is out of your reach, or when the ask is serious.
• Don't use both on the same prospect in the same week. It reads as desperate.
• Free InMails (open profile recipients) are a different product from paid InMails. Treat them separately.

The rest of this post is the reasoning behind those four lines.

2. What Actually Shows Up in the Prospect's Inbox

A connection request arrives as a notification and a pending request. The recipient can accept, ignore, or decline. If they accept, your message history begins a normal thread. If they ignore, you can still send a follow-up note inside some paid tiers, but mostly you have to wait.

An InMail arrives as a message in a separate "InMail" folder, usually with a subject line and a response prompt ("Interested / Not interested / Maybe later"). The recipient can reply without connecting. The message is visually flagged as an InMail — the prospect knows you paid to reach them.

That tagging matters. An InMail that reads like a generic connection request feels worse than the connection request would have, because the prospect knows you could have just sent the free version.

3. The Credits Math (And Why "Free" Isn't)

Sales Navigator Core includes 50 InMail credits per month. Unused credits roll over up to a cap. If a prospect replies to your InMail (positively or negatively), the credit is refunded — so an InMail that gets a reply costs you nothing.

That last point is where the economics get interesting. At a 22% reply rate, each InMail effectively costs you about 0.78 of a credit. At a 14% reply rate, 0.86. If your reply rates are below 10%, you're burning credits much faster than the math suggests — the "refund" stops cushioning you.

• Don't InMail a prospect who wouldn't be worth a meeting. The economics punish you when the list is weak.
• Don't InMail a prospect you can just connect with. The connection path has no credit cost and a longer half-life.
• Do InMail when reply rate will be high enough that refunds absorb the cost.

4. Acceptance Rate vs Reply Rate — Two Different Metrics

Connection requests have a two-step funnel: acceptance, then reply. InMails have one step: reply. That difference confuses a lot of people who compare the two raw numbers and think InMail is worse.

• Connection request: 32% acceptance → 26% reply rate on first message to connections → 8.3% of prospects messaged ever reply.
• InMail: 18% reply rate → 18% of prospects messaged ever reply.

In that scenario, InMail produces more replies per prospect messaged — it just costs credits. For high-value prospects where the pool is small, paying for the higher conversion can make sense. For a volume campaign where the pool is huge, the free path wins on total replies.

5. When InMail Is Worth It

• You need to reach someone fast. Competitive deal, a trigger event, a campaign tied to a news item. Connection requests can sit for days; InMail lands today.
• The prospect is outside your network reach. You've been muted by LinkedIn's connection request filter, or they have a "connect via InMail only" preference, or they're a 3rd-degree contact with no shared network.
• The ask is serious. Candidate recruiting for senior roles, partnership inquiries, enterprise sales into named accounts where a plain connection request undersells the seriousness.
• You have a strong subject line. InMail's subject line is a real asset. A vague one ("Quick question") gets ignored; a specific one ("Re: your recent comment on Series C pricing structures") pulls open rates above 60%.
• Open Profile recipients. Free InMails to "Open Profile" users are a genuinely different product. Use those first before burning paid credits.

6. When Connection Requests Win

• Volume plays. Anything over 100 prospects per week. The credit math doesn't work at volume.
• You want the long-term network. A connection stays in your graph forever. It powers future organic posts, warm intros, and subsequent outreach.
• You're running a multi-touch sequence. After a connection is accepted, you have unlimited messages. After an InMail is ignored, you have none.
• You have a strong profile. If your profile is doing real selling, the connection request is a lower-pressure way to get the prospect to visit and self-qualify.
• Early-career and mid-career targets. They're generally more likely to accept a well-personalized request than to respond to a colder-feeling InMail.

7. The Hybrid Sequence

For named-account enterprise lists, the sequence that consistently outperforms either channel alone:

1. Day 1: Connection request with a personal note referencing something specific about the prospect.
2. Day 5: If accepted, first real message (question-led, 60–80 words).
3. Day 5, different prospect: If not accepted, send a targeted InMail with a different hook. Don't copy the connection request text.
4. Day 12: Follow-up on whichever channel is now active — the connection thread, or the InMail thread.
5. Day 19: One more value-add touch. After this, move to email or phone.

The trick is treating the two channels as a tree with a decision point at day 5, not as two parallel campaigns. Sending both a connection request and an InMail to the same prospect in week one reads as desperation.

8. A Quick Decision Framework

Run each prospect through these four questions:

1. Is this a named account or one of 500 similar prospects? If named, InMail is on the table. If 1-of-500, use connection requests.
2. Is there a time-sensitive trigger (funding round, job change, news item)? If yes, InMail. If no, connection request.
3. Are they a 3rd-degree contact with no shared network? If yes, InMail or skip. If closer, connection request.
4. Is the ask serious enough to justify a subject line? If yes, InMail. If no, connection request.

Three "no"s and the answer is almost always connection request. Three "yes"es and the answer is almost always InMail.

9. What to Do Before Either Channel

Both channels underperform when the groundwork is missing. Before you spend a credit or send a request:

• View the prospect's profile. Many will visit yours back organically, softening the cold touch.
• Like or thoughtfully comment on one of their recent posts. Takes 30 seconds. Meaningfully raises response rates on both channels.
• Make sure your own profile doesn't read like a resume. If it does, the recipient visits and bounces, regardless of which channel you used.

If you're running this at scale through Infonet, the platform sequences these warm-up actions automatically before the connection request or InMail goes out. The difference in response rate between "cold opener" and "opener that follows two warming touches" is consistently 8–12 percentage points — bigger than the difference between most first-message variants we test.

The Honest Takeaway

Most teams overuse InMail because credits feel like they need to be spent, and underuse connection requests because "free" feels less serious. The better heuristic: connection requests are your workhorse. InMail is a scalpel for the prospects who genuinely need it. And neither works if the profile and the groundwork aren't there first.