Key takeaways
- The most common reason comment-to-DM looks broken is testing from the account that owns the post, since Instagram will not deliver a private reply to that account.
- A Draft or Paused badge means saved, not running, and a live automation with unpublished changes is still running its previous version.
- Comment-to-DM requires an Instagram professional account, Business or Creator, connected through Meta's login, and a personal account will not finish the connect flow.
- Meta allows one private reply per comment within 7 days of the comment, so a comment that already used its reply needs a fresh comment, not a fresh automation.
In this article
The commonest version of comment-to-DM not working is not a fault at all. You tested from the account that owns the post, and Instagram will never deliver a private reply to the account that owns the post. That one explains a large share of the panic. The rest fall into a short list, and the list has a natural order, because some causes make the others impossible to diagnose. Working down that order saves you from changing four settings at once and never learning which one mattered. The nine checks below run from the most likely cause to the least, each with the thing to look at and what a healthy result looks like. By the end you will have either a working automation or a precise description of what is wrong, which is what support needs from you anyway.
Short answer: test from a second Instagram account, confirm the automation is live and listening on that exact post, check the comment really contains the keyword, and confirm the comment is newer than 7 days and has not already received its one private reply. Those four resolve most cases.
If you want to see how Instagram DM automation is supposed to work before you debug it, start there.
What "comment-to-DM not working" usually means
In nearly every case the message was never attempted, rather than attempted and lost.
That distinction shapes the whole diagnosis. A comment-to-DM automation has to clear several gates before a send is even queued. The comment has to reach your tool, match a live automation, pass its keyword and exclusion rules, belong to a post the automation watches, and fall inside Meta's private-reply allowance of one reply per comment within 7 days of the comment. If any gate fails, nothing is sent and nothing fails visibly. The platform rules are set out in Meta's private replies documentation.
So before you start changing message text or reconnecting accounts, work out which gate stopped it. The order below is roughly how often each one turns out to be the answer.
The nine checks, in order
Step 1: Comment from a second Instagram account
Instagram will not deliver a private reply to the account that owns the post, so a test comment from your connected account gets ignored by design. Good tools skip those deliberately, since otherwise the echo of their own public reply would re-trigger the automation. Use a friend's account, or a second account of your own that is not the connected one. This is the most common reason a first test looks broken, and it costs nothing to rule out first.
Step 2: Confirm the automation is actually live
A "Draft" or "Paused" badge means saved, not running. A live automation showing "Unpublished changes" is still running its previous version, which is its own trap: you fixed the keyword, never published, then tested against the old keyword. Check the badge on the automation's row, publish anything pending, and re-test. If the tool refuses to set it live, it usually says what is unfinished. In HyperDM, a reply saved during setup listens on no posts at all until you pick one.
Step 3: Check the account type and the connection
Comment-to-DM requires an Instagram professional account, Business or Creator, connected through Meta's login. A personal account can start the connect flow and will not finish it. In your tool's channel settings, the Instagram card should read Connected rather than "Needs attention" or "Reconnect needed". Switching a personal account over takes about thirty seconds in Instagram's settings, under account type and tools.
Step 4: Check Instagram's own message permissions
Inside Instagram, under the account's privacy and message settings, sit controls for whether connected tools may access your messages and who may message you at all. If message access for connected apps has been turned off, an approved app receives nothing to act on, and your automation looks dead while the connection looks healthy. Review these after any Instagram app update, because the defaults occasionally move.
Step 5: Confirm the automation is watching that post
Scope is where "it worked yesterday" stories usually land. An automation set to specific posts only listens to the posts you picked, so a comment anywhere else is ignored. An automation armed for your next post binds to the first post that gets a matching comment and then stays there. And a boosted post is a separate media object: comments on the ad copy are a different stream from comments on the original, so an automation scoped to organic posts will not answer them.
Step 6: Check the keyword match rules
Three things to verify here. The match mode, first: "exactly the keyword" means the whole comment has to be the keyword, so "GUIDE please" fails it while "contains the keyword" passes. Then exclusions, because a "but doesn't contain" word wins even when your keyword matched. Then where the comment was left, since top-level comments are what trigger automations and a reply inside somebody else's comment thread usually does not.
Step 7: Check whether that comment already used its reply
Meta allows one private reply per comment. If you tested earlier, or a previous automation answered that comment, the allowance is spent and nothing more can be sent against it. The fix is a fresh comment, not a fresh automation. This is per comment rather than per person, so the same tester can just leave a new comment and get a new attempt.
Step 8: Check the comment's age against the 7-day limit
A private reply is only permitted within 7 days of the comment being created. Comments that predate your automation going live are not answered automatically; on Growth and up, a specific-post automation can reach them from Results, Reach people who already commented, while they are under 7 days old. If a post took off and replies queued behind an hourly sending limit, some can age past the deadline and never send at all. HyperDM's sending pace page shows the queue, what is waiting, and whether anything will pass the 7-day limit at the current rate.
Step 9: Reconnect, then check for a platform outage
A token can expire or be revoked, which shows as "Reconnect needed" and is fixed by re-authorising. "Needs attention" is a different animal: Meta accepted the connection but is not delivering events, and a retry on the subscription usually clears it. If everything on your side is healthy and nothing is arriving for anyone, check whether Meta is having a bad day. Our write-up of what happens when Meta's API goes down covers how outages present and what recovers on its own.
Symptom to cause, at a glance
| What you see | Most likely cause | Check |
|---|---|---|
| Nothing at all happens | Commented from the connected account | Step 1 |
| Public reply posts, no DM arrives | Delivered to Requests, or queued | Step 8, then the recipient's Requests folder |
| Worked before, stopped today | Unpublished changes, or token expired | Steps 2 and 9 |
| Works on one post, not another | Scope, or the post is a boosted copy | Step 5 |
| Fires on the wrong comments | Match mode set to contains | Step 6 |
| Fired once for a tester, never again | That comment used its one reply | Step 7 |
Fixing comment-to-DM not working for good
Most cases of comment-to-DM not working are a scope problem, a match-mode problem, or a tester problem, and all three are visible in under five minutes if you check them in order. Keep the order: test from a second account, confirm live status, verify the connection, then work through permissions, scope, keywords, the one-reply allowance and the 7-day deadline before you touch anything to do with tokens or outages. The habit worth building is a repeatable test. One post, one keyword, one second account, run after every change you publish. If you want those checks enforced rather than remembered, HyperDM's comment-to-DM feature reports what it made of every comment that has arrived since your automation went live.
Frequently asked questions
HyperDMRun the automations. Add AI when you’re ready.
Comment-to-DM, keyword replies and follow gates — set them up, test them, then add optional AI answers from your real catalog. Free on one DM channel, 50 conversations a month, no card.



