Add Facebook Messenger fundamentals guide

_config.yml

@@ -108,6 +108,7 @@ collections:
       - whatsapp-channel-fundamentals.md
       - sms-channel-fundamentals.md
       - instagram-dm-fundamentals.md
+      - facebook-messenger-fundamentals.md
       - message-editor-overview.md
       - message-editor-basics.md
       - share-a-location.md

_i18n/en/integrations/setup-overview.md

@@ -36,11 +36,14 @@ If you sell through WhatsApp, connect the commerce platform first and then conne
 
 Connect Instagram when customers should be able to start direct-message conversations that reach your Inbox, playbooks, routes, or AI agents. Instagram uses its own direct login and is separate from Facebook Messenger.
 
+Connect Messenger when customers should be able to message your Facebook Page and reach your Inbox, routes, or compatible playbooks. Messenger uses Facebook login and requires access to the intended Page and Meta Business account.
+
 Keep reading:
 
 - [Connect WhatsApp]({% link _integrations/connect-whatsapp.md %})
 - [Connect your catalog to WhatsApp]({% link _integrations/connect-catalog-to-whatsapp.md %})
 - [Instagram DM fundamentals]({% link _numbers/instagram-dm-fundamentals.md %})
+- [Facebook Messenger fundamentals]({% link _numbers/facebook-messenger-fundamentals.md %})
 
 ### 4. Add capture and checkout tools
 

_i18n/en/numbers/facebook-messenger-fundamentals.md

