ReachleeFacebook comment-to-message not working?
The checklist, in order of likelihood.
Someone commented on your Facebook Page post and the Messenger reply never came. This is the list we work through, ordered by how often each cause turns out to be the real one, with the symptom, the check and the fix for each. Most cases are solved by the first two.
The short answer
Most Facebook comment-to-message automations that "don't work" were never triggered. The most common cause is testing from the Page's own profile or a Page admin: the Page's own comments are ignored, so nothing fires. Next: the post is on a personal profile or in a Group, which the Messenger Platform does not support. Then, in order: the comment already used its one private reply, it is older than 7 days, the keyword didn't match, the message landed in Message Requests or Spam, the automation is scoped to a different post, the Page lost its connection, a follow-up went outside the 24-hour window, or the Page hit a rate limit. On Business Suite, also remember the 15-minute delay.
1. You tested from the Page itself or from an admin
This catches more cases than everything else combined. You publish the post, comment the keyword as the Page or from the admin's profile, and nothing happens. The Page's own comments are ignored: Meta sends no event for a Page commenting on its own post, and Reachlee drops them deliberately so your manual replies never trigger a private reply to yourself. The automation is configured perfectly and looks broken.
- Symptom: no public reply, no Messenger message, nothing in the activity log.
- Check: was the test comment posted as the Page, or from a profile with a role on the Page?
- Fix: comment from a profile with no Page role, then wait a minute (15 on Business Suite).
2. It's a personal profile or a Group, not a Page
Meta's Messenger Platform works with Facebook Pages only. A personal profile cannot receive comment webhooks or send Messenger messages through the API, and professional mode doesn't change that. Groups are out too: the Groups API was withdrawn. If a tool shows nothing to connect, this is why. The rulebook is in Facebook Page automation rules.
- Symptom: the tool can't find the post, or the profile or Group doesn't appear in the connect flow.
- Check: was the post published by a Page, or by a profile or inside a Group?
- Fix: create a Page (free, minutes), publish the post from it, attach the automation there.
3. The commenter already got their one private reply
Meta allows only one message to the person who commented, per comment, and no tool can send a second. It bites when two automations match the same comment: Business Suite's Comment to message still switched on plus a Reachlee automation, or two automations with overlapping keywords. Only one wins. "The wrong reply went out" and "it only works sometimes" are usually this bug.
- Symptom: an unexpected message arrives, or it works for some comments and not others.
- Check: can more than one automation, in more than one tool, match the same comment?
- Fix: disable the duplicate. Reachlee's pre-flight gate already refuses a second reply to the same comment.
4. The comment is older than 7 days
A private reply must be sent within 7 days from when the comment was created. Meta enforces it, and older comments are permanently ineligible. It shows up when you attach an automation to a post that has been collecting comments for weeks: only the last 7 days can be reached. Reachlee's Retrigger covers exactly that window, skipping people already messaged. Business Suite cannot act on earlier comments at all.
- Symptom: new comments trigger fine, old ones never do; Retrigger reports comments skipped as too old.
- Check: when was the comment posted relative to today?
- Fix: none for the old ones. Reply publicly under them, and Retrigger the last 7 days.
5. The keyword didn't match
On Business Suite the match is strict: keywords are case-sensitive, so "Link" does not match "link", and you get 5 keywords to cover variations. Reachlee matches case-insensitively, but spelling still matters. Emoji are the sneaky one: a comment that is just a heart contains no keyword, and people asking in full sentences never typed the word at all.
- Symptom: some commenters get the reply, and the ones who don't typed something slightly different.
- Check: read the exact comment. Casing? Spelling? Emoji instead of a word?
- Fix: put the exact keyword in the post copy, add the variations people type, or match any comment on giveaway posts.
6. The message landed in Message Requests or Spam
The reply was sent and delivered; the person just can't see it. In practice, we have seen a brand-new Page's first private replies land in the recipient's Message Requests or Spam folder until the Page has some conversation history, while established Pages deliver to the main inbox. That is observed behaviour, not a Meta rule, and it fades as the Page has real conversations.
- Symptom: the log shows sent and the public reply appeared, but the tester saw nothing.
- Check: ask the tester to open Messenger → Message Requests, and the Spam folder inside it.
- Fix: nothing on your side. Have a few real conversations from the Page and tell early commenters where to look.
7. The automation is on a different post
If the automation is scoped to one post, only comments on that exact post count. You reshared the post and people commented on the copy. Or you boosted it: Meta delivers comments on boosted and ad posts and Reachlee handles them, but the automation must include the post being boosted. An ad built from a separate creative is a post your automation has never heard of.
- Symptom: comments on the original post work; comments on the boosted or reshared version don't.
- Check: which post did the comment land on, and does the automation's scope include it?
- Fix: add the other post or switch to every-post scope. Boost the existing post rather than creating a new creative.
8. The Page was disconnected or lost permissions
Every tool sending Messenger messages needs a Page access token from someone who can perform the messaging task on the Page. If that person loses their Page role, leaves the business portfolio, or revokes the app, every send fails silently. Page tokens don't expire on a 60-day clock like Instagram tokens, so this is rarer on Facebook. Reachlee, a Meta-verified tech provider, flags the Page as needing reconnection and blocks sends rather than piling up failures.
- Symptom: every automation on the Page stopped at once; a reconnect prompt appears.
- Check: does the person who connected the Page still have a role on it? Was the app revoked?
- Fix: reconnect from a profile that still has the messaging task. On Business Suite, confirm you can still open the Page's Inbox.
9. The follow-up was outside the 24-hour window
If the first message arrived and a second never did, nothing is broken. Businesses have up to 24 hours to respond to a user, and the window opens when the person messages the Page, taps Get Started, clicks a Click-to-Messenger ad, opens an m.me link or reacts to a message. Your private reply is not on that list, so until they write back there is no window for a follow-up. Reachlee's reminder fires at least 30 minutes later, inside the window, only once the person has replied, and cancels on reply or click. Details in the Messenger 24-hour rule.
- Symptom: first message delivered, second never sent, or logged as outside the window.
- Check: did the person reply to the first message? If not, no window was ever open.
- Fix: end the first message with a question, and ask for an email so you have a channel that doesn't expire.
10. The Page hit a rate limit
If sends stopped abruptly Page-wide and the Page is still connected, look at volume. Meta limits private replies to 750 per hour per Page, the Send API to 300 calls per second per Page for text, and applies a Business Use Case limit of 200 times the Page's engaged users per 24 hours. A viral post on a tool that doesn't pace itself trips throttle codes 32, 80001 or 80006. Reachlee reads the rate-limit headers and backs off, queuing sends rather than dropping them.
- Symptom: sends worked, then stopped Page-wide during a spike; the log shows throttle errors.
- Check: how many private replies went out in the last hour? Are other tools also sending for this Page?
- Fix: wait it out, and consolidate to one sender per Page.
Business Suite only: the delay and the desktop rule
Two Business Suite "failures" are not failures. The reply is sent after a 15-minute delay unless you reply to the person first, so a test that ends after five minutes will always look broken. And Comment to message plus Custom keywords are desktop-only to set up; open Business Suite in a desktop browser and go to Inbox → Automations. If the free tool's constraints (5 case-sensitive keywords, one fixed reply, no follow-up) are the real problem, see Business Suite's comment-to-message limits.
The five-minute diagnostic
Comment from a profile with no role on the Page
Eliminates the number-one cause. If the reply arrives, the automation was always fine. On Business Suite, wait the full 15 minutes.
Confirm it's a Page, connected, and read the exact comment
The post must belong to a Page that shows as connected. Then check casing, spelling, emoji, the comment's age (7 days) and which post it landed on.
Check Message Requests, and stop if it's the second message
If the log says sent, the message exists; new Pages land in Message Requests in practice. A missing second message is the 24-hour window: fix the first message's copy, not the configuration.
Almost every "Facebook comment-to-message isn't working" report is one of three things: the test was run from the Page or an admin so no event existed, the post isn't on a Page at all, or the thing that failed was a follow-up Meta's 24-hour window was never going to allow. None of those are fixed by switching tools, because Meta's rules apply identically to every tool on the Messenger Platform. What differs is visibility: whether you can see per comment that the event arrived, the keyword matched, and what Meta said on send. Setup for both paths is in How to auto-message Facebook commenters; the wider picture is in Facebook Messenger automation.
Facebook comment-to-message troubleshooting, answered.
Why didn't the automation reply when I commented on my own Page's post?
Because the Page's own comments are ignored. A Page commenting on its own post is not an event Meta sends to apps, and Reachlee drops those comments on purpose so your manual replies never trigger a private reply to yourself. Comments from the Page admin's profile behave the same. Test from a profile with no role on the Page.
I set up Comment to message in Business Suite and nothing happened after 5 minutes. Is it broken?
Probably not. Business Suite sends keyword replies after a 15-minute delay unless you reply first. Wait the full 15 minutes, then check that the comment's casing exactly matches one of your 5 case-sensitive keywords and that the test came from a profile that isn't the Page or an admin.
The person got the first message but not the follow-up. What went wrong?
Nothing. A private reply to a comment does not open the 24-hour window; only the person's own action does. Until they reply there is no window for a follow-up. Reachlee's reminder only fires inside the window, at least 30 minutes after the first message, and cancels on reply or click. Write a first message that asks a question worth answering.
Why does it work on the organic post but not on the boosted one?
Meta does send webhooks for comments on ad posts and Reachlee handles boosted Page posts. The usual culprit is scope: the boosted version was built as a separate ad creative, so its comments belong to a post the automation doesn't include. Boost the existing post, add the ad's post, or use every-post scope.
My tester says nothing arrived, but the log says sent. Who's right?
Both, usually. In practice a new Page's first private replies can land in Message Requests or Spam until the Page has some conversation history. It's observed behaviour, not a documented rule. Ask the tester to open Messenger → Message Requests and check Spam inside it.
All my Facebook automations stopped at once. What should I check first?
The connection, then rate limits. If the person who connected the Page lost their role or revoked the app, every send fails silently; look for a reconnect prompt. Otherwise, 750 private replies per hour per Page and a Business Use Case cap of 200 times engaged users per 24 hours apply; throttle codes 32, 80001 and 80006 in the log confirm it.
Does switching from Business Suite to a paid tool fix any of this?
It fixes what belongs to the tool: the 15-minute delay, 5 case-sensitive keywords, one fixed reply, no follow-up, no lead capture, no analytics. It does not change Meta's rules: Pages only, one private reply per comment, 7 days, the 24-hour window. The Instagram version of this checklist is Why did my Instagram automation stop working?, with its rules in Instagram automation rules.
Instagram