FEATURES
Everything ChatBridge24 does
One WhatsApp number, worked by a team, with the conversations attached to the records they belong to. Every feature below runs on that one connected number, and every one of them has a page of its own — this page is the map.
The features, on one connected number
The Features menu lists these, and this is the same list.
-
Shared inbox
One number your whole team can work, with read state in both directions.
-
Audience segmentation
Audience filters, a CSV built in your own browser, and a build that stops rather than guesses.
-
Message templates
Build, submit and send every shape Meta approves, media headers included.
-
WhatsApp chatbot
Draw the conversation in blocks, test it, publish it — with limits that stop a bot becoming a bill.
-
Marketing campaigns
Each recipient is reserved once, before anything is sent, so a retry never sends twice.
What is on which plan
Two features, and sending through the API, are tiered. The rest are on every plan.
The shared inbox, message templates and contacts and audiences are on every plan. Chatbot scenarios and marketing campaigns run on WhatsApp Business API numbers: scenarios need Professional or above, and campaigns need Enterprise, as does sending approved templates from your own systems through the REST API. Nothing else is held back.
You pay per connected number, on its own plan, with its own renewal date. There is no charge per seat and no cap on how many people work a number, so adding a colleague to the inbox costs nothing. The plans and what each one includes: ChatBridge24 pricing.
With a CRM, or with none
Every feature above works on its own.
None of this needs a CRM. The inbox, the templates, the campaigns, the advanced WABA bot, the contacts and the API work on their own in the standalone WhatsApp workspace. If you do have a CRM, the same features keep working and the conversations reach your records too. Three ways to run it:
Bitrix24
The full ChatBridge24 app on the Bitrix24 Marketplace — Open Channels, a WhatsApp tab on CRM cards, automation steps
Any other CRM
For WhatsApp Business API numbers: a signed webhook for each new message, and on the Enterprise plan the REST API to send approved templates back
No CRM at all
The standalone workspace, with the inbox, templates, campaigns and the bot
ChatBridge24 is available as a full-featured app on the Bitrix24 Marketplace: read about the Bitrix24 WhatsApp integration and the Bitrix24 WhatsApp bot. Any other system connects through WhatsApp for any CRM, over the REST API and signed webhooks.
Also included
The REST API, and the tools your team works with.
WhatsApp REST API
The API serves WhatsApp Business API numbers. API keys, the read routes and the webhooks are on every plan; sending approved templates through the API is in the Enterprise plan. Keys are scoped and stored only as a hash. An idempotency key is required on every send, so a retry is answered with the first outcome rather than a second message to a real person. Webhooks are signed, retried for about eleven hours, and their destination is checked before every delivery so it cannot be pointed at a private address.
Team tools
Roles and teams, and assignment with real permissions. Staff check-ins are consent-based: one position, shared by tapping, with no background tracking of any kind.
Good to know before you choose
Two questions buyers ask, answered plainly.
- Conversations are one to one. A WhatsApp Business API number in ChatBridge24 works in one-to-one conversations between your number and each customer.
- Email is for your account; WhatsApp is for your customers. A standalone workspace receives email for the account itself — confirming your address at sign-up, resetting a password, inviting a colleague, and a warning to its administrators before a number’s Meta connection needs renewing. Conversation notifications reach you in the app and, on a Bitrix24 portal, in Bitrix24.
See it working
Connect one number and watch your own conversations arrive. Nothing to host, nothing to paste.
From the blog
Further reading on this subject.
Building an advanced WABA bot
How a WhatsApp chatbot should answer the repeated question and hand over cleanly.
Running a WhatsApp shared inbox
Ownership, internal notes and response times, without double replies.
Templates approved first time
The three categories and the rejection reasons that cost the most time.