Skip to content

Parallel Bot Connection

Hotline allows connecting to bots in parallel with other systems — bot constructors, custom scripts or external services. Almost any bot can be connected to Hotline in parallel mode and get instant ability to work with its message flow through a working topic group.

Difference between Hotline sessions and Telegram Bot API

Sending a bot token to connect to Hotline does not terminate the existing session, as happens when using the standard Telegram Bot API. Both sessions in this case work simultaneously, complementing each other's functionality.

How It Works

With parallel connection, Hotline continues to perform its main role — relays messages from users of the connected bot to the backend group and back, from operators on the backend group side to users (more details in capabilities overview).

Hotline also sees outgoing messages from the parallel session from the connected bot to users and can display them in the group as intercepted (intercepted messages).

Parallel connection does not impose any restrictions on using any available Hotline parameters, which opens up many usage options for such bundles.

At the same time, the parallel connected bot can:

  • Show its own welcome (with media or buttons)
  • Process its commands and button presses from users
  • Parse incoming messages from users
  • Provide webapp interface and much more

Flexible topic activation

Using the PRIVATE_KEYWORDS parameter, you can configure topic activation in the backend group only after receiving a special command from the user (for example: "call operator", "help", /help, /chat).

Parallel connection is safe

The parallel session will not disconnect and will not affect your bot's existing session in any way. Your bot will still be able to see all incoming messages from users and callbacks from button presses. At the same time, your bot will not see outgoing messages through the Hotline session.

Main Usage Scenarios

  • Contacting Operators

    Ability to contact a support operator directly from the bot with your functionality (buttons, webapps, scenarios, forms).

  • AI Bot Control

    Convenient interface for monitoring AI bot correspondence with users, with the ability for operator intervention in dialogue.

  • Backup System

    Preserving message flow through the bot and ability to communicate through Hotline in case of main tool failures.

  • Mobile Access

    Quick responses on behalf of the bot from any device via Telegram, when working with a large CRM is inconvenient.

  • Broadcasts and Segmentation

    Using Hotline's broadcast system in parallel with your main communication system.

  • Functionality Extension

    Adding buttons, menus, WebApp or additional message parsing to Hotline's basic functionality.

Implementation Example

Our demonstration bot shows parallel connection work:

  • Launch @demobuttons_bot and send it some interesting message

  • This bot is connected by its token in parallel to Hotline and the popular n8n constructor, on which button display and reactions to their presses are implemented

  • The bot responds to the /start command and shows a welcome with buttons to select the topic of appeal, while Hotline relays outgoing messages with buttons and incoming messages from the user to the backend group, from where operators can then respond to the user

  • You can join the working group via the link https://t.me/+GCqhEvR4iKM2NWJi, there intercepted messages from the parallel bot will be visible and you can test sending a message to yourself

  • For the connection, the HIDE_INFO parameter is activated, so user names are hidden, also the /info command is disabled in the group

  • The bot also has a WebApp button with a form through which you can send us feedback about the parallel connection work

Parameters for Parallel Connections

Often when using parallel connections, the following parameters may be used.

Disabling or setting welcome:

WELCOME

Welcome message that user receives on first contact and when their request was closed (switched to /close status). Can be completely disabled on paid version. Free version requires Hotline link in welcome message.

Default value: standard welcome message in English.

Learn more about parameter

Double welcome

If the parallel bot issues a welcome, a welcome from Hotline is added to it. In the free version of Hotline, the message with system copyright cannot be removed.

Disabling output of possible errors:

Disabling Hotline interception of outgoing messages:

Creating topics only by keywords in dialogue:

Message relaying

If the PRIVATE_KEYWORDS parameter is not used, all messages from the user are relayed to the backend group from the moment of first appeal.

Important Notes

Alternative approach

If you have a bot with large functionality and significant user flow, it may be more correct to create a separate bot specifically for Hotline and support service, rather than using parallel connection to it (this can consume many updates).

Constructor limitations

Some bot constructors do not allow receiving arbitrary user messages and give errors. For such systems, parallel connection is not advisable.

Get Help

If you wish to purchase a paid version of the Hotline system, or you need personal help setting up a parallel connection, contact our support service.