Switching from Wazzup24

We are putting this at the top rather than the bottom, because a comparison page that cannot name a case against itself is not worth reading.

• You want several messengers in one place. Wazzup24 sells WhatsApp, Telegram, a Telegram bot, Instagram and Viber as channels you buy individually. If your customers reach you on Telegram and Instagram as much as on WhatsApp and you want all of it in the same CRM, that is what they are built for and we are not. ChatBridge24 is WhatsApp only, deliberately.
• You are not on Bitrix24. They support several CRMs. Almost everything specific we can say about our product is about its depth inside Bitrix24, and that depth is worth nothing to you if you are on something else.
• You want to try it this afternoon with no conversation. They publish a short free trial and a self-serve flow. Our official-platform onboarding needs your own Meta business authorisation, which is a few more minutes and one Facebook sign-in — that is the cost of the account being yours.

Read their current feature list and pricing on wazzup24.com.

We checked. Wazzup24’s prices are not in its pages’ HTML — they are rendered by JavaScript, so there is nothing stable to cite and no way to show you a dated quotation that will still be honest in a month. Several vendors in this category do the same thing.

So: read their price on their own pricing page, on the day you are deciding. What we will tell you is our model, in full, in the page source, with no figure hidden behind a sales call:

• $50, $80 or $119 per connected WhatsApp number per month, depending on whether you want the chatbot and marketing campaigns.
• No seat charge and no per-user minimum. There is no seat count in the product to bill for.
• No per-conversation or per-message fee from us, and no markup on Meta’s. On the official platform your WhatsApp Business Account is yours and Meta bills you directly on it.

The full price list. The one thing to compare carefully is the unit: a price "per channel" and a price "per connected number" are different things once you have more than one number or more than one messenger.

Rather than claim anything about their implementation, here is ours, named:

• Open Channels, plus a tab on the record. Conversations land in the Open Channel you bind the number to, and a WhatsApp tab appears on the Lead, Deal, Contact and Company cards and on Smart Process items — so an agent can answer without leaving the record.
• Two automation steps. "Send a WhatsApp message" and "Send an approved template", available on leads, deals, contacts, companies and Smart Processes. The template step carries up to thirty values, each one filled from a field you pick on the record, inside the message itself rather than in a column of numbered boxes.
• Every automation outcome on the record’s timeline. Including the refusals — "this person has no mobile number on their profile", "the 24-hour window has closed" — written where the person who can fix it is looking.
• Record creation you configure. A first inbound message can create a Lead, a Contact or a Smart Process item, with a field map you set, carrying both the phone number and the messenger identifier so Open Lines binds to that record instead of making its own.
• Click-to-WhatsApp attribution into CRM fields. If the customer arrived from an advert, the advert identifier, headline and link can be written into fields you choose.
• A template engine that submits every shape Meta supports — media headers, carousels, URL buttons with a variable, copy-code buttons, authentication templates, limited-time offers — and tracks each one through Meta’s review. How that works.
• A public REST API and outgoing webhooks, with scoped keys and a required idempotency key on every send, so a retried request cannot charge twice or send twice.
• Both transports. The official Cloud API, or a QR-linked device for the cases that need group chats. When to pick each.

Your number. If it is already on the official WhatsApp Business Platform, moving it between providers is a Meta operation: the number is registered into the destination WhatsApp Business Account, and we support that migration path directly. You will need two-step verification turned off at the current provider first, and a new PIN. If it is a QR-linked number, you scan a code and it is done.

Your approved templates. Templates belong to a WhatsApp Business Account, not to a provider. If the account is yours, they travel with it; if the account belonged to the provider, they do not, and you will be re-submitting them — which is a strong argument for the account being yours whoever you use.

Your history. Conversations already written into your Bitrix24 are Bitrix24 records and stay exactly where they are. We do not import a competitor’s message archive, and we will say so rather than imply otherwise.

Your automation rules. These do not transfer. A rule that calls another application’s step has to be pointed at ours — which is a few minutes per rule in the Bitrix24 designer and the one genuinely annoying part of any switch. There is no way around it, for anybody, in either direction.