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.