# Instagram Comment-to-DM Setup: Step-by-Step Guide > Connect an eligible Instagram professional account through Meta’s official login, select media and a keyword such as GUIDE, then configure an optional public reply and one private reply. Activate narrowly and test with a real eligible comment. Delivery is queued and subject to matching, moderation, plan quotas, Meta acceptance and private-reply limits. - Source: https://dmnow.co/blog/comment-to-dm-instagram-setup - Author: DM Now Team - Published: 2026-08-02 - Last reviewed: 2026-08-11 - Tags: dm-automation, how-to, comment-automation --- Comment-to-DM can handle repeated eligible link requests without manually copying the same response. It is not a guarantee that every comment will match or every private reply will be delivered. Here is the constraint-aware setup. ## Step 1: Switch to a professional account Meta's messaging capabilities require an eligible professional account. In Instagram, review **Settings → Account type and tools** and choose Creator or Business if appropriate. Eligibility, permissions and Meta review can affect connection, and account-type changes may affect profile features. ## Step 2: Connect Instagram to DM Now Create a [free DM Now account](/signup) (no card required) and click **Connect Instagram**. You will go through Meta's official Business Login — the same OAuth pattern as "Sign in with Google". You approve specific permissions; no password is ever shared with DM Now, and you can revoke the connection anytime from Instagram's settings. ## Step 3: Choose your trigger Create a new automation, then choose **Quick setup** for a single private reply or **Flow builder** if the journey must wait for a genuine recipient reply before continuing. Set: - **Which posts** — one or more media items loaded by the picker, or all posts on the account. Use **Load more posts** to browse the account's media history, or start with the reel you are about to publish. - **The keyword** — the word that fires the flow. Rules of thumb: | Good keyword | Why | | ------------ | --------------------------------------------------------------------------------- | | GUIDE | Matches the payload; natural to say on camera | | WIN | Perfect for giveaways; high energy | | DROP | Launch-coded; short and memorable | | Any comment | Attempts every eligible comment that passes moderation, cooldown and quota checks | ## Step 4: Write the private reply and optional public acknowledgement Two messages, written once: **The public comment reply** — short, warm, and accurate even if private delivery later fails: “Thanks — I’ll try to send that by DM.” It can acknowledge the request, but it is not proof that the DM arrived or that the workflow improves reach. **The DM** — the payload: "Here's your free Reels Growth Guide 👉 [your link] 🎁". Keep it to one or two lines, lead with the goodie, and write it the way you actually talk. Optional steps include an [ask-for-follow request](/features/ask-for-follow), which DM Now cannot verify, and [lead capture](/features/lead-generation). Quick setup defaults to a 60-minute per-person cooldown. A comment allows one initial private reply within seven days; a Live comment is eligible only while the broadcast is live. For people who do not follow the account, the reply can appear in Message Requests. Include the resource and optional request in that reply, or use Flow builder and wait for a real recipient response before sending later prompts. After that response, subsequent messages must remain within the 24-hour messaging window. See [Meta's official Private Replies documentation](https://www.postman.com/meta/instagram/request/23987686-189d7215-22b3-403f-b2f5-a46c7e66a514). ## Step 5: Test with a real eligible interaction Activate the automation narrowly, comment from an eligible test account and check Activity for sent, skipped and failed outcomes. Confirm both public and private copy in Instagram. The simulator available to developers does not prove production Meta delivery. ## Step 6: Publish and tell people the keyword The automation only matches the intended request if people know the word. Put it in the caption (“comment GUIDE and I’ll DM it to you”), say it in the Reel and pin a comment repeating it. On stories, use an eligible text instruction such as “reply GUIDE” with a separate [story automation](/features/story-automation). ## What to expect after going live Eligible replies are queued and account-paced. A matching interaction can create a contact subject to plan limits; source-media context is visible in Activity rather than attached to the Contact record. An active media-scoped automation can handle future eligible comments on a previously selected post. [Re-trigger](/features/re-trigger) is only bounded recovery for recent skipped events. From there, graduate to the full playbooks — [lead magnets](/use-cases/lead-magnet), giveaways, launches — which layer capture and reply-gated follow-up onto the basic private reply you just built. ## Frequently asked questions ### What keyword should I use for comment-to-DM? Short, meaningful, and easy to say out loud: GUIDE, LINK, PLAN, WIN. Use a word tied to the payload so the comment reads naturally, and avoid words people would type anyway — unless you deliberately want to catch every comment on that post. ### Does the commenter have to follow me first? Following is not required for the limited private-reply path, but the comment and account must be eligible and delivery is not guaranteed. If you add DM Now’s follow-request step, disclose that the product cannot verify whether the person followed. ### Why send a public reply and a DM together? A public reply can acknowledge the comment while the private reply carries the requested link. Either can fail independently, and DM Now does not claim that the pair improves ranking or conversion. Keep both accurate and avoid saying “sent” unless that wording remains acceptable when private delivery fails. ### Can I test the automation before going live? In production, activate narrowly and perform a real eligible interaction, then review sent, skipped or failed outcomes in Activity. The repository includes a development-only simulator, but production users should not rely on it as proof that Meta will accept a real delivery.