Instagram Comment-to-DM Not Working? Check These
A symptom-by-symptom lookup for Instagram comment-to-DM and auto DMs that don't send: account, connection, keywords, Meta's 7-day and one-message rules.

Start with the pattern, not the error message. If no comment on any post gets a DM, the problem is the account or the connection. If some comments get one and others do not, it is usually matching or one of Meta's message rules. If the DM was sent but the customer cannot find it, it is delivery. Each pattern has its own checks below.
Everything here comes from Meta's developer documentation and help pages, read on 12 November 2026. We have not invented error codes or 'tested fixes'. Your tool's own help pages and logs are the next stop after this list.
Find your branch
- Did the automation run at all on any post? No: see Account and connection below. Yes: continue.
- Did it run on this post but skip some people? Yes: see Matching and Meta's message rules below.
- Does your tool show the message as sent, but the person cannot see it? Yes: see Delivery below.
- Did people get two messages, or the wrong one? Yes: see Conflicts below.
- Did it work for a while and then stop? See Limits and pauses below.
Account and connection
Symptom for this whole section: nothing triggers, on any post.
| Likely cause | How to check | Fix |
|---|---|---|
| Private account. Meta's webhook docs say private accounts do not receive comment notifications, so tools never hear about the comment | Instagram settings: Account privacy | Switch to a public account. Comment-to-DM needs a public professional account |
| Not a professional account, or the account is not linked to the Facebook Page your tool uses (for tools that connect through Facebook Login) | Profile, Edit profile: account type and the connected Page | Switch to a business or creator account and link the Page your tool expects. Our scheduling set-up guide walks through the link |
| Message access is switched off. Meta's set-up guide asks account owners to turn on 'Allow access to messages' for connected tools | Instagram Settings, Messages and story replies, Message controls, Connected tools | Turn the setting on, then reconnect the tool |
| The person who connected lacks the right Page role. Private replies need a token from someone who can perform the messaging task on the linked Page | Page access in Meta Business Suite or business settings | Have an admin with full control reconnect, or grant the needed access. If you manage several clients, our access guide covers who should hold what |
| The tool's connection lapsed or lost permissions | The tool's connection or account settings page; any 'reconnect' warning | Reconnect and accept every permission it asks for. Skipping one can break messaging only |
| The feature is not available in your region. Meta says some organic messaging features are unavailable for businesses in Europe and Japan because of privacy rules | Is the template missing from Meta Business Suite's list? | Check Meta's regional page, or use a tool that supports your region |
Matching and Meta's message rules
Symptom for this section: the automation works on the post, but some commenters get nothing.
| Likely cause | How to check | Fix |
|---|---|---|
| Keyword did not match. In Meta Business Suite, keywords are case-sensitive and must match exactly. Other tools vary | Compare the comment with your keyword list: capitals, plurals, typos, emojis, extra words | Add the variants you see. Put the exact keyword in capitals in the caption |
| The comment is older than 7 days. Meta allows private replies only within 7 days of the comment for posts, ads posts and reels | Comment date versus today | Answer older comments by hand with a normal reply asking them to message you |
| Live comment after the broadcast. For Instagram Live, private replies are possible only during the broadcast | Was the comment on a Live? | Pin a comment or caption that tells viewers to message you |
| The comment already had its one message. Meta allows one private reply per comment | Your tool's log for that comment | Wait for the person to reply. Our 24-hour window guide covers what you can send then |
| The person opted out. A good tool skips anyone who replied STOP | The tool's opt-out or suppression list | Leave it. Contacting someone who opted out breaks Meta's developer policy |
| The automation is scoped to another post, or only to new posts | The automation's post or 'next post' setting | Attach it to this post, or create one per post |
| Replies to replies, or comments by your own account | Was it a reply in a thread, or written by the business? | Many tools only act on top-level comments from other people. Check your tool's help page |
| Collab post owned by a partner. Meta says only the creator of a partnership ad or collaborative post can manage its comments in Inbox | Who created the post? | Run the automation from the creator's account |
Delivery: sent, but not seen
| Likely cause | How to check | Fix |
|---|---|---|
| It went to Requests. Meta delivers private replies to the inbox only if the person follows you, otherwise to Requests | Test from a non-follower account and open Requests | Say 'check your message requests' in the caption and public reply |
| It went to Hidden requests, which Meta says holds requests that may be offensive, spam or caught by Hidden Words | On the test account, open Requests, then Hidden requests | Keep the message plain, personal and to one link. You cannot change the other person's filters, so also invite people to message you directly |
| Your own team cannot see the replies. Meta says Business Suite Inbox does not sync messages from your Instagram Hidden requests folder | Instagram app: Messages, Requests, Hidden requests | Move wanted chats to the main folder. Our one-inbox guide covers daily triage |
| The public reply went out, the DM did not | Compare the public reply time with the tool's send log | Set the tool to post the public reply only after the message is sent, or turn public replies off |
Conflicts: two messages, or the wrong one
| Likely cause | How to check | Fix |
|---|---|---|
| Two automations listen to the same comments. For example Business Suite's 'Comment to message' and a third-party app | Business Suite Inbox, Automations; and your Page's connected apps under Advanced messaging | Keep one per post. Turn the other off |
| Duplicate notifications from boosted or ad posts. Meta notes these can arrive twice | Do duplicates happen only on boosted posts? | Ask your tool whether it removes duplicates by comment ID |
| A template automation won. Meta says when a keyword automation and a template such as the away message both trigger, the template is sent | Was it outside your set hours? | Adjust away hours, or accept the away message as the reply |
| Messages you did not set up. Meta lists four sources: Inbox automations (labelled 'Sent by automated response'), click-to-message ads, the Messenger welcome message, and third-party apps | Read the bottom of the message; check Ads Manager templates and connected apps | Turn off the source you do not want |
Limits and pauses: it worked, then stopped
| Likely cause | How to check | Fix |
|---|---|---|
| Rate limit. Meta's rate-limit page lists 750 private replies per hour per account for comments on posts and reels | Did the post get a burst of keyword comments? | Wait, then check whether your tool retries skipped comments. Private replies stay possible for 7 days after each comment |
| Meta Business Agent was switched on. Meta says this pauses existing automations such as away messages and instant replies | Business Suite Inbox settings | Decide which one you want running |
| Your tool's own plan or usage cap | The tool's usage or billing page | Raise the cap or narrow the automation |
| The connection expired or was revoked, for example after someone left the business or changed access | Reconnect warnings in the tool; Page roles | Reconnect with an admin account |
| The campaign ended | The automation's end date or status | Switch it back on, or update the caption so people stop commenting |
Prevent the next failure
Most of the causes above are quiet: nothing tells you a connection lapsed or a keyword stopped matching until a customer says they never got the link. A short routine catches them early. This is our suggested routine, not a Meta requirement.
Before each campaign post
- Comment the keyword from a non-follower test account and find the message in Requests.
- Comment one near miss (lowercase, plural or with an emoji) and note whether it matches.
- Open the link from the message on a phone.
- Check that only one automation covers the post, in Business Suite and in any other tool.
- Confirm the caption tells non-followers to check their message requests.
Once a week while automations run
- Compare keyword comments with messages sent for each live post. A gap means skipped comments.
- Look for reconnect warnings in your tool and in Business Suite.
- Read the replies people sent back, and answer the ones still waiting.
- Review the opt-out list and add anyone who asked to stop outside messaging.
- Switch off automations on posts whose offer or deadline has passed.
Keep a note of every change you make to an automation, with the date. When something breaks, the last change is the first suspect, and support will ask for it.
What to send your tool's support
If none of the above fits, contact the tool's support with facts they can check. A vague 'it doesn't work' costs a day.
Support request
- Account
- @handle, account type (business or creator), public or private
- Post
- Link to the post, its type (post, reel, ad, Live) and when it was published
- Automation
- Name, keyword list, which posts it covers, whether a public reply is on
- Example comment
- Exact text, time and the commenter's handle (with their permission), and whether they follow you
- What happened
- Nothing, public reply only, message in Requests, two messages
- Already checked
- Connected tools setting, Page role, Business Suite automations, other apps
Once it works, the set-up guide How to Set Up Comment-to-DM on Instagram has a measurement log so you can see whether the flow earns its place, and Instagram DM Automation: What to Set Up First helps you decide what else to automate. For posts that fail to publish rather than messages that fail to send, see Instagram and Facebook scheduling failures.
Common questions
Why does my Instagram auto DM work for me but not for customers?
You are probably testing from an account that follows you or has a role on the business. Customers who do not follow you get the message in Requests, and comments older than 7 days cannot get a private reply. Test from a separate non-follower account.
Can I resend a comment-to-DM message that failed?
Meta allows one private reply per comment, within 7 days. If the person later messages you, you can answer within the 24-hour window their message opens.
Does comment-to-DM work on a private Instagram account?
No. Meta's webhook documentation says private accounts do not receive comment notifications, which is what comment-to-DM tools rely on.
Sources
- Meta for Developers: Set up Instagram webhooks (Live apps, Advanced Access, public accounts only, 36-hour retries) (checked 12 Nov 2026)
- Meta for Developers: Instagram private replies (7 days, Live during broadcast, one message, inbox or Requests, ads duplicates, requirements) (checked 12 Nov 2026)
- Meta for Developers: Instagram messaging, get started (Allow access to messages, Connected tools) (checked 12 Nov 2026)
- Meta for Developers: Rate limiting (750 private replies per hour per account) (checked 12 Nov 2026)
- Meta Business Help Centre: Troubleshoot Meta Business Suite Inbox issues (message sources, Hidden requests, regions, collab posts) (checked 12 Nov 2026)
- Meta Business Help Centre: About Inbox automations in Meta Business Suite (keyword matching, priority, Meta Business Agent) (checked 12 Nov 2026)
- Meta Business Help Centre: About professional features in Instagram Direct professional inbox (Requests and hidden requests) (checked 12 Nov 2026)
- Meta for Developers: Developer Policies, sections 5.2 and 5.4 (opt-out, negative feedback) (checked 12 Nov 2026)
Written by the KeepsPosted editorial team from Meta's developer documentation and help pages listed, read on 12 November 2026, with AI assistance for drafting. The decision tree and the grouping of causes are our own; the causes come from Meta's documents, not from test logs, and tool-specific behavior varies.


