Messenger's 24-Hour Messaging Window Rules for Businesses in 2026

Once a customer sends you a message, a 24-hour window opens. Inside it, you can send free, unlimited messages, including promotional content — the restrictions that apply outside the window don't apply here.

The window resets every time the customer sends a new message, not on a fixed clock. An active back-and-forth conversation can stay inside the free window indefinitely as long as the customer keeps replying; it's only silence on their end that eventually closes it.

There's a separate exception called the human-agent tag, which extends your reply window to seven days after the customer's last message. It's tempting to read that as extra runway for automation, but it isn't — the tag is explicitly for a human being replying, not a bot. It exists for the case where a customer's issue genuinely takes longer than a day to resolve and a live agent is still working it, not as a general-purpose way to keep a conversation open.

Meta actively monitors for automated replies sent under this tag and treats it as a policy violation, not a gray area. If your escalation flow hands the conversation to a live agent, the seven-day tag is exactly the right tool. If it's still routing replies through a bot, it's the wrong one, and it's a detectable one.

Message Tags used to let businesses send order confirmations, account updates, and event reminders outside the 24-hour window without triggering promotional restrictions. According to Meta's own changelog, that system was deprecated as of 2026-04-27, and tags like CONFIRMED_EVENT_UPDATE, ACCOUNT_UPDATE, and POST_PURCHASE_UPDATE now return error code 100 instead of sending.

The same changelog shows Recurring Notifications going the same way on 2026-01-07, replaced by Marketing Messages in most markets — Australia, the EU, Japan, South Korea, and the UK were carved out as exceptions, so it's worth checking your own market against the current documentation rather than assuming the old flow still applies.

If your order-confirmation or appointment-reminder flow was built on either of those, it's silently failing right now, not gracefully degrading. Error code 100 doesn't show up as a dramatic outage — it just means messages quietly stop arriving.

The categories most exposed here are the ones that used to route naturally through Message Tags: order confirmations, shipping updates, appointment reminders, event RSVPs. Any flow that assumed one of those could reach a customer outside the 24-hour window without a live agent involved needs a fresh look.

Go through each of those flows individually and ask where the message is actually sent from — inside the 24-hour window triggered by the customer's own activity, through the human-agent tag with a live person on the other end, or through one of the newer approved message types. If the answer is 'it's always worked, so we never checked,' that's the flow most likely to be failing silently right now.

Meta has rewritten this rulebook twice in one year, and there's no reason to assume it's finished. The safest default is to treat the 24-hour window as your primary channel, and everything else — human-agent tags, Marketing Messages, whatever comes next — as a narrow exception you check against current documentation before relying on.

Don't hardcode a tag name into your flow logic and forget about it. Check the changelog on a schedule, not only when something breaks — by the time a flow silently fails, customers have usually already noticed.

It also helps to design for graceful failure rather than assuming success. A flow that logs an error when a message type gets rejected is one you'll catch within a day. A flow that just moves on silently is one you'll catch when a customer complains they never got their order confirmation.