Blog
Comment to DM in one rule
One keyword, one public reply, one private link. That is the whole automation.
3 minute read
Do this
Keep the change small enough to test from a second account the same day.
- Print the keyword in the caption so people know the word.
- Set Watch to every post, one existing post, or the next post. Turn a next-post rule on before you publish.
- Open Automations after you publish. The notice confirms the post. The rule then watches only that post.
- Keep the public reply under one sentence.
- Put the URL in the DM. Track it.
One rule is a complete handoff, not just a trigger
The caption, public acknowledgment, private message, and destination describe the same offer. A keyword rule is simple only when those pieces agree. Set Watch before you publish. Next post or Reel waits until the earliest new post exists. Open Automations to attach it and read the notice. If the post offers a checklist but the DM opens with an unrelated discount, the automation can run technically while failing the customer expectation. Prepare the resource first, choose one readable keyword, and let the opening private reply fulfill the promise without depending on a later message.
A workflow to try
Draft the four pieces together. The post says what CHECKLIST delivers, the public reply tells the commenter where to look, the DM explains the file and contains the destination, and the landing page opens on mobile. Test a fresh comment from an independent account. Inspect message requests as well as the main inbox, then follow the link. Read the first real conversations before adding a lead ask or follow gate. Each added step should have a clear purpose for the recipient.
Checks before you change the setup
A comment grants one eligible private reply, not a general messaging window. If you need another message, the recipient must respond before ordinary follow-ups become eligible. Do not count a public reply as proof of private delivery or a URL click as a sale. If the rule goes quiet, inspect account, scope, keyword, and the actual rejection before changing copy. Keep the successful baseline so later experiments can be compared with a known working flow.
A short message outline to adapt
The first private reply can identify the requested resource, provide its maintained destination, and invite a relevant question. The public acknowledgment can tell the person where to look without exposing personal details. Set Watch before you publish. For the next post, turn the rule on, publish, and open Automations. The notice names the post. Keep the caption honest if an email ask or gate is required before delivery. Read the four pieces together whenever you change one: invitation, acknowledgment, private message, and destination. If the resource disappears, pause or update the promise instead of letting a live rule keep announcing a file that no longer opens. A simple workflow stays simple when the business maintains the whole handoff, not only the keyword setting.
Questions
Print the keyword in the caption so people know the word. Set Watch to every post, one existing post, or the next post. Turn a next-post rule on before you publish. Open Automations after you publish. The notice confirms the post. The rule then watches only that post. Keep the public reply under one sentence. Put the URL in the DM. Track it.
Keep the handoff understandable: public text can acknowledge the request, while the private reply delivers the promised destination. Do not publish someone’s email or other personal details. Verify the actual DM before treating the public acknowledgment as evidence that delivery succeeded.
The caption promises a usable resource, not merely a reply. Open the destination on mobile, verify access, and inspect the complete private handoff. Set Watch before you publish. For the next post, turn the rule on and open Automations after you publish. A working keyword cannot fix a missing file or an unsuitable landing page.