ChatBridge24

ON THE BITRIX24 MARKETPLACE

Bitrix24 WhatsApp, in Open Channels and the CRM

ChatBridge24 is available as a full-featured app on the Bitrix24 Marketplace. With the Bitrix24 WhatsApp integration, customer messages arrive in your Open Channels, your team replies from Bitrix24, and each conversation appears in a WhatsApp tab on the Lead, Deal, Contact or Company it belongs to, and on the items of the Smart Processes you choose.

Install from the Bitrix24 Marketplace

Last verified 2026-11-13 — against the shipped application.

Lead · Layla Mansour CRM record Layla Mansour NEW LEAD PHONE +971 50 ●●● ●●●● SOURCE WhatsApp — click-to-message ad AD Marina Walk · 2-bed · October RESPONSIBLE Karim A. STAGE Viewing booked CREATED BY CHATBRIDGE24 On her first message · 09:14 Overview Timeline WhatsApp Files REPLY WINDOW 23:41 Hi — is the 2-bedroom on Marina Walk still available? 09:14 It is. I can hold a viewing for you tomorrow at 4pm if that suits. 09:16 That would be great, thank you. 09:17 APPROVED TEMPLATE Your viewing is confirmed for Tue 4:00pm. Reply RESCHEDULE to move it. 09:18 Write a reply… SEND EVERY MESSAGE IS ON THE RECORD · NOTHING TO COPY ACROSS
The WhatsApp tab on a CRM record: the lead fields written on a first message, the thread inside the record, the reply window and the composer. A drawing of the product, not a photograph — the names and numbers are invented.

What it does inside Bitrix24

Six parts, in one app.

01

Open Channels

The app registers itself as an Open Channels connector, so a WhatsApp number binds to an Open Channel and behaves like any other channel: the queue routes the chat, an operator answers in the Bitrix24 messenger, and delivery and read ticks come back the same way.

02

A WhatsApp tab on the CRM record

A tab is placed on the Lead, Deal, Contact and Company cards, and on the cards of each Smart Process you switch it on for. An agent reads the thread and replies without leaving the record they are looking at.

03

Automation steps

A step for the automation designer on leads, deals, contacts, companies and Smart Processes that sends an approved template from a WhatsApp Business API number, with its values filled from the record’s own fields.

04

Records created from a first message

A first inbound message can create the record itself — a Lead, a Contact or a Smart Process item, your choice. A Lead or a Contact carries the messenger identifier and, where WhatsApp shows it, the phone number, so Open Channels uses that record rather than creating a second one.

05

Where the lead came from

When a first message creates a Lead or a Contact, the campaign and form answers in it are written into the record’s Comment field, and its utm values into Bitrix24’s own UTM fields; a record that already existed has the details added to its comment. The details of a Click-to-WhatsApp ad can be mapped to fields you choose.

06

The Bitrix24 advanced bot

It answers customers on your WhatsApp Business API numbers with scenarios you draw in blocks — buttons, questions that check the answer, conditions, business hours and a hand-off to your team. It is included in the Professional and Enterprise plans, and the Bitrix24 WhatsApp bot page describes it in full.

The details that decide it

Written from the inside.

Much of what matters in a WhatsApp CRM integration does not show in a feature list, so here are the details that keep conversations and records in order.

  • A conversation keeps one Bitrix24 chat for life. WhatsApp is moving one-to-one chats onto private identifiers, so the address of a contact can change in the middle of a conversation. The chat key is pinned at the first delivery and never rewritten, so a customer’s history stays in one Bitrix24 chat.
  • The automation step reports back, every time. Every outcome — sent, failed, or refused with a reason — releases the step and writes an entry on the record’s timeline, so an automation rule never waits on a message.
  • A refusal is on the record, not in a log. If a rule could not send — no mobile number on the responsible person’s profile, a step with fewer value boxes than its template needs, the 24-hour window closed — the reason appears in the CRM timeline where the person who can fix it will see it.
  • Messages wait while you finish setting up. Inbound messages that cannot yet be delivered — because no Open Channel is bound, or a Bitrix24 authorisation has expired — are held rather than failed, and are delivered once the condition is fixed, for up to 30 days.
  • Delivery and read ticks come back. When WhatsApp reports a message delivered or read, the tick appears on the operator’s message in Bitrix24.

