WhatsApp-to-CRM integration services: how to choose
Almost every service in this category solves half the problem: it delivers messenger conversations into a CRM and stops there. A customer asks for a call back — the call happens in another system. You need the official WhatsApp — a middleman console and a second bill appear. You add a third channel — the bill triples. AISAR closes those three gaps inside one plan — here is what that means in practice and how to choose a service for your situation.
Updated: 8 September 2026. By the AISAR team
Choose AISAR if
- customers ask for call backs: SIP telephony, a softphone and call recordings live in the same window as the conversation — most services in the category have no calls at all;
- you need the official WhatsApp without an extra link: we connect WABA directly through the Meta Cloud API, with no middleman console or billing;
- you have more than one channel: the Business plan at 20 000 ₸ includes 3 channels and 5 users, rather than one channel with every next one sold separately;
- the team works shifts: our own inbox with assignment, roles, an "unassigned" filter and quality scores, rather than a chat inside someone else’s CRM.
Take a connector if
- everything really happens inside Bitrix24 or amoCRM, there are one or two operators and a separate window would only get in the way;
- you need one channel on a minimal budget: with a single number, per-channel billing is usually cheaper than a bundle;
- calls already run in a separate telephony system and a split conversation history suits you.
Three things almost nobody has
These are what trips teams up a month after connecting, when the service is chosen and moving is too late.
Calls in the same window
A customer who wrote on WhatsApp usually wants a call back. Without telephony inside the service the call moves to another system and the customer history splits in two: conversations here, recordings there. In AISAR it is one card: a SIP number, a browser softphone, recording, a missed-calls log and click-to-call from a Bitrix24 card.
Among the compared: AISAR and Chat2Desk. ChatApp, Radist.Online and Teletype have none; Wazzup and Pact.im do not state it publicly.
WABA directly, with no middleman
The official WhatsApp can come straight from Meta or through a BSP middleman. In the second case you get its console, its bill and its template rules, and moving the number means switching partners. AISAR works with the Meta Cloud API directly: one console, one bill, templates on our side.
Directly — AISAR. Wazzup goes through Gupshup and ODCEM, Pact.im and Radist.Online through 360dialog, ChatApp does not disclose its provider.
Channels in the plan, not one by one
Per-channel billing looks cheap on the first number and stops being cheap on the third: WhatsApp, the official WABA and Instagram are three times the price. The Business plan includes 3 channels and 5 users for 20 000 ₸, so the bill does not grow every time you add another way to reach you.
Bundled — AISAR. Wazzup, Radist.Online and ChatApp bill per channel or number, Teletype per operator.
Three kinds of service that share one name
Listicles put them in one list, though they are different products, and picking the wrong kind costs differently.
CRM connectors
No workspace of their own: the service delivers conversations into Bitrix24 or amoCRM, and the operator works where the deals already are. Cheap to start and invisible to a team that lives in the CRM. The flip side is that you inherit the CRM chat: shifts, assignment and per-operator analytics are whatever the CRM provides.
Platforms with their own inbox
The service has an operator workspace of its own: every channel in one window, assignment, roles, quick replies, statistics. The CRM does not go away — it syncs. This is what teams pick once there are more than two or three operators and response discipline matters, not just "messages landing on the card".
Bot and funnel builders
Here the scenario is the product and the inbox is an accessory. Good when the job is automated sequences and qualification, bad when humans still handle most of the questions: live conversation is secondary in these tools.
What you pay for: three models
Comparing plan prices is pointless until you know what is being counted. There are three models, and with the same number on the price list the yearly total differs several-fold.
Per channel or number
The most common connector model. Connect WhatsApp — one plan; add the official WABA and Instagram — you pay three times. Do the maths for the number of channels you actually need, not for the first one.
Per operator
The price grows with the team while channels are usually unlimited. Good with one or two operators and many channels, bad with a large shift.
Channels and users bundled in the plan
The plan includes several channels and several employees, with add-ons beyond the bundle. Ours is the Business plan: 20 000 ₸ a month for 3 channels and 5 users. This model is predictable once you have more than one channel.
We do not quote competitors’ amounts here: price lists change more often than this page. Verified, dated figures per service are on the comparison pages below.
Calls and chats in one window
This is where we differ from the category the most. A customer who wrote on WhatsApp often asks for a call back — and if the service cannot call, the conversation moves to a separate telephony system and the customer history splits in two. In AISAR the call lives on the same card as the chat.
Your own number and SIP trunk
A landline or mobile number from your telecom operator connects over SIP — no need to change the number your customers already know. Trunks with registration and by IP are both supported.
Softphone in the browser and on a phone
An operator takes and makes calls right in the AISAR tab, with nothing to install. Whoever prefers it works from the same account in Zoiper on a phone or on a desk SIP handset.
Recording, missed calls and review
Calls are recorded and sit on the call card next to the conversation. Missed ones are collected in a separate log tab with a personal unreviewed counter — the call-back queue is visible in the morning, not in a month-end report.
Click-to-call from a Bitrix24 card
If the team works in Bitrix24, a call starts by clicking the number on a lead or deal card while the conversation itself runs through the operator’s softphone. The call result comes back into the portal.
Telephony is part of the Business plan and needs no separate product: the same roles, permissions and statistics as the chats.
The official WhatsApp: directly or through a middleman
The official WhatsApp Business API can be connected directly through the Meta Cloud API, or through a BSP middleman. The practical difference: a middleman brings its own console, its own billing and its own template rules, and moving the number to another service means switching partners inside that middleman.
Choosing for your situation
Four forks that settle the choice faster than a feature table.
Everything happens in Bitrix24 or amoCRM, one to three operators
Take a connector: a separate window only adds context switching. Look at the price for the number of channels you need and whether the service supports your CRM edition.
There is a sales or support team working shifts
You need a platform with its own inbox: assignment, roles, an "unassigned" filter, quality scores. A CRM chat either lacks this or shapes it around deals rather than a queue of enquiries.
Customers often ask for a call back
Rule out services without telephony straight away, or you end up with two systems and a torn history: conversations in one, call recordings in another. Check specifics rather than the word "calls": SIP, softphone, recording, click-to-call from the CRM card.
You need the official WhatsApp with broadcasts and templates
Ask the service who provides its WABA. "Directly through Meta" means one console and one bill; naming a BSP means a second console, a second bill and dependence on its rules. No answer at all is also an answer.
Frequently asked questions
The things usually discovered after connecting.
A connector delivers conversations into your CRM and has no workspace of its own — the operator sits in Bitrix24 or amoCRM. A platform provides its own inbox with assignment, roles and statistics, and syncs with the CRM. The first is cheaper and simpler; the second is needed once a team, not one person, handles enquiries.
Yes, almost every service can connect a personal number by QR code — fast and with no moderation. But such a connection has no official templates or mass broadcasts, and WhatsApp itself may block the number for unusual behaviour. Broadcasts and guaranteed delivery require the official WhatsApp Business API.
It depends on the billing model, not on a line in the price list. With per-channel billing, count the price for every channel you need; with per-operator billing, for the whole shift. Our Business plan is 20 000 ₸ a month and includes 3 channels and 5 users; competitors’ dated prices are on the individual comparison pages.
A BSP is a Meta partner through which a service gets access to the WhatsApp Business API. If the service works via a BSP, you get its console and its bill on top of the service subscription, and templates and limits follow the middleman’s rules. A direct Meta Cloud API connection removes that link.
A personal number on QR reconnects freely: disconnect in one service, scan the code in another. The official WABA is harder — the number is tied to a Meta account and the move goes through a partner change. If both services sit on the same BSP, it is a partner switch in its console; if not, it is a full number migration.
Inbox, CRM and telephony. One plan.
Connect WhatsApp, Telegram and Instagram Business in minutes — and compare it yourself. 7 days free, no card required.
Try AISAR