Bitrix Messenger Integration Module for Telegram, WhatsApp, Viber

Customers open notifications from messengers 5–10 times more often than email. A Telegram bot for an online store or WhatsApp broadcast increases repeat purchase conversion by 30–40%. Additionally, integrating the Telegram API is 3 times simpler than the WhatsApp Cloud API and requires no provider costs. The module reduces support costs by 20–30% and pays for itself in 1–2 months. We are a team of certified Bitrix developers with many years of experience — we create modules that seamlessly connect Telegram, WhatsApp, Viber, and VK to your catalog events. Our modules handle up to 10,000 messages per day without failures. Order a turnkey module — get a ready-to-use solution with documentation, user linking, and message templates in 5–25 days. Contact us for a consultation and project evaluation.

This module addresses the main pain point: customers no longer miss order status notifications, reducing support load and increasing loyalty.

Which messengers are supported?

• Telegram — via Bot API (simple, free, reliable).
• WhatsApp platform — via official Meta Cloud API or third-party providers (WABA360, GreenAPI, Chat-API).
• VK Notify — notifications via VK Mini Apps API.
• Viber — via Viber REST API.

Telegram is implemented first — excellent documentation, stable API, reasonable limits (30 messages per second per bot). Telegram is 3 times cheaper to operate than WhatsApp, as per official documentation.

Why prefer Telegram over WhatsApp?

Telegram's Bot API is not only free but also handles up to 30 messages per second, compared to WhatsApp's 1 message per second per phone number. This makes Telegram 30 times more efficient for high-volume notifications. Additionally, Telegram audience coverage among active buyers is 40–50%, and integration takes 1–2 days — far quicker than WhatsApp.

How is the module architecture designed?

local/modules/vendor.messenger/
├── lib/
│   ├── Channel/
│   │   ├── TelegramChannel.php
│   │   ├── WhatsappChannel.php
│   │   └── ChannelInterface.php
│   ├── NotificationRouter.php   # Select channel for sending
│   ├── TemplateEngine.php       # Message templating
│   └── SubscriptionManager.php  # Subscription management
└── install/db/install.sql

Table b_messenger_subscription — user-channel linking:

How does Telegram account linking work?

1. User clicks “Link Telegram” in the personal account.
2. System generates a one-time code and link https://t.me/yourbot?start=CODE123.
3. User goes to the bot, sends /start CODE123.
4. Bot via Webhook receives the message, finds the record by code in b_messenger_link_token table, and saves chat_id in b_messenger_subscription.

The entire process takes 2–3 seconds.

CREATE TABLE b_messenger_link_token (
    TOKEN varchar(32) NOT NULL,
    USER_ID int NOT NULL,
    CHANNEL varchar(50) NOT NULL,
    EXPIRES_AT datetime NOT NULL,
    PRIMARY KEY (TOKEN)
);

Webhook for incoming messages

Telegram sends updates to a URL like /api/telegram/webhook/. In Bitrix, this is handled via a custom handler:

// local/api/telegram/webhook/index.php
$update = json_decode(file_get_contents('php://input'), true);

if (isset($update['message'])) {
    \Vendor\Messenger\TelegramWebhookHandler::handle($update);
}

The handler parses the incoming message: if it's /start TOKEN — links the account. If it's a text request — passes it to chat logic (if a support chatbot is implemented).

Sending notifications

Notifications are tied to Bitrix events via mail events or directly through handlers:

\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'sale',
    'OnSaleStatusOrder',
    [NotificationRouter::class, 'onOrderStatusChange']
);

The method onOrderStatusChange determines the appropriate channel for the user, composes a message from a template, and sends it. For Telegram:

$response = \Bitrix\Main\Web\HttpClient::post(
    "https://api.telegram.org/bot{$token}/sendMessage",
    json_encode([
        'chat_id'    => $chatId,
        'text'       => $message,
        'parse_mode' => 'HTML',
    ]),
    ['Content-Type' => 'application/json']
);

Telegram Bot API documentation: https://core.telegram.org/bots/api

Message templates: structure and configuration

Message templates for each event and each channel are stored in the b_messenger_template table. Variables like {{order_id}}, {{status}}, {{tracking_number}} are supported. Template editing is available in the administrative section.

For Telegram, HTML formatting is supported (<b>, <i>, <a>). For WhatsApp, only asterisks for bold (*text*).

Send queue

Sending to messengers is done asynchronously via a queue in the b_messenger_queue table. This protects against blocking the main process during network delays of messenger APIs and allows retrying on temporary errors:

A cron job processes the queue every minute, retrying failed attempts with exponential backoff.

What's included in the solution

• Analysis of your business processes and channel selection.
• Architecture design: tables, handlers, templates.
• Development of integration with Telegram and WhatsApp (basic).
• Configuration of send queue with retries.
• Creation of 5–7 notification templates for your events (order, payment, shipment).
• Operational documentation and training for your administrator.
• 30 days of support after launch.
• Project management and communication via Slack/Telegram.

How long does development take?

Pricing

Our pricing is tailored to your scope and requirements. Contact us for a free estimate.

The module delivers a rapid return on investment by reducing support costs and boosting repeat purchases.

Our experience

With over 10 years in Bitrix development and more than 100 successful projects, including 50+ custom modules for e-commerce and messaging, we deliver robust, scalable solutions trusted by businesses of all sizes.

Get a consultation for your project — we’ll estimate the scope and suggest the optimal solution. We guarantee stable module operation under load and prompt support.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.