2026-08-27

LinkedIn Cold Message Templates That Get Replies

10 LinkedIn cold message templates by trigger, the 300-character note that beats InMail, and the Day 1/3/7/14 follow-up structure that stops on reply.

Most LinkedIn cold outreach dies before anyone reads a word of it. The invite sits ignored, the note gets skimmed and dismissed, and the follow-ups never matter because the first step failed. A better pitch won't fix that. On LinkedIn, a cold message is really two messages: a 300-character connection note that earns you the right to talk, and a short first message after they accept. This post covers both. Ten LinkedIn cold message templates sorted by trigger, the Day 1/3/7/14 follow-up structure, and the one rule that protects every reply you get.

The connection note beats InMail for cold

InMail announces itself. It arrives labeled, and years of recruiter volume have taught people to skim past the tab it lands in. LinkedIn doesn't publish InMail reply rates, so I won't quote one. The structural problem is enough: an InMail is a stranger's paid message, while a connection request is a person asking to know you. One of those gets a fair read.

The note's 300-character limit is the feature, not the thing to fight. You can't fit a value proposition, three bullets, and a calendar link into 300 characters. You can fit one observed detail and one honest reason to connect. That's the entire format. It's why notes work for cold where InMail doesn't.

One detail, one reason, no pitch

Every template below follows the same skeleton. One observed detail that proves a human looked: a line from their post, a job opening, a tool in their stack. One honest reason you want to connect. And no pitch, no link, no 'quick question,' no compliment about their 'impressive background.' The note's only job is the accept. The pitch can wait, and the best sequences often never pitch at all.

Two mechanical rules. Stay under 300 characters after you fill in the brackets, and read the note out loud once before sending. If it sounds like a template, it still is one.

Ten templates you can copy, sorted by trigger

Fill the brackets with things you actually observed. A template with a real detail in it stops being a template.

The mutual connection does the intro

Hi [first name], [mutual name] and I worked together at [company], and your name came up when I asked who's actually good at [topic]. Figured I'd skip the six degrees and connect directly.

Their post already wrote your note

Hi [first name], your post on [topic] got passed around our team chat this week. The point about [specific claim] matches what we're seeing with [your situation]. Connecting so I don't miss the next one.

You were in the same room

Hi [first name], we were both at [event] last week and I never made it past the coffee line to say hi. Your question during [session] was the sharpest moment of the day. Consider this the lazy follow-up.

Their job openings tell you the timing

Hi [first name], saw [company] is hiring [number] [role]s. That usually means [your honest read on what's changing]. I like watching teams your size make that jump, so I'd like to follow along.

The tool in their stack is common ground

Hi [first name], noticed from [job post or stack page] that you run [tool]. We do too, and I've collected some strong opinions about [specific feature]. Happy to trade notes sometime, zero agenda.

They picked your competitor

Hi [first name], saw you're on [competitor]. Fair pick, they're good at [specific strength]. I build in the same space and want to understand what made the decision, not argue with it. No pitch fits in 300 characters anyway.

They just raised or launched

Hi [first name], congrats on [the round or launch]. The [specific detail from the announcement] caught my eye, since most companies in [space] bury that part. Connecting before your inbox becomes a sales conference.

They said something honest on a podcast

Hi [first name], caught your [podcast name] episode on the drive home. Your answer on [specific question] is the first straight one I've heard on that topic. Wanted to connect before I forgot where I heard it.

Their comment beat the post

Hi [first name], your comment on [author]'s post said more in four lines than the post did in forty. I try to keep my feed stocked with people who disagree in public with evidence. Hence the request.

Peers don't need a trigger

Hi [first name], we both run [function] at companies about the same size, so our weeks are probably 80% identical. I keep a short list of peers doing my job better than I do. You qualify.

The Day 1 message starts a conversation, not a pitch

An accept is permission to talk. It isn't permission to send four paragraphs and a booking link, and the fastest way to get archived is to treat it that way. The Day 1 message references the trigger from your note. It asks one question the person can answer from their phone.

Good to be connected, [first name]. Since you [the trigger, e.g. wrote that post about pipeline reviews], one thing I keep going back and forth on: [an honest, specific question about the problem you work on]. How does [company] handle it today?

Your profile already says what you sell. You don't have to hide it, you just don't lead with it. People check who's messaging them before they reply, so let the profile do the disclosure and the message do the conversation.

Day 3 is proof, Day 7 is a question, Day 14 is goodbye

Three follow-ups over two weeks is enough. More reads as a script, and the entire value of this channel is that it doesn't.

Day 3 carries proof: one real number or one named artifact. Something like 'Hi [first name], following up with something concrete. [Customer] cut [metric] from [X] to [Y] in [timeframe]. If [problem] is on your list this quarter, it's worth ten minutes.' Without a customer number, send a teardown, a benchmark you ran, or a template you made, under its real name. Never invent the stat. People check.

Day 7 is one question, sized for a phone screen: 'Is [problem] something you're actively working on right now, or parked for later? One-word answer is fine.' You're not asking for a meeting. You're asking for a signal, and 'parked' is a perfectly good one because it tells you when to come back.

Day 14 is the breakup: 'Last one from me, [first name]. I'll assume the timing's off and close the loop here. If [problem] moves up the list, everything's in this thread and I'm easy to find.' Send it and mean it. The breakup only works if it's real.

Personalization is a detail they can verify, not a compliment

'I'm impressed by your background' and 'I love what you're doing at [company]' are mail-merge tells. They fit anyone, which means they prove no one looked. The detail that moves replies is one a stranger couldn't fake without doing the work: a phrase quoted from their actual post, the number of [role]s they're hiring, the tool named in their job listing. One is enough. Two starts to feel like surveillance.

If a line could be sent to 200 people unchanged, it isn't personalization. Cut it.

Every benchmark you've read is self-reported

LinkedIn doesn't publish acceptance or reply-rate data, and nobody audits the screenshots people post about their own outreach. Every rate you've seen quoted is somebody grading their own homework. So no benchmark table here. Anyone quoting you a reply rate with a decimal point is selling a course.

Volume has a harder ceiling. LinkedIn caps invitations at roughly 100 per week, and no wording change compensates for a weak list. Ten well-chosen invites beat forty sprayed ones.

A reply ends the sequence, permanently

The fastest way to burn a warm thread is a scheduled Day 7 nudge landing two days after the person answered you. It outs the earlier messages as a machine. It retroactively poisons the ones that worked. So the rule is absolute: the moment a prospect replies with anything, even 'thanks for connecting,' the automation stops for good. A human writes what comes next. A templated response to a human sentence reads as exactly what it is.

The moment a prospect replies, with anything at all, the sequence stops for good.

That rule is the reason PoliteReach exists. It's built for founders and small sales teams running outreach on their own accounts. You write the connection note and the Day 1/3/7/14 messages before the campaign starts. Nothing is generated at send time, so what goes out is exactly what you approved. The published caps are the trust argument.

• 12 to 16 invites a day per account, jittered daily so no two days look alike
• A rolling 7-day counter that keeps each account under LinkedIn's limit of roughly 100 invitations a week
• Invites only go out during office hours you set
• Pending invites older than 30 days are withdrawn automatically, keeping the sent-to-accepted ratio healthy
• A reply halts that person's sequence instantly, for good

It's in early access, there's no pricing page yet, and it won't write your messages for you. That part has to be you. The waitlist is at politereach.com.