The Instagram 24-hour messaging window, explained

If you automate Instagram DMs — or are choosing a tool that does — one rule matters more than any feature list: a business account may only message a user within 24 hours of that user's most recent inbound message or eligible interaction. Meta enforces it at the API level, and how a tool handles it separates safe automation from account-risking automation.

What the rule says

Meta's messaging platform gives a professional account a "window" to send DMs to a specific person. The window opens — and re-opens — when that person interacts: they send you a message, or they tap a button inside your DM conversation. From that moment you have 24 hours to send messages. When the clock runs out, you can't start again until they interact again.

The window is per-person, not per-account. Every follower has their own clock, reset by their own actions.

Where comments fit

A comment on your post is not a message, so it doesn't open a full conversational window. What Meta allows instead is a private reply: one DM tied to that specific comment. That single reply is how comment-to-DM automation legitimately starts a conversation with someone who never messaged you.

This is why well-built tools structure the flow the way Cookping does: the private reply is an opening message with a button. When the follower taps it, that tap is an inbound interaction — now a real 24-hour window is open, links can be sent, and features that require consent (like follow-status checks) become available.

Why "check once" isn't enough

The subtle failures happen after the first send. Consider what a delivery pipeline actually does: it retries failed sends, waits for follow-gate confirmations, and processes backlogs after an outage. Each of those can execute hours after the comment arrived. A tool that checked the window only when the comment came in will happily send a message at hour 30.

The correct behavior — and the architecture rule Cookping is built on — is to persist the follower's latest eligible interaction timestamp and re-check the deadline immediately before every send: first attempts, retries, backoff, manual replays, and delayed follow-gate continuations. If the window has closed, the delivery is marked expired and the Meta send API is never called.

What this means for creators

  • A viral Reel is fine. Every commenter gets their private reply regardless of when they comment — each comment carries its own reply allowance.
  • Slow taps are fine. If someone taps your opening message two days later, that tap opens a fresh window and the recipe goes out.
  • Silence is respected. If someone comments but never taps, they get the opening message and nothing more. That's the system working, not failing.
  • "Expired" in your analytics is a good sign. It means your tool refused a non-compliant send instead of gambling with your account.

Questions creators ask

Can I buy my way around the window? No. It applies to every tool using the official API, at every price point. Tools that bypass it aren't using the official API — which is the thing Instagram actually bans.

Does the window differ between Instagram and Messenger? The 24-hour standard window is the same idea across Meta's messaging platform; some Messenger-specific message tags have different rules, but they don't apply to Instagram recipe delivery.

How does Cookping handle it? It's enforced in the delivery layer itself — every send path re-checks the deadline, and expired deliveries are recorded with their reason so you can see them in analytics. You don't configure anything.