Connecting Viber to Bitrix24 Open Channels

Connecting Viber to Bitrix24 Open Channels

A client writes in Viber — the message goes into the void. The operator doesn't see the conversation, no lead is created, and the advertising budget is wasted. We encounter such situations constantly: Viber is often perceived as "just another channel," but its setup hides pitfalls — from an incorrect account type to outgoing message limitations. Our team of certified Bitrix24 specialists solves this problem turnkey: we guarantee stable connection and correct message routing.

How to connect Viber to Bitrix24 Open Channels?

Connecting Viber requires creating a Viber Public Account (formerly Public Chat) via the Viber partner portal. Important: this is not a personal account but a business account with an auth_token. After registration, obtain a token (string like 4bxxxxxxxx-xxxxxxxx) and enter it in the "Contact Center" → "Open Channels" → select the channel → "Channels" → "Viber". Bitrix24 automatically registers a webhook — no manual URL entry is required.

Typical mistake when creating an account

Many newcomers select the "Community" type instead of Bot — then the token is not accepted. The Viber Public Account for bots is exactly the Bot type. Additionally, the account must be verified (pass moderation), otherwise the webhook will not activate.

Why is Viber important for your business?

Viber is the primary messenger in Belarus (coverage >80%), Ukraine, and Moldova. If your audience is concentrated in these regions, without Viber you lose up to 80% of clients who prefer messenger communication. For the Russian audience, Telegram and WhatsApp are priorities, but for a multichannel strategy, Viber is mandatory.

What we do when setting up Viber integration

Our typical project includes five stages with a guaranteed result:

1. Audit the current open channel — check CRM integration settings, operator rights, lead creation mode.
2. Create a Viber Public Account — register the bot, go through verification, get the auth_token.
3. Connect in Bitrix24 — enter the token, set up a welcome message and subscription message.
4. Testing — send test messages from real devices, check delivery, statuses, lead creation.
5. Documentation and training — hand over instructions for operators, describe limitations (e.g., stickers not displayed).

Specific case breakdown

Recently, a client from Minsk reported that Viber messages weren't reaching operators. The reason: the bot account had not passed verification due to an incomplete description. We recreated the Public Account, specified the correct business activity description (Viber requirement), obtained the token, and reconnected. Additionally, we configured an auto-responder for greetings and phone number requests — now leads are created automatically. Resolution time: 2 hours. According to Viber documentation, the account must contain a real business description — Viber Bot API Guidelines.

When Viber integration is not justified

If your audience is Russia or distant foreign countries, focus on Telegram and WhatsApp. Viber only provides growth when messenger penetration is high. Also note: the operator cannot initiate a dialog — the client must write first. This Viber Bot API limitation cannot be bypassed. Our team sets up Viber integration 2 times faster than the market average, thanks to ready-made templates.

Timeline and what's included

Setting up Viber integration takes 1 to 3 business days depending on complexity. The cost includes:

• Creation and verification of Viber Public Account
• Connection to Bitrix24 Open Channel
• Configuration of auto-replies and greetings
• Testing from three devices
• Written instructions for operators

We have been working with Bitrix24 since its early versions, with over 100 similar integrations. We provide a 30-day guarantee on stable webhook operation. If you have problems with Viber, contact us for a free consultation. We will assess the project in one day and offer an optimal solution.

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.