Installing it

Three steps, inside your own portal.

01

Install the app

From the Bitrix24 Marketplace, into the portal you want it in. It runs inside Bitrix24; there is nothing to host and nothing to maintain, and it registers what it needs by itself.

02

Connect a number

Sign in to Meta in its own sign-up flow and pick your business and phone number — no tokens to paste.

03

Bind it to an Open Channel

Choose which Open Channel the number’s conversations should land in, so your existing queue and routing rules apply. Open Channels is optional: the app also works as a WhatsApp inbox with the automation steps.

What appears in your portal

Named, so nothing is a surprise.

Installing the app registers everything the integration needs, automatically. All of it is checked and restored afterwards — including after the app is updated:

  • an Open Channels connector, which appears as a channel in Contact Center;
  • a WhatsApp tab on the Lead, Deal, Contact and Company cards, and on the cards of each Smart Process an administrator switches it on for;
  • the automation step that sends an approved template from a WhatsApp Business API number;
  • event handlers, so a reply typed in Bitrix24 reaches the customer on WhatsApp.

Uninstalling removes them. Messages already delivered stay in your Bitrix24, because they are Bitrix24 records; what we hold is deleted on the schedule in the privacy policy.

What it costs

Per connected number.

On the official platform, from $50 per connected number per month, with your whole team included and no seat charge. The Bitrix24 app is part of every plan, with no connector fee. Meta’s per-message charges are billed to you by Meta at its own rates, and we add nothing to them. The full price list: ChatBridge24 pricing.

Questions

From real installs.

Does it work on a self-hosted Bitrix24?

Yes. The app runs the same way on Bitrix24 On-Premise as on a cloud portal; a self-hosted portal issues its own authorisation tokens and the integration follows them.

Do I have to use Open Channels?

No, and this is worth knowing before you set it up. Many portals use the app as a WhatsApp inbox and an automation sender and never bind an Open Channel at all. Binding one later delivers the messages that are still waiting for it.

Can several numbers go to different Open Channels?

Yes. Each connected number binds to the Open Channel you choose, so a sales number and a support number can route to different queues.

Does the WhatsApp tab appear on Smart Process cards?

Yes, on the Smart Processes you choose. Some Smart Processes are separate lead pipelines and others are only storage, so an administrator switches the tab on for each one in the app’s CRM settings and points it at that process’s name and phone fields; fields called Name and Phone are matched for you. The tab then finds the conversation by the phone number on the item and by the contacts linked to it.

Will the CRM tab appear twice?

No. Before it adds a tab, the app reads what is already registered in your portal, and it replaces an existing tab rather than adding a second one.

What happens to an automation rule if the message cannot be sent?

The step is released with the reason, and the reason is written to the record’s timeline. The rule never hangs.

Can an automation rule send to the responsible person instead of the customer?

Yes — point the step’s "Send to" at any phone field on the record, including the responsible person’s mobile. It only ever sends where you point it: there is no fallback that guesses, because guessing is how an internal notice reaches a prospect.

Read on

The bot, the app’s own listing, and what it costs.

Bitrix24 WhatsApp bot

The advanced bot inside the app: scenarios you draw, a Test chat, and versions you publish.

ChatBridge24 on the Bitrix24 Marketplace

The app’s listing on Bitrix24, where an administrator installs it into your portal.

ChatBridge24 pricing

Per connected number, per month. Every plan includes the Bitrix24 app and your whole team.

WhatsApp Business API pricing

Meta’s per-message pricing since July 2025, and the 1,000 free service messages a month every number gets from 1 October 2026.

Put WhatsApp in your Bitrix24

It installs into your own portal, registers everything it needs, and keeps your conversations in your CRM.

From the blog

Further reading on this subject.

The best WhatsApp for Bitrix24

Ten things to check before you choose a WhatsApp setup for your portal.

Building a bot in Bitrix24, step by step

Plan, draw, test and publish a bot that hands over to your Open Channels team.

WhatsApp marketing from your Bitrix24 CRM

Campaigns to CRM segments, automation by deal stage and UTM lead tracking.

What gets created in your Bitrix24 portal

The connector, the CRM tabs, the robot and the event handlers, by name.