WhatsApp Messages Not Showing in Bitrix24 Open Lines? Work Through This Checklist

Yesterday we spent a whole morning on a message that "didn't arrive." It had arrived — it was sitting in the CRM widget, plain as day. It just never showed up in Bitrix24 Open Lines, and the reason turned out to be embarrassingly simple once we found it.

That morning produced an internal runbook. This is the public version: seven real causes for WhatsApp messages missing from Open Lines, in the order we now check them in production.

Understand this first: there are two pipelines, not one

Most WhatsApp–Bitrix24 integrations surface messages in two separate places:

1. The CRM widget — the WhatsApp chat panel embedded on a lead or deal. This reads from the integration's own message store.
2. Open Lines (Open Channels) — Bitrix24's native messaging queue, with operator distribution, CRM auto-contact creation, and the Contact Center inbox. Messages only get here if the integration forwards them through a connector bound to a specific Open Line.

These pipelines fail independently. A message can be delivered, stored, and visible in the widget while Open Lines stays completely silent — which is exactly the confusing state we debugged. If your widget shows messages, the WhatsApp side of your integration works; the problem lives in the forwarding step or the Open Line binding. That narrows the search enormously.

The checklist

1. Is an Open Line actually bound to this number?

The #1 cause, and the one that got us. Every WhatsApp connection needs an explicit link to an Open Line — and depending on how the connection was created, that link may never have been set. The nasty part: some admin UIs display a placeholder line name even when nothing is bound, so it can look connected while being connected to nothing.

Check it from both ends: your integration's settings should name the exact Open Line each number feeds, and that line should exist in Bitrix24 → Contact Center. If you can't tell which line a number feeds, assume it's none.

2. Is the connector active on that line?

A line can exist and be bound, but the connector on it can be inactive — usually after the line was edited or recreated. In Contact Center, open the line and confirm your WhatsApp connector is listed and enabled. Good integrations re-activate this automatically on the first message; older setups may need a manual toggle.

3. Was the Open Line deleted or archived?

Lines get "tidied up" by well-meaning admins more often than you'd think. If the bound line no longer exists, messages have nowhere to land — and most integrations fail silently rather than crash. Rebind to a live line.

4. Is the webhook subscription still intact?

Everything between WhatsApp and Bitrix24 starts with a webhook. On official API (Cloud API) numbers, your app must be subscribed to the WhatsApp Business Account — a subscription that can be lost after token changes, app review events, or number migrations. Symptom: nothing arrives anywhere, widget included. If both pipelines are dead, look here first, not at Bitrix.

5. Is the sender blocked? (The silent one)

A contact blocked on the WhatsApp Business API produces no webhook at all. No error, no log line — silence. If exactly one customer "stopped writing" while everyone else flows normally, check the block list before touching any settings. Someone on your team may have blocked them months ago. We wrote up the blocking rules and their surprises separately.

6. Is the message sitting in an unassigned queue?

Sometimes the message is in Open Lines — just not where you're looking. If the line's queue has no available operators, or routes to a department nobody checks, conversations pile up unassigned. Open the line's queue settings and check who's supposed to receive new dialogs, and whether "offline" operators are skipped.

7. On API numbers: are you inside the messaging rules?

Official-API numbers come with Meta's conversation rules: customers can always write in, but if your outbound suddenly fails — or an automation stopped replying — check the 24-hour customer-service window and your template quality status in WhatsApp Manager. Inbound problems are rarely caused by this; outbound problems usually are.

How our own debugging session actually went

For the curious — the real sequence from our incident: message visible in the widget (so inbound worked), nothing in Open Lines (so forwarding didn't), UI showing a line name that turned out to be a placeholder (cause #1 in disguise), and one detour through the block list (cause #5) triggered by an earlier blocking test on the same number. Total time: one morning. With this checklist: about ten minutes.

Two changes came out of it. WASync now creates and binds an Open Line automatically the moment a WhatsApp Business API number connects — so cause #1 can't happen to new connections — and the connector self-activates on the first message, covering cause #2.

The five-minute triage

---

Setting up from scratch instead of debugging? Our step-by-step guide to connecting WhatsApp to Bitrix24 covers both QR and official-API routes — with the Open Line wiring done for you.