LinkedIn InMail vs Connection Request: Which Should You Send First?

InMail costs credits. Connection requests are free. But which one actually gets replies?

It's the most common question in LinkedIn outreach, and most advice answers it with a shrug. The truth is that InMail and connection requests are different tools for different jobs, and picking the wrong one wastes either your money or your most valuable prospects. This guide breaks down what each channel actually is, how they compare on the metric that matters (replies, not opens), when each one wins, and a simple framework so you always know which to send first.

We'll keep the numbers honest. Reply rates on LinkedIn vary wildly by industry, targeting, and message quality, so treat any benchmark as a rough range rather than a promise.

InMail explained

InMail is LinkedIn's paid messaging product. It lets you send a direct message to someone you are not connected to, landing straight in their inbox without a connection request. You get a monthly allotment of InMail credits with a paid plan like Premium or Sales Navigator, and you can buy more.

A few mechanics matter:

• Credits are limited. You don't get unlimited InMails. Each tier includes a set monthly number, so every send has a real cost — both in dollars and in opportunity, since you can't send another until your balance refreshes.
• Credit refunds. LinkedIn refunds an InMail credit if the recipient replies within a set window (historically around 90 days). So a reply effectively makes that InMail "free" again, which is a strong nudge to write messages people actually want to answer.
• Open Profile exceptions. Some users turn on Open Profile, meaning anyone can message them without spending a credit. It's worth checking before you burn one.
• Subject lines. InMail includes a subject line, which connection requests don't. That gives you an extra hook — and an extra way to get ignored.

InMail's appeal is reach: you can contact a CEO, a hard-to-reach buyer, or someone outside your network immediately, without waiting for them to accept anything.

Connection requests explained

A connection request asks someone to join your network. You can attach a short note (the limit is tight — typically around 300 characters, and sometimes notes are restricted depending on your account and the recipient). If they accept, you're 1st-degree connections and can message each other freely, forever, at no cost.

Key mechanics:

• Free, but capped. Connection requests don't cost credits, but LinkedIn limits how many you can send per week to protect the network from spam. Blowing past sensible limits risks restrictions on your account.
• The note is optional and short. You can send with or without a note. Either way you have far less room than an InMail to make your case.
• Acceptance is the gate. Nothing happens until they accept. A great message to someone who never accepts is wasted.
• Compounding value. Once connected, you can message them anytime, see more of their activity, and stay on their radar. That long-term access is something InMail doesn't give you.

For help writing the note itself, see our LinkedIn connection request message templates.

Open rate vs reply rate: the comparison that matters

People love to quote InMail "open rates," but opens are vanity. A message that's opened and ignored did nothing for you. The metric that pays your bills is the reply rate.

Here's the honest picture, with the caveat that real numbers depend heavily on your targeting and copy:

