International SMM

Livegram

Tool · this deep dive is built from the official pages of the platform itself and of the tools that support it.

Overview

Livegram is a builder of feedback bots for Telegram. It does not hold the conversation itself: you create your own bot, hand it over to the service, and from then on a reader writes to your bot and the message arrives in your Telegram as an ordinary message. You reply there, and the reply goes back to the reader from your bot.

The service describes itself this way: «Livegram Bot — это конструктор ботов, который позволяет создавать боты для обратной связи в Telegram» — a builder of bots for feedback in Telegram (our translation). The words «for feedback» are the important part: you cannot build a shop, a quiz or a bot with its own menu through Livegram, and the help says so outright.

The problem it solves is the same for everyone. Open direct messages in Telegram mean anyone can write to you, and the correspondence drowns among your other chats. A feedback bot puts one layer between you and the reader: the address for letters is public, your personal account is not, and every enquiry arrives in one place where it can be answered in turn.

How it works

Understanding the arrangement removes half the questions.

The service has no access to your Telegram account. It operates a separate bot that you register for this purpose with @BotFather, Telegram's own service bot. The bot has a token: a string that is the key to controlling it. By handing the token to Livegram you hand over control of that bot — and of nothing else.

The same fact answers the question about transferring a bot to someone else. The service describes the transfer as handing over the token: the new owner sends /addbot and then the token, which is taken from @BotFather via /mybots → «API Token». Whoever holds the token owns the bot.

Getting started: seven steps

  1. Open @BotFather and send /newbot.
  2. Enter the bot's name — what the reader sees in the chat header. It can be changed later with /setname.
  3. Enter the username — it must be free and end in «bot». It is entered, in the help's own words, «без знака @», that is, without the @ sign.
  4. Take the token that @BotFather issues.
  5. Open @LivegramBot and send /addbot.
  6. Send the token there as a separate message.
  7. Test it. The help says plainly: «попробуйте отправить ему любое сообщение, а затем ответить на него» — send the bot any message, then reply to it.

The bot's avatar and description are set not in Livegram but where the bot was created: the commands /setuserpic and /setabouttext in @BotFather.

How to reply

There is no special reply command — Telegram's own reply is used. The help describes the gesture: «сделайте свайп влево (или кликните два раза) по сообщению, на которое хотите ответить» — swipe left, or double-tap, on the message you want to answer.

This matters more than it looks. Since the addressee is determined by which message you reply to, an ordinary message sent «into the void» reaches nobody — while a reply to someone's enquiry reaches exactly its author.

What can be sent

The service names text, photos, video, voice messages and stickers. One asymmetry is spelled out separately: bots «могут принимать аудиофайлы, но ответить на такие сообщения невозможно по техническим причинам» — audio files can be received, but replying to them is not possible.

The same page names two limits on the reader's side: they cannot forward someone else's message to the bot and cannot edit their own. If they do press «edit», they are offered to send the message anew. Hence a useful consequence for whoever answers: two or three similar messages in a row from one person are usually a correction, not spam.

When more than one person answers

Operators in Livegram are not a list of accounts but a connected group chat. You create a chat with the people who should answer and add the bot to it; after that enquiries arrive in the chat and any participant can reply.

Two conditions are stated directly, and both break the connection if missed: the bot must be added to the chat by the same account that connected it to the service, and «Anonymity» must be switched off in the administrator rights. If the bot has several languages, each language is bound to the chat separately — and each language may have a chat of its own.

Four conversation modes

The mode decides how enquiries land in the operators' chat and what the operators see about the person.

Standard — all enquiries in one common stream. The service calls it suitable for roughly up to ten enquiries a day: beyond that the stream mixes and becomes hard to sort.

Personal — a separate topic per person, with the public name and @username visible in the topic title and the profile reachable.

Private — also a topic per person, but «в названии топика отображается только публичное имя пользователя — без @username» — only the public name, no @username — and the profile cannot be opened even if it is public.

Anonymous«в названии топика отображается только номер обращения»: only the enquiry number. The person cannot be identified by name or by username.

One warning is worth reading before pressing anything: «при активации «Анонимного» режима переключиться обратно на другие режимы будет невозможно» — once Anonymous is switched on, going back to the other modes is impossible. The service itself advises trying it on a separate bot first.

Topic-based modes require a private group with topics enabled and the bot holding rights to manage them.

