Skip to main content
The channel determines whose support is talking to the customer, the module supports two types of channels, you can hold several and different types at the same time, the management lives in the section “Channels”. | Type | On whose behalf is | What is | | Limitations |---|---|---|---| | Bot | Telegram bot | Token by @BotFather | No | | | Live User Account | Phone number, api_id and api_hash with my.telegram.org | Risk of Telegram restrictions, see below | The bot is the default. The user chooses when customers are used to writing to a personal account and don’t want to transfer them to a bot, and pays for this with the risk described below.

General rules

The token or credentials are checked before they’re saved: a channel with non-working details will not be created, the secrets themselves live in a secure vault and don’t come out, the panel shows only the sign “key is set.” Shutting down the channel stops receiving and sending, but it doesn’t affect the history of the tickets. You can’t delete the channel that already has tickets; the panel will suggest turning it off. Channels can work through an outbound proxy (SOCKS5, HTTP or Axottle node) if direct access to Telegram from the panel server is limited. Channel statuses on the review page: “Connected”, “Reconnected”, “Error”, “Waiting”, “Re-entry”, “Disconnected”.

User Account (MTProto)

An account session is equal to the account itself: whoever owns it reads correspondence, contacts and groups without a password, while Telegram itself restricts and blocks accounts for automation, connect a separate service number that is not a pity to lose, and do not use a personal one.
Entry takes place in three steps and requires the participation of a person:
1

Start the entrance

Enter the phone number and a pair of api_id and api_hash from my.telegram.org. Telegram will send the code to the application or via SMS.
2

Enter the code

Enter the code from Telegram. If your account has two-factor protection enabled, the panel will also ask for a password.
3

Enter the 2FA password

After the password, the status will be “Entered”, and the channel can be turned on.
The login session lasts 10 minutes: if you don’t have time, start with the first step. The confirmation code and the 2FA password are not stored anywhere, they go through a single request to Telegram and disappear. The pair api_id and api_hash are needed once on the first login. The “Re-entry” status means that the session has stopped working: it was terminated from another device, Telegram has withdrawn it or the account is blocked, in which case the module stops trying and waits for the person to not show the panel “connected” while the messages go nowhere. Only one channel can be added to a single number: two channels would split the update stream in half, and each would see half of the messages. The End Session button logs the Telegram-side account and deletes the session from the vault; the ticket history remains.
Incoming files on the channel-account are not downloaded, only the fact of attachment is recorded. Files are sent by the operator only on the bot channel. Details on the page Entries and storage .