Channels

Messenger usage policy: reply windows and automation

Understand ordinary Messenger windows, the ad-entry exception, human replies, and private replies to comments.

Published · Updated

Use this guide to organize team replies and automation in Message Pro. Official sources were reviewed on October 17, 2026. Meta rules and actual account capabilities govern execution.

Integration usage flow
Illustrative usage map; capabilities depend on the provider and actual configuration.

When is the messaging window open?

Most entry points have a 24-hour window. Meta’s September 28, 2026 update says a conversation started by a person’s first message after a Click-to-Messenger ad may have up to 7 days from that message. Viewing or clicking an ad without sending the message does not establish that window.

Meta messaging-window changelog

Keep sending routes distinct

RouteLimit to understand
Ordinary replyUse the conversation’s actual window; do not assume every conversation has 7 days.
Human AgentA separate period of up to 7 days for manual human replies, not permission to run a bot. The route and its permissions must be available.
Outside the windowUse only an authorized purpose-specific mechanism available to your account. An old conversation does not grant campaign permission.
Private reply to a commentPrivate-reply rules allow one message within 7 days of an eligible comment or visitor post, not an open-ended sequence. Continue the conversation only after the person replies to the private message; the ordinary reply window then applies.
Official Messenger policiesPrivate replies to comments

A practical Message Pro process

  1. 1

    Check how it started

    Review the conversation’s latest interaction and source. If you cannot establish the ad-entry exception, do not rely on 7 days.

  2. 2

    Identify the responder

    Separate a human reply from an automated message. Tell the customer when the service is automated and provide a clear handover route.

  3. 3

    Check the available route

    If sending is blocked or the needed mechanism is unavailable, keep the follow-up as internal work and consult an administrator. Do not relabel the message to bypass a restriction.

  4. 4

    Inspect the result

    Check acceptance and delivery. Record the rejection reason before retrying.

Team examples

For an ordinary inquiry, review the window before automating a reply. For an ad-originated contact, verify the first post-ad message and availability of the exception. For a post comment, prepare an appropriate private reply and wait for customer engagement before planning a full conversation follow-up.

Connect Facebook Messenger

Apply the rules to chat, AI, and workflows

  1. 1

    Before a manual reply

    Review the last inbound message, customer context, and purpose. Use an available sending route consistent with the rules above.

  2. 2

    In AI instructions

    Avoid repeated retries after rejection and do not treat a human-reply allowance as automation permission. If the route is unavailable, use handover or internal follow-up.

  3. 3

    In a workflow

    Check eligibility at the sending step, especially after Wait or scheduling. Permission at workflow start does not prove permission after time passes.

  4. 4

    After sending

    Inspect acceptance, delivery, and the customer reply. Handle opt-outs before campaigns or reminders and retain the failure reason for the team.

Team test example

Test a reply in the ordinary window, a delayed follow-up outside it, and a private reply to a comment. Do not start a comment-follow-up sequence before the person replies. For an ad entry, verify the exception rather than applying seven days to all conversations.