Skip to content
All articles
InMail5 min read

LinkedIn InMail Examples and Templates

A working InMail names one hook about the recipient, makes one point and asks one small question. The three examples here are illustrative, follow LinkedIn's own brevity and personalization guidance, and promise no reply rate.

On this page

A working InMail does three things in a few lines: it says why this specific person, it makes one concrete point, and it asks for one small next step. LinkedIn's own writing guidance for Recruiter is the closest thing to a house style, and it is short: be brief, personalize the message around something from the person's profile, treat it as a conversation starter, and skip pasted job descriptions or bare links (LinkedIn Help (opens in a new tab)). The examples below follow that shape. They are original, labelled illustrations, not real messages from clients, and no reply rate is claimed for any of them.

What a good InMail has to do

You are writing into a stranger's inbox with one credit, so the message carries the whole ask. Inside the 200-character subject and 2000-character body limits (LinkedIn Help (opens in a new tab)), three jobs have to be done:

  1. Name the hook. One sentence that proves you looked at this person, not at a list.
  2. Make one point. A small, specific observation or offer, not a product tour.
  3. Ask one thing. A question that is easy to answer in one line.

LinkedIn's guidance says simpler, more direct messages "produce greater responses" (LinkedIn Help (opens in a new tab)). Take that as a direction of travel, not a promise about your list.

Three illustrative examples

Each of these is an original illustration written for a made-up sender and trigger. Swap in your own specifics. No claim is attached to how any recipient reacted.

Trigger: they posted about a problem you solve

Subject: Your post on outbound hiring

"Your post argued that adding SDRs before fixing sequencing just multiplies the mess. I work with teams at that exact stage on LinkedIn outreach workflow.

Quick question: when you map a new sequence, do you start from the reply you want, or from the first message?"

Why it fits the shape: the hook is the post, the point is agreement plus relevance, and the ask is a single either/or question.

Trigger: the company is hiring for a role your product supports

Subject: Saw the ops hire

"Saw you're hiring an ops lead. When our clients hit that point, the bottleneck is usually handoffs between outreach and replies, not headcount.

Is that hire meant to own the outreach stack, or to take the follow-up load off the sales team?"

Why it fits: one observation, one diagnosis framed as experience, one clarifying question. It does not attach a deck.

Trigger: a shared group or interest

Subject: Same pilot-tracking pain

"We are both in the operations group, where the same thread keeps resurfacing: nobody trusts the pilot tracking sheet.

Curious how your team handles it today. Worth comparing notes?"

"Worth comparing notes?" is deliberately low-commitment, which matches LinkedIn's advice to ask for advice or opinions rather than push for a meeting (LinkedIn Help (opens in a new tab)).

How to personalize without slowing down

Personalization is one specific sentence, not a research project. LinkedIn's own method is to begin by reviewing the member's contact preferences under the Additional Info section of their profile, then reference profile content, shared experiences or interests in the message (LinkedIn Help (opens in a new tab)). That gives you a repeatable pattern:

  1. Read the profile for one hook: a recent post, a role change, a group, a stated interest.
  2. Write the hook as a sentence only that person could receive.
  3. Keep the rest of the message the same across a batch.

This is the difference between a template and a mail merge. The structure travels; the first sentence does not. If you want the broader sequencing view — where the InMail sits relative to a connection note or a follow-up — see InMail versus message and what an InMail is.

Mistakes that waste a credit

LinkedIn's guidance flags several directly: pasting a job description or a URL instead of writing to the person, opening with no context about who you are, and treating a networking inbox like a job board (LinkedIn Help (opens in a new tab)). Two more follow from the platform mechanics:

  • Spending all 2000 characters. Length signals that the message was not written for the reader. The examples above are a few sentences each.
  • Sending when a free route exists. If the person is a 1st-degree connection, you can message them for free (LinkedIn Help (opens in a new tab)); if they are a Premium member with Open Profile enabled, LinkedIn says you can message them for free too (LinkedIn Help (opens in a new tab)). Using an InMail there wastes a credit.

LinkedIn also warns, in its Sales Navigator guidance, that messages marked as spam can lead to account restrictions, and recommends personalizing messages and leaving time for a reply before following up (Sales Navigator Help (opens in a new tab)). Both habits are cheap and reduce risk.

The limit to keep in mind

LinkedIn's writing advice was written for recruiters, and the source page says so (LinkedIn Help (opens in a new tab)). The principles — brevity, one specific hook, a question — carry over to sales outreach, but the framing ("candidate", "role") does not. Rewrite the examples for your own buyer instead of lifting the recruiter language.

If you are comparing outreach tools, Visit Clapa. If you are still choosing the channel, start with the step-by-step send guide.

FAQ

What is the best LinkedIn note to request a connection?

LinkedIn's own checklist is short: keep it brief and specific, say how you found the person or what you have in common, explain why you want to connect now, and use a clear, polite tone (LinkedIn Help (opens in a new tab)).

How long should an InMail be?

Short. You have up to 2000 characters in the body and 200 in the optional subject (LinkedIn Help (opens in a new tab)), but the examples here keep the body to a few sentences on purpose.

Should an InMail have a subject line?

The subject is optional, but LinkedIn's guidance calls a direct, informative subject line part of what captures attention (LinkedIn Help (opens in a new tab)). Keep it to a handful of words drawn from the hook.

Can I reuse one InMail template for everyone?

You can reuse the structure, but not the first sentence. LinkedIn advises personalizing the message with something from the person's profile, so the hook has to change per recipient (LinkedIn Help (opens in a new tab)).

Sources

Put the workflow in perspective.

Explore Clapa, then use the guide to ask the right questions.

Explore Clapa