Connecting Facebook Messenger

Facebook Messenger connects through the official Facebook Login for Business — you pick your Facebook Page, and its conversations land in AISAR's shared inbox alongside WhatsApp, Instagram, and Telegram. Here's what you'll need and how to get through the setup.

What you'll need

A published Facebook Page — an unpublished (draft) page cannot be connected.
An admin or editor role on that page, with permission to reply to messages (Facebook shows this as a Messaging task on the page) — an Analyst or Moderator role without messaging rights won't work.
Readiness to sign in to Facebook and grant AISAR the requested permissions: see the list of your pages, send and receive messages on their behalf, subscribe the page to new-message webhooks, and confirm the rights through Business Manager.
Agreement with Meta's Platform Terms — the wizard's connect button stays disabled until this checkbox is ticked.

Where to find it

In my.aisar.app open Settings → Channels → Add channel, find the Facebook Messenger card in the catalog, and click Connect.

How to connect

Click Connect on the Facebook Messenger card — the wizard opens, with three steps: Overview, Settings, Security.
The Overview step lists what the channel gives you (a unified inbox, AI agents and automations, team access, Messenger ad-click attribution), which permissions AISAR will request from Facebook, and a separate block for what AISAR does NOT read: the page's feed and posts, ad accounts, insights and analytics.
On the Settings step, enter a Channel name (required), optionally a Description, pick a Timezone, and decide whether this channel allows broadcasts, automations, and inbound handling, plus which teams can see it.
The Security step explains what AISAR will store (the page's ID and name, an access token scoped to that one page, who connected the channel) and what it won't (your personal Facebook token is never kept on the server). Tick the agreement checkbox and click Connect with Facebook.
A facebook.com popup opens — sign in with the account that manages the page you want, and grant the listed permissions.
Facebook returns you to AISAR on the "Select a page" step — a list of every Facebook Page you manage, with its avatar and name. Pages without messaging rights are marked "Needs a role with reply permission" and can't be picked; pages already connected to AISAR are marked "This page is already connected in AISAR" and are likewise disabled.
Click the page you want — AISAR creates the channel and subscribes the page to webhooks. A "Facebook authorization complete" screen appears; click Continue to return to the channel list, where the new channel already shows Connected.

The "Security" step of the Facebook Messenger wizard: what AISAR stores and the "Connect with Facebook" button

The "Select a page" step: a list of Facebook Pages with access and already-connected markers

The page list stays valid for 10 minutes after signing in to Facebook. If you don't pick a page in time, the screen shows "Connection session expired" — click Start over and sign in again.

What happens after connecting

Messenger messages — text, photos, videos, audio, files, stickers, button taps — land in the Chat section next to your other channels; any agent with access to the channel can reply.
The contact card shows the sender's Facebook profile name and avatar. For some accounts registered by phone number, Facebook doesn't expose a profile at all — the contact card then stays without a name or photo; that's Facebook's own limitation, not AISAR's.
Like Instagram Business and the WhatsApp Business API, Messenger has a reply window — about 24 hours from the customer's last message. While it's open, the composer works as usual; once it closes, a soft warning appears above the input, and sending anyway comes back as "not delivered".
If access to the page is revoked on Facebook's side (password change, app disconnected), the channel switches to Expired status with a reconnect button — it re-opens the Facebook sign-in and asks you to pick the same page again.

Common issues

Symptom	Cause and what to do
The page list is empty, "No pages available" screen	AISAR didn't find any page where your account can reply to messages. Check in the page's Business Settings that you have an admin or editor role, not just Analyst, and that AISAR's app has access to the right page.
The page you want is listed but greyed out	The "Needs a role with reply permission" hint means your role on the page doesn't include the Messaging task — ask your Business Manager admin to grant it.
"This page is already connected in AISAR"	A single Facebook Page can only be connected to one company in AISAR. If it wasn't your own company that connected it earlier, contact support — the app doesn't reveal on its own where the page is currently connected.
The connection session expired before you could pick a page	The page list stays valid for 10 minutes after signing in to Facebook. Click "Start over" and go through the connection again without delaying the page choice.
The Facebook popup closed without a result, or never opened	Check that your browser isn't blocking popups for my.aisar.app, and that you didn't close the window by hand before sign-in finished. Start the connection again.
The plan channel limit is reached when trying to connect Facebook Messenger	Your company's plan caps how many channels can be connected at once. Disconnect an unused channel, or raise the limit with an extra-channel add-on — plan details are on the pricing page.
Some customer messages don't arrive long after the last conversation	Messenger limits the reply window the same way the WhatsApp Business API and Instagram do — about 24 hours from the customer's last message. This is Meta's own platform limit, not AISAR's.

Current version limits