Private Reply Window
Also known as: 7-Day Private Reply, Comment Reply Window
Updated Jun 1, 2026
The Private Reply Window is the seven-day grace period the Instagram Graph API gives a Business or Creator account to send a direct message to anyone who left a public comment on its media. It is the only sanctioned mechanism for sending the very first DM to a user who has not initiated the conversation — every legitimate comment-to-DM funnel runs through it.
Under the hood, the call is POST /{ig-user-id}/messages with a recipient block of {"comment_id": "<id>"}. Meta clocks the seven days from the comment's creation timestamp, not from when your webhook received it, so a backlogged worker can blow the window even though the user just commented. The platform allows exactly one private reply per comment — additional attempts return error subcode 2534014. For Instagram Live, the window collapses to the duration of the broadcast itself.
Why it matters
The window is the legal-and-technical foundation of comment-triggered DMs. Without it, sending a DM to a non-following commenter would be cold outbound and policy-violating. With it, the same DM is treated as a contextual reply. Rate limits scale accordingly: the Graph API permits roughly 750 private replies per hour per professional account on regular posts and Reels, and 100 per second during a Live.
Gotchas
- The seven days are calendar days, not business days, and start from
created_timeon the comment object. - If the commenter deletes the comment before you call
messages, the window slams shut immediately — the recipient handle disappears. - Once the user replies inside the DM thread, you flip onto the 24-hour messaging window, which is a different rule set with different message tags allowed.
- Comment replies in the public thread are a separate API surface (
POST /{ig-comment-id}/replies) and don't consume the private reply allowance.
For a tactical walkthrough, see how to automate Instagram DMs legally.
Example
Example. A creator posts a Reel at 09:00 on a Monday. A viewer comments "RECIPE" at 09:14. The webhook fires, but the worker is rate-limited and backs off to a 120-second retry. The DM lands at 09:16 — well inside the seven days. Six days later, that same viewer comments "RECIPE" again on a different post; this is a brand-new window. The dedup table (keyed on commenter + media + account) prevents a double-send on the original post, but the new comment opens a fresh DM channel.
Related terms
API
24-Hour Messaging Window
Meta's 24-hour reply window. When a user DMs a business account, the account can reply for 24 hours; after that, only message tags or paid Sponsored Messages re-open the channel.
API
Human Agent Tag
A message tag in Meta's Messenger Platform that extends the 24-hour messaging window to 7 days — but only for human-operated replies, not bot-generated. Bot platforms can't claim it.
DM Automation
Comment-to-DM Funnel
A creator monetization pattern: a Reel asks viewers to comment a keyword, which triggers an automated DM with a link or product. Converts at 15-25% click-through vs 1-3% for link-in-bio.
Read more
Compliance
How to Automate Instagram DMs Legally — The Compliance Guide
What Meta's Messenger Platform Policy actually allows for DM automation, the difference between official API tools and gray-area scrapers, and how to stay safe.
DM Automation
Instagram DM Auto-Reply Rate Limits — The 30-50/Hour Rule and Every Other 2026 Cap
Every rate limit Meta enforces on auto-DMs in 2026 — per-hour caps, bot-flag thresholds, the 24-hour messaging window, and how to design automations that never throttle.