Skip to main content
Belcenter AIHelp center
Configure a bot

Connect a Facebook Page to Messenger

Authorise with Meta, choose a Page, and verify messages without technical setup.

The Messenger skill allows the bot to answer messages on your Facebook Page. It is independent of WhatsApp: no phone number, WhatsApp Business account, or technical token is required. Your Page remains yours.

Connect your Page

  1. Open a bot you can edit and add the Messenger skill. For a new bot, click Save in the top right corner before connecting.
  2. In Messenger, select Connect Messenger. Allow the pop-up window if your browser blocks it.
  3. Log in with Meta and grant permissions for the Pages you manage.
  4. Return to BeAI and select your Page. Existing connections are flagged; taking them over requires confirmation and the necessary permissions.
  5. Click Connect this Page. BeAI verifies permissions and completes the connection; Meta authorization alone is not enough to activate the bot.

When full Page discovery is enabled by your administrator, Connect Messenger also requests permission to read Pages upon this initial authorization. This permission helps locate an authorized Page that Facebook omits from its list. You select the relevant Pages within Facebook; no integration deletion or technical setup is required. Existing working connections continue with their current permissions.

Pages are displayed by their name: no technical ID or secret is required. If you reload the page before confirming, Resume Page selection restores the available selection for its validity duration, exclusively with the BeAI account that initiated the connection.

The skill can be saved before connecting; without a configured Page, the bot will not receive Messenger conversations. Connection actions do not replace saving other settings. They preserve current inputs and do not trigger the floating Save reminder on their own.

The panel follows the same layout as WhatsApp: the steps and connection button are grouped in a card. Once connected, this card displays the Page, its status, and the controls to verify, refresh, and disconnect. Tracking timestamps are gathered directly below. On smaller screens, the buttons move beneath the connection details.

In the bot list, the Messenger logo next to the name indicates that the skill is active. The configuration panel allows you to check separately that the Page is connected and that its messages are being received.

Verify operation

Page connected confirms that the connection has been completed. Check connection tests access to the Page; this command does not send a test message to a customer and does not prove that a full conversation is working.

Message reception is reported separately. As long as no event has been received from the Page, the panel prompts you to confirm reception with a message. Send a new message to the Page from another Facebook account, then check that it appears in conversations. The Channel → Messenger filter helps locate these interactions.

The last verification and the last received message are displayed when available. An expired or revoked authorization requires Renew authorisation; it does not delete your existing conversations.

While the app is under Meta review, testing is restricted to accounts authorised for this app. Public access depends on Meta's approval of Messenger permissions; a successful test connection does not yet confirm public availability.

Limitations of this release

Written messages and quick reply buttons are supported. Your interlocutor can also send an attachment directly in Messenger:

Format Processing Limit
JPG, PNG, WebP or GIF photo or screenshot Text reading and visual analysis 10 MB, 40 million pixels
PDF document Content reading, including scanned pages 10 MB, 100 pages
DOCX or ODT Text reading; embedded images are not analysed 10 MB, 100 000 extracted characters
TXT, CSV or JSON in UTF-8 Textual content reading 100 000 bytes
Voice message MP3, MP4/M4A, OGG, WAV, FLAC, AAC or WebM Transcription followed by bot response 10 MB, 3 minutes
MP4, WebM or MOV video Video analysis and audible speech processing 10 MB, 1 minute

A message can contain at most 5 files and 18 MB in total. Unsupported formats, excessively long content, protected files, and expired links are not read: the history indicates the limit or failure. The bot may ask the user to resend the file or explain their request in writing, without fabricating its content.

The history displays images, audio/video players, documents, and downloads. Voice note transcripts appear beneath the player. If reading fails after download, the file remains viewable. During human takeover, new attachments are archived without AI analysis or response. Media processing during an active session follows standard message pricing; work already performed remains billable even if the subsequent response is interrupted.

Incoming Messenger audio calls are set up automatically when you select Connect this Page or Check connection. BeAI verifies the Page's eligibility with Meta, prepares incoming call reception, and links them to the bot voice. No server, SIP number, token, or network settings need to be entered by the user. Connecting does not import previous conversations or past attachments from your Page.

The status Incoming audio calls → Enabled confirms readiness. Then call your Page from Messenger to test an actual conversation. Not available for this Page means Meta does not allow this feature for this Page; messaging remains connected. Unavailable, retry the connection check indicates that setup or the voice engine is unavailable. BeAI does not make outbound Messenger calls and does not process video from calls.

