LinkedIn Comment to DM Outreach Templates (7 Examples)
These templates are for founders and sellers who would rather start a LinkedIn conversation under someone's post than in a cold inbox. One principle makes every LinkedIn comment to DM outreach template work: continue the thought from your comment instead of announcing that you left one. "Saw you liked my comment" is a receipt. "The point you made about churn in month two got me wondering..." starts a conversation.
Below are seven messages. They are grouped by whether you're already connected, and the last one is for when nobody replies. Fields like {their_point} are yours to write by hand. No tool can fill them in honestly, and that hand-written line is the reason this approach beats cold outreach.
Which LinkedIn comment to DM outreach template to use
| Scenario | Template | Goal |
|---|---|---|
| You commented on their post, not connected | 1. The note that picks up the thread | Accepted request |
| You both commented on a third person's post | 2. The shared-thread note | Accepted request |
| Your comment pushed back on their point | 3. The respectful disagreement | Accepted request and a real exchange |
| They replied to your comment | 4. Move the reply into DM | Longer private conversation |
| Already connected, you commented | 5. The question you couldn't fit | First reply |
| They commented on your post | 6. The inbound thank-you | Reply and discovery |
| No answer after about a week | 7. The resource nudge | Reply or a clean close |
Templates when you're not connected yet
Connection-request notes have to stay under 300 characters, and merge fields expand when they're filled in. Before you judge the length, draft each note with the real name and topic in place.
1. The note that picks up the thread
Hi {first_name}, I commented on your {post_topic} post. Your point on {their_point} is the bit most people skip. I'm working on the same problem at my end and want to keep reading what you write. Happy to connect?
This names one specific thing from their post, which proves you read it. It also gives a reason to connect that isn't a pitch. Send it within a day of commenting, while your comment is still near the top of their notifications.
2. The shared-thread note
{first_name}, we both ended up in the comments on {author_name}'s post about {post_topic}. Your take on {their_point} was sharper than the post, honestly. Would be good to connect and compare notes.
Here the third-party author is the common ground, so you don't have to invent a reason to reach out. Use it for buyers who rarely post themselves but comment a lot. Many senior people fall into that group.
3. The respectful disagreement
Hi {first_name}, I pushed back a little in your comments on {post_topic}. Not to score a point. I think {their_point} holds for most teams but breaks at {edge_case}. Curious if you've hit that. Happy to connect either way.
People remember a thoughtful disagreement, and they forget "Great post!" almost immediately. Only send this if your comment was civil and specific. If the thread turned heated, skip the DM.
Templates when you're already connected
There's no 300-character cap here. Still, a first message should fit on a phone screen without scrolling, so keep it to three or four lines.
4. Move their reply into DM
Thanks for replying to my comment, {first_name}. I didn't want to hijack your post with my side of it, so moving here: when you said {their_reply_point}, was that learned at {company} or somewhere earlier? Asking because we're about to make the same call.
The comment section is public, and some questions belong in private. If you say that plainly, the switch to DM makes sense to them and doesn't feel like a funnel.
5. The question you couldn't fit
{first_name}, one thing I couldn't fit into my comment on your {post_topic} post: how did you decide when {their_point} was worth the cost? Most writing on it skips the "when".
It's short and asks one question, and only the author can answer it. For more openers built on someone's own content, see Outreach Opener Referencing Their Content.
6. The inbound thank-you
Hi {first_name}, thanks for the comment on my {post_topic} post. You mentioned {their_comment_point}, which made me think you've run into this at {company}. How are you handling it today?
This is the warmest lead on the page, because they raised their hand in public. Ask about their situation before you say anything about yours. Save the offer for message two or three, using the pacing in First message after LinkedIn connection templates.
When nobody replies
7. The resource nudge
Hi {first_name}, came across {resource} and thought of your post on {post_topic}, specifically the {their_point} part. No reply needed, it just felt like it belonged next to what you wrote.
Send it about a week after the previous message. It gives them something useful instead of a "just bumping this." If it also gets silence, stop following up and send one polite close. 6 LinkedIn Breakup Message Templates (Copy and Paste) has versions that don't sound bitter.
Why the comment turns a cold lead warm
When you comment on someone's post, LinkedIn notifies them, and the notification shows your name, photo and headline. By the time your connection request arrives, you're the person from the comments, not a stranger with a job title. That shift in familiarity is the whole warm-lead advantage, and cold outreach can't reproduce it.
It also matters for account safety, which most people don't consider. LinkedIn pays attention to how recipients respond to your invitations. Requests that sit ignored, or get marked as coming from someone the recipient doesn't know, count against you. Enough of those and LinkedIn restricts your ability to send invitations. A request from someone who appeared in their notifications yesterday is much less likely to get that response, so your acceptance history stays healthy.
The third benefit is relevance you didn't have to invent. A cold message has to guess at a reason to talk from someone's title and company. With this approach, the person picked the topic themselves by writing the post.
So here's my position. For any prospect who posts, a LinkedIn comment to DM outreach template should be your first touch, not a cold note. Keep cold sequences for prospects who never post, and use the no-pitch structures in LinkedIn Cold Message Without Pitching: Templates for those.
The trade-off is real. A comment worth reading takes a few minutes, so you won't write fifty a day. Use this for your best-fit accounts, the ones where a single reply is worth the time.
About timing: don't DM within minutes of commenting. A message that lands right after your comment makes the comment look like bait. Wait a few hours, and send within a day.
What makes these sound scripted
Quoting their post back word for word. Paraphrase it. Repeating a sentence verbatim reads like a scraper did it, even when you typed it yourself.
Pointing at likes. "Noticed you liked my comment" refers to a click, not a thought. Like-based DMs usually sound automated because they usually are.
A comment with nothing in it. If your comment was "Great insights!", there's no thought to continue, and every template above falls flat. Write a comment you'd be comfortable having quoted back to you.
Pitching in the note. The connection note exists to get accepted. If you're tempted to cram a value prop into it, sending the request without a note is better, and Connection request with or without a note templates covers when that works. For this play, though, the note is what links the request to your comment, so keep it and keep it clean.
Identical sentence shapes across a batch. Treat these templates as skeletons. If ten prospects all get "Your point on X is the bit most people skip," someone will screenshot it eventually.
Running the follow-up without babysitting it
The comment itself should stay manual. Nothing in this play benefits from automating it, and a canned comment undoes the warm-lead advantage before the DM is even sent.
The steps after the comment are where a tool helps. In Ampliflow's drag-and-drop workflow builder, you can set up a sequence like this: connection request with template 1, an If/Else branch on acceptance, a delay, template 5, another delay, then template 7. Auto-pause on reply stops the sequence the moment they answer, so a scheduled nudge never lands on top of a real conversation. Replies come into the unified smart inbox, and A/B testing lets you compare template 1 against template 3 on the same type of prospect.
Campaigns run in the cloud through the Unipile API, so you connect your account once with the Chrome extension and can close your laptop afterwards. Sends go out only during the working hours you configure, with randomised timing jitter and real-time account safety scoring watching for anomalies. Daily caps are 25 connection requests on every paid plan, and 25 messages on Standard, 50 on Pro, 80 on Team. For a comment-led play those caps won't hold you back. The time it takes to write good comments will.
Standard is $19/mo at the founding price (regular $39/mo), and that's enough for this workflow. Details are on the Pricing page, and every plan starts with a 7-day free trial.
If price is your only filter and you just need a few follow-ups fired, Dux-Soup at $14.99/mo or Linked Helper at $15/mo costs less. Ampliflow's case is cloud execution and real-time safety scoring, not being the cheapest option.