How to Auto-DM Everyone Who Comments on Your LinkedIn Post
LinkedIn has no native way to DM your commenters and ManyChat does not support LinkedIn. Here is the setup, what happens with people you cannot message, and the mistake that wastes half the responses.
How do you automatically DM everyone who comments on your LinkedIn post?
You need a tool that watches the post, reads new comments, and sends a DM to each person who leaves one. LinkedIn has no native way to do this, and ManyChat does not support LinkedIn at all, so it has to be a LinkedIn-native tool holding a session on your account.
The setup itself takes about two minutes. Getting it right takes a bit more thought, and how the mechanic works end to end is worth reading first.
What do you need before you start?
Three things, and the software is the least important of them:
How do you set it up in Gelee?
Pick Post Commenters from the campaign library, paste the URL of the post you want watched, and launch. That is the whole configuration.
What runs underneath is a four-step sequence per commenter: check whether we can DM them, send the DM, reply publicly once the DM is confirmed, or ask them to connect if a DM is not possible. You do not wire those steps together. The preset ships pre-wired because the order is what keeps it honest.
What happens with people you cannot message yet?
They are the majority, and how a tool treats them decides half your results. Most commenters are second or third degree, which means no DM by default.
Two things help. If they have already sent you an invite, accepting it opens the DM immediately, so the sequence checks for that first. If not, the public reply asks them to connect, and they get picked up once they do rather than being dropped.
How fast does the DM go out?
Fast enough that it still feels like a reply, which matters more than instant. Gelee sweeps a new post every hour for its first 48 hours, then daily, because that is the shape of how comments actually arrive.
Perfectly instant would be worse, not better. A DM landing the same second as the comment reads like a machine to the person receiving it, and to LinkedIn.
What should the DM actually say?
Give them the thing, in one short message, with no conditions attached. They commented for a resource, so send the resource. Asking them to book a call before they get it is the fastest way to burn the goodwill you just earned.
One line of context, the link, done. The conversation, if there is one, comes after they have what they asked for.
Should you reply to their comment as well?
Yes, and this is the part most people skip. The public reply does two jobs: it tells the person to check their inbox, and it shows everyone else scrolling that the thing works.
The rule is that the reply has to come after the DM is confirmed sent. If it fires on intent rather than confirmation, one failed send leaves you publicly claiming something you did not do, in your own comment section, under your real name.
How do you keep it from looking automated?
Vary the public reply, because that is where automation is visible. Twenty comments means twenty replies stacked in one place where any human can scroll them.
Gelee draws from about 50 written variations for the sent case and 42 for the connect-first case, picked per comment. They are written by people up front rather than generated live, so there is nothing to review after the fact and nothing to fail when an API is slow.
What is the most common mistake?
Delivering the resource and then doing nothing. The DM lands, they say thanks or ask a question, and it sits unanswered because nobody was watching that inbox.
Every reply to a delivery DM is a warm inbound lead who already knows what you do, and the templates here cover what to send. Decide before you launch who is answering them, whether that is you or the same system that sent the DM.