Calls use the configured voice bot and its tools, the standard voice rate, and its options. Recording adheres to the bot setting. They appear under Channel → Messenger call, along with their history, summary, and detected language once closed. Access, supervision, and recording permissions are identical to those of other calls. Facebook identifiers are never presented as telephone numbers. The 24-hour text reply window does not control incoming call admission.

The bot only responds within 24 hours of the last genuine message received from the interlocutor. A read receipt, delivery receipt, or bot echo does not extend this period. Outside this window, no automated reply is sent.

Duplicates of the same message do not generate a new reply. If an outbound message returns an ambiguous result, its status remains uncertain and it is not automatically resent. A message accepted by Meta does not guarantee that it has been read by its recipient.

Instructions added by an administrator in supervision apply to the next Messenger user message. They do not trigger any unsolicited message to the interlocutor.

If the connection fails

  • Connection unavailable: your administrator must complete the Messenger activation for the platform. You do not need to enter any technical settings.
  • After activation by your administrator: refresh the bot form, then resume Connect Messenger. Platform activation does not select a Page for you: confirm the desired Page to complete the link.
  • Authorization denied or cancelled: start Connect Messenger again and check the requested permissions.
  • No Pages available: use Repair Page discovery in the Page selection. BeAI checks authorized Pages again, including those missing from Meta's usual list. This action preserves other connections and does not require you to enter any technical identifiers. Authorization remains valid for 15 minutes, with no extension. If the Page is still missing, use Review authorized Pages in Facebook, then Edit previous settings if prompted; check messaging permissions and the Facebook account used. BeAI cannot grant Facebook permissions on your behalf.
  • Selection expired: start the connection process again; the Page does not become active until its connection has been confirmed.
  • Facebook does not confirm the connection: retry Connect this Page in the same window. The selection remains available throughout its 15-minute validity period; a temporary failure does not require you to authenticate again. BeAI checks whether Facebook has already accepted the connection before repeating the operation.
  • Expired or revoked access: renew authorization. The confirmation button is disabled when the selection is no longer usable. Settings and history are preserved.

Reconfiguring an already connected Page

The Page selector displays existing connections: another bot, another connected app, already connected BeAI app, or unverified existing connection. These Pages remain visible. A Page without messaging permissions remains listed, but its connection is disabled.

To move a Page from another BeAI bot to this one, you must have permission to edit both bots. Select the Page, read the warning, and tick the confirmation box. The previous bot retains its connection until Meta verifies it; its link is then terminated and the new bot's link is activated in a single operation. History is preserved, and previous processes can no longer send replies using the moved connection. This takeover may terminate an ongoing call on the previous bot. The identity of an inaccessible bot or organisation is not disclosed.

For a third-party app, including a BeAI connection from another environment, the warning indicates that it is subscribed to the Page. You can confirm the connection to BeAI, but this subscription does not establish which app Meta uses as the default recipient. BeAI does not remove other apps and does not automatically alter message routing: check the conversation routing settings in Meta to prevent multiple replies. A previous link does not bypass missing Facebook permissions.

If the connection changes during selection, BeAI asks you to verify and confirm again. A temporary outage keeps the selection valid for its remaining duration; the previous bot is not disconnected prematurely.

The API returns connection_status, other_application_connected, takeover_required and the opaque takeover_token for each Page. To confirm, send confirm_takeover: true and this takeover_token in /onboarding/complete, along with onboarding_token and page_id. The server verifies the same permissions and the same confirmation as the console.

Switch or disconnect the Page

Use Disconnect Page, then confirm. This action removes the link from this bot and unlinks the BeAI app subscription; it does not delete your Page or other applications associated with it. Previous voice routing is restored once Meta confirms this action, and BeAI calls are stopped. Already recorded conversations remain accessible. To choose a different Page, disconnect the current Page first, then reconnect.

The same bot editing permissions and organisation scope apply to the console and to the public API. Under /api/v1/bots/{id}/skills/messenger, the operations /onboarding, /onboarding/start, /onboarding/discover, /onboarding/complete, /refresh, and /disconnect use the same validation. Meta secrets remain managed by the server.

If you remove the app from Meta or request the deletion of your Meta connection data, BeAI clears the permissions and Page selections associated with that Meta account. The bot stops responding using this connection. This action preserves your BeAI account and the organisation's conversation history; a new connection is required to resume Messenger. A request for full deletion of organisation data must go through your administrator.

