> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tied.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Facebook Messenger

> Connect a Facebook Page and answer Messenger conversations from the same inbox as every other channel.

A customer taps "Send Message" on your Facebook Page instead of hunting for a contact form, and that thread deserves the same routing, history and AI agent as one that arrived by email. Messenger is Tied's connector for that Page, not a separate silo next to it.

<Info>
  **1 billion+ monthly active users.** Messenger is still where a large share of small and mid-size
  businesses get their first inbound message, simply because the Page already exists.
</Info>

## What it takes

| Requirement | |
| - | - |
| **Plan** | All plans |
| **Account type** | A Facebook Page — not a personal profile or an Instagram-only account |
| **Permissions** | Admin access to that Page |
| **Time** | Minutes |

Connecting authorizes Tied against the Page, not your personal Facebook account. Once it's linked, Tied subscribes to six of the Page's webhook fields on your behalf — among them new messages, delivery receipts, read receipts, echoes of outbound sends, and the handover protocol's `standby` field for Pages managed by more than one tool — so nothing gets missed between the Page inbox and Tied.

## What you can send

Standard Messenger surfaces: text, images, video, audio, files, and Messenger's own quick-reply buttons. There's no rich card or carousel primitive here the way [Google RCS](/channels/rcs) or [Apple Messages](/channels/apple-messages) has one — Messenger's vocabulary is closer to a normal chat app than an interactive one.

<Warning>
  **Meta's 24-hour messaging window applies.** Once a customer has been quiet for 24 hours, Tied
  disables the reply composer in the dashboard so a standard human-agent reply can't be typed. That
  block is enforced in the dashboard UI only — Tied doesn't block a send server-side on this channel,
  so anything going out through an automation or a flow outside the composer isn't stopped by Tied
  itself. (Meta's Human Agent tag extends the window to 7 days, but it's an installation-level setting
  that defaults to off and needs Meta's approval to enable — not something you flip per account.) Plan
  resolutions inside your window.
</Warning>

## No channel fee

Messenger carries no carrier cost and no Tied channel fee — you pay for resolutions, not delivery. See [Channel fees](/pricing/channel-fees).

## Next

<CardGroup cols={2}>
  <Card title="Instagram" icon="camera" href="/channels/instagram">
    The other Meta inbox — same underlying account family, same connection model.
  </Card>

  <Card title="Channel fees" icon="radio" href="/pricing/channel-fees">
    Why Messenger costs nothing to deliver on, and what does.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.