Send a Page comment to Messenger.

Steps

The Page is a separate connection from Instagram.

A connected assistant can build this Page comment rule after the Page is connected. The setup is on /how-to/connect-your-agent.

• Upgrade to Pro if the workspace is on Free.
• Connect the Facebook Page.
• Create a comment rule on the Page. Set Watch, the keyword, and the Messenger text. Next post or Reel waits until you publish, then you open Automations.
• Comment on a Page post from another profile to test.

Connect and test the Page as its own account

A Facebook Page connection is separate from an Instagram connection. Confirm that you can authorize the correct Page and that the workspace is on Pro or above before writing a rule. Personal profiles and Groups are not this workflow. Identify the Page post, keyword, private message, and destination in advance. A Page comment rule uses the same Watch choices. Choose Next post or Reel, turn the rule on, and publish. Open Automations to attach the rule. If Business Suite already replies to the same word, save that configuration and coordinate which system owns the test so you do not mistake duplicate automation for success.

A workflow to try

For a menu offer, publish a Page invitation using MENU and create the matching rule on that Page account. Keep the public response brief and put the requested destination in the opening private message. Ask an independent profile to leave a fresh comment. Verify the public acknowledgment, Messenger inbox or message requests, and the actual URL. If email capture is part of the offer, explain the purpose and inspect the saved lead with a test address you control.

Checks before you change the setup

A successful first private reply does not imply that a later automated sequence is eligible. The person must respond before ordinary follow-up messaging can use the standard window. If neither response appears, check Page connection, post scope, enabled state, and keyword. If only Messenger fails, investigate the send result, private-reply eligibility, and conversation ownership. Do not treat a personal-profile test or an old already-replied comment as an independent customer event.

Keep the old Page setup recoverable during migration

Record the prior Business Suite or messaging-app configuration before turning off overlap. Move one post and keyword first, then test the private destination and any capture step. Tell the team which responder is active so a support operator does not accidentally reenable the old automation during the test. If the result is not ready, restore the known prior setup rather than leaving both responders to race. Preserve Page-specific wording and the correct account identity. A migration is successful when a new eligible Page request follows the intended journey, not when the Instagram equivalent still works or the new rule merely appears enabled.