Meta's 24-Hour Messaging Window, Explained Properly
Almost every "my automation suddenly stopped working" report traces back to this one rule. It takes five minutes to understand and saves weeks of confusion.
If you run any kind of Messenger automation, this is the single most important platform rule to understand. Nearly every "the bot stopped sending messages and I don't know why" report comes back to it.
The rule
When a person sends your Facebook page a message, a 24-hour window opens. Inside that window you can send them as many standard messages as you like — text, images, files, quick replies, templates.
When the window closes, standard messages are rejected by the API. Not delayed, not queued — rejected.
| Event | Effect on the window |
|---|---|
| Customer sends a message | Opens / resets to a fresh 24 hours |
| Customer clicks a quick reply or postback button | Resets |
| Customer reacts to a message | Does not reset |
| You send a message | Does not extend it |
| Customer comments on a post | Does not open a messaging window on its own |
The window is per person, per page. Nothing you do on your side extends it — only the customer engaging again does.
Why Meta has this rule
It exists to stop Messenger from becoming an inbox full of unsolicited marketing. From Meta's point of view, a business should be able to answer a conversation the customer started, not start unlimited new ones.
Understanding the intent helps, because it explains why the exceptions below are narrow and why abusing them is treated seriously.
What you can still send after it closes
There are limited message tags for genuinely necessary follow-ups. Each has a specific meaning and Meta audits their use.
| Tag | Legitimate use | Not for |
|---|---|---|
POST_PURCHASE_UPDATE | Order confirmed, shipped, out for delivery, delayed | Upsells, "you may also like", discount codes |
ACCOUNT_UPDATE | Changes to the customer's account or application status | Newsletters or promotions |
CONFIRMED_EVENT_UPDATE | Reminders for an event the customer registered for | Inviting people to new events |
HUMAN_AGENT | A human replying within 7 days when the bot could not resolve it | Automated messages of any kind |
Using a tag for marketing is the fastest way to get a page's messaging permissions restricted. POST_PURCHASE_UPDATE with a discount code attached is exactly the pattern Meta looks for. The restriction usually arrives with no warning and is slow to appeal.
The HUMAN_AGENT tag
This one is the most useful for commerce, and the most misunderstood. It extends the reply window to 7 days, but only for messages sent by an actual human agent — not automation.
It is meant for cases where a customer asked something at 2am, the bot could not answer it, and your team gets to it two days later. That is legitimate. Scheduling automated follow-ups under this tag is not.
Designing around the window
Do the important work early
Ask for the address, confirm the order and send the invoice while the customer is actively chatting. Do not defer anything essential to "we'll message you tomorrow".
Use one well-timed reminder
If a customer goes quiet mid-order, a single reminder a few hours later — still inside the window — recovers a meaningful share of abandoned orders. Two reminders annoy people.
Give them a reason to reply
A question reopens the window. "Shall I confirm the order?" is far more useful than "Let us know if you need anything."
Track window state per conversation
Your tooling should know, for each customer, when the window closes — and should not silently attempt sends that will fail.
Alert on send failures
A rejected send is a lost customer. It should surface somewhere a human looks, not just an error log.
Broadcasts and the window
This is where most pages get into trouble. You cannot broadcast a promotion to everyone who ever messaged your page — the vast majority of them are outside their window.
Your realistic broadcast audience is people who have messaged you in the last 24 hours, plus recurring-notification subscribers if you have set that up and they explicitly opted in.
A tool that lets you blast your whole contact list without warning you about this is setting your page up for a restriction.
Comments are a separate path
A comment on your post does not open a messaging window. But a private reply to that comment does — and that is why comment automation is so valuable for lead generation.
The catch: one private reply per comment, within 7 days of the comment. Details in the comment automation guide.
Does the window reset if the customer only reacts to my message?
No. Reactions do not count as engagement for this purpose. Only an actual message, quick reply, or postback button click resets it.
What happens if I send after it closes?
The API returns an error and the message is never delivered. The customer sees nothing. If your tool does not surface that error, you will believe the message went out.
Does the window apply to Instagram DMs too?
Yes, Instagram messaging via the Meta API follows the same 24-hour standard messaging rule, with its own smaller set of tags.
Can I ask customers to message me to reopen it?
You can ask inside the window. Once it has closed you have no way to reach them through Messenger except via a valid tag — which is exactly why you should not let it close on an unfinished order.
Let the platform track the window for you
botmiq knows each conversation's window state, times reminders inside it, and flags sends that would fail instead of losing them silently.
Start free trial