Message formatting and contact identity

Responses are adapted for Messenger applications: short paragraphs, bulleted lists, and visible links. Markdown bold or heading markers are not sent as raw text. A long response is split at paragraph, line, or word boundaries, within the limit allowed by Meta.

BeAI retrieves the first and last name of the profile associated with the Page when Meta allows it. The name appears in active sessions and conversation details, as well as in the from_name API field. If Meta does not provide the profile, Messenger remains displayed; the technical session ID is not presented as a phone number.

Platform administrators can view tools in the history, with the same presentation as for calls and WhatsApp: name and status completed, in progress, or failed. The small i button opens details: arguments, result, and duration when this information has been retained. Secrets are masked. These lines are not sent to the contact; they remain restricted to platform administrators, including in the API and exports. Backfilling legacy conversations retrieves available details without replaying any tool; missing information is marked as unavailable.

Reminder and session end

WhatsApp, Messenger, and the website chat share the Close WhatsApp / Messenger / Website chat conversations settings in system settings, restricted to platform administrators. The API uses the same settings under history section whatsapp: PATCH /api/v1/system-settings/whatsapp with reminder_enabled, inactivity_reminder_minutes, and close_after_reminder_minutes.

After the first inactivity delay, BeAI simply asks "Do you have any other questions?", with no closing warning. The question is sent only once per session. A response naturally continues the same conversation; it cancels the ongoing expiry, and any subsequent inactivity closes after the sum of both delays, without further follow-ups. If there is no response to the question, the session closes silently after the second delay: no Session ended message is sent. With the default delays, the question arrives after 5 minutes, followed by closure 5 minutes later.

If the automatic question is disabled, silent closure occurs after the sum of the two delays. The question and the closure do not use AI and are not billed. No reminder is sent while a message is being processed or after expiry of Meta's 24-hour window. A transmission with an uncertain result is not repeated automatically. A response already awaiting processing prevents closure. After closure, a new message opens a new session. These settings do not affect voice calls.

At the end of the session, BeAI analyses the history to produce a summary, detect the language, and assess sentiment, just like for calls. Media actually played or read are included. The summary is written in the organisation's language and appears in the conversation details as well as in fields summary, language, and sentiment of GET /api/v1/conversations/{id}. The analysis may take a few minutes; an in-progress or failed status is displayed if necessary. A failure preserves the history and is subject to limited automatic retries. This analysis does not send any message to the contact. Incomplete legacy sessions are also upgraded without retroactive billing.

Shared timeouts never reactivate a conversation taken over by a person. During a human takeover, the summary covers the AI session up to its closure; subsequent human exchanges remain in the history.

Duration of Facebook authorisation

BeAI already obtains a long-lived Page token. This token may not have a technical expiry date, whereas Meta sets a deadline for data access. Meta access valid until indicates the earliest known deadline; it is not a guarantee of permanent access.

The connection is checked automatically every day. A check may detect an authorisation extended by Meta and update its date, but does not renew your Facebook consent. A warning appears in the 14 days before expiry, also exposed by connection.renewal_required in the API. Use Renew authorisation, authorise Facebook, then confirm the same Page. You can also verify access immediately with Check connection or POST /api/v1/bots/{id}/skills/messenger/refresh.

The connection can be revoked before its expiry, particularly if permissions on the Page or app permissions are removed. Temporary unavailability of Meta indicates a check to be retried; on its own, it does not disable a valid connection.

Reactions, read receipts, and typing indicator

Reactions received from Meta appear below the relevant message in the history and in conversation tracking. Replacing or removing them updates this indication. During an active AI session, a reaction from the contact is forwarded immediately to the bot along with the message concerned, including its replacement or removal. The bot interprets it in the context of the conversation; any response uses standard pricing. This activity resets the inactivity timer, without extending Meta's 24-hour response window. A session that has ended or been taken over by a team member remains in history mode, without AI responses or reaction processing fees. Only messages already stored in BeAI can be associated; the connection does not import prior reactions.

When BeAI processes an incoming message, it asks Messenger to mark it as read and display the typing indicator. These indications depend on Meta and the Messenger client used; their unavailability does not prevent the bot from responding.

A team member takes over the conversation

To allow the bot to request a team member in BeAI, add the Chat human handover skill. As soon as this request is made, the bot pauses and a message invites the contact to wait. Browser notifications repeat every 15 seconds until the request is handled or the configured timeout expires. If no one takes the request, an apology message announces the return to the bot. The team member's name is announced when they take over the conversation.

