Automate the DMs you already get.

Order

Do not automate three offers on day one.

A connected assistant can build the comment rule in this sequence. Story rules and DM keyword rules stay in Automations. The setup is on /how-to/connect-your-agent.

• Pick an existing post or story, or set Watch to the next post or Reel and publish after the rule is on.
• Match the keyword to that ask.
• Read the first ten threads in the inbox and fix the wording.
• Add a reminder on Pro only after the first message gets taps.

Automate one repeated request first

Choose a job you already answer manually: a guide link, opening hours, a menu, or a booking destination. Keep the reply fixed when the correct answer is stable. Decide whether customers naturally arrive through comments, story interactions, or direct keyword messages, then build around that behavior. For a comment rule, set Watch to every post and Reel, one existing post or Reel, or the next post or Reel. Tie the rule to an identifiable connected account and an understandable invitation. Automation cannot turn a like or profile view into permission to message someone.

A workflow to try

Write the destination and response before enabling the trigger. For a guide request, the message can explain what the file contains and give one primary next step. Test the whole journey from an independent account. Read the first conversations to learn whether people recognize the offer and can open the link. Add lead capture only when you have a reason to retain an email or phone, and explain that reason before asking. Track the requested action rather than treating every reply as a sale.

Checks before you change the setup

If you later add Pro scheduling or a reminder, check the last inbound message at the intended send time. A comment-led private reply does not open the ordinary messaging window without a recipient response. If questions begin to vary, consider optional Growth AI only after the knowledge and fallback are ready. Keep a human responsible for exceptions. Do not launch overlapping rules, migrate another messaging app, and change the caption in the same test; isolate one variable at a time.

Review actual threads before widening the rule

Read a limited sample for recognition, fulfillment, and unresolved questions. If several people ask what the message refers to, fix the invitation or opening context. If the destination fails, repair it before adding more triggers. If questions require facts the saved reply does not cover, prepare those facts before considering AI. Do not label every conversation as converted merely because the rule fired. Keep exact resource requests distinct from qualification or support requests. This review helps you add the next rule for a real observed need rather than launching a complex account-wide system that nobody can diagnose when one stage goes quiet.