Everything in ChatBridge24
One WhatsApp number, worked by a team, with the conversations attached to the records they belong to. Everything below is in the product today; two of these have a page of their own and the rest are described here until they earn one.
With a page of its own
The two most people come for.
Shared inbox
Assignment with real permissions, internal notes with @mentions, saved replies, labels and views, read state in both directions, and the 24-hour window shown before you type rather than after Meta refuses.
Message templates
Every shape Meta supports — media headers, carousels, buttons that copy a code or open a link with a value in it, authentication, limited-time offers — built, submitted, tracked through review and sent with your own values.
Also in the product
Described here until each earns a page.
Marketing campaigns
An audience from your CRM, a spreadsheet, a pasted list or your own contacts; per-campaign pacing and sending hours; a frequency cap; and a do-not-contact list the build refuses to send around. Each recipient is claimed in one database statement before any money moves, so a retried batch cannot charge twice or send twice. In the top tier.
Chatbot scenarios
A scenario you draw: ask a question, branch on the answer, set a value, wait, or hand the conversation to a person. Every run writes a transcript showing which branch it took and why a step declined, which is the only place that is recorded. In Pro and above.
Bitrix24
Open Channels, a WhatsApp tab on the Lead, Deal, Contact and Company cards and on Smart Processes, two automation steps, record creation you configure, and Click-to-WhatsApp attribution into CRM fields. The full page.
REST API and outgoing webhooks
Scoped API keys, 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. Webhooks are signed, retried for about eleven hours, and their destination is checked so it cannot be pointed at a private address.
Contacts and audiences
Every contact a number has ever spoken to, with eighteen filters, a CSV export built in your browser, and a block list that follows a person across all of your numbers. An audience is a saved filter or a fixed list, and a build that cannot read the opt-out list refuses rather than sending to it.
Team tools
Roles and teams, assignment rules, an overdue-reply reminder posted into your own internal WhatsApp group with the responsible colleague mentioned, and consent-based staff check-ins — one position, shared by tapping, with no background tracking of any kind.
What is deliberately not here
Two absences worth knowing about.
Group chats, on the official platform. Meta’s Cloud API has no group messaging at all. That is an absence in the interface rather than a setting, so no vendor on the official transport has it. The QR-linked option does.
Email. There is no email delivery in the product today, so there are no email notifications, no emailed reports and no newsletter. Notifications reach you in the app and, on a Bitrix24 portal, in Bitrix24. We would rather say so than ship a setting that silently does nothing.
See it working
Connect one number and watch your own conversations arrive. Nothing to host, nothing to paste.