We recently worked with a client whose Zoho SalesIQ Zobot performed flawlessly on their website, yet every message sent to their company’s Facebook Page through Meta Messenger vanished without a trace: the bot never replied, and no operator ever received the conversation. Meanwhile, the Zoho SalesIQ interface showed green lights across the board — as if everything were working perfectly. The real culprit turned out to be a small, poorly documented configuration trap, and the reason it’s so hard to diagnose is that it never surfaces as an error message anywhere in the Zoho UI.
In this article, we walk through the exact symptom, how we systematically ruled out the usual suspects, what the actual root cause was, and how you can avoid the same pitfall in your own Zoho ecosystem.
The Symptom
- The Zobot built in Zoho SalesIQ runs perfectly on the website.
- Messages sent to the company’s Facebook Page via Meta Messenger receive no response at all from the bot.
- In Settings > Channels > Facebook, the channel appears active, and the Page is listed as „Connected.”
- There is no „Token expired” warning, no red indicator, no error log entry.
- The messages don’t appear anywhere in the SalesIQ Conversations dashboard — not in Active, not in Missed, not in Closed.
That last point is the critical clue: if the message doesn’t appear anywhere in SalesIQ, it means the data handoff from Meta never started in the first place. The problem isn’t inside the bot or the routing logic — it’s at the integration layer itself.
What We Systematically Ruled Out
Before we found the real cause, we worked through the standard checklist. You should run through these in order too:
1. Is Meta Messenger enabled as a channel on the Zobot? In the Zobot editor, under the „Deploy on” / „Channels” section, you must explicitly tick the Facebook Messenger checkbox. If only Website was checked, the bot will never run on Messenger — no matter how perfect everything else is. → This was fine for us.
2. Brand and Department alignment. The Zobot is bound to a specific Brand + Department pair, and the Facebook Page is also assigned to a Brand. If these don’t match, the bot won’t pick up the Facebook chat. → This was also fine for us.
3. Unsupported card types in the bot flow. Meta Messenger doesn’t support several Zobot card types — for example, suggestions, drop-down lists, calendar, slider, smiley/star feedback, and even the „Go back” / „Restart” actions. If any of these appear in your flow, the bot can stall partway through. → Our flow used only single-select button cards, so this wasn’t the issue either.
4. „Token Authentication Expired” warning. SalesIQ normally displays a token-expiration message when the OAuth connection is broken. No such warning appeared in our case. And that was precisely the misleading part.
The Real Cause: Silent Authentication Break on Multi-Page Facebook Access
The client manages not one, but multiple Facebook Pages under the same Facebook account. When you connect a Facebook channel in Zoho SalesIQ, the Facebook OAuth screen presents you with a Page selection dialog asking:
„Which Pages and Instagram accounts do you want to use with [Zoho Social]?”
By default, Facebook pre-selects all managed Pages. Here’s the trap: if you uncheck any of them — whether because you think „I won’t need SalesIQ for that Page anyway,” or just by accident — Facebook issues a scoped access token that:
- appears to be a successful authentication to Zoho,
- actually does work for a while on the connected Page,
- but because of the permission inconsistency, the webhook subscription for Messenger events eventually gets silently deactivated,
- AND Zoho SalesIQ’s UI never signals this failure.
As a result, the Page remains „Connected” in SalesIQ, but Facebook stops sending message webhooks to Zoho. The messages are effectively lost between Meta and Zoho — invisible to both ends of your support operation. You only would find your messages inside your Meta Business Manager site.
Step-by-Step Solution
- In SalesIQ, navigate to: Settings → Channels → Facebook
- For the affected Page, click Disconnect / Remove.
- In a separate browser tab, open business.facebook.com and go to Business Settings → Business Integrations. Check whether „Zoho Social” (or a similar Zoho app) is listed. If yes, remove it from there as well. This ensures Facebook issues a fresh permission prompt instead of returning a cached response.
- Return to SalesIQ and click Add Channel → Facebook → Connect.
- On the Facebook OAuth screen, leave every managed Page checked — even the ones you don’t plan to use with SalesIQ.
- Under „Edit permissions,” verify that all requested permissions are granted (messaging, pages_manage_metadata, pages_messaging, etc.).
- After saving, select the specific Page you want to bind to SalesIQ and assign it to the correct Brand + Department.
- Send a test message from a separate Facebook profile to the Page’s Messenger, then check the SalesIQ Conversations dashboard — the message should now appear.
Prevention Checklist
If you’re managing multiple Facebook Pages under a single account, make these checks part of your routine:
- Always leave every Page ticked on the OAuth permission screen, if you plan to actively use one in SalesIQ.
- After every connection, send a test message to the Page’s Messenger and verify it arrives in SalesIQ. This is the only reliable confirmation.
- If the list of Pages, the admin roster, or Business Manager permissions change — re-verify the SalesIQ integration. Changes like these can trigger silent breakage.
- Periodically audit the Business Integrations list (business.facebook.com → Business Settings → Business Integrations) and remove expired or unused integrations.
- If you’re rolling out SalesIQ alongside Zoho Social on the same Facebook account, check that Page permissions aren’t conflicting — multiple Zoho services request access through the same underlying Facebook OAuth app.
Summary
If your Zoho SalesIQ Zobot runs on the website but not on Meta Messenger, and the SalesIQ UI reports zero issues, the first thing to suspect is the multi-page Facebook permission trap. The fix itself is straightforward, but the diagnosis is misleading because the Zoho interface doesn’t reflect what Meta is silently doing in the background.
This experience reinforces something we see across Zoho integrations in general: the „Connected” status is never enough on its own — the real proof of a working integration is actual traffic. A single test message tells you more than every green checkmark on the configuration screen.
Frequently Asked Questions
Why does the Zoho SalesIQ chatbot work on the website but not on Meta Messenger?
The three most common causes, in order: (1) Meta Messenger isn’t ticked as a deployment channel in the Zobot’s configuration — only Website is; (2) the bot’s Brand + Department pair doesn’t match the Brand assigned to the Facebook Page; (3) the Facebook OAuth connection was established with scoped permissions — typically because only some of the available Pages were selected on the permission screen — and the Messenger webhook subscription has since silently deactivated, while SalesIQ continues to display „Connected.” The third case is the hardest to catch, because Zoho never reports an error.
How can I verify whether Zoho SalesIQ is actually receiving messages from Meta Messenger?
The channel status shown on Settings > Channels > Facebook can be misleading. The only reliable test is this: send a message from a separate, independent Facebook profile to the Page’s Messenger, then check the SalesIQ Conversations view across the Active, Missed, and Closed tabs. If the message doesn’t appear in any of them, Meta isn’t forwarding data to Zoho at all — the problem is at the integration layer, not inside the bot or routing. If it does appear in Missed or Closed without an operator assignment, then incoming traffic works, but the routing or bot configuration is broken.
What does it mean when Zoho SalesIQ shows a Facebook Page as „Connected” but no messages arrive?
This is the classic „silent OAuth failure” pattern: the access token Facebook issued is technically valid, so Zoho accepts it and treats the channel as Connected. However, the token carries narrower permissions than the Messenger webhook subscription requires. During internal synchronization, Facebook detects the inconsistency and deactivates the webhook subscription — but the only trace of this lives on the Facebook App Dashboard side, not in the Zoho UI. The fix is to fully reconnect the integration while making sure every managed Facebook Page is granted access on the OAuth screen, even if you’ll only bind one of them to SalesIQ afterwards.