Instagram automation guide
Instagram Comment-to-DM Not Working? Troubleshooting Guide
Follow the path from comment to delivery. Change one thing at a time so you can tell what fixed the problem.
By CommentFor · Published
Start with a fresh test: use a second Instagram account to leave the exact keyword on the selected post after the automation is active. Check the automation’s activity and sending status, then check the receiving account’s message requests. Repeating the same comment is a poor test because it may already have received its one private reply.
“The DM did not arrive” can describe several different failures. The connection may need attention, the comment may not match a trigger, delivery may be waiting in a queue, or the message may be outside the inbox you expected. Work through these checks in order before changing your campaign copy.
1. Confirm the connected account
The Instagram account that owns the post must be the account connected to the automation. A personal account is not the professional account required by this workflow. For an agency, check the username against the client brief rather than relying on an avatar; similar account names are easy to confuse.
If the connection is expired or permissions are missing, reconnect through the official Instagram login. Never give a third party your Instagram password as a repair step. If Instagram or the product says a permission is unavailable, save that exact message for support rather than repeatedly reconnecting.
2. Check activation and the selected post
A saved draft is not a running campaign. Confirm the automation is active and the selected post or reel is the one receiving comments. Next post and Rewind have different jobs: Next post covers a future publication, while Rewind handles eligible earlier comments. A campaign attached to the wrong post will not be repaired by changing the keyword.
Open the post from your own brief and compare its address with the selection. For an all-posts campaign, check other active campaigns too. Several overlapping triggers make a test harder to interpret.
3. Test the exact keyword
Start with one simple keyword, such as GUIDE. Leave that exact word in a new comment from the test account. Avoid combining spelling changes, emoji, and exclusions in the first test. Once the basic path works, test the matching variations you actually plan to advertise.
Read any exclusions and once-per-user settings before assuming a matching comment must create a new send. Use a different test account when you need to check a repeat-visitor rule. Our keyword guide explains how to keep the trigger understandable.
4. Check the reply window and previous replies
Instagram private replies are limited by a reply window and a one-reply-per-comment rule. A comment that is too old or already answered is not equivalent to a new eligible comment. Rewind cannot make an expired comment eligible again.
A follow-up conversation is a separate case from the initial private reply. An initial send does not authorize an ongoing sequence to someone who has not responded. See the private-reply and messaging-window explanation and Meta’s private-replies documentation before planning a follow-up.
5. Separate queued delivery from failed delivery
A burst of matching comments can create a queue. CommentFor paces sends rather than promising that every message will arrive immediately during a spike. Check whether the item is pending, sent, or failed, and whether a platform error was recorded. Do not launch several replacement automations while the original queue is still running.
Check the CommentFor status page for a wider incident. A healthy status page does not prove a particular account is connected correctly, but it helps distinguish a campaign-specific problem from a service issue.
6. Look in the receiving account’s message requests
Have the tester inspect both the inbox and message requests. Sender-side status and recipient-side placement are different observations. Then open the delivered link and check that the destination works on a phone. A successful send with a broken landing page is a link problem, not a trigger problem.
Optional features need their own checks
Story automations, public comment auto-replies, follow gates, email capture, and DM flows are paid-plan features in CommentFor. Test the basic keyword-to-link path first. If that works and a paid-plan gate does not, inspect the gate’s requirements and the recipient’s next action separately.
What to send support
Send the post address, approximate time and time zone of the test, the selected keyword, the visible delivery status, and the exact error text. Explain whether the comment was new and whether the same comment had already received a private reply. Do not send passwords, access tokens, captured email lists, or payment details.
Contact CommentFor support with this small reproduction. It is more useful than “all DMs stopped” and reduces the number of back-and-forth questions.