How to Write a LinkedIn Outreach Message That Gets a Reply
Start from something the person did on LinkedIn this week, write four lines inside a character budget, and have the two follow-ups written before the first message goes out. Templates, a worked example and the ten-point check we run before sending.
Here is how to write a LinkedIn outreach message that gets a reply: pick one thing the person did on LinkedIn in the last two weeks, write four short lines about it (the signal, why it matters to them, who you are, one small ask), keep a connection note under 200 characters and a first message under 400, and write both follow-ups before you send anything. No pitch, no meeting request, one question. The templates, the character budget and a filled example follow.
What you need to write a LinkedIn outreach message
You need less than the ranking guides suggest. A free LinkedIn account works for connection notes and messages to first-degree connections; InMail needs Premium or Sales Navigator. You need a list of 20 to 50 people who match your ideal customer, each with one recent LinkedIn action next to their name. If your list has names but no actions, build it first with the prospect list guide and come back.
You also need a presentable profile, because every recipient opens it before replying. Headline that says who you help, a real photo, one recent post. Ten minutes fixes most profiles. And you need a spreadsheet with five columns: name, signal, date sent, reply, next step. That sheet is where the follow-ups live.
Time: about four minutes per person once the signal is in the sheet. Twenty messages is an hour and a half, including the research.
Step 1: Start from what the person did, not from who they are
The message is about the signal, not about the person's job title. A signal is a public action that tells you the person is thinking about the problem you solve right now (the buying signal lesson defines the term and lists the ones worth chasing). "Head of Sales at a 60-person SaaS" is a list entry. "Commented on a competitor's post about CRM data decay on Tuesday" is a reason to write.
| Signal | Where to find it | What it tells you | Opening line it supports |
|---|---|---|---|
| Commented on or liked a competitor's post | The competitor's post, "reactions" list | They are reading about your category this week | "Saw your comment under [name]'s post on [topic]" |
| Wrote a post about the problem | Search: "[problem]" filtered to Posts, past week | They own the problem and have an opinion | "Your post on [topic] made a point I had not seen" |
| New job in the last 90 days | Profile, "Experience", or search filter "Changed jobs" in Sales Navigator | New budget, new tools, no incumbent loyalty | "Congrats on the move to [company]. First 90 days usually mean [X]" |
| Company is hiring for the role you make easier | Company page, "Jobs" tab | They are about to pay a salary for the thing you do | "Noticed [company] is hiring a [role]" |
| Followed or engaged with an industry leader on your topic | The leader's recent posts | Interest, weaker than a comment | "You and I both follow [name]; their take on [topic] ..." |
Pick the strongest signal per person and ignore the rest. One signal per message. If you want the engagement signals found and scored for you instead of scrolling reaction lists every morning, Intentsly's LinkedIn signals watch competitor and industry-leader posts and rank the engagers against your ideal customer, which is the step this guide replaces with manual work; the competitor engagers how-to covers doing it by hand.
Write the signal into the sheet in one line, with the date. You will reuse that line in all three messages.
Step 2: Pick the channel: connection note, message or InMail
The channel decides the length, so decide it before you write.
| Channel | Who can receive it | Length to work to | Use it when |
|---|---|---|---|
| Connection request with a note | Anyone not yet connected | Under 200 characters | Default for cold outreach; the note is read in the invitation box |
| Message to a first-degree connection | People already connected | Under 400 characters | After acceptance, or for existing connections who just showed a signal |
| InMail | Anyone, if you have Premium or Sales Navigator credits | Under 400 characters, subject under 60 | The person does not accept requests, or you have no time to wait |
| Message request via a shared group or event | Members of a group or event you both belong to | Under 400 characters | You share a group and want to skip the connection step |
Two things about the note limit. Third-party guides disagree on the cap: Hublead quotes LinkedIn Help at 200 characters, QuickMail says 300. LinkedIn's own help pages could not be opened while writing this, so neither figure is confirmed here. Trust the counter in the invitation box, and write every note under 200 so it fits whichever limit your account shows. Hublead also reports that free accounts get three personalised notes a month; if that is what your account shows, spend the three on the strongest signals and send the rest without a note, then put the signal in the first message after acceptance.
On length for the longer formats, the only primary data found is LinkedIn's own: in LinkedIn's analysis of InMails sent between May 2021 and April 2022, InMails under 400 characters got a response rate 22% above the average, InMails over 1,200 characters got 11% below it, and InMails sent one at a time did about 15% better than bulk sends. That is recruiter data, not sales data, so treat it as a direction rather than a benchmark. The direction is clear: short, individual, written for one person.
Step 3: Write the four lines inside the character budget
Every outreach message, whatever the channel, is the same four lines. The budget keeps the note under 200 characters and the message under 400.
| Line | Its job | Note budget | Message budget | Example (hypothetical) |
|---|---|---|---|---|
| 1. Signal | Prove you looked | 60 characters | 90 characters | "Saw your comment under Priya's post on CRM data decay." |
| 2. Why it matters to them | Show you understood the problem | 50 | 110 | "Most teams only notice it when the quarter's pipeline turns out to be half stale." |
| 3. Who you are | One clause, no adjectives | 40 | 80 | "I run RevOps for five-person sales teams." |
| 4. One small ask | A question they can answer in a sentence | 40 | 80 | "Did you end up fixing it in the CRM or upstream?" |
Rules per line. Line 1 names the specific thing: the post topic, the author, the role they hired, the company they joined. "Love what you're doing at [company]" is not a signal, it is a template. Line 2 is the hardest and the one that gets the reply: say the consequence of the problem in their words, not yours. Line 3 is the only line about you, and it is a fact, not a claim. Line 4 asks for information, never for time. "Worth a call?" on a first message is the most common reason a message gets ignored.
Connection note (write it in the sheet first, then paste; count the characters):
Saw your comment under Priya's post on CRM data decay. I run RevOps for 5-person sales teams. Did you fix it in the CRM or upstream?
That is 132 characters. First message after acceptance, where the four lines get their full budget:
Thanks for connecting, Dan.
Your comment under Priya's post on CRM data decay stuck with me. Most teams only notice it when the quarter's pipeline turns out to be half stale.
I run RevOps for five-person sales teams, so I see the same thing every quarter.
Did you end up fixing it in the CRM or upstream?
That is 307 characters. Nothing about your product yet. If they answer "upstream", you have a conversation; if they answer "neither, it's still a mess", you have a qualified lead. Either way the next message can be about them.
A short list of asks that get answers, for line 4: "How did you solve X?", "Is that still the plan after the move?", "Who owns that now, you or ops?", "Was that post from a real incident?". Asks that do not: "Open to a quick chat?", "Can I send you a deck?", "Would you be interested in learning more?".
Step 4: Write the two follow-ups before you send the first message
Follow-ups written in the moment turn into "just checking in". Write both before you send message one, put them in the sheet, and send them on a schedule. A cadence inside what the ranking guides suggest: follow-up one three days after the first message, follow-up two five days after that, then stop. Lemlist's guide sets the floor at 24 hours between messages and no more than one message a day; Nutshell's suggests the break-up message after two or three silences. Three messages total is enough. A fourth reads as pressure.
Each follow-up carries the same signal forward and adds one new thing: a resource, a number, or a question from a different angle. Never repeat the first message with "bumping this".
Follow-up one (three days later):
One more thought on the data decay point. The fix that held for two of my clients was a monthly "who still works there" pass on the top 200 accounts, done by the SDRs, not ops. Happy to send the checklist if useful. Is the stale-pipeline problem still on your list this quarter?
Follow-up two (five days after that, the last one):
Last note from me, Dan. If the pipeline hygiene thing is handled, ignore this and I will stop. If it is not, I can show you how the monthly pass works in 15 minutes, no deck. Either answer is fine.
The second follow-up is the first and only place a meeting is mentioned, and it gives permission to say no. That permission is what gets the "not now, ask me in January" replies, which are worth more than silence.
A worked example: Ridgeline Ops writes to Dan at Fieldstone (hypothetical)
Ridgeline Ops is a hypothetical five-person RevOps consultancy. Dan is the hypothetical Head of Sales at Fieldstone, a 60-person SaaS company. Here is the whole sequence from the sheet.
| Day | Channel | Signal carried | Message |
|---|---|---|---|
| Day 0 (Tuesday) | Connection request with note | Dan commented under Priya K.'s post on CRM data decay on Monday | "Saw your comment under Priya's post on CRM data decay. I run RevOps for 5-person sales teams. Did you fix it in the CRM or upstream?" |
| Day 1 | Dan accepts, no reply | Nothing sent; the acceptance is not a reply | |
| Day 1 | Message | Same comment | The 307-character first message above |
| Day 4 | Message | Same comment plus a resource | Follow-up one, the monthly pass checklist |
| Day 9 | Message | Same comment, permission to decline | Follow-up two, the last note |
Three outcomes, and what Ridgeline does with each. Dan replies to message one with "Upstream, we fixed the forms": Ridgeline asks what broke the forms in the first place, and the conversation is about Dan's process for two more messages before anyone suggests a call. Dan replies to follow-up two with "Not now, Q1": Ridgeline writes "January" in the sheet and sends nothing until then. Dan never replies: the row is closed on day 9, and Ridgeline does not message Dan again unless a new signal appears. A new comment in three months is a new conversation, with a new line 1.
Notice what the sequence never contains: a feature, a pricing mention, "we help companies like yours", a calendar link in message one, or the word "solution".
Where this goes wrong
Three mistakes account for most of the silence.
The compliment that could go to anyone. "Impressive background" and "love your content" are the first line of thousands of messages a week, and recipients read them as the opening of a pitch. If line 1 would make sense sent to anyone else, it is not a signal. The test: could the recipient tell which post, which hire, or which comment you mean? If not, rewrite it or send no note.
Two asks in one message. "Would love to connect and also hear how you think about X and maybe grab 15 minutes" gives the reader three things to say no to. One question, answerable in a sentence. The meeting ask waits for the second follow-up, or for the reply.
The pitch disguised as a note. The connection note has room for a signal and a question, not for what you sell. Putting "we help B2B teams cut churn by 30%" in the note turns the invitation into an advert, and a pile of ignored invitations is bad for the account as well as the campaign. The Indie Hackers dataset PhantomBuster cites (16,492 invitations, 2023) put average acceptance at 37%, and 63% of the acceptances came within 24 hours. That is the rate a signal-first note competes with, and a note that reads like an advert is the kind the reader has already learned to decline.
A fourth, smaller one: sending on Saturday. In LinkedIn's InMail data, Saturday sends did 8% worse than average, and the ranking guides lean towards Tuesday to Thursday for sales messages. It is a small effect. The signal matters far more than the day.
The ten-point check before you press send
Run this on every message, in the sheet, before it goes out. One failed check means rewrite, not send.
- Line 1 names a specific post, comment, hire or job change, with a date inside the last two weeks.
- The recipient could tell exactly which action you mean.
- Line 2 states a consequence of their problem, in words they would use.
- Line 3 is one factual clause about you, with no adjectives.
- There is exactly one question, answerable in a sentence.
- No meeting request, calendar link, deck or price anywhere in message one.
- Connection note under 200 characters; message or InMail under 400.
- Nothing in the message would make sense if sent to a different person.
- Both follow-ups are written and dated in the sheet.
- Today's count for this account is under 15 sends, and never over 30.
What to do with the replies
A reply within the first hour of their message doubles as a second signal: they are at their desk and thinking about the topic. Answer their question, ask one more about their situation, and only then offer the call, phrased as "I can show you the monthly pass in 15 minutes" rather than "let's hop on a call". Put the reply and the next step in the sheet the same day.
Keep the daily volume where your account survives. Our own caps on the AI SDR side are a maximum of 30 messages and 30 connection requests per LinkedIn account per day, and we recommend 15; by hand, 15 well-written messages is also about what one person can do in an hour. If you need to find the right 15 people first, the decision-makers guide covers the search strings, and the guides index has the rest of the outbound series.
When the four-line structure is working and the limit is your time rather than your writing, that is the point to let the finding and the first conversation run without you. We ran the signal-first version of this on ourselves, with Intentsly's AI SDR doing the sending and the replies from LinkedIn signals, and booked 14 qualified demos in 14 days with zero manual outreach, at a reply rate 4x our previous cold campaigns. Try the AI shows you which buyers are showing signals for your offer right now, with no account, which is the fastest way to see whether the signal-first message has enough people to write to.
FAQ
How long should a LinkedIn outreach message be?
A connection note under 200 characters, a first message under 400 characters and an InMail under 400 with a short subject line. Those lengths come from the four-line structure: signal, why it matters, who you are, one ask. LinkedIn's own InMail data found the shortest messages got the best response rates, and nothing in sales outreach suggests the opposite.
Should I add a note to a LinkedIn connection request?
Add a note when you have a real signal to put in it, and send the request blank when you do not. A blank request is better than a generic note, because a generic note reads as a pitch. If your account limits personalised notes, spend them on the strongest signals and move the signal into the first message after acceptance.
How many LinkedIn connection requests can I send a day?
Work to 15 a day per account and never above 30. Those are the caps we run on our own sending, and they leave room under whatever weekly invitation limit LinkedIn applies to your account. New or quiet accounts should start lower, around 10 a day, and increase over two or three weeks as acceptances come in.
What is a good reply rate for LinkedIn outreach?
There is no reliable public benchmark for sales messages; the figures in ranking guides are unsourced. Measure your own: replies divided by first messages sent, per week, per signal type. If signal-first messages do not beat your old template within two weeks of 15 messages a day, the problem is line 2 or the list, not the channel.
InMail or a normal message: which is better?
A normal message to a first-degree connection, every time you can get one, because it costs nothing and arrives in the main inbox. Use InMail only for people who do not accept connection requests or when you cannot wait for acceptance. Whichever you use, keep it under 400 characters and write it for one person, not in bulk.
What should the first message say after someone accepts my request?
Thank them in one line, then run the four lines at full budget: the same signal from the note, the consequence of the problem in their words, one clause about you, and one question they can answer in a sentence. No deck, no calendar link, no "would love to learn more about your business". The meeting ask comes after the reply or in the last follow-up.
