> For the complete documentation index, see [llms.txt](https://docs.klink.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klink.cloud/getting-started/setup-channels/facebook-messenger.md).

# Facebook Messenger

Engage with your audience directly on Klink.cloud using Facebook Messenger. Seamlessly connect and communicate with customers on this widely used platform. Klink.cloud makes it easy for you to manage conversations, respond promptly, and deliver exceptional customer service—all within the convenience of Facebook Messenger.

{% hint style="info" %}
Follow below tutorials to connect Facebook Messenger
{% endhint %}

{% content-ref url="/pages/SypQUTKv2fwi7xbFHBrq" %}
[Connect to Facebook Messenger](/getting-started/setup-channels/facebook-messenger/connect-to-facebook-messenger.md)
{% endcontent-ref %}

{% content-ref url="/pages/SvcdkgXQ4bLRbmlKV3jV" %}
[Primary Routing Setup (Facebook & Instagram)](/getting-started/setup-channels/facebook-messenger/primary-routing-setup-facebook-and-instagram.md)
{% endcontent-ref %}

### FAQ

<details>

<summary>What is 24 Hour Messaging Window Policy by Meta</summary>

Facebook Messenger has a policy called the "24-hour rule" that applies to businesses interacting with users.

The 24-hour messaging window in Facebook Messenger is a rule aimed at preventing businesses from spamming users. Here's how it works:

* **Businesses have 24 hours to respond to users with any kind of message, including promotional content.** This window opens whenever a user initiates contact through a message, clicks a button within a Messenger ad, or replies to a previous message from the business.
* **Any interaction from the user resets the 24-hour window.** So if a user replies to your message within 24 hours, the business can continue the conversation free

</details>

<details>

<summary>How to Facebook Message reply after 24 Hour</summary>

#### After the 24-Hour Window

Once the 24-hour window closes, sending promotional or regular messages is restricted. Businesses can only send further messages using specific tags approved by Facebook, which include:

* **Post-Purchase Update**: Information about a user's recent transaction.
* **Account Update**: Important notifications about a user's account status.
* **Event Update**: Updates about events for which the user has registered interest.

![](https://420146782-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqqwHJh6YA4uvzfFRLnoR%2Fuploads%2FoHrUWdFp661UrqNBKQIh%2FScreen%20Shot%202024-04-12%20at%2012.26.00%20AM.png?alt=media\&token=82c75f44-712d-4231-962d-aa2a7f6ecf39)

\
These tags ensure that messages sent after the 24-hour window are necessary and non-promotional.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.klink.cloud/getting-started/setup-channels/facebook-messenger.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
