Comment-to-DM Templates: The Messages That Actually Get Replies
Delivery DMs, public comment replies, and what to say to people you cannot message yet. All under sixty words, none of them asking for a call in the first message.
What should your comment-to-DM messages actually say?
Short, plain, and delivering the thing immediately. Every template below is under sixty words on purpose, because the person is on their phone and expecting a link, not a pitch.
Take them as shapes rather than scripts. Copy them exactly and they will read like everyone else running the same play. For the post that earns the comment, see the comment-below format.
What is a good delivery DM?
One line of context, the thing, and nothing else asked of them:
> Hey {firstName}, here is the outreach teardown you commented for: {link}. It is the twelve sequences we ran last quarter with reply rates on each. No opt-in, just the doc.
> {firstName}, thanks for commenting. Here is the template: {link}. Page two is the part most people find useful, the objection lines.
> Here you go {firstName}: {link}. Took about a day to write up, so tell me if any of it is unclear and I will fix it.
Note what none of them do. No calendar link, no qualifying question, no "quick call?"
Why should the first DM never ask for anything?
Because they asked you first, and answering a request with a request is the fastest way to spend goodwill you just earned. They commented for a resource, so send the resource.
The ask, if there is one, belongs in the conversation that follows. Roughly one in five people replies to a good delivery DM, and those replies are a much better place to sell than the delivery itself.
What should the public comment reply say?
Something short that tells them to check their inbox, without claiming more than happened:
> Just sent it over.
> In your DMs now.
> Sent, check your inbox.
> Just messaged you the link.
The important thing is not the wording. It is that you have twenty of them, not one, and that the reply only fires after the DM is confirmed sent, which is where most setups go wrong.
What do you say to people you cannot DM?
Ask them to connect, and make it clear the thing is still coming:
> Can't DM you as we're not connected, sent you a request and I'll fire it over as soon as you accept.
> Not connected so LinkedIn won't let me message, send me a request and it's yours.
> Send a connect and I'll get it straight to you.
Then actually deliver when they connect. A tool that promises this and drops them is worse than one that never offered.
How do you follow up without being annoying?
Once, and only with something useful. If they opened the resource and went quiet, a single message a few days later that adds to it is fine:
> {firstName}, did the teardown land ok? The bit on follow-up timing is the part people usually push back on, happy to talk through it if useful.
If that gets nothing, stop. They took a free thing and were not interested, which is a normal and acceptable outcome.
How do you personalise these at volume?
Use their first name and the specific thing they commented for, and stop there. Deeper personalisation on a delivery message is wasted effort, because the context is already obvious to both of you.
Where personalisation actually pays is the reply after they respond. That is a real conversation, and it deserves a real answer rather than another template.
How many variations do you need?
For DMs, a handful. For the public comment replies, far more than people expect, because those stack visibly in one place. Twenty comments produce twenty replies that anyone can scroll in a row.
Gelee ships around 50 written variants for the sent reply and 42 for the connect-first reply. That is not overkill. It is the number at which a busy comment section stops looking automated.