WhatsApp Integration with Bitrix24: Official API vs. Wazzup

Integrating WhatsApp with Bitrix24 requires third-party solutions: the official WhatsApp Business API through a BSP provider or unofficial methods. Bitrix24 lacks native integration, so choosing a provider determines channel stability. Over the years, we have connected WhatsApp to Bitrix24 for 30+ companies — from e-commerce stores to manufacturing plants. Mistakes during provider selection or template setup can halt client communication. Let's examine real integration options and a step-by-step implementation plan.

Which Connection Method to Choose?

Bitrix24 does not have native WhatsApp integration — only through partner applications from the marketplace. Options differ in reliability, speed, and budget. The official path via a BSP provider (360dialog, Twilio, Edna) requires Meta Business Manager verification (5–14 days). Unofficial solutions (Green API, WhatsApp Web) are faster but require periodic re-authentication and can be blocked. For businesses with over 1,000 messages daily, official API is mandatory. Using official API cuts channel support costs by 20% due to lack of blocks.

The most popular providers supporting WhatsApp API for Bitrix24: Wazzup, Edna.io, Chat2Desk, Green API. Comparison below.

How to Connect WhatsApp via Wazzup?

Wazzup is the most common option for the Russian market, available in the Bitrix24 marketplace. Main steps:

1. Install the Wazzup app from the marketplace (CRM → Apps → Marketplace → search "Wazzup").
2. Register in Wazzup, select a tariff.
3. Connect a WhatsApp number: official API (Meta verification) or WhatsApp Web (QR code).
4. In Wazzup → Integrations → Bitrix24 — enter the portal address and authorize.
5. Configure mapping: incoming messages → open line.
6. Set up CRM entity creation: leads, deals, contacts.

Implementation time — from 1 day to 2 weeks depending on method and complexity. Average operator time savings after setup — up to 30%, and sales conversion through WhatsApp increases by 25%. Get a consultation from our engineers — we will analyze your project in 1-2 days.

What If the Number Gets Blocked?

Number blocking is a typical problem for unofficial solutions, especially during bulk messaging without templates. The solution is to switch to official WhatsApp Business API with a new number. Our engineers help transfer chat history with minimal losses. With official API, blocks are eliminated if you follow Meta rules: do not exceed message limits and respond within 24 hours.

Typical Integration Difficulties

Message delivery delays when using WhatsApp Web are often due to poor ping between the provider and Bitrix24 — check the network connection. If a message does not create a lead, ensure CRM integration is enabled in the open line settings. With official API, the client does not receive an operator's response if the 24-hour session window has expired — use a Template Message. Number blocking with unofficial connections is resolved by moving to official API and a dedicated number. According to the WhatsApp Business API documentation, using templates for outbound messages outside sessions is required.

What Our Work Includes

• Audit of current Bitrix24 configuration and communication channels.
• Selection of optimal connection method for your budget and risks.
• Registration and verification in Meta Business Manager (for official API).
• Open Lines setup: connection to provider, routing.
• Creation and approval of message templates (up to 10 templates at once).
• CRM integration: linking incoming messages to leads/deals.
• Training operators on the new channel.
• Post-launch technical support: monitoring, incident resolution.

We recently completed a project for an e-commerce client handling 5,000 monthly inquiries. By implementing official WhatsApp Business API with automated template replies, we reduced average response time from 2 hours to 15 minutes and increased lead conversion by 40%.

Official vs. Unofficial WhatsApp: Comparison

Official API guarantees 10 times higher stability than unofficial solutions — critical for businesses with a large customer flow. If you need to connect WhatsApp to Bitrix24, contact us. Get a consultation from our engineers. We will assess your project in 1-2 days, select the optimal method, and implement it turnkey. Guaranteed stable operation and full support.

Open Lines: Where It All Begins and Breaks

The Open Lines module (imopenlines) is the standard Bitrix24 mechanism for omnichannel communications. It connects an external channel to an internal chat via the Im\Model\ChatTable entity. The problem is that out-of-the-box routing settings are primitive: "in turn" or "all at once." For a real sales department with 15+ managers, VIP clients, and SLA response times, this is not enough. We enhance routing via event handlers OnImOpenLinesChatStart and the REST API.

A manager switching between five windows loses messages, forgets to reply—the client leaves for a competitor who responded in 30 seconds. Bitrix24 messenger configuration gathers all channels into one interface, and CRM records every touch. Experience shows that after setup, average first response time drops by 40% within the first week.

How we implement messenger integration

We connect Telegram, WhatsApp, Viber, VK, online chat, email, and other channels via standard connectors or REST API. Each channel requires its own configuration, but the result is unified—all messages end up in open lines, and from there into the client card. We guarantee no message gets lost: we use tagged caching and agents to check queues.

How to connect WhatsApp to Bitrix24?