@@ -0,0 +1,186 @@
+Connect Facebook Messenger when customers use your Facebook Page to ask about products, purchases, or support. Hellotext can bring eligible Page conversations into the Inbox so your team, routes, and compatible playbooks can respond with shared context.
+
+Messenger in Hellotext is tied to a Facebook Page. It is separate from personal Messenger conversations and from the Instagram integration.
+
+## What Facebook Messenger is best for
+
+Use Messenger for:
+
+- Product and support questions sent to your Facebook Page.
+- One-to-one replies from the Inbox during an eligible conversation.
+- Supported quick replies, buttons, and postback interactions.
+- Routes that send messages, ask questions, branch, or assign an active conversation.
+- Playbooks that explicitly support Messenger.
+- Keeping Page conversation history available to the team in Hellotext.
+
+A Page follower is not automatically reachable in Messenger. The customer must first create an eligible interaction with the Page before Hellotext can reply through that Page-scoped identity.
+
+## Know the current automation scope
+
+Messenger does not currently have the same product coverage as WhatsApp or Instagram DM:
+
+- It is not a delivery option in the campaign creator.
+- It is not currently selectable under **Incoming channels** for a custom AI agent.
+- Routes and playbooks can use Messenger only when that specific flow supports it.
+
+Do not assume a playbook supports Messenger because it works on another channel. Review the channels exposed by that playbook and test the complete Messenger flow before launch.
+
+## Before you connect Messenger
+
+Confirm that:
+
+- Your business has the Facebook Page you want customers to message.
+- You have a Facebook account with administrator access to the company's Meta Business Suite and the Page.
+- You can authorize the permissions Hellotext requests for Page messaging and webhooks.
+- The Page is not already connected to another Hellotext business.
+- Your team knows who should receive and answer Messenger conversations in the Inbox.
+
+Hellotext currently connects one Facebook Page per Hellotext business. A Facebook Page can also be connected to only one Hellotext business at a time.
+
+Facebook Messenger and Instagram are separate integrations in Hellotext. Connecting one does not connect the other.
+
+## Connect your Facebook Page
+
+1. In Hellotext, go to **Settings → Integrations**.
+2. Find **Messenger** in the communication integrations and select it.
+3. Review and confirm the connection requirements.
+4. Select **Log in with Facebook**.
+5. Sign in with the Facebook account that has access to the intended Meta Business account and Page.
+6. Select the correct Page and authorize the requested permissions.
+7. Return to Hellotext and confirm that the Page appears as connected.
+8. From a personal Facebook account, send a test message to the Page and confirm that it reaches the Inbox.
+
+If Hellotext reports that the Page belongs to another business, remove it from that Hellotext business before trying again.
+
+## How Messenger conversations begin
+
+A customer starts an eligible conversation by messaging the connected Facebook Page or using a supported Messenger interaction. Hellotext then:
+
+1. Receives the Page-scoped Messenger identity and supported message content.
+2. Finds or creates the corresponding customer profile.
+3. Adds that Messenger identity to the customer profile.
+4. Opens or updates the private conversation in the Inbox.
+5. Makes the conversation available to the team, route, or compatible playbook handling it.
+
+The identity is scoped to the connected Facebook Page. It is not a general Facebook identifier that can be reused with another Page.
+
+Messages sent directly as the connected Page can also synchronize into the Hellotext conversation. This keeps the Inbox history aligned with supported activity sent from Messenger or Meta's own Page tools.
+
+## Understand the messaging window
+
+Meta applies a standard 24-hour messaging window after the customer messages the Page. A new eligible customer message opens the window again. Meta controls final delivery eligibility even when the conversation remains visible in Hellotext.
+
+Hellotext does not currently provide a campaign or approved utility-template flow for reopening a closed Messenger conversation. When the standard window is no longer available, wait for the customer to write again or continue through another channel only when that customer is eligible there.
+
+Do not use another channel to bypass consent or a closed Messenger conversation. Each destination must satisfy its own reachability and subscription rules.
+
+## Messages and interactions Hellotext supports
+
+Hellotext can process supported Messenger activity such as:
+
+- Text messages of up to 2,000 characters.
+- Compatible images, GIFs, audio, video, and PDF attachments.
+- Voice messages and stickers.
+- Replies to previous messages.
+- Quick replies and postback button interactions.
+- Buttons and product cards created by compatible playbooks or message flows.
+- Delivery, read, edit, and reaction activity when Meta provides it.
+
+Public Facebook comments, Page posts, and conversations sent to a personal Facebook profile are not ordinary Messenger conversations for the connected Page in Hellotext. Test the exact customer entry point you plan to use.
+
+## Manage Messenger conversations in the Inbox
+
+Messenger conversations use the same Inbox ownership model as other supported customer channels. Your team can:
+
+- Reply from an eligible Messenger conversation.
+- Assign or reassign the conversation to a teammate or team.
+- Add internal context without sending it to the customer.
+- Apply response rules for Messenger when the plan supports channel-specific rules.
+- Close the conversation when no further action is needed.
+- Continue work when a new eligible customer message arrives.
+
+Content available on WhatsApp, Instagram, or Webchat may not have the same presentation or compatibility in Messenger. Preview and test the Messenger version of attachments, buttons, and product cards you intend to use.
+
+Keep reading: [Inbox and conversations overview]({% link _team/inbox-overview.md %}), [Assign conversations]({% link _team/assigning-conversations.md %}), and [Response times and response rules]({% link _team/understanding-response-times.md %}).
+
+## Use routes and compatible playbooks
+
+Routes can use Messenger while the customer, Page, and conversation remain eligible. Test message and question steps, branches, replies, and Assignment steps, including what should happen when the Messenger window closes or the integration becomes unavailable.
+
+Some playbooks can consider Messenger when the customer already has a reachable Page-scoped identity and that playbook includes Messenger support. The playbook still evaluates channel availability, message compatibility, and provider eligibility before sending.
+
+Custom AI agents do not currently expose Messenger in their incoming-channel selector. Do not promise AI handling for a Messenger conversation unless the exact playbook or route you configured supports it and you verified it end to end.
+
+Keep reading: [Getting started with routes]({% link _journeys/getting-started-with-journeys.md %}) and [How Hellotext decides whether a playbook can send]({% link _journeys/how-hellotext-decides-whether-a-playbook-can-send.md %}).
+
+## Customer profiles and consent
+
+An incoming Messenger conversation can add a Page-scoped Messenger identity to a customer profile. That identity is specific to the connected Facebook Page and should not be treated as a phone number, WhatsApp subscription, or permission to send marketing through another channel.
+
+If the same customer exists under another profile, review the data before merging profiles. Preserve the correct conversation, identifiers, properties, and purchase history.
+
+Respect unsubscribe and block requests. A customer writing to the Page does not provide unlimited permission for future outbound messages.
+
+Keep reading: [Customer profiles]({% link _audience/customer-profiles.md %}) and [Who can I message? Consent and subscriber status]({% link _audience/consent-and-subscriber-status.md %}).
+
+## Pricing and usage
+
+Facebook Messenger messages are included in Hellotext's non-SMS messaging calculation. The variable amount becomes the Hellotext charge only when it is higher than the plan minimum, performance fee, and SMS amount for the billing period.
+
+Review [Fair-use message policy]({% link _billing/fair-use-message-policy.md %}) for the current published rate and calculation.
+
+## Reauthorize or replace the connection
+
+Messenger can stop receiving or sending messages if Page access changes, permissions are removed, the Page is disconnected from the Meta Business account, or Meta invalidates the authorization.
+
+First confirm that the Facebook account still has administrator access to the correct Meta Business account and Page. If Hellotext must be authorized again:
+
+1. Go to **Settings → Integrations**.
+2. Find the connected Messenger Page.
+3. Remove the Messenger integration.
+4. Select **Messenger** again and repeat the Facebook login.
+5. Select the same Page and authorize the requested permissions.
+6. Send a new test message from a personal Facebook account.
+
+Removing the integration disables its Messenger channel. Confirm that you have the correct Page access before removing it, and contact support when the correct recovery path is unclear.
+
+## Troubleshoot a missing or failed Messenger message
+
+If an incoming message does not appear:
+
+- Confirm that the correct Facebook Page is connected in Hellotext.
+- Send a private message to the Page from a personal Facebook account.
+- Check that the interaction is a Messenger message rather than a public comment, Page post, personal-profile message, or Instagram DM.
+- Confirm that the Facebook account and Hellotext still have the required Page permissions.
+- Check whether the customer profile or conversation is blocked.
+
+If a reply does not send:
+
+- Confirm that the customer messaged the Page within the standard messaging window.
+- Check that the Messenger integration and channel are active.
+- Review the exact failure reason before retrying.
+- Confirm that the text, attachment type, and attachment size are compatible with Messenger.
+- Avoid repeated retries when Meta has rejected the Page, destination, or conversation state.
+
+See [Why a message did not send]({% link _troubleshooting-deliverability/why-a-message-did-not-send.md %}) for the shared delivery checklist.
+
+## First Messenger launch checklist
+
+Before relying on Facebook Messenger, confirm that:
+
+1. The intended Facebook Page is connected to the correct Hellotext business.
+2. A test Page message creates or updates the correct customer profile.
+3. The conversation appears in the Inbox with the correct Messenger identity.
+4. The right teammate, team, route, or compatible playbook receives the conversation.
+5. Text, attachments, replies, buttons, and product cards you plan to use were tested.
+6. Assignment reaches the correct person or team.
+7. Your team understands the 24-hour window and reauthorization process.
+
+## Related guides
+
+- [Messaging channels overview]({% link _numbers/messaging-overview.md %})
+- [Instagram DM fundamentals]({% link _numbers/instagram-dm-fundamentals.md %})
+- [Inbox and conversations overview]({% link _team/inbox-overview.md %})
+- [Conversation lifecycle in Inbox]({% link _team/conversation-lifecycle.md %})
+- [Playbooks and automation overview]({% link _journeys/playbooks-overview.md %})
+- [Getting started with routes]({% link _journeys/getting-started-with-journeys.md %})

