# How to message people who reply to your comments
> How to move a LinkedIn comment thread into a private message without sounding like a bot, plus the note to send and the first message to follow it with.
- HTML: https://getkinlead.com/messaging-prospects-who-interact-with-your-comments
- Markdown: https://getkinlead.com/messaging-prospects-who-interact-with-your-comments.md

**Short answer:** Answer the person in the comments first, say what you're going to send them, then send a short connection request that reminds them of the thread. The private message carries the thing you promised, then one plain question about their situation. The meeting ask comes later, once they've told you the problem is real.

## The mistake of the instant DM

A comment reply looks like an opening, and sometimes it is. But the person replied to an idea in public, not to you. A message that lands two minutes later reads like you were sitting on it, waiting for someone to bite.

The usual result isn't an angry reply. It's silence, and then the thread goes cold. The next time your name shows up in their notifications, they remember the pitch and not the point you made.

The version that works is slower and cheaper. Answer them properly in the comments. Say what you're going to send. Send it. Everything below is detail on those three moves.

**The instant pivot**

- Public: they reply to your comment about onboarding drop-off.
- Private, 40 seconds later: 'Thanks for the comment! I'd love to show you how our platform solves onboarding. Do you have 15 minutes next week?'

**The same thread, one day later**

- Public: 'The week-one drop is worse for self-serve accounts in the ones I've looked at. I have a two-page breakdown of what the accounts that stick do differently. Sending it over.'
- Private, next day: 'Hi Priya, the breakdown from Mark's post. The bit about the second login on day three is the one most teams miss.'

## The public to private transition

Your reply in the comments has two readers. One is the person who wrote to you. The other is everyone scrolling the thread after them. Answer the first honestly and the second one notices, which is the reason to spend a beat in public instead of racing to the inbox.

You also need a reason for the request to exist. A bare 'let's connect' gives them nothing to accept. A specific file, a teardown of their own page, or a number from your accounts that would be awkward to drop into a comment thread gives the request a job.

Not every comment deserves a request. Someone who wrote 'great post' is being polite. Someone who described their own version of the problem, asked a follow-up, or disagreed with a reason is worth the time.

1. **Answer what they actually said.** Reply to a detail, not the topic. 'The drop shows up at day three, not day one, in the accounts I've looked at' proves you read the comment. 'Great point' plus an agreement does not.
2. **Add one thing they don't have.** A number from your own accounts, a counter-example, or a question that reframes the problem. One addition, not four. This is the part people remember and the reason the request gets accepted.
3. **Say what you'll send.** Name the thing: the checklist, the teardown, the two pages of numbers. Naming it tells them what's coming and tells everyone else reading the thread that you hand things over.
4. **Give it a day before the request.** Your public reply should read like the end of a conversation, not the start of a funnel. A few hours or overnight is enough. LinkedIn doesn't publish a rule for this and you don't need one.

## Writing the connection request

By the time the request lands, the hard part is done. You don't need to introduce yourself or explain what your company does. Two sentences: this is who I was in that thread, and this is what I said I'd send.

Use their words, not yours. If they wrote 'handover', the note says handover. Sales nouns like solution, partner and platform make the note look like it came from a sequence, because usually it did.

Don't ask for a meeting here. You're asking to connect. The meeting ask works much better after you've handed over the thing you promised, because then you're the person who did what they said they would.

> The note has one job: get accepted. Anything you add about your product makes that job harder.

```
Hi {first name}, you replied on {author}'s post about {topic}. The bit about {their specific point} is the part most people skip. I said I'd send the {artefact} and I'll get it over as soon as we're connected.
```

## The first message after they accept

Acceptance isn't interest. It's a door held open for a second. Send the thing you promised the same day. Three days later the thread is a memory and you're a stranger with a PDF.

Then ask one question about their situation, not about your product. Keep it short enough to answer from a phone in one line. 'Would you like to jump on a call' is a question about your calendar, not theirs.

What they answer tells you where you stand. If they describe the problem in their own words, you have a conversation. If they say thanks and go quiet, you gave something useful to someone who wasn't buying. That happens, and it isn't a reason to chase.

| | Part of the message | What it's for | Example |
| --- | --- | --- | --- |
| The reminder | Places you back in the thread | The checklist from Mark's post. |
| The thing you promised | Gives value before any ask | Page two covers the second login on day three. |
| The question | Tests whether the problem is live | Are you seeing the same drop at day three? |

- **you:** Hi Sarah, the checklist from Mark's post. Page two is the bit about the second login on day three, which is where most of the accounts I've seen lose people.
- **them:** Read it, thanks. We have the same drop but I'd assumed it was pricing.
- **you:** Could be both. What does day three look like on your side right now?
- **them:** People sign up, connect one tool, then nothing. We've tried a few emails.

> One question per message. Ask two and people answer the easier one.

## When they don't accept or don't answer

Most people won't accept, and it says little about the conversation. They might not have opened LinkedIn that week, they might have a rule about adding vendors, or they might have meant to and forgot.

If the request sits there, don't send another one. Reply once more in the comment thread with the thing you promised, in the open. It costs you nothing, it's useful to everyone else reading, and it keeps the door open without pressure.

If they accept and then go quiet, one follow-up is right. Ask about the problem they described, not about your calendar. Then stop. Three follow-ups after a single comment reply is how a good first impression turns into a block.

There's also a temptation to work one popular competitor post and message everyone in the comments the same afternoon. It looks coordinated because it is, and the people in that thread can see each other. Start with the two or three comments that showed real thinking, and spread the rest out.

```
Hi {first name}, one thing worth adding to what we talked about on {author}'s post: {one specific observation about their situation}. If {problem} is on your list this quarter I can send the longer version. If not, no reply needed.
```

## Doing this with Kinlead

Reading competitor posts and their comment threads by hand takes an hour a day. The [Steal Customers](/features/steal-customers) agent watches competitor company pages and any founder or employee profiles you add, reads the comments on their recent posts, and turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about and what they commented.

Those leads sit in a group, and any campaign can point at that group. Connection notes are written by AI from the campaign's goal, tone and, if you have one, your own sales playbook, and they open with why that person became a lead. Queued messages can be read and edited on the Actions page before they send, and any campaign can be paused. Sending runs from your own LinkedIn account at one action every five minutes, inside the limits and send window you set.

You can [book a call](/demo) and watch it work on a competitor's page.

## Related

- [Steal customers feature](https://getkinlead.com/features/steal-customers.md)
- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

**Should I wait for them to follow me first?**

No. A real exchange in the comments is enough reason to send a request. Waiting for a follow hands the timing to someone who isn't thinking about you.

**What if they reply to my comment but don't accept the request?**

Leave the request alone and don't send a second one. Post the value you promised in the comment thread so it's still there if they come back later.

**Is a comment reply a buying signal?**

Sometimes. It's a signal that the topic is live for them, which is a lower bar. That's why the first message asks a question instead of assuming they're in the market.

**How many people from one post should I message?**

LinkedIn doesn't publish exact limits, so work inside whatever your account has and space the requests out. As a habit, take the two or three comments that showed real thinking rather than every name in the thread.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
