Start with one eligible Facebook Page post, one keyword, and one resource. Verify the comment match, opening question, Yes response, and delivery separately.
Start with a Page and a specific promise
Facebook comment-to-Messenger automation connects a comment on an eligible post from your connected Page to a private response from that Page. It is not a way to message everyone who follows you, collect conversations from somebody else's posts, or turn a personal profile or Facebook group into an automated sales desk.
Choose a resource that fits the post: a menu, buying checklist, class timetable, product guide, or booking page. Tell people what they will receive and which word to comment. The automation should fulfill that promise, not introduce a surprise pitch wearing the checklist's jacket. Keep the first campaign narrow enough that you can check every step yourself.
Planning your first workshop? Comment CHECKLIST and we will message you about the free preparation checklist.
Build the comment-to-Messenger handoff in Triggered
- Open Accounts, connect the Facebook Page you manage, and grant the requested permissions. Confirm that you selected the intended Page, not another business you also help manage.
- Create an automation for that Facebook account. Select a specific eligible Page post for the first test, rather than expanding the campaign across all content immediately.
- Set CHECKLIST as the keyword and use exact matching for a controlled test. The caption and rule should use the same word.
- Choose Ask First with Yes / No buttons. Add the opening question, delivery message, and the public URL of the promised resource.
- Add a short public reply if you want to help people find Messenger. Save the automation with Active selected when you are ready to test.
Ask First is useful when you want an explicit next step before delivering the content. Immediate delivery is a separate option that puts the resource in the first permitted private reply. Do not configure one while writing campaign instructions for the other.
Write messages that explain what happens next
- Opening question: Want the workshop preparation checklist?
- Yes label: Yes, send it
- No label: Not now
- Public reply: Sent you a Messenger message. Check your message requests if it is hiding.
- Delivery message: Here is the workshop checklist you asked for. Start with the equipment section before buying anything exciting.
An opening question should identify the resource and make the choice obvious. Keep Yes and No labels short. A person should not need to decode a joke to understand whether tapping a button sends them a guide. Save the personality for the surrounding copy, where it cannot accidentally become a consent mechanism.
In this Ask First workflow, Triggered attempts the optional public response after the opening question succeeds. That public reply helps the recipient look for the message, but does not prove they saw it. Never include an email address, customer-specific access link, or other private information in a comment reply.
A private reply is not an unlimited messaging invitation
The first private response does not by itself open the standard messaging window for an ongoing conversation. A relevant recipient interaction is required. Triggered's Ask First buttons use quick replies so a Yes response can be received and processed. Clicking a website-link button is not the same interaction.
Keep the initial workflow focused on the request. If you enable optional email collection, explain whose updates the person is joining and keep the SKIP option so they can receive the resource without subscribing. Permission to receive one checklist is not automatically permission for an ongoing marketing list. Future email campaigns belong in your email provider, with appropriate unsubscribe handling.
Test on both sides of the conversation
- A match receipt shows the comment reached the automation.
- Waiting for reply means the opening question is not a completed delivery.
- A successful send does not establish that the recipient read the message or clicked the link.
- The recipient's actual Messenger view is part of the test, not an optional decorative extra.
Have somebody using a different personal Facebook account leave a fresh matching comment on the selected post. Note the approximate time. Confirm the comment is visible, then check Activity in Triggered. In Messenger, inspect both the main inbox and message requests. Do not use the Page's own comment as your only test.
Choose Yes and confirm the delivery contains the correct, accessible resource. Use a separate fresh test to choose No and check that the final resource is not delivered. Also test a nonmatching comment. If several tools are connected, make sure another provider is not answering the same keyword and creating a very enthusiastic duplicate conversation.
Expand only after the small test works
If there is no Activity match, check the account, selected post, active status, and keyword. If there is a match but the private step fails, inspect the recorded error and connection health. A reconnect prompt deserves attention; repeatedly disconnecting a healthy account is not a troubleshooting strategy. It is cardio for settings pages.
Once the handoff works, expand deliberately and review the first real campaign. If you enable link tracking, treat recorded opens as raw activity that may include automated previews, not verified sales. Change the resource, caption, or message one at a time so the next result tells you something useful. Account permissions, platform availability, and recipient settings can still affect delivery.
Sources and platform guidance
The setup examples above describe Triggered. These publisher documents explain relevant platform behavior; another tool’s features are not automatically available here.
Written for Triggered’s current workflow. Platform permissions and capabilities can change. ManyChat is an independent product; this guide is not affiliated with or endorsed by ManyChat.