Use case
A Page comment can qualify for one private reply.
Someone comments your keyword on a Facebook Page post. DripDM replies under the comment and sends the Messenger message.
3 minute read
Same dashboard
The Page uses the same rule list as Instagram. You still connect the Page with Meta login.
Pro is the first plan that includes Pages.
Connect the Page post to a requested resource
A local venue can ask Page visitors to comment EVENTS for the current calendar. Connect the Page through Meta login on Pro or above, scope the comment rule to the campaign, and write the public and private replies separately. A Page comment rule uses the same Watch choices: every post, one existing post, or the next post. Turn a next-post rule on before you publish, then open Automations to attach it. The public reply stays under the post; the private reply provides context and the requested destination in Messenger. Test with a non-admin account so the result is not confused with your Page management view.
This is a Page workflow, not automation for a personal Facebook profile or group. The comment can permit one eligible private reply, but ordinary ongoing messages require the recipient to answer. Do not queue reminders simply because a public comment exists. If Instagram and the Page promote different events, keep the account selection and rule scope separate. Confirm permissions and inspect private delivery before telling customers that the calendar is in their inbox.
Prepare a test before asking your audience
Connect an eligible professional Instagram account through Meta login, or a Facebook Page on Pro or above. Select the intended account before editing a rule. Confirm the destination opens on a phone and that the offer matches what the caption promises. Use a second, eligible account for a real trigger test; an editor preview cannot prove provider delivery.
Inspect the public reply, private message, and destination separately. A successful public reply does not prove that the DM was delivered. Keep a record of the test time and inspect activity when something fails. Check permissions and rule scope before repeatedly triggering the same recipient. Disable a stale campaign rather than leaving an expired offer running.
Capacity, permissions, and realistic outcomes
Free includes one account, 1,000 DMs per month, 100 contacts, and 10 captured leads. Pro is $9 per month for three accounts and adds the follow gate, one follow-up nudge, scheduling, product cards, older-comment replay, and Facebook Pages. Growth is $14 for three accounts with 1,000 monthly AI credits. Business is $29 for ten accounts, five seats, and 2,500 AI credits. Paid messaging, contact, and lead quotas are uncapped in the plan configuration; Meta restrictions still apply. Sheets is a Business entitlement and needs provider authorization. Direct Meta Ads audience export is disabled, including on Business.
A comment can qualify for one private reply, subject to Meta eligibility and time limits. It does not itself open a general 24-hour conversation window. The recipient must reply before ordinary follow-up messaging can use that window. A link click or a new follow is not a substitute for an inbound message. Delivery also depends on account permissions, token health, recipient settings, and provider rate limits.
Questions
Yes. The public reply stays on the post. The private message goes to Messenger.
This workflow is for an authorized connected Facebook Page, not personal-profile or group automation.
Check the actual trigger, delivery activity, recipient reply, and destination separately. A scan, queued job, or link tap is not a completed sale. Use your booking or checkout system to confirm the final outcome.