Blocking

A block is issued as a reply to the person's message. The command is /ban, with the term written after it: the formats 24h, 365d and 12m are accepted. Without a term the block is permanent. A reason can be added in the same message, and the person sees it in the block notification. It is lifted with /unban, and /clear exists for clearing the stream.

The service lists the commands like this: the owner has /ban, /unban, /clear; the reader has /lang, /unsubscribe, /subscribe.

Broadcasts

A broadcast goes to those who have already written to your bot — it cannot be otherwise: Telegram's own rule says that «bots can't start conversations with users. A user must either add them to a group or send them a message first». A bot never introduces itself first.

There are eight selections: everyone; those who joined after a given date; those who joined before it; those who have a username; every Nth person; those active within a given period; a list from a file; and by the reader's language. The post accepts HTML markup and is sent with /done.

The «from a file» selection works differently: the /my_users command exports what the service calls an «обезличенная база» — a depersonalised database — of the bot's users; you remove the people you do not want and broadcast to the rest.

Broadcast speed is limited not by Livegram but by Telegram itself. Its documentation names the limits outright: «In a single chat, avoid sending more than one message per second» and «For bulk notifications, bots are not able to broadcast more than about 30 messages per second, unless they enable paid broadcasts». These are platform limits for any bot, yours included.

Languages

A bot can have several languages: the texts are set separately for each, and the reader switches language with /lang. The languages are chosen from a list inside the service. If you have an operators' chat, a new language must be bound to it as well — otherwise enquiries in that language will not reach the chat.

Money

A subscription exists and is enabled with /pro. The one effect the service names is this: removing the line «Этот бот был создан с помощью @LivegramBot» from the welcome message. Payment is for a chosen period.

Neither the sum nor the periods appear in the help — the /pro command itself shows them inside the bot. So the price is worth checking there rather than in retellings: the figures circulating in third-party articles differ from one another by orders of magnitude, and none of them is confirmed by the service.

What happens to the correspondence

The service writes that «все пользователи бота, а также история общения сохраняются в базу» — all bot users and the history of the conversation are saved to a database.

Disconnecting the bot does not touch that database. The help's wording is unambiguous: «Пользователи бота и сообщения удалены не будут» — users and messages will not be deleted. It appears in the instruction for reconnecting a bot after a token reset, which is precisely why reconnecting does not cost you the correspondence. The word throughout the help is «disconnect», never «delete».

From Telegram's side the picture is this: a bot sees «your public name, username, and profile pictures» and the messages you send it, and does not see your phone number or last seen time.

The practical conclusion for anyone setting up a feedback bot: access to the correspondence goes to everyone who is in the connected operators' chat. The service describes no rights separation inside that chat — so the chat's membership is the list of people reading the enquiries.

The service's rules

The terms of use are short. The user agrees not to break the laws of their country, not to assist violence and harassment through connected bots, not to distribute pornography and not to engage in political propaganda. The document is marked: «Последнее изменение: 12 марта 2025 года» — last changed 12 March 2025.

Contact with the service goes through @LivegramSupportBot; the help names no other support address.

On the age of the instructions

The Livegram help is assembled from separate pages with different dates: some are marked 2017, the terms of use are from March 2025, and the description of conversation modes refers to Telegram topics, which did not exist in 2017. The material, in other words, was edited in pieces.

What this affects: button names and menu structure («Тексты», «Чаты») are described from the interface of those years and may have shifted. The mechanics/newbot → a username ending in «bot» → token → /addbot, replying via reply, operators through a connected chat, /ban as a reply to a message — are described identically in every revision of the help and match how Telegram bots work in general.

Verified data

The checked data this deep dive rests on.

About the platform

a builder of feedback bots: a reader writes to your bot, the message arrives in your chat, and you answer there

Verbatim: «Livegram Bot — это конструктор ботов, который позволяет создавать боты для обратной связи в Telegram»

source, checked 2026-08-17

the service names six capabilities: talking to customers, all message types, multiple languages, saving users and conversation history, broadcasts, statistics

The list is from the same page, in the same order

source, checked 2026-08-17

Getting started

the bot is created in @BotFather with /newbot, then its token is handed to @LivegramBot with /addbot

The bot's username must end in «bot» and is entered, verbatim, «без знака @» — without the @ sign

