Instagram's 24-hour messaging window: what you can send, and when you cannot
Instagram gives a business 24 hours from a person's last message to send that person a DM through the API. Meta calls it the standard messaging window, it opens when the person messages you and reopens every time they message again, and once it closes an ordinary send is refused until they get in touch. Inside the window you can send several messages, and promotional content is allowed.
Instagram runs two separate clocks and most articles merge them. Twenty-four hours is how long you may keep replying to somebody who messaged you. Seven days is how long you have to send the single private reply that answers a comment. Neither one extends the other.
The rule, as Meta states it
Meta's Instagram messaging documentation puts it in two sentences. An app has 24 hours to respond to any message an Instagram user sends the professional account. And an app may only send a message to an Instagram user after that user has messaged the account first. The second sentence is the one people miss. The window is where the permission comes from, so a closed window leaves you with no route to that person at all rather than a late one.
Meta's Messenger Platform and Instagram Messaging API policy names it the standard messaging window and defines it as the 24 hour period in which you are allowed to send a message to a person. The same policy confirms two things worth knowing before you plan anything. You are not limited to a single reply inside the window, and a message sent inside it may carry promotional content, which is unusual in business messaging generally.
Why the window exists at all
Meta does not publish an essay on its reasoning, but the rest of the policy shows what the rule is protecting. Every other route to a person's inbox is fenced off: message tags exist for a short list of approved use cases, the policy states plainly that they may not be used for promotional content, and misuse can end in sending restrictions. The window treats a person's last message as the consent, and consent that never expires would make the API a broadcast channel.
Read that way, the rule stops being arbitrary. Somebody who messaged you an hour ago is in a conversation. Somebody who messaged you in March is a stranger you have contact details for.
What opens the window, and what does not
The window opens on something the person does, and it restarts from zero each time they do it again. The distinction that catches people out is between things that count as a message and things that feel like contact but are not.
| What the person does | Opens the window? | What you get instead |
|---|---|---|
| Sends a DM | Yes | 24 hours from that message |
| Replies to your story | Yes | It arrives as an ordinary inbound message |
| Mentions you in their story | Yes | Also delivered as an inbound message |
| Taps a call-to-action button in your message | Yes | Listed as a window-opening action in Meta's policy |
| Reacts to one of your messages | Yes | Listed in the same policy |
| Comments on your post or reel | No | One private reply to that comment, within 7 days |
| Likes, follows, saves or views a story | No | Nothing. No documented call reaches them |
The last two rows are where the money is lost. A person who comments on your reel has not opened a messaging window, so you cannot run a sequence at them. What you have is one private reply, addressed to that comment, valid for seven days. A person who liked the post has given you nothing the API can act on at all.
The human agent tag, and what it is actually for
There is one documented way past 24 hours on Instagram, and it is narrower than the blog posts suggest. Meta's Human Agent feature lets an app tag a message with human_agent and send it within seven days of the user's message. Meta's own description of the allowed usage is support a human agent gives when an issue cannot be resolved inside the standard window, with the examples being a business that is closed for the weekend or a problem that takes more than a day to sort out.
| Detail | |
|---|---|
| Window it grants | 7 days from the user's message |
| Intended sender | A human agent, replying to an unresolved issue |
| Access requirement | Successful App Review, and business verification |
| Allowed content | Support. Tags may not be used for promotional content |
| Penalty for misuse | Message sending restrictions |
Worth knowing about the wider list of message tags: they are documented on the Messenger side, alongside the messaging_type field that carries them. Meta's Instagram send-message guide mentions tagging a response so a human agent can reply outside the window, and shows no tag field in its own request examples. HookSend does not send either field. Nothing in its Meta client sets a tag, and the reason is in the next section.
Two windows, two clocks, and why every post confuses them
Search for Instagram's messaging window and you will find articles that open with 24 hours, then tell you a comment can be answered a week later, then give advice that only works under one of the two rules. Both numbers are real. They govern different calls.
| Standard messaging window | Private reply window | |
|---|---|---|
| Length | 24 hours | 7 days |
| Starts when | The person messages you | The comment is created |
| What it lets you send | Ordinary DMs, addressed to the person | One DM, addressed to the comment |
| How many messages | Several | Exactly one, ever |
| Restarts | Every time they message again | Never. One comment, one window |
| Extendable | To 7 days with the human agent tag | No |
| Live broadcasts | 24 hours from their message, as in any conversation | Only while the broadcast runs |
Keep them apart and the odd behaviour of comment-to-DM tools starts making sense. A comment from Monday can still be answered on Thursday, because the seven day clock is still running. A person who replied to that DM on Monday cannot be messaged on Thursday, because their 24 hours ran out on Tuesday. Same conversation, two clocks, different answers.
What this means for a follow-up sequence
Most people arrive at this topic because they want a sequence: the link now, a nudge tomorrow, a last call at the weekend. On this API the first message is free and every message after it depends on the person doing something.
- Message one is the private reply to the comment. You get one, within seven days, and it has to carry whatever you promised in the caption.
- Message two needs the person to act. If they reply, the 24 hour window opens. If they tap a button in your DM, Meta's policy counts that as a window-opening action and your app hears about it as a postback.
- Message three onwards runs on the same clock, and each reply from them resets it to a fresh 24 hours.
- A follow-up timed for three days later is not buildable unless the person messaged in between, tag or no tag.
This is why HookSend caps a campaign's follow-up delay at 1,440 minutes. Twenty-four hours is the longest delay that can still land inside the window the first reply opened, so the field simply does not accept a longer one. A tool that offers a seven day drip on comment-to-DM leads is either relying on the human agent tag for marketing, which the policy forbids, or the drip quietly fails.
What it looks like when you hit the wall
Meta does not fail quietly here, which is useful. A send after the window has closed comes back as an error about being outside the allowed window, and the failure is permanent for that conversation: no retry helps, because nothing about the request was wrong. HookSend treats that rejection as final rather than retrying it, for the same reason.
- In the inbox, an open conversation shows how many hours of the window are left, and a closed one is labelled as such before you type anything.
- A manual reply into a closed conversation is refused with a message saying the recipient has to write again or interact with your post first.
- In the logs, a DM rejected for the window is a failure rather than a skip, because the send was attempted and Meta said no.
If you are looking at a closed window on a lead you care about, the only route back is something the person does: a new message, a reply to a story, or a tap on a button in a DM you sent earlier. Nothing you can call will reopen it from your side.
Questions people ask about this
- What is Instagram's 24-hour messaging window?
- It is the period Meta allows a business to message somebody through the Instagram messaging API. Meta's documentation gives an app 24 hours to respond to any message an Instagram user sends the professional account, and permits sending only after that user has messaged first. Inside the window you can send more than one message, and promotional content is allowed.
- What resets the 24-hour messaging window?
- Another message from the person. Every new message restarts the clock at a fresh 24 hours. Meta's messaging policy also lists reacting to a message and tapping a call-to-action button in a message among the actions that open the window. A like, a follow, a story view or a saved post does not open anything, and neither does a comment on your post.
- Can I message someone on Instagram after 24 hours?
- Only with the human agent tag, and only within its own limits. Meta's Human Agent feature allows a tagged message up to seven days after the user's message, and describes it as support a human agent gives when an issue cannot be resolved inside the standard window. It requires successful App Review and business verification, and Meta's policy forbids using message tags for promotional content.
- Is the 24-hour window the same as the 7-day private reply window?
- No, and confusing them is the most common error on this subject. The 24 hour window governs ordinary DMs to somebody who messaged you, and it restarts each time they message again. The seven day window governs the single private reply that answers a comment, it starts when the comment is created, and it never restarts. Neither one extends the other.
- Why did my Instagram follow-up message fail to send?
- Usually because the 24 hour window closed. A follow-up can only land if the person replied to your first DM or tapped a button in it, and the clock runs from their last action rather than from yours. Meta refuses a late send with an error about being outside the allowed window, and no retry fixes it. The person has to get in touch again.