Meta Messaging Window & Message Tags: The 24-Hour Rule, Human Agent Access, and Why Automation Apps Get Rejected
If your Messenger or Instagram automation stops sending after a day, or Meta rejects your submission for messaging-policy reasons, you have hit the messaging window. Here is how the clocks actually work in 2026 and where teams get stuck.
Meta does not let a business message people freely. Every reply your app sends is measured against a strict timing rule and a short list of approved exceptions. Get the timing or the exception wrong and messages fail silently — or worse, the Page gets restricted. Most rejected messaging apps are not broken in code; they break a policy the developer did not know was being enforced.
The 24-hour standard messaging window
Under Meta’s Messenger Platform policy, once a person messages your Page you have up to 24 hours to respond with standard messaging. Each new message from that person resets the 24-hour timer. Meta also allows one extra message after the window closes — the 24 + 1 allowance. After that, standard messaging stops until the person writes again.
Instagram works the same way: your app has 24 hours to respond after an Instagram user messages first, and a conversation can only begin after the user reaches out. You cannot open a thread with someone who never contacted you.
Message tags: the narrow exceptions
Message tags let you send a specific, non-promotional message outside the 24-hour window — but only for a defined use case. This is where automation platforms most often get flagged: a tag used for the wrong purpose, or used to slip a marketing message past the window, is a policy violation.
| Tag | What it is for | Instagram? |
|---|---|---|
| ACCOUNT_UPDATE | A non-recurring change to the person’s account | No |
| CONFIRMED_EVENT_UPDATE | Reminder or update for an event the person registered for | No |
| POST_PURCHASE_UPDATE | Update on a recent purchase, e.g. shipping | Yes |
| CUSTOMER_FEEDBACK | A feedback survey, within 7 days of the last message | No |
| HUMAN_AGENT | A human reply within 7 days (see below) | Yes |
⚠ Message tags cannot carry promotional content. Older tags such as SHIPPING_UPDATE and RESERVATION_UPDATE were retired when Meta consolidated the list — calling a tag that no longer exists returns an error.
Human Agent access: the 7-day window that needs App Review
The HUMAN_AGENT tag lets a real person — not a bot — respond up to 7 days after the customer’s message, built for cases that cannot be resolved inside 24 hours, like a weekend or a support escalation. It sounds like the easy fix for a window that already expired, and that is exactly why apps misuse it.
Human Agent is not available in standard access or development mode. You must pass App Review for the Human Agent feature before you can use the tag in production — and Meta requires the messages to come from a human, not automation. Scripting messages under this tag is a policy violation.
Instagram is not a carbon copy of Messenger
Fewer tags
ACCOUNT_UPDATE, CONFIRMED_EVENT_UPDATE and CUSTOMER_FEEDBACK are not available for Instagram messaging. HUMAN_AGENT does apply to Instagram.
Handover changed
Since 23 October 2025 the Handover Protocol is no longer supported for Instagram — businesses moved to Conversation Routing.
Different permissions
Instagram uses instagram_business_basic plus instagram_business_manage_messages; Messenger uses pages_messaging.
The permissions behind the window
Messenger messaging needs pages_messaging; the Instagram messaging API needs instagram_business_manage_messages. If you only message your own Page or account you can operate in standard access. The moment you message Pages or accounts you do not own — which is every messaging SaaS — you need Advanced Access through App Review, plus Business Verification and a reviewable demo.
Why messaging apps get rejected or restricted
Using tags for promotions
Any marketing content sent under a message tag or outside the window is a violation, and a common cause of restriction.
Automating the Human Agent tag
HUMAN_AGENT is for human replies only; scripting it gets flagged.
Messaging first
Contacting a person who never messaged the Page breaks the entry-point rule.
Demo that does not prove the use case
App Review reviewers must see the real, policy-compliant flow — a vague screencast fails.
Get the window, the tags, and the Human Agent gate right and your automation keeps sending inside policy; get them wrong and messages fail or the Page is restricted. Mapping which messages are standard, which need a tag, and which genuinely need Human Agent App Review is the tricky part — and it is exactly what a proper submission handles. If you are preparing a Messenger or Instagram messaging app for review, I help teams get pages_messaging and instagram_business_manage_messages approved with a clean, policy-aligned submission. See the Messenger bot App Review guide, the Instagram messaging approval guide, and the App Review rejection reasons.
This article is educational and reflects Meta’s publicly documented messaging policy as of 2026. Platform rules change — always confirm against current official documentation. No specific outcome or timeline can be guaranteed.