InMail That Actually Gets Read: A Strategic Guide for Premium Users

The most common complaint about Premium Business InMail is "the reply rate is terrible." That complaint is almost always self-inflicted: users treat 15 monthly credits like they treat 200 daily connection requests, blast them at lookalike lists, and conclude the channel is broken. The channel is fine. The strategy is wrong.

The wrong way to think about InMail

InMail is not cold email with a LinkedIn skin. It is a paid permission slip to message someone you cannot reach by connection request — typically because they have closed their network, you have no mutual ties, or they sit at a level where a connection request would feel forward. The frame should be: "What did I learn that makes this person worth one of my 15 monthly credits?" If you cannot answer that in one sentence, do not send the InMail.

Three perfect uses (and one bad one)

InMail earns its place in exactly three scenarios:

1. The unreachable decision-maker. A CRO, head of growth, partner at a fund — someone whose inbox is closed but whose decisions matter most.
2. The warm signal from your 90-day viewer list. They already showed interest by viewing your profile; you do not need to ask permission to start a conversation.
3. The trigger-event response. A funding round, a promotion, a content post that directly maps to your offer — InMail before competitors get there.

And the bad use: generic lookalike lists. If you are using InMail because the contact does not accept connection requests, fine. If you are using it because you ran a Sales Navigator search and want to message 15 random matches, you are spending the wrong tool — see Premium vs Sales Navigator for which job you are actually doing.

Targeting — earn the credit before you spend it

For each potential InMail, walk through this checklist before sending. If any answer is "no", do not send.

• Can I name a specific reason this person, today, would want to read this?
• Is there a trigger event in the last 30 days that makes the timing not arbitrary?
• Can my message reference something specific to them — not just their title?
• Do I have one credible piece of proof (recommendation, case, mutual connection) I can include?
• Is my ask small enough that "yes" is plausible in 90 seconds?

This filter alone moves reply rates from low single digits into the 20–40% range for operators who run it strictly.

Message structure that beats the template trap

Templates are not the enemy; they are how you stop reinventing the wheel. The trap is sending obvious templates. A four-line structure that works without sounding canned:

1. Line 1 — specific observation. About their recent post, role change, company event. Proves you did not blast.
2. Line 2 — your bridge. What you have done that connects to that observation. Short, no flexing.
3. Line 3 — the offer. Something concrete and low-friction. Not "let me know if you want to chat". A specific resource or a 15-minute slot.
4. Line 4 — out. Make declining easy. "If now is the wrong moment, no worries."

Example skeleton (do not copy verbatim — adapt to your voice):

Saw your post on the Q1 hiring freeze — the way you framed pipeline-vs-headcount mirrors what we ran into when we crossed $4M ARR. We worked through it by replacing two SDR hires with a managed outbound layer; I have a 1-page write-up I can share. Worth a 15-min walkthrough next week, or just send the doc? Either is fine.

That is a message that respects the reader's time and asks for nothing extravagant. It will out-convert any "I help companies grow" template.

Five mistakes that kill reply rates

Fix these five and the channel becomes one of the highest-converting outreach surfaces a small operator has access to — but only because of the precision discipline, not in spite of it. The full Premium workflow is in our Premium breakdown.

Frequently asked questions