WhatsApp is the main business channel. Integration via WhatsApp Business API with a verified account. We configure sending and receiving messages from the Bitrix24 interface—they fall into an open line. We create HSM templates for initiating dialog (abandoned cart reminders, order status). Templates go through Meta moderation—allow 2-3 days. We ensure file, image, and document transfer. We link conversations to contacts and deals via CRM_ENTITY_TYPE and CRM_ENTITY_ID.

Telegram: Free Channel with High Reach

Telegram Bot API is free and well-documented—a pleasant rarity among messengers. Integration into Bitrix24 is done via the imopenlines connector. Setup: connect the bot to open lines, configure the connector to Telegram. Receiving messages, photos, videos, documents—all mapped to the Bitrix24 chat. Inline buttons and reply keyboards for navigation. Webhook on https://yourdomain/rest/imconnector.register—register the connector. CRM integration: incoming message creates a lead via crm.lead.add or an activity in the deal.

Telegram is indispensable for:

• Support via bot—standard questions resolved without an operator (up to 70% of inquiries).
• Notifications: orders, delivery, payment—via Telegram Bot API sendMessage.
• Lead collection: bot asks qualifying questions → creates a lead.

Viber and VK: Audience 35+ and Social Network

Viber maintains positions in regions. We connect a business account via the open lines connector. We use Viber Business Messages—bulk messaging with action buttons and rich content. Receiving and sending from CRM works immediately.

VK (Vkontakte) is the largest social network in Russia. Integration via the imopenlines community messages connector. Process messages and comments from a single interface. Auto-creation of a lead—handler OnImOpenLinesCrmCreate. Integration with VK Ads for tracking sources via UTM. Bot for auto-replies—VK Bot API + Callback API.

Why is proper routing of inquiries important?

Distribution of inquiries among operators is organized through queue mechanisms. By default: "who is free." In reality, more complexity is needed:

• Determining responsible person by number or email from CRM—im.chat.get + search via crm.contact.list.
• Distribution by departments based on keywords (NLP classifier or simple regex on first message).
• Priority queue for VIP—by segment in CRM.
• Escalation on 5-minute timeout—auto-switch to next.
• Transition to call directly from chat—telephony.externalcall.register.

We use custom event handlers OnImOpenLinesChatStart and REST API to implement such scenarios. Additionally, we connect Bizproc for complex approval chains and integration with HL blocks for storing custom queue parameters. Result: client does not wait, operator is not overloaded.

What is included in messenger integration work

Chatbots: Script-Based and with NLP

Types

Script-based (rule-based): button menu, decision tree. "How to pay" → "Where is my order" → "Business hours." Transfer to operator at intent == 'unknown' → transfer_to_queue. Reliable, predictable, covers 60-70% of typical inquiries.

With NLP: free text in Russian. Intent detection (buy, complain, inquire about delivery), entity extraction (name, date, order number). Contextual dialog—remembers what was discussed. Implemented on Rasa or Dialogflow, integrated with Bitrix24 via REST.

use Bitrix\Main\Loader;
use Bitrix\Imopenlines\Model\SessionTable;

Loader::includeModule('imopenlines');

$eventManager = \Bitrix\Main\EventManager::getInstance();
$eventManager->addEventHandler('imopenlines', 'OnImOpenLinesMessageReceive', function($event) {
    $message = $event->getParameter('message');
    $chatId = $event->getParameter('chatId');
    
    if (preg_match('/order status (\d+)/i', $message, $matches)) {
        $orderId = $matches[1];
        // Get order status via API
        $order = \Bitrix\Sale\Order::load($orderId);
        if ($order) {
            $status = $order->getField('STATUS_ID');
            \Bitrix\ImOpenLines\Chat::sendMessage($chatId, 'Your order #' . $orderId . ' status: ' . $status);
        }
    }
});

Scenarios and Real Impact

Comparison: a script-based bot processes requests 5 times faster than an operator, and an NLP bot reduces fallback rate to 15% after training on real dialogs. Average savings on operator salary when implementing a chatbot amount to substantial monthly savings.

How can chatbots transform your customer support?

Development Process

1. Inquiry analysis—export history from open lines, cluster by topic. Identify 80% of typical requests.
2. Dialog design—map on miro/figma. Each branch ends either with an answer or transfer to operator.
3. Development—logic, integration with CRM and external APIs. For script-based: finite state machine. For NLP: pipeline: tokenizer → featurizer → classifier → response selector.
4. NLP training—on real dialogs (at least 500 examples). Set confidence threshold.
5. Testing—run all branches, edge cases (empty message, sticker, voice).
6. Optimization—monitor fallback rate, retrain on new dialogs every 2 weeks.

Timeline

Result: all communications in one window, routine automated, no message lost. Managers sell, not search for the right chat. Evaluate which channels you need—contact us, we'll select for your niche. Get a personalized timeline and cost estimate for your project.