Use case
Catch comments that are already there.
Pro can run a rule against comments on a post you already published. Use it when the Reel took off before the automation existed.
3 minute read
What it scans
DripDM reads recent comments on the media and applies the keyword rule.
People who already got a private reply from another attempt are not a second send. Plan on one private reply per comment.
Backfill eligible requests, not an entire historical audience
If a guide launch collected GUIDE comments before the rule existed, configure the live rule first and replay against the intended media on Pro. Confirm the old caption still offers the same guide. DripDM scans recent comments and applies matching and delivery protections. The scanned count describes work inspected; it does not mean every scanned comment received a private reply. Inspect delivery activity after the run.
Older comments can be outside provider eligibility bounds, and a prior private reply cannot be reset just by rerunning the rule. Avoid changing a generic account-wide keyword to a new offer before sweeping old posts. That sends the wrong resource to someone who requested a previous one. Replay covers comments that are already on a post. Next post or Reel covers a post you have not published yet. Turn that rule on, publish, and open Automations to attach it. Replay is a recovery workflow for qualifying comments, not an import of historical contacts, a message to everyone who liked a post, or a guarantee that years of comments remain reachable.
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
Pro and above. It is listed as “run a rule on old comments.”
No. Scanned comments still need to match and pass eligibility, cooldown, duplicate, quota, and provider checks.
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.