Instagram Comment-to-DM Not Sending? A Troubleshooting Checklist
By ReacHook Team · 2026-10-28 · 1 min read
Comment-to-DM is the most common Instagram automation: someone comments a keyword, and a tool sends them a private message. When it stops working, the cause is usually one of a short list, and most of that list is written into Meta's own rules. This checklist walks through it in the order that tends to save the most time.
How comment-to-DM works under the hood:
When someone comments, Instagram notifies your connected tool through a webhook. The tool then calls Meta's Messaging API with the comment's ID to send a private reply. Meta treats this as a tightly scoped message type, which is why the rules below are strict. They apply to every tool that uses the official API, not just yours.
Quick diagnosis: symptom, cause, fix:
| What you see | Most likely cause | What to do |
|---|---|---|
| Nothing was sent for a comment from last week | Private replies must go out within 7 days of the comment | It cannot be sent now. Invite the person to message you first. |
| The same person commented twice and got one DM | Only one message can be sent to the commenter through a private reply | Expected. If they reply to your DM, the conversation can continue. |
| A follow-up message never arrived | Follow-ups are allowed only after the person replies, and within 24 hours of that reply | Design message one so it asks for a reply, such as a button tap or a single word. |
| A live comment got no DM after the stream | Replies to live comments can be sent only while the broadcast is running | Use a different trigger once the stream ends. |
| Delays or gaps during a viral spike | Private replies are capped at 750 calls per hour per account | Check whether your tool queues the overflow. |
| A long message with emoji failed | Text is capped at 1,000 bytes of UTF-8, and emoji use several bytes each | Shorten the text and move detail to a linked page. |
| Every comment fails, not just some | The access token is invalid or expired, a permission was revoked, or the account is no longer professional | Reconnect the account in your tool and re-grant permissions. |
| The tool says sent, but the person never saw it | The message may be sitting in the Message Requests folder, or the recipient may have restricted requests | Test from an account that does not follow you. |
| Messages arrive late | Webhook delivery can be batched and retried | Meta retries failed webhook deliveries for up to 36 hours with decreasing frequency. Check your tool's status. |
| A warning or restricted features on the account | Instagram account restrictions are separate from API rules | See our guide to automated behavior warnings. |
Rows one to six are limits written into Meta's documentation. They are not bugs in your tool, and no tool using the official API can bypass them.
A seven-step checklist:
- Check the comment's age. If it is more than 7 days old, a private reply is no longer possible.
- Confirm the account type and connection. Meta's Messaging API works with Instagram professional accounts. In your tool, check the account still shows as connected.
- Open your tool's activity log. Find the specific comment and read the status and any error message. This usually answers the question.
- Check volume. If hundreds of comments landed in one hour, you may be queued behind the 750 per hour ceiling.
- Check the message. Is it under 1,000 bytes? Does it ask the person to reply or tap, so follow-ups are possible?
- Test with a second account that does not follow you. Comment on the keyword, then check the DM and the Message Requests folder.
- Reconnect if failures are account-wide. If every comment fails, re-authorise the account and re-grant the requested permissions.
What is usually not the problem?
- "Instagram banned comment-to-DM." Meta documents private replies as a supported feature of its Messaging API, with the rules above.
- "I need a verified badge." The documentation we reviewed lists a professional account and specific permissions and does not mention a verified badge.
- "My keyword is right, so it must be broken." Check how your tool matches keywords: exact word, case, and extra spaces and punctuation can all matter, depending on its settings.
When to contact support and what to bring
If the comment is recent, the volume is normal, the message is short, and the connection is fine, ask your tool's support team. Bring the comment link or ID, the time with the time zone, the status shown in the log, any error code, and whether other comments from the same period worked. Reachook records a status and error message for each trigger, including queued and failed sends, so those details are available when you need them.
See how Reachook's comment-to-DM automation works to see the full flow.
Why did my comment-to-DM work yesterday but not today?
The most common reasons are a lost connection or expired access, a volume spike that hit the hourly ceiling, or a changed message that is now too long. Check the activity log for the specific comment.
Can I send a DM to someone who commented two weeks ago?
Not as a private reply. Meta requires private replies to be sent within 7 days of the comment. They can message you first, which opens a conversation.
Is there a limit on how many comment-to-DMs I can send?
Meta documents 750 private replies per hour per Instagram professional account for comments on posts and Reels. We found no fixed daily cap in Meta's documentation.
Does comment-to-DM work on Reels and Live?
Yes, Meta's private replies cover comments on posts, Reels and Live. Live comments can be answered only while the broadcast is running.