Add an AI chatbot to Facebook Messenger

People message your Facebook Page the moment they have a question, and they expect an answer now, not next business day. Every hour a message sits unread is a lead going cold. Connect Messenger to Evoriqa and the AI answers every message itself — the same knowledge-grounded pipeline that runs your website widget — and the reply goes straight back out in the Messenger thread. When someone asks for a real person (or you run out of message credits), the thread flips to your team's wait queue with its real arrival time and fires a desktop alert so nothing slips. Want a human on every thread instead? A per-channel AI replies switch turns Messenger human-first, and the AI copilot drafts each reply for your team to review and send.

Here's how to connect Evoriqa to your Page's Messenger inbox.

What you'll need

• A Evoriqa workspace (create one free, no credit card)
• A trained chatbot in your account
• A Facebook Page you're an admin of
• A Facebook developer account at developers.facebook.com

Step 1: Have your agent trained

Before it can help with anything, your agent needs to know your business. Crawl your website, upload your docs, or paste in your FAQs so the answers it sends come from real content instead of guesses. Our training guide walks through it step by step. Do this once and the same knowledge backs every channel you connect it to.

Step 2: Create a Meta app and add Messenger

Go to developers.facebook.com and open the My Apps dashboard.

1. 1Click Create App and choose the Business app type.
2. 2Give it a name and create the app.
3. 3From the product list, find Messenger and click Set up.
4. 4Open Messenger → Settings (newer dashboards call it Messenger API settings), scroll to Access Tokens, and connect the Facebook Page you want the agent to answer for.
5. 5Click Generate token and approve the permission prompt. Copy the token. That's your Page access token.
6. 6Open app Settings → Basic and copy the App Secret too. Meta signs every incoming message with it, and the channel won't accept messages without it.

Keep this tab open, you'll come back to the Webhooks section in a moment.

Step 3: Connect the channel in Evoriqa

Open Evoriqa, go to the chatbot you want to handle Messenger, and open its Channels tab. (Channels are set per chatbot. There's no separate global Channels page.) Pick Messenger and fill in three values:

1. 1Meta App Secret: from app → Settings → Basic.
2. 2Verify token: any string you invent. Meta uses it once to prove the webhook is really yours, so pick something and keep it handy; you'll paste the same value into Meta next.
3. 3Page access token: the token you generated for your Page.

Click connect and Evoriqa shows you the Callback URL. Leave this tab open alongside your developer tab.

Step 4: Point Meta's webhook at Evoriqa

Back in your Meta app, in Messenger settings, find the Webhooks section.

1. 1Click Add Callback URL (or Edit).
2. 2Paste the Callback URL from Evoriqa and the verify token you chose.
3. 3Click Verify and Save. Meta calls the URL and confirms the token matches.
4. 4In the webhook fields list, subscribe to messages. (Leave message_echoes off. It just sends your own replies back at you.)
5. 5Then subscribe your Page. In the same Webhooks panel, find your Page in the list, click Add subscriptions, and tick messages there as well.

That last step is the one almost everyone misses. Step 4 subscribes your *app*; step 5 subscribes your *Page*. Do only the first and the webhook shows a reassuring green Verified badge while Meta never sends you a single message.

Step 5: Give yourself a role on the app

A brand-new Meta app is in Development mode, and in that mode Meta only delivers messages from people who have a role on the app or the Page. Message it from an unrelated personal account and nothing arrives — no error, no log, just silence.

In the app dashboard open App roles → Roles and add the Facebook account you'll test with as Administrator, Developer, or Tester (accept the invite from that account). If you're testing as the Page admin, you're already covered.

Step 6: Send a real test message

Open your Facebook Page from your test account and send it a message, something you know your knowledge base covers.

The AI answers in seconds, right in the Messenger thread, grounded in your knowledge base. No one on your team had to touch it. Open your Evoriqa shared inbox and the conversation is there, tagged as Messenger, with the AI's reply already logged. To see a handoff, reply again asking for a person: the thread flips to needing a human and joins the wait queue, and if you've turned on desktop alerts your browser pings you the moment it does. A teammate opens it, replies from the inbox, and it goes straight back out in the Messenger thread.

Nothing in the inbox? The channel row shows a small health chip that tells you which half is broken. No messages yet means Meta isn't calling at all. Recheck the Page subscription in step 4 and your app role in step 5. Signature rejected means Meta *is* calling and the App Secret on the channel is wrong, so re-copy it from Settings → Basic.

Desktop alerts are opt-in per browser. Turn them on from the inbox header or Settings → Notifications.

Before you go live

Everything above works while your app is in Development mode, which is perfect for testing with your own team. To let real customers message the Page, Meta requires you to switch the app to Live and request Advanced Access to the pages_messaging permission through App Review, which includes verifying your business. It's Meta's process, not ours, and it's worth starting early. Approval takes days, not minutes.

Take it further

• Every message is auto-tagged with intent, sentiment, and a lead score, so your team triages the thread at a glance.
• Repeat customers merge into one contact timeline across every channel, so context follows them into Messenger.
• The AI answers in Messenger just like it does in your website widget, always within your plan's message quota, credit balance, and spend cap.
• Prefer your team on every thread? Turn off AI replies for the channel and each message waits in the inbox, with an AI copilot drafting a suggested reply and writing handoff summaries.
• Connect the same shared inbox to WhatsApp, Instagram, SMS, and your website: one knowledge base, every channel.
• Running this for a client? Everything is fully white-label, so it reads as their brand, not ours.

Your Facebook Page messages now get answered the moment they arrive, with the AI handling the routine ones and your team stepping in the instant a customer asks. See what else it can do on the Messenger channel page, or create your workspace free and run it against your own Page.