_i18n/en/numbers/messaging-overview.md

@@ -10,9 +10,11 @@ Use **WhatsApp** when your customers already prefer chat, when you want richer c
 
 Use **Instagram DM** when customers discover your business on Instagram and initiate product or support conversations there.
 
-Many businesses use several channels: SMS for reach, WhatsApp for richer outbound and conversational experiences, and Instagram for customer-initiated conversations. Campaigns, routes, and playbooks can use the channels differently, so confirm how channel selection works for the experience you are launching.
+Use **Facebook Messenger** when customers contact your Facebook Page and your team needs those conversations in the Inbox.
 
-Keep reading: [SMS channel fundamentals]({% link _numbers/sms-channel-fundamentals.md %}), [WhatsApp channel fundamentals]({% link _numbers/whatsapp-channel-fundamentals.md %}), and [Instagram DM fundamentals]({% link _numbers/instagram-dm-fundamentals.md %}).
+Many businesses use several channels: SMS for reach, WhatsApp for richer outbound and conversational experiences, and Instagram or Messenger for customer-initiated social conversations. Campaigns, routes, and playbooks can use the channels differently, so confirm how channel selection works for the experience you are launching.
+
+Keep reading: [SMS channel fundamentals]({% link _numbers/sms-channel-fundamentals.md %}), [WhatsApp channel fundamentals]({% link _numbers/whatsapp-channel-fundamentals.md %}), [Instagram DM fundamentals]({% link _numbers/instagram-dm-fundamentals.md %}), and [Facebook Messenger fundamentals]({% link _numbers/facebook-messenger-fundamentals.md %}).
 
 ## SMS sender options
 
