Running a product launch on comment-to-DM: a practical playbook

Published 28 August 2026 · 6 min read

A launch post is the highest-leverage place to use comment-to-DM automation. The interest is concentrated in a few hours, the intent is unusually clear, and every reply you send by hand in that window is a reply you send late. Here is a way to set one up that does not fall over.

Before the post goes up

Decide the keyword first, because the post copy has to teach it. Pick something short, unambiguous, and unlikely to appear in ordinary conversation. LAUNCH works. Yes does not — people type it constantly for other reasons, and you will send DMs to everyone agreeing with a comment three levels down.

Set the automation to arm for your next post if it is not published yet, or point it at the specific post once it is. Arming ahead of time matters more than it sounds: the first fifteen minutes of a launch are often the busiest, and an automation you set up afterwards has already missed them.

Write the DM like a person, not a funnel

The DM lands in a personal inbox next to messages from friends. Match that register. One or two sentences, the link, and a genuine offer to answer questions beats a formatted block with three emoji bullet points and a countdown timer.

Include the link as a tracked short link so you can see clicks separately from opens later. And say what the link is before you give it — "here's the pre-order page" reads as helpful, a naked URL reads as spam.

Reply publicly as well

Turn on the public comment reply. Two reasons: the commenter gets a visible acknowledgement even if they miss the DM, and everyone else scrolling the comments sees that commenting the keyword does something. A launch post with fifty comments and fifty visible replies reads as active in a way that silence does not.

Vary the public reply if your tool supports it, or keep it short enough that repetition is not obvious. Fifty identical "Sent! 📩" replies look automated because they are.

Gates: use them deliberately

A follow gate — only DM people who follow you — makes sense on a launch where you expect reach beyond your audience, and costs you conversions when your audience is already the buyer. Email capture makes sense when the launch is a waitlist rather than a purchase. Neither is free; every gate is friction you are trading for something. Add them because you want the thing on the other side, not because they are available.

Set once-per-user

People comment more than once when they are excited. Once-per-user means an enthusiastic commenter gets one DM instead of four, which is the difference between helpful and irritating. Set it before the post goes live, not after the first complaint.

If the post takes off before you are ready

This happens more often than anyone plans for. Because Instagram allows private replies for seven days after a comment, a post that went viral yesterday is still reachable today. CommentFor calls this Rewind: it sweeps the comments already on a post and sends to the ones still inside the window. You will lose the ones older than seven days, so the sooner you run it the more you recover.

Measure the right thing

Comments are a vanity number on a launch. The chain that matters is comments to DMs sent, DMs sent to link clicks, link clicks to whatever counts as a conversion for you. Tracked links give you the middle of that chain; your own analytics give you the end. If clicks are high and conversions are low, the problem is the landing page, not the automation — and no amount of DM tuning will fix it.

After the launch

Turn the automation off, or scope it to the specific post. An armed keyword left running catches comments on unrelated posts weeks later and sends people a launch link that has expired. Set an exclusive-post trigger if you want it to stay live but only for that post.

The full trigger and gate list is on Features, and How it works walks through the setup screen by screen.