Home Features Creators FAQs Blog
About Contact

Private Reply Limits: One Automated DM per Comment

One comment to one private reply, with additional attempted messages stopped at an eligibility boundary

Last reviewed: August 2026. Instagram Private Reply — one DM per comment — is a Meta platform limit, not a CommentLink preference. Official Instagram Platform docs (updated 30 June 2026) have described this shape: only one message can be sent to the commenter for that comment; it must be sent within 7 days for posts and Reels; for Live, only during the broadcast. Follow-up messages only if the recipient responds, within 24 hours of that response. Recheck Meta’s Private Reply page before you plan a campaign. We will not freeze a screenshot as policy.

Your first bubble has to carry the payload. This article is that one-send constraint. The 24-hour messaging window for multi-step flows after they reply is a different piece: messaging window and multi-step flows. CommentLink has no Live comment trigger; treat Live-during-broadcast as Meta’s rule, not a product we ship.

What “one private reply per comment” actually means

One comment id, one automated private reply. If they comment LINK twice, those are two comments and can be two private replies — if both match and you still have send budget. If they comment once and stay silent, you do not get a nurture DM on day two for that same comment. A delay node is not a loophole.

The 7-day clock is for sending that one private reply after the comment on posts and Reels. It is not seven extra DMs. If you arm a rule on old media, confirm you are still inside Meta’s window. Recheck the current docs; this surface moves.

Live is tighter in Meta’s documentation: a private reply to a Live commenter only while the broadcast is live. CommentLink does not subscribe to Live comments. Do not plan a CommentLink Live AutoDM. On-demand path: the same keyword on a Reel. More: Live comment automation.

Design the first DM like it is the only DM

Link, button, “check Requests if you do not follow us.” If they never reply, that bubble is the whole relationship from this comment. Related: link in the first DM.

Ahmedabad furniture Reel. Caption: “Comment CATALOG.” First DM must include the catalogue URL. A flow that says “reply YES for the PDF” withholds the file from everyone who screenshots and leaves. They used their one private reply on a prompt.

If you need a fit question, put the public asset in the same bubble: “Rate card: [URL]. If you need a custom 4BHK quote, reply with city + timeline.” Silent people still got the card. Talkative people continue.

What continues after they reply — and what does not

After they respond, you may send follow-ups inside Meta’s messaging rules (the 24-hour article owns that clock). Buttons, collect_email, condition, ai_reply, human_handoff — those nodes run on inbound, not on a silent timer. If you built a three-day drip that fires without their reply, you designed against the private-reply limit.

  1. They comment KEYWORD on a post or Reel.
  2. CommentLink sends one private reply (inside Meta’s 7-day window for those surfaces — confirm current docs).
  3. If they stay silent: stop. No second private reply on that comment.
  4. If they reply: later nodes may run under the messaging window.
  5. A new comment is a new comment id — not a retry of the old one.

DM-keyword and Story-reply triggers are different entry points. They are not extra private replies on the original comment. Do not chain “if silent, wait and private-reply again.”

Public reply is not a second Private Reply

A public “check your DMs” is a comment on the media, not a second private message. Use it to point at Requests. Keep it one sentence. Details: public check-your-DMs reply.

Do not put the only URL in the public comment if the caption promised a DM. You then trained people to skip the private reply, and you published the link to every lurker. Public pointer, private payload.

Mistakes that burn the one send

  • Two automations on the same keyword “so they get a reminder.” Instead: one rule. The second send will fail or violate the one-message rule.
  • Delay 24 hours then send the URL without a reply. Instead: send the URL in message one.
  • Planning five qualification questions before any asset. Instead: asset plus one question, or a form URL inside message one.
  • Treating Live chat as a CommentLink trigger. Instead: Reel keyword. We have no Live trigger.
  • Assuming a human can “private-reply again” on the same comment id as a new automation event. Instead: humans reply in the open thread under messaging rules, not as a second comment private reply.
  • Arming a rule on a month-old post without checking the 7-day window. Instead: confirm Meta’s current window before you promise DMs on archive content.

Copyable one-send checklist

Before publish: payload in send_message or send_buttons. Requests note. Optional one-line public reply.

Test A: comment, do not reply, wait past any delay, confirm no second DM.

Test B: new comment from the same tester if you need another private reply.

Test C: reply to the first DM, confirm node two runs.

If Test A fails (a second bubble appears without a reply), you have two rules or a misunderstanding of delay. Fix that before a launch.

What CommentLink cannot do with this limit

We cannot send two AutoDMs for one Instagram comment as two Private Replies. We cannot sell extra comment-reply quota. We cannot use a delay, AI reply, or WhatsApp node to bypass Meta’s one-message-per-comment rule. WhatsApp starts when they write on WhatsApp; silence on Instagram is not a WhatsApp send.

We cannot private-reply Live comments in this product. We cannot treat Trial Reels as a special trigger. Recheck Meta docs when you next plan — last reviewed here August 2026 — and do not invent a second-send feature from a competitor screenshot.

How this differs from the 24-hour window article

This page: one private reply per comment, 7-day send window for posts/Reels, Live-during-broadcast in Meta’s docs, first bubble must carry the payload. The companion owns what happens after they respond — session clocks, multi-step nodes, what a delay can and cannot do once the thread is open. Do not paste that clock in here as a second copy. If you only remember one sentence: silent commenters get one DM, not a sequence.

Worked split: they comment CATALOG, get the URL, go quiet for three days. You do not get a “just checking in” private reply on that comment. If they then DM you “got it, what’s the teak dining table in 8-seater?” that inbound is a new thread event — dm_keyword or a human — not a second comment Private Reply. If they comment CATALOG again on the same Reel, that is a new comment id and can get its own one send, still inside Meta’s window and your hourly cap.

FAQ

Can I send two AutoDMs for one Instagram comment?

Not as two Private Replies on that comment. Meta allows one. Continue only after they message you back.

How long do I have to send the private reply?

Meta’s docs have described 7 days for posts and Reels. Confirm the current Private Reply page. That is time to send the one message, not seven extra DMs.

Does a delay node let me send a second DM if they stay silent?

No. Delay does not create a second private reply on a silent commenter.

Can CommentLink auto-DM Live comments?

No Live comment trigger in the current product. Meta has described Live private replies only during the broadcast — that is not a CommentLink feature.

Is a public “check your DMs” a second Private Reply?

No. It is a public comment. Keep it short. Put the payload in the private reply.

If they comment LINK again, do they get another DM?

A new comment is a new comment id. It can get its own private reply if it matches and you still have send budget. It is not a retry of the old comment.

Related reading

Send the link in a private DM

Connect Instagram with Meta login and send a private DM when someone comments a keyword.

See comment-to-DM