An automatic greeting sent by the Page before BeAI's first response is preserved in the history without interrupting the AI. Meta does not distinguish this greeting from human intervention. As soon as BeAI has replied, an external message triggers the human takeover described below.

When a message sent from your Page outside BeAI is received by the webhook, BeAI ends the AI session with the reason Human takeover. The intervention appears as a message from the Page team. Meta does not always provide the author's individual name: BeAI retains the text without inventing an identity.

Subsequent incoming and outgoing messages continue to populate this same history. The bot no longer responds, no longer runs tools, and no longer sends inactivity reminders. The Inactivity before return to bot setting of the Chat human handover skill accepts 1 to 10 080 minutes, with 60 minutes by default. Each team message, and each contact message during this takeover, resets this timer. The next incoming message received after a period without exchanges opens a new AI session; the previous one remains closed. Reactions alone do not reactivate a closed session. Meta's 24-hour response window remains a separate limitation. A setting change applies to the next activity. A response already transmitted to Meta at the moment of the takeover may still arrive; BeAI keeps a record of it.

To return the conversation to the bot, a user authorised to edit this bot can choose Reactivate AI on the next message in the conversation details. This command sends nothing: the next real incoming message will open a new session. The previous session remains closed.

The API exposes the same history via GET /api/v1/conversations/{id}: team messages use role: operator and reactions use reactions: [{"emoji":"👍","actor":"contact"}]. The reason is in channel_metadata.messenger.closed_reason: human_takeover. POST /api/v1/conversations/{id}/messenger/resume corresponds to reactivation, with the same editing permissions and scope. Text exports also preserve visible reactions.

Attachments are also available in GET /api/v1/conversations/{id}, under messages[].attachments (available, metadata.status, metadata.error, metadata.audio_transcript, or metadata.content_text). The download_url link uses GET /api/v1/conversations/attachments/{id}?download=1, with your API key and the same permissions as history. An unavailable file or one outside your scope returns 404. Temporary Meta links are never exposed.

The shared setting is available via GET/PATCH /api/v1/bots/{id}/skills/chat-human-takeover. The legacy field from /api/v1/bots/{id}/skills/messenger remains accepted as a backwards-compatibility alias:

{"inactivity_timeout_minutes": 60}

Permissions mirror those for editing the bot; an out-of-bounds value is rejected. History also exposes channel_metadata.messenger.human_last_activity_at, human_resume_at, and, following an automatic handover, ai_resume_reason: human_inactivity. Earlier pending events remain archived without being replayed to the bot.

The same automatic journey is available in the API: POST /api/v1/bots/{id}/skills/messenger/onboarding/complete and POST /api/v1/bots/{id}/skills/messenger/refresh. The connection status returns calling_status (enabled, ineligible, unavailable, disabled, or unknown) and calling_checked_at. Calls are channel: messenger_call conversations within the same /api/v1/conversations and /api/v1/runtime/conversations operations as other calls; voice connection secrets remain private.

Repair Page discovery via API

Following onboarding/discover, an empty list remains a valid selection for 15 minutes. POST /api/v1/bots/{id}/skills/messenger/onboarding/recheck uses the same onboarding_token:

{"onboarding_token": "selection-retournee-par-discover"}

The response contains data.signup, data.connection, and data.pending with the updated list and connection warnings. Only the user who initiated the connection, and who remains authorised to edit the bot, can repair discovery. An expired or revoked authorization must be restarted. The command does not connect any Page, does not extend the expiry time, and does not delete any application; then use onboarding/complete to confirm the Page. The GUI command applies the exact same checks.

If Meta requests an additional read permission, BeAI indicates this in the Page selection. Repair Page discovery then opens Facebook to request this permission and relaunch the search. Simply authorize the desired Page, without deleting any integration or entering a token. This additional read access depends on the access granted to the application by Meta; it is not required for existing Messenger connections that are already working.

In the API, connection.last_error: page_discovery_permission corresponds to this scenario. Re-run POST /api/v1/bots/{id}/skills/messenger/onboarding/start with {"repair_pages": true}, follow authorization_url, then resume discover and complete. When full discovery is configured on the server, the same read consent is requested upon a normal call to start, even without this field. Otherwise, the usual three Messenger permissions remain in use. A Facebook authorization cannot be renewed or expanded without the consent requested by Meta.

Documentation updated with the application