Home › Insights › How to Write LinkedIn Comments That Get Replies

LinkedIn Strategy

How to Write LinkedIn Comments That Get Replies

A comment that gets ignored and a comment that starts a conversation are usually separated by one thing: specificity. Here is how to write the second kind.

The comment has one job

Not to demonstrate empathy. Not to show you read the post. Not to get likes. Its job is to get a reply from this specific person about their specific situation.

Every word you write should be evaluated against that single criterion. Does this make them more or less likely to reply?

The anatomy of a comment that earns a reply

Effective comments do one of three things:

1. Name what the post didn't say. Identify the tension underneath what was written — the thing they were clearly thinking but didn't type. Surface it precisely.
2. Add a specific observation. Extend their thinking with something a generic reader couldn't have contributed. Not agreement — a contribution.
3. Ask one precise question. About something specific in their situation. Answerable in two sentences. Not applicable to everyone who posted about the same topic — only to them, about this post.

The hardest thing to avoid

The most common failure mode is opening with agreement. "Love this", "so true", "this resonates" — these are the most recognisable signals that you didn't think hard enough to say anything real. They get ignored because they deserve to be ignored.

The comment that starts a conversation is one that could only have been written for this specific post. If it could have been sent to anyone who wrote something vaguely similar, it's not specific enough.

Length and format

Two to three sentences. Written as a peer, not an advisor. No hashtags. No emojis. No flattery before getting to the point. Plain language that sounds like it came from someone who has been in a similar situation — not someone studying leadership from the outside.

Examples

Post about a founder letting someone go

Weak comment: "This resonates. Leadership is hard. Thanks for sharing."

Strong comment: "The bit about knowing for six months — that gap between knowing and acting is where most of the cost actually lives. How long did it take before the team dynamic changed after?"

Post about revenue pressure

Weak comment: "So important to talk about this. The pressure founders face is real."

Strong comment: "Most of the pressure in that situation isn't the number — it's managing what you're telling the team versus what you're actually thinking. Did you end up being transparent with them about the timeline?"

Scaling this without burning out

Writing ten of these comments per day manually is exhausting. Pressure Radar finds the posts most worth your comment time and drafts a starting comment in your voice — based on your actual writing style, not a generic template. You edit, approve, and post. The hard part is done.