| Factor | InMail | Connection request + message | | --- | --- | --- | | Cost per send | Credits (limited / paid) | Free (weekly cap) | | Reaches non-connections instantly | Yes | No — must be accepted first | | Message length | Long, with subject line | Short note, then full access after accept | | Typical reply rate | Often lower per message; ranges widely | Often higher once connected; ranges widely | | Long-term access to the person | No | Yes, after they accept | | Best for | Hard-to-reach or time-sensitive targets | Building a network and ongoing outreach | | Refund on reply | Yes (within LinkedIn's window) | Not applicable (free) |

Two patterns hold up across most B2B outreach. First, a cold InMail usually has to do all its persuading in one shot, so its reply rate per message tends to run lower than a warm conversation with an existing connection. Second, the connection-request path often produces more total replies over time, because acceptance turns a stranger into someone you can message freely and follow up with naturally.

That said, "lower reply rate per InMail" doesn't mean InMail is bad — it means InMail is best reserved for cases where the connection path won't work or won't work fast enough.

When InMail wins

Reach for InMail when one of these is true:

• The person is hard to reach. Senior executives and busy buyers may ignore or never see connection requests, but a sharp, relevant InMail can land directly in their inbox.
• Timing is urgent. If you need a response this week — a trigger event, a renewal, a fast-closing opportunity — you can't afford to wait days for a connection to be accepted.
• You're out of the recipient's network entirely. When you have no shared connections and acceptance is unlikely, InMail removes the gate.
• The target has Open Profile on. You can message them without spending a credit, so the usual cost objection disappears.
• Your message is genuinely strong. Because replies refund the credit, a well-targeted InMail to the right person can be nearly free in practice.

The discipline with InMail is restraint. Limited credits force you to spend them only on prospects where the payoff justifies it, and to write each one as if it's your only shot — because it is.

When connection requests win

For most sellers and founders, the connection request is the default first move:

• High-volume prospecting. Because requests are free (within weekly limits), they scale across a large list in a way InMail credits never will.
• You want a relationship, not a one-off. Once connected, you can follow up, comment on their posts, and stay visible. That ongoing access compounds.
• You have something in common. Shared connections, the same group, or a recent interaction make acceptance far more likely — and a warm accept beats a cold InMail almost every time.
• You're running structured sequences. Outreach works best as a series of touches, not a single message. The connection path supports a natural multi-step follow-up after the accept.

The catch is patience and pacing. Connection-based outreach is a slower burn, and sending too many too fast is exactly what gets accounts flagged. Staying inside safe limits matters — see our notes on safe LinkedIn outreach limits.

A decision framework

When you're staring at a prospect deciding which to send, run this quick logic:

| Situation | Send first | | --- | --- | | Standard B2B prospect, you want a relationship | Connection request (with or without a note) | | You share connections, group, or recent interaction | Connection request | | Large list, high volume, building pipeline | Connection request | | Senior exec / unreachable buyer | InMail | | Time-sensitive opportunity, can't wait for an accept | InMail | | No shared network and low accept odds | InMail | | Recipient has Open Profile | InMail (it's free) |

The simplest rule of thumb: default to a connection request, escalate to InMail only when the connection path is too slow or too unlikely to work. Connections are free, scalable, and build lasting access; InMail is a precision tool you spend on the prospects who are worth a guaranteed knock on the door.

Whichever you choose, what wins is relevance and follow-up — not the channel itself. A lazy message fails on both. For the bigger picture, read our LinkedIn B2B lead generation guide.

How InstaLeadSync handles both at scale

Deciding channel-by-channel is fine for a handful of prospects. Across hundreds, you need a system. InstaLeadSync is an all-in-one, LinkedIn-led growth platform (invite-only and done-for-you) that runs outreach through a browser extension on your own real LinkedIn session — not a cloud bot. Actions are human-paced, respect daily caps, and warm up gradually so your account stays healthy.

In practice that means you build branching sequences that lead with a connection request, follow up automatically once someone accepts, and adapt the path based on whether they reply or go quiet. Requests that sit unanswered auto-withdraw after about 14 days to keep your pending list tidy. A 0–100 account-health score watches for trouble and auto-pauses outreach if LinkedIn shows a checkpoint, and every reply flows into a built-in CRM so no warm conversation gets lost.

Frequently asked questions

Should I send an InMail or a connection request first?

For most B2B prospects, send a connection request first — it's free, scalable, and builds lasting access once accepted. Reserve InMail for hard-to-reach executives, time-sensitive opportunities, or people unlikely to accept a request.

Do InMails get more replies than connection requests?

Not usually, per message. A cold InMail has to persuade in one shot, so its reply rate tends to run lower than a conversation with an accepted connection. Numbers vary widely by industry and message quality, so test with your own audience.

Are InMail credits wasted if no one replies?

LinkedIn refunds an InMail credit when the recipient replies within its set window (historically around 90 days). If they don't reply, the credit is spent. That's why InMails should be reserved for high-value, well-targeted prospects.

How many connection requests can I send per week?

LinkedIn enforces weekly limits to curb spam, and they can change. The safe move is to stay well under aggressive numbers and pace requests like a human. See our safe LinkedIn outreach limits for current guidance.

Can I automate both channels safely?

Yes, if it's done human-paced from your real session rather than a cloud bot. InstaLeadSync runs connection requests and follow-ups through a browser extension with caps, warm-up, and an account-health score that auto-pauses on checkpoints.

Send the right message, the right way

The channel matters less than the discipline behind it — relevant targeting, a real reason to reach out, and consistent follow-up. If you'd like to see how InstaLeadSync runs all of that safely from your own LinkedIn account, book a call with our team, or email team@instaleadsync.com.