source, checked 2026-08-17

to test: send your bot any message and reply to it

Verbatim: «Чтобы проверить работу бота, попробуйте отправить ему любое сообщение, а затем ответить на него»

source, checked 2026-08-17

Account and access

contact with the service goes through @LivegramSupportBot

The help names no other support address

source, checked 2026-08-17

Content

disconnecting a bot from the service does not erase the data: the service writes that the bot's users and messages will not be deleted

Verbatim: «Пользователи бота и сообщения удалены не будут». The word throughout the help is «disconnect», never «delete»

source, checked 2026-08-17

Features

the answer is given with Telegram's own reply — swipe left or double-tap the message

There is no separate command for addressing an answer: the reply decides the addressee

source, checked 2026-08-17

text, photos, video, voice messages and stickers are accepted; audio files are accepted but cannot be replied to

Verbatim: «могут принимать аудиофайлы, но ответить на такие сообщения невозможно по техническим причинам»

source, checked 2026-08-17

a reader cannot forward someone else's message to the bot and cannot edit their own: on trying to edit, they are offered to send it anew

Hence a consequence: several similar messages in a row from one person are usually a correction, not a repeat

source, checked 2026-08-17

more than one person can answer: the bot is added to a group chat, and every participant sees the enquiries and answers them

Two conditions are named outright: the bot must be added to the chat by the same account that connected it to the service, and «Anonymity» must be off in the administrator rights

source, checked 2026-08-17

four conversation modes: Standard — every enquiry in one stream; Personal — a topic per person with the name and @username; Private — a topic without the @username and without access to the profile; Anonymous — only the enquiry number

The topic-based modes require a private group with topics enabled and the bot holding rights to manage them

source, checked 2026-08-17

owner's commands inside the assembled bot: /ban, /unban, /clear; reader's commands: /lang, /unsubscribe, /subscribe

The list is given by the service itself

source, checked 2026-08-17

a broadcast goes by one of eight selections: everyone; those who joined after a date; those who joined before it; those with a username; every Nth person; those active within a period; a list from a file; by the reader's language

The post accepts HTML markup and is sent with the /done command

source, checked 2026-08-17

the /my_users command exports what the service calls a depersonalised database of the bot's users — it can be trimmed and the remainder broadcast to

The only described place where the data leaves the service

source, checked 2026-08-17

Platforms

Telegram

The service exists only inside Telegram: it assembles Telegram bots and names no other platform

source, checked 2026-08-17

Pricing

a subscription is enabled with /pro and paid for a chosen period; the effect the service names is removing the line «Этот бот был создан с помощью @LivegramBot» from the welcome message

The sum, the currency and the periods are not printed on the help pages — the /pro command itself shows them

source, checked 2026-08-17

Restrictions

switching Anonymous mode on is irreversible: the other modes cannot be restored afterwards

Verbatim: «при активации «Анонимного» режима переключиться обратно на другие режимы будет невозможно»

source, checked 2026-08-17

the service calls Standard mode suitable for roughly up to ten enquiries a day

The service's own guideline, not a measurement

source, checked 2026-08-17

an assembled bot never has its own commands or menu: the service builds feedback bots only

Verbatim: «Если вы хотите сделать бота со своими собственными командами, меню… вы должны использовать для этого какой-нибудь другой сервис»

source, checked 2026-08-17

Moderation

a block is issued as a reply to the person's message with /ban; the term follows it — 24h, 365d, 12m; a reason may be added in the same message and the person sees it in the notification

Without a term the block is permanent; it is lifted with /unban

source, checked 2026-08-17

the terms of use forbid breaking the laws of your country, assisting violence and harassment, distributing pornography and engaging in political propaganda

The document is marked: «Последнее изменение: 12 марта 2025 года» — last changed 12 March 2025

source, checked 2026-08-17

Languages

an assembled bot can have several languages: the texts are set separately for each, and the reader switches with /lang

The languages come from a closed list inside the service; if an operators' chat is connected, the language must be bound to it as well

source, checked 2026-08-17

transfer

a bot is transferred by transferring the token: the new owner sends /addbot and the token, taken from @BotFather via /mybots → «API Token»

Hence: whoever holds the token controls the bot

source, checked 2026-08-17

Catalogue section: all similar See also: catalogue index · scheduler comparison · find by situation · platform restrictions