@@ -36,6 +38,7 @@ Before launching a campaign, playbook, or route, confirm that:
 - [SMS channel fundamentals]({% link _numbers/sms-channel-fundamentals.md %})
 - [WhatsApp channel fundamentals]({% link _numbers/whatsapp-channel-fundamentals.md %})
 - [Instagram DM fundamentals]({% link _numbers/instagram-dm-fundamentals.md %})
+- [Facebook Messenger fundamentals]({% link _numbers/facebook-messenger-fundamentals.md %})
 - [Connect WhatsApp]({% link _integrations/connect-whatsapp.md %})
 - [Who can I message? Consent and subscriber status]({% link _audience/consent-and-subscriber-status.md %})
 - [Capture tools overview]({% link _captures/capture-overview.md %})

_i18n/en/team/inbox-overview.md

@@ -62,7 +62,7 @@ Keep reading: [Message editor overview]({% link _numbers/message-editor-overview
 
 For website conversations, also review [Webchat Widget playbook]({% link _captures/webchat-widget-playbook.md %}).
 
-For social conversations, review [Instagram DM fundamentals]({% link _numbers/instagram-dm-fundamentals.md %}).
+For social conversations, review [Instagram DM fundamentals]({% link _numbers/instagram-dm-fundamentals.md %}) and [Facebook Messenger fundamentals]({% link _numbers/facebook-messenger-fundamentals.md %}).
 
 For satisfaction after closed conversations, also review [CSAT Pulse playbook]({% link _journeys/csat-pulse-playbook.md %}).
 

_i18n/es/integrations/setup-overview.md

@@ -36,11 +36,14 @@ Si vendes por WhatsApp, conecta primero tu plataforma de eCommerce y después co
 
 Conecta Instagram cuando los clientes deban poder iniciar conversaciones por mensaje directo que lleguen a tu Inbox, playbooks, rutas o agentes de IA. Instagram usa su propio inicio de sesión directo y es una integración separada de Facebook Messenger.
 
+Conecta Messenger cuando los clientes deban poder escribir a tu página de Facebook y llegar a tu Inbox, rutas o playbooks compatibles. Messenger usa el inicio de sesión de Facebook y requiere acceso a la página y cuenta de Meta Business correctas.
+
 Sigue leyendo:
 
 - [Conecta WhatsApp]({% link _integrations/connect-whatsapp.md %})
 - [Conecta tu catálogo a WhatsApp]({% link _integrations/connect-catalog-to-whatsapp.md %})
 - [Fundamentos de Instagram DM]({% link _numbers/instagram-dm-fundamentals.md %})
+- [Fundamentos de Facebook Messenger]({% link _numbers/facebook-messenger-fundamentals.md %})
 
 ### 4. Agrega herramientas de captura y checkout