How to reply to comments on your LinkedIn post: 20 examples

To reply well to a comment on your LinkedIn post, answer the point the person made and add one thing they didn't have, such as a detail from your work or the reason behind a decision. Ask a question back only when you want to hear the answer. A reply like "Thanks for sharing!" could sit under any comment, so it gives the commenter nothing to respond to.

Disclosure: I build Voxily, a Chrome extension that drafts replies inside LinkedIn's comment box. It doesn't post for you. The method below works without it.

A four-step method for replying to comments

• Read what they actually said. Find the sentence that carries their point: agreement, a question, a doubt or a story.
• Answer that point first. If they asked something, the answer goes in your first sentence.
• Add one thing: a detail from your work, the reason behind a decision or a limit on what you claimed.
• Ask a question only when you want the answer. If every reply ends in a question, the questions stop meaning much.

You don't have to answer every comment. For comments you leave on other people's posts, see how to write useful LinkedIn comments as a founder.

Before-and-after replies to LinkedIn comments

Everything in this section is illustrative: the post, the comments and both versions of every reply. None is a transcript of a real thread or a recorded Voxily generation. Replace any experience or result with facts from your own work.

The post: you announced a new self-serve onboarding for your small scheduling tool and stopped offering demo calls. New users get a three-minute setup video, a checklist and your email address.

Replying when someone agrees with you

Add the part of the story the post left out.

Comment: "Same here. Demo calls were eating half my week."

• Before: "Totally agree!"
• After: "Did you drop them all at once? I kept one open slot a week for the first month, in case the video missed something."

Comment: "100% agree. Async is the way."

• Before: "Thanks, glad it resonates!"
• After: "It works here because setup takes five minutes. If setup needed a data import, I'd still offer a call."

Comment: "More founders should do this."

• Before: "Appreciate it!"
• After: "One condition: answer the emails fast. The video only replaces a call if questions still get a same-day reply."

Answering a question in your comments

Put the answer in the first sentence. If you don't know yet, say so.

Comment: "What if a buyer's procurement team insists on a call?"

• Before: "Great question! Happy to chat."
• After: "None has asked yet. If one does, I'll take the call. Self-serve is the default, and calls are still available."

Comment: "What's in the video? Full tour or just setup?"

• Before: "Check it out on our site!"
• After: "Just setup: connect a calendar, invite a teammate, send the first reminder. The full tour is in the help docs."

Comment: "Did signups change?"

• Before: "Yes, it's been great so far!"
• After: "Too early to say. It's been two weeks and the numbers are small. I'll post again after a full month."

Responding to pushback on your post

Concede what's true, then state the part you still hold.

Comment: "This only works for cheap tools. Above $500 a month, buyers want a human."

• Before: "Respectfully disagree!"
• After: "Fair, our plans are well under that. I'd guess the line sits wherever someone who never uses the product approves the purchase. Where have you seen it?"

Comment: "Dropping demos feels like hiding from customers."

• Before: "That's not what I meant at all."
• After: "I can see how it reads that way. My email is on every onboarding screen and I answer it myself. I dropped the call, not the conversation."

Comment: "Nobody watches onboarding videos."

• Before: "Agree to disagree."
• After: "Some won't, so the checklist works without the video. The video is for people who want to see it done once."

Handling an off-topic comment

Answer briefly or offer to cover it elsewhere.

Comment: "Unrelated, but how did you pick your pricing?"

• Before: "Haha, long story!"
• After: "I asked five early users what they'd pay and went below the lowest answer. I'll write up the rest separately."

Comment: "What did you record the video with?"

• Before: "Just a screen recorder!"
• After: "The recorder that came with my laptop. Writing the captions took longer than recording."

When someone pitches in your comments

You don't owe a pitch a reply. If you answer, keep it short.

Comment: "We automate demo booking for SaaS teams. Mind if I DM you?"

• Before: "Sure, send it over!"
• After: "Thanks, but we've just stopped booking demos, so it isn't a fit."

Comment: "Nice post. We built a tool for exactly this, link in my profile."

• Before: "Cool, I'll check it out!"
• After: "Thanks. We're keeping onboarding in-house and want a month of data before changing anything."

Replying to congratulations

Thank them, then give one detail from the work.

Comment: "Congrats on shipping the new onboarding!"

• Before: "Thank you so much!"
• After: "Thanks, Priya. The hard part was cutting the checklist from eleven steps to four."

Comment: "Congrats! Big milestone."

• Before: "Thanks!!"
• After: "Thanks. It's a small change, but it's the first one that came straight from support emails."

When someone corrects you in the comments

If they're right, fix it before you say it's fixed. If they're wrong, give the fact and the source of the confusion.

Comment: "Small thing: your pricing page still says 'Book a demo'."

• Before: "Good catch, thanks!"
• After: "You're right, thank you. Fixed now. That button led to a calendar I'd already closed."

Comment: "You say the video is three minutes. The one on your site is closer to six."

• Before: "Thanks for the feedback!"
• After: "Correct. Setup is the first three minutes and the rest covers settings. I should have said so."

Comment: "Pretty sure you still need a call to set up calendar sync."

• Before: "Nope, you don't."
• After: "Not anymore. Calendar sync moved into the setup screen last month. The old help article says otherwise, so I'll update it."

Replying to a long comment or personal story

Respond to the one detail that taught you something. Don't summarize their comment back to them.

Comment, summarized: a story about dropping demos at a previous company, then bringing them back for enterprise accounts after sales objected.

• Before: "Wow, thanks for sharing your story!"
• After: "Who decided which accounts counted as enterprise, sales or product? That seems like the part that would cause arguments."

Comment, summarized: a story about an onboarding video that went stale because the product's screens kept changing.

• Before: "So true, thanks for sharing!"
• After: "I hadn't planned for that. I'll re-record when a setup screen changes and put the recording date under the video."

Drafting comment replies with Voxily

Voxily adds a button to LinkedIn's comment boxes, including the reply box under a comment. Click it and pick one of eight moods. Voxily drafts from the post, the comment you're answering and your saved persona, and puts the draft in the reply box for you to edit and post. If you've already typed a rough reply, the button offers to fix that text instead.

Voxily doesn't know the post is yours or what happened after you published it. Details like the open slot or the eleven-step checklist above have to come from you. Check every claim a draft makes about your work.

Free includes 10 reply generations a day and one persona. The LinkedIn reply assistant page shows the steps and the moods.

Questions about replying to LinkedIn comments

Should you reply to every comment on your LinkedIn post?

No. Reply where you can add an answer or a detail. A pitch, or a comment that fits any post, can go unanswered.

How do you reply to a negative comment on LinkedIn?

Answer the specific objection, concede what's true and give one reason for the part you still hold. If a comment attacks you rather than your point, you don't owe it a reply.

Can AI write replies to comments on my post?

It can draft them. You still add what happened after you posted and remove any claim that isn't true.

Before your next reply, point to the sentence in the comment it answers.