Livegram connects a bot you make in @BotFather to a private inbox. Your readers write to the bot, messages land with you or your team, and replies go back out under the bot's name — never your personal account.
No credit card. No server. Works entirely inside Telegram.
Instead of writing code and renting a server, you create a bot the normal way — through Telegram's own @BotFather — and hand its token to Livegram. From that moment your bot is live: anyone who opens its link and presses Start can write to you, and everything they send is forwarded into a chat you choose.
The routing runs both ways. A subscriber's message arrives as a card in your admin chat; you use Telegram's ordinary Reply function, and your answer is delivered back under the bot's name. Livegram itself is just the relay — a proxy between two Telegram chats, with the conversation living in Telegram and nowhere else.
Four steps, all inside Telegram. No hosting, no deployment, nothing to install.
Send /newbot to Telegram's official bot-making bot. Pick a display name and a username ending in bot, and it hands you an API token.
Open @LivegramBot, send /addbot and paste the token — or simply forward the @BotFather message and Livegram reads it out.
Choose where messages land: your own chat, or a private group your team can answer from. Then publish the bot's t.me link.
Messages arrive in the chat you chose. Swipe, hit Reply, and your answer goes out under the bot's name.
All of it free. The paid plan only removes Livegram's own ads and branding.
You create the bot in @BotFather, pick its username and avatar, and paste the token into Livegram. Livegram never owns the bot — it operates the one you authorised, and revoking the token ends the connection instantly.
Text, photos, videos, voice messages, documents and stickers are forwarded exactly as they were sent. Your audience never has to think about format.
Each message arrives as its own card in your admin chat. Swipe, hit Reply, type — the answer goes back under the bot's name, never your personal account.
Point the bot at a private group and your whole team sees every incoming message. Anyone can pick one up, and handovers stay visible in one place.
/mybots lists every bot you have connected and configures each independently — its own admin chat, its own texts, its own audience.
Add several interface languages to a bot, and route each language to its own chat. Welcome texts are edited per language.
Replace the default greeting with your own wording, per language. A clear welcome message cuts down on "hello?" messages that need a second round-trip.
Send an announcement to everyone who has written to your bot, all at once — the right channel for service updates a channel post would miss.
See how many users your bot has and how many messages have gone through it, so you can watch the trend after you promote it or change the greeting.
Forwarded messages stay in your admin chat like any other Telegram messages, so a returning person arrives with context. Livegram stores no message content — the only thing kept on its side is the bot owner's Telegram ID, for sign-in and account management.
Connecting a bot, editing texts, broadcasting and reading analytics all happen in a chat. No dashboard, no hosting, no deployment.
Messages travel between people inside Telegram — Livegram only relays them. Content is not read by the operator and is not stored anywhere outside Telegram.
| Command | What it does | When to use it |
|---|---|---|
/start | Starts your session with Livegram and shows the main menu. | The first thing you send. Also useful to get back to the top level. |
/addbot | Connects a new bot by its @BotFather token. Paste the token, or forward the @BotFather message. | Right after creating a bot, or any time you add another. |
/mybots | Lists every bot on your account and opens its settings — admin chat, texts, languages, broadcasts, statistics. | Day-to-day management and configuration. |
/lang | Changes the language of the Livegram interface. | If you would rather manage your bots in another language. |
/pro | Opens the Livegram Pro subscription — plans, prices and payment. | To remove ads and the "created with" label from your bots. |
/ads | Opens Livegram advertising options for buying a placement. | If you want to promote a product to the Livegram audience. |
/help | Shows built-in help and answers to common setup questions. | When something is not behaving as expected. |
/feedback | Contacts Livegram support. | A bug report or a question /help does not cover. |
All commands are sent to @LivegramBot, not to your own bot.
The same bot solves very different problems, depending on where you put the link.
Let readers submit tips, memes, photos and corrections without opening your DMs to a hundred thousand people. Submissions land in a private chat where you or your editors triage them.
Point the bot at a private group and put your support team in it. Customers get one place to write — no ticket portal, no login — and the whole team sees the thread.
Put the bot link on receipts, in your app or at the end of a course. People answer more readily in a chat they already have open than in a web form.
For a small shop or repair service, the bot is a low-friction order form: the customer sends what they want and a photo, and you confirm. No forms to build.
Large groups drown individual questions. A bot gives every member a private line to the moderators, answered collectively from a shared chat.
Newsrooms, HR teams and student unions can publish a bot link as a confidential channel. Be clear about limits: Telegram still knows who sent the message.
Send traffic straight to your bot instead of a contact form. One tap, already logged in, no captcha, no reply lost to spam.
Hand out one bot link at the start of a term for homework questions and submissions — without giving out a teacher's personal contact details.
Livegram is funded by ads shown inside the bots — that is what keeps the core product free for everyone.
Everything you need to run a feedback bot on Telegram. No card, no trial timer, no feature locked behind a paywall.
/addbotOne subscription, applied to your whole account. Pro removes all ads for your account and clears the "This bot was created with @LivegramBot" label from every bot you own — for all your users.
Livegram uses regional pricing so Pro costs a fair amount everywhere — pick a region above to preview it. Longer terms are billed once, up front. Pay by card or Telegram Stars in the bot, or on the website (payments processed by Whop). Subscriptions renew automatically and can be cancelled at any time — see the Refund Policy. The exact price for your account is always shown in the bot before you pay.
Setup walkthroughs, support playbooks and troubleshooting — written for people running a real Telegram channel. Click any guide to read it in full.
A feedback bot is a two-way channel between you and your audience. Someone opens your bot, writes a message, and that message arrives in your Telegram. You reply, and your answer goes back to them from the bot — your personal account is never shown.
Livegram is the piece in the middle. You own the bot; Livegram routes the messages. Building the bot, receiving messages, adding admins, broadcasts and analytics are all free.
You need two things:
@BotFather is Telegram's own bot for creating bots. It is the only legitimate place to get a token.
/newbot.Acme Support. You can change it later.bot — for example AcmeSupportBot. This one is much harder to change, so choose carefully.Treat that token as a password. Anyone who has it controls your bot completely. Do not paste it into a group chat, a screenshot, or a public issue tracker.
Tap the token in BotFather's message to copy it. On desktop, select the whole string — including the numbers before the colon. A token that is missing its leading digits will be rejected.
/start)./lang and choose one./addbot.Livegram validates the token with Telegram and confirms the connection. From this point your bot is live — it will answer people immediately.
If you want to see or manage everything you have connected, send /mybots. That is the control panel for renaming, checking stats, sending broadcasts and disconnecting bots.
Do not skip this. Testing takes thirty seconds and catches almost every setup mistake.
t.me/YourBotUsername.Reply is the core mechanic and the single thing new owners get wrong most often: a message typed into @LivegramBot without being a reply goes nowhere useful. Always reply to the specific forwarded message.
Testing from your own account works, but if you can, ask a friend to test as well. That confirms the experience a stranger actually gets.
People trust a bot that looks finished. Back in @BotFather:
/setuserpic — upload a logo or avatar./setabouttext — the short line shown on the bot's profile before someone starts it./setdescription — the text shown on the empty chat screen, above the Start button. Use it to say what the bot is for and when you answer: "Send us your question. We reply on weekdays, 9:00–18:00 CET."Then share the link. Where it works best:
A link alone converts badly. A sentence of context — "Questions about an order? Write to @AcmeSupportBot" — converts much better.
Livegram is free because it is ad-supported. In the free version your bot carries the label "This bot was created with @LivegramBot" and ads may be shown. If you would rather your bot looked entirely like your own, Livegram Pro removes both — see the Pro guide.
/newbot), copy the token, send /addbot to @LivegramBot and paste it. That is the whole setup./revoke it in BotFather.A solo feedback bot is fine until one of three things happens: you go on holiday, volume outgrows one person, or you hire someone. At that point everything you need is already in Livegram — you connect a group chat as the destination, and the whole team answers from there.
The mechanics stay identical. Users write to the bot; messages land in the group; anyone in the group replies to a message and the answer goes out from the bot. Your users never see who typed it, or how many of you there are.
Acme — Support inbox, not chat./mybots, choose the bot, and set the group as the destination chat.Livegram supports connecting a separate chat or group where a team answers — this is the documented multi-admin, call-centre setup.
Write to the bot from a second account. The message must appear in the group. Reply to it from a different team member's account, and confirm the answer reaches the user. Test with two different people, not just yourself — that is what proves the setup is genuinely shared.
That second rule is a feature, not a limitation. It means the group doubles as a place to coordinate: "I'll take this one", "escalating to billing". Nothing leaks as long as you never wrap coordination inside a reply.
Claim before you answer. Two people replying to the same person is the classic failure of shared inboxes. Adopt one convention and enforce it: react to the message with an emoji when you pick it up, or post taking as a plain group message. Whichever you choose, it must be visible to everyone before the reply is written.
Hand over explicitly. At the end of a shift, post a short list of what is still open and what is waiting on someone else. "Nothing open" is also a valid handover — it is information.
Pin the rules in the group. A pinned message with your reply conventions, tone rules and escalation path costs five minutes and saves every new hire an hour.
Use one clear closing line. Something like "Anything else I can help with?" signals to your team that a conversation is done, without any status system.
Set expectations publicly. Put working hours in the bot's description via /setdescription in @BotFather. Most complaints about slow support are actually complaints about unclear expectations.
Watch group size. A support group of 20 people is not a team, it is an audience. Keep write access to the people who actually answer; everyone else can read a channel summary instead.
When someone leaves, remove them from the group the same day. Group membership is the permission to speak as your company — there is no separate revocation step.
Keep the bot's Livegram ownership with a role, not a person, where you can. If the bot is connected under one employee's personal Telegram account and that person leaves on bad terms, recovery is awkward. See the security guide for how to handle token rotation with /revoke.
If you run several products or brands, do not funnel them into one group and sort by hand. Livegram lets you manage several bots from one account — create a bot per brand, point each at its own group, and the routing is done for you.
/mybots.taking) before volume makes collisions expensive.A Telegram channel broadcasts. Subscribers cannot reply, and the discussion group attached to a channel is public by nature — great for conversation, useless for anything sensitive, anonymous or half-finished.
A submission bot solves a different problem. It gives every subscriber a private line to you: a story tip, a question for a Q&A post, a screenshot, a job listing, a confession. You collect it in one place, you decide what gets published, and the sender never sees your personal account.
This is the same feedback-bot setup as any support bot — only the framing changes.
Follow the standard flow: /newbot in @BotFather → copy the token → /addbot in @LivegramBot → paste. Full detail is in the five-minute setup guide.
Name it for the job, not for your brand. AcmeSuggestBot reads as an invitation; AcmeBot reads as customer service. The username is effectively permanent, so decide before you send it.
This is the step most channel owners skip, and it is the one that determines submission quality. In @BotFather use /setdescription — the text shown above the Start button in an empty chat — and treat it as a short editorial brief:
Send us your tip. Include what happened, when, and a screenshot if you have one. We publish anonymously by default and never share your username. Replies within 48 hours.
Four things a good brief always covers:
Add /setabouttext for the one-line version shown on the bot's profile, and /setuserpic for an avatar that matches your channel.
Order of effectiveness, roughly:
Do not only announce it once. Submission volume tracks how recently you asked.
Submissions arrive as ordinary forwarded messages: text, photos, videos, voice notes, files, stickers. If your channel has more than one editor, connect a group chat as the destination so the whole editorial team sees the queue (see the support-team guide).
A workable triage habit for a two-person channel:
Livegram hides your account from the sender. It does not hide the sender from you — you see who wrote, because that is how you reply.
So if you promise anonymity, you are promising editorial anonymity: you know who they are, and you will not publish it. Say exactly that. Vague promises of "full anonymity" are the kind of thing that damages trust when a subscriber works out how it actually functions.
If a submission is genuinely sensitive, consider deleting your copy after publication. Livegram stores no message content of its own — the only thing kept on its side is the bot owner's account ID — but the forwarded copy in your admin chat is a normal Telegram message, and managing it is on you.
The single strongest driver of repeat submissions is visible proof that submissions get used. Credit contributors when they allow it ("via a subscriber"), and post occasionally about what came in. A channel that says "this week's post came from a reader tip" gets more tips next week.
Once you have a base of people who wrote to the bot, you can also broadcast to them — for example, a themed call for submissions. Do it sparingly and read the broadcast guide first.
...SuggestBot), and write /setdescription as an editorial brief: what, what format, anonymity, response time.Telegram support is not email support in a smaller window. Three properties change how you should work:
Everything below follows from those three facts.
The cheapest support improvement available to you is the bot description. Use /setdescription in @BotFather:
Support for Acme. We reply Mon–Fri, 9:00–18:00 CET, usually within 4 hours. For urgent order issues include your order number.
You have now converted "why is nobody answering" into "they answer tomorrow morning" — same speed, entirely different customer experience.
When more than a handful of messages arrive daily, answer in priority order rather than arrival order. A simple three-bucket model:
A one-line acknowledgement on a bucket-1 message within minutes buys you hours of patience. Silence does the opposite.
Templates save time. Scripts destroy trust. The difference is that a template is a skeleton you finish, and a script is a wall of text you paste unchanged.
Keep your templates in a pinned message in the team group and structure each one the same way:
Five to eight templates cover most of the volume in a small operation: cannot log in, payment failed, where is my order, how do I do X, feature request, bug report, refund request, out-of-hours auto-reply.
Rules that hold up under pressure:
Replying without using Reply. In Livegram a reply must be an actual Telegram reply to the forwarded message. A message typed loosely into the chat does not reach the user. This is the number-one cause of "we answered and they say we didn't".
One inbox, no ownership. With several people in the group, every message needs a visible owner. Emoji reaction or a taking message — pick one and be consistent.
Answering out of hours by accident. If someone replies at 23:00 once, users learn that 23:00 works. Either it is your policy or it is not.
Losing the follow-up. Anything you promise to come back on must leave Telegram and enter something with a due date. The bot is an inbox; it is not a task manager.
Treating feedback as noise. Repeated feature requests are your roadmap arriving for free. Log them somewhere countable.
Forgetting where the record lives. Messages stay in your Telegram admin chat — that chat is your archive. Livegram stores no message content on its side. If a conversation matters for a dispute or a case study, your chat copy is the one to keep.
Livegram provides basic analytics — the number of users and messages. That plus two numbers you can count by hand is enough for a small team:
Be honest about the ceiling. A feedback bot is excellent up to roughly the point where all of the following are still true: one queue, a few agents, no formal SLA, no compliance obligation to retain history, and no need to know who handled what.
Consider a dedicated help desk when you hit any of these:
None of these are failures of the bot; they are a different product category. Many teams keep the Telegram bot as the front door and connect it to a desk behind the scenes.
Livegram lets you send a message to everyone who has written to your bot. That is a genuinely valuable list: these are people who contacted you voluntarily, in a private one-to-one chat, with notifications on.
It is also the most fragile asset you own. A channel subscriber who dislikes a post scrolls past. A bot user who dislikes a broadcast presses Block, and they are gone permanently — you cannot message them again, ever, and there is no re-subscribe flow.
Treat every broadcast as a withdrawal from an account you cannot easily refill.
People wrote to your bot to ask a question. Unless you told them otherwise, they did not sign up for a newsletter. Legally this varies by jurisdiction; practically the rule is simple: your broadcasts must be things this specific audience would have asked for.
The clean approach is to say so up front. Put a line in your bot description via /setdescription:
We occasionally send service updates here (a few times a year). Send /stop to opt out.
You have now converted an assumption into a disclosure, at zero cost.
Note that Livegram's acceptable use explicitly prohibits spam, phishing and collecting personal data without consent. This is not just etiquette — sending unwanted bulk messages is a policy violation on both Livegram's side and Telegram's.
There is no universal number, but useful anchors:
A rough test: if you cannot name the specific benefit to the reader in one sentence, it is not ready to send. "We wanted to update you on our journey" is not a benefit.
Watch what happens after each send. If your user count drops noticeably after a broadcast, that is your audience telling you the frequency or the content was wrong. Livegram's basic analytics show user and message counts — check them before and after.
The instinct is to send everything to everyone because the list is right there. Resist it.
If you run several bots for several products, broadcast per bot — that is exactly why multi-bot management exists. Someone who wrote to your support bot about a refund does not want your new-podcast announcement.
If you cannot segment, that is itself an argument for sending less. A message relevant to 20% of the list annoys the other 80%, and 80% of your audience is a large number of Block buttons.
Two kinds of opt-out exist, and both are binding.
Explicit. Someone replies "stop", "unsubscribe", "don't message me". Honour it on the spot and say so in one short line: "Done — you won't get announcements from us. You can still write here any time if you need help."
Silent. Someone blocks the bot. Telegram then rejects any send to that user with a 403 Forbidden: bot was blocked by the user error. There is nothing to fix and nothing to work around — a block is a permanent, deliberate decision, and attempting to reach that person another way is the behaviour that gets bots reported.
Broadcasting is rate-limited by Telegram itself, not by Livegram:
429 Too Many Requests and pauses your bot — a short pause first, a longer one on repeat.In practice Livegram handles the pacing for you, which is why a broadcast to a large audience delivers gradually rather than instantly. A list of 100,000 users takes roughly an hour at the standard rate. Do not interpret slow delivery as a failure and re-send — a duplicate broadcast is far more damaging than a slow one.
Telegram also offers a paid broadcast option in @BotFather that raises the ceiling to about 1,000 messages per second, charged in Telegram Stars per message above the free 30/second.
Before you press send, five checks:
Keep it short enough to read in a notification. Say what it is, why it matters to them, and what to do — in that order. Sign off in a way that keeps the channel two-way: "Reply here if you have questions" reminds people this is a conversation, not a megaphone, and it is the line that makes the next broadcast welcome.
403 block is final — never route around it.429 means slow down.Livegram is free — bot creation, message forwarding, multiple admins, broadcasts and analytics all cost nothing. That is funded by advertising: Livegram sells ad placements to its own audience, and in return the free tier shows ads and carries a small attribution label.
Pro is the alternative funding route. You pay a subscription instead of being advertised to, and both the ads and the label disappear.
Three things, all described in the bot's own wording:
1. Ads are switched off inside @LivegramBot. Your own working interface — the place where you read and answer messages — stops showing promotions.
2. The copyright label is removed. In the free version, your bot carries "This bot was created with @LivegramBot". Pro removes it. For anyone using a bot as a customer-facing brand surface, this is usually the reason to upgrade: the bot reads as your product rather than as someone else's platform.
3. Ads are switched off in all your connected bots — for all of their users. This is the part people underestimate. Pro is an account-level subscription, not a per-bot one. Whether you run one bot or fifteen, a single Pro subscription clears ads across all of them, and the people writing to your bots stop seeing ads too.
That last point is worth restating plainly: your users' experience changes, not just yours. A subscriber writing to your support bot on the free tier may see Livegram advertising; on Pro they see only you.
Pro is a presentation-layer upgrade. It does not add message capacity, extra admin features, longer retention, priority routing or an SLA. Everything functional is already free.
Specifically:
If you are considering Pro hoping it unlocks a capability, check the free feature list first — it very probably already includes what you need.
| Period | Price (₽) | Price ($) | Effective per month |
|---|---|---|---|
| 1 month | 250 ₽ · 220 ⭐ | $2.92 | $2.92 |
| 3 months | 625 ₽ · 550 ⭐ | $7.30 | ~$2.43 |
| 6 months | 1,125 ₽ · 990 ⭐ | $13.14 | ~$2.19 |
| 12 months | 2,000 ₽ · 1,760 ⭐ | $23.36 | ~$1.95 |
The longer commitments are meaningfully cheaper — twelve months costs roughly two-thirds of what twelve monthly renewals would. If your bot is part of a business you expect to still be running next year, the annual tier is the obvious choice. If you are trialling, start monthly.
Open @LivegramBot and send /pro to see the current tiers and start a purchase.
Available methods:
The service is operated by "Krionit Lab" LLC, registered in the Kyrgyz Republic. Livegram is an independent service and is not affiliated with Telegram FZ-LLC.
Worth it if:
Probably not worth it if:
A reasonable heuristic: at around $2/month on the annual tier, Pro pays for itself the moment the bot touches a paying customer. Below that threshold, stay free without guilt — the free tier is the product, not a crippled demo.
When @BotFather created your bot, it gave you a token — a long string with a colon in it. That token is the bot. Anyone holding it can read every incoming message, send messages as your bot to your entire audience, and change the bot's behaviour. There is no second factor and no per-action confirmation.
Rules that follow directly:
/addbot. Delete the message afterwards where you can.If a token leaks: open @BotFather, select the bot, and use /revoke. This invalidates the old token immediately and issues a new one. The old one stops working the same second — which also means your Livegram connection breaks and you must reconnect with the new token via /addbot. Revoke first, reconnect second; do not delay revocation to avoid downtime.
Everyone in your bot's admin group can send messages to your users as your brand. That is a real permission, and it should be managed like one.
Be clear-eyed about the layers:
In Telegram. The conversation between your user and your bot lives in Telegram's infrastructure under Telegram's own policies. Neither you nor Livegram controls that layer.
In Livegram. Messages pass through Livegram purely as a proxy: they travel between people inside Telegram, and Livegram only relays them. The operator does not read the content of conversations, and content is not stored outside Telegram. The only thing Livegram keeps is the bot owner's Telegram ID — for authorization and account management.
In your group chat. This is the copy you actually control — and the one people forget. Anything forwarded into your admin group stays in that group's history under Telegram's normal rules, independent of Livegram's 30-day deletion. If a user sends a document, a photo of an ID, or anything sensitive, that content is sitting in a group chat that several people can scroll through indefinitely.
Anywhere you copied it. Screenshots in Slack, exported chats, pasted quotes in a bug tracker. This is where most real leaks happen.
The practical implication: the 30-day auto-deletion protects the routing layer, not your operational copies. If you want data gone, delete it in your own group too.
If you run a bot that collects messages from the public, you are a data controller in the eyes of most privacy regimes, whatever the scale. You do not need a legal department, but you do need to be able to answer four questions.
Put a short version in the bot description via /setdescription, and link a fuller privacy note if you have a website. Two sentences done honestly beat a template policy nobody read.
Do not collect what you do not need. If your bot is a support channel, you do not need ID photos, card numbers or passwords, and you should say so explicitly in the description: "Never send passwords or card details here." Users will otherwise send them, and then the sensitive data is your problem.
/revoke and reconnect./setdescription, including "never send passwords or card details here"./revoke in @BotFather the moment you suspect exposure, then reconnect with /addbot.Work through these in order. Most "the bot is broken" reports resolve at problem 1, 2 or 4.
Symptom. You open your bot, press Start, and nothing happens. No welcome, no reaction.
Cause. Usually the bot was never successfully connected, or it was disconnected. Occasionally the token was pasted incompletely.
Fix.
/mybots. If your bot is not in the list, it is not connected — reconnect with /addbot and paste the full token from @BotFather.Symptom. /addbot rejects the token.
Cause. An incomplete copy (missing the digits before the colon), stray whitespace or a line break, a token that was already revoked, or a token from a different bot.
Fix.
/mybots, choose the bot, and open API Token. Tap the token to copy it cleanly rather than selecting by hand./revoke in @BotFather to issue a new token and try that one.Symptom. Someone says they wrote; you see nothing.
Cause. Wrong destination chat, a group setup problem, or you are looking in the wrong place.
Fix.
/mybots.Symptom. You type an answer; the user insists they got nothing.
Cause. You did not use Telegram's Reply function. This is the single most common Livegram problem.
Fix.
A message typed into the chat without being a reply is not routed to anyone. If you have a team, put this rule in the group's pinned message — it is the first thing every new team member gets wrong.
Symptom. Replies to one specific person stop working while everyone else is fine.
Cause. That person blocked your bot. Telegram returns 403 Forbidden: bot was blocked by the user.
Fix. There is no fix, and that is correct behaviour. A block is a deliberate decision and Telegram enforces it absolutely — the bot cannot message that user again unless they unblock it themselves. Do not attempt to reach them through another bot or account; that is the behaviour that gets bots reported. If they are a customer you genuinely need to reach, use a channel they chose, such as email.
Symptom. A user receives an answer meant for someone else.
Cause. Someone replied to the wrong forwarded message, or replied to their own team member's message instead of the user's.
Fix. Reply only to the forwarded user message itself — never to a colleague's comment about it. In a busy group, always scroll to the original before replying rather than using the newest visible message. Adopt a claim convention (an emoji reaction on the message you are handling) so two people never work the same thread.
Symptom. You can no longer manage the bot — the account that set it up is unavailable, or an ex-colleague controls it.
Cause. Bot ownership sits with the Telegram account that created it in @BotFather, and Livegram management sits with the account that connected it.
Fix.
/revoke to issue a new token. The old one stops working instantly, cutting off any existing connection. Then reconnect under your own Livegram account with /addbot.Symptom. Rebranding, or the placeholder name you set in a hurry.
Cause. These are Telegram-level settings, not Livegram settings.
Fix. In @BotFather:
/setname — the display name shown at the top of the chat. Changeable freely./setuserpic — the avatar./setabouttext — the line on the bot's profile page./setdescription — the text above the Start button in an empty chat.The username (@YourBot) is the exception: it is effectively permanent. Changing it, where possible at all, breaks every link you have ever published. If you must, create a new bot and run both in parallel while you migrate.
Symptom. You sent to thousands of users and it is taking a long time.
Cause. Telegram's rate limits, not a Livegram problem. Bots are limited to roughly 30 messages per second across chats, one per second to any single chat, and about 20 per minute in groups.
Fix. Wait. Delivery is paced deliberately to avoid 429 Too Many Requests, which pauses your bot — 30 seconds the first time, longer on repeat. Never re-send a broadcast you think stalled. A duplicate message is far more damaging than a slow one, and doubles the block rate.
Symptom. Delivered count is lower than your user count.
Cause. Those users blocked the bot, deleted their account, or were deactivated. Telegram rejects those sends.
Fix. Nothing to fix. A gap between total users and delivered messages is normal and expected — every list has attrition. A growing gap after each send is a signal that your broadcasts are unwelcome: reduce frequency and improve relevance before the next one.
Symptom. Your customer-facing bot shows advertising or third-party attribution.
Cause. This is the free tier working as designed — Livegram is ad-funded.
Fix. Send /pro in @LivegramBot. Pro removes ads inside @LivegramBot, removes the "This bot was created with @LivegramBot" label, and removes ads from all your connected bots for all of their users. It is account-level, so one subscription covers every bot you run. Payment is by card, Telegram Stars, or on the website.
Symptom. History you expected to find is gone.
Cause. Livegram does not store conversations, so there is no server-side history to consult — the record is your admin chat, which follows Telegram's normal rules. If messages are missing there, they were deleted in Telegram itself.
Fix. Check your admin chat and Telegram's search first — the forwarded messages stay there like any other Telegram messages, and that chat is your archive. For disputes or legal records, treat the admin chat as the copy that persists, and save anything critical out of it at the time.
Write to our support bot @LivegramSupportBot, and use /help in @LivegramBot for the built-in reference. When you write in, include: your bot's username, what you did, what you expected, what happened instead, and whether a second account reproduces it. Never include your token.
/mybots to check), or you did not use Telegram's Reply./revoke in @BotFather is the emergency stop — it kills a leaked token and any hijacked connection instantly.403 block is permanent and correct. Do not route around it./feedback reaches Livegram support; /help is the built-in reference. Never send your token to anyone.123 answers about building, running and paying for a Livegram bot.
Livegram is a no-code feedback bot builder for Telegram. You create your own bot with @BotFather, connect it to Livegram, and it becomes a two-way channel between you and your audience: people write to your bot, their messages arrive in your admin chat, and your reply goes back to them from the bot. Your personal Telegram account is never shown to the people writing in.
Open @LivegramBot and press Start, then send /addbot. Livegram will ask for a bot token — get one from @BotFather with the /newbot command, then paste the token back into Livegram. Once the token is accepted, your bot is live and ready to receive messages.
@BotFather is Telegram's own official bot for registering bots. Every Telegram bot in existence — including yours — must be created there, because only Telegram can issue a bot account and its API token. Livegram cannot create the bot for you; it can only run a bot you already registered.
A token is the long string @BotFather gives you right after you create a bot, in the format 123456789:AAE.... It is the password to your bot — anyone holding it can control the bot completely. If you lose it, open @BotFather, send /mybots, pick your bot and choose API Token. A bot has exactly one valid token at a time: generating a new one with /token instantly invalidates the old one.
The name is the display name and can be almost anything, including spaces and non-Latin characters. The username is the @handle, must be 5–32 characters, may contain only Latin letters, digits and underscores, and must end in bot (for example MyShopSupportBot). Usernames are globally unique, so popular ones are usually taken.
Under five minutes in practice. The slowest part is choosing a username that isn't already taken in @BotFather. Once the token is pasted into Livegram, the bot starts working immediately.
Open /mybots, select your bot, and use the Texts section to set the welcome message people see when they press Start — this is the single most important setting, because it tells visitors what your bot is for and what to send. Then share your bot's link (t.me/YourBotUsername) wherever your audience is: a channel description, a pinned post, your website, or your bio.
No. Livegram hosts and runs the bot logic for you, so there is nothing to install, deploy, or maintain. Everything is configured from inside Telegram by chatting with @LivegramBot.
No. Creating and connecting bots, receiving and replying to messages, adding admins, broadcasts and analytics are all free. The optional Livegram Pro subscription only removes Livegram's own ads and the "This bot was created with @LivegramBot" label.
Send /help in @LivegramBot for the built-in reference, and /feedback to reach the support team. For billing questions and formal requests, write to admin@livegram.io.
When someone writes to your bot, Livegram forwards that message to your admin chat — either your private chat with @LivegramBot or the group you connected for your team. You will see the message together with the information you need to identify the sender.
Use Telegram's Reply function on the forwarded message and write your answer. Livegram sends your text back to that user from your bot. This is the whole workflow — there is no separate "answer" command to learn.
Nothing is delivered. Livegram routes each answer using the message you replied to, so without a reply it has no way to know which of your users you meant. Always tap Reply on the specific incoming message.
Text, photos, videos, voice messages, files and stickers are all supported in both directions. You can reply with the same range of content, so sending a screenshot, a price list PDF or a voice note back to a customer works normally.
No. Replies are delivered by the bot, so your users see the bot's name and avatar, never your personal Telegram account, username, or phone number. This is the core reason most people use Livegram.
You see whatever Telegram exposes to any bot: the person's Telegram ID, first name, last name and username if they have one, plus their interface language. You do not see their phone number or email unless they deliberately share it in the conversation. If someone has no username set, the bot is the only way to reach them — you cannot message them directly.
No, and this is a Telegram platform rule rather than a Livegram limitation. A bot can only message people who have pressed Start on it at least once. This is why broadcasts only reach people who have already written to your bot.
Yes. Open /mybots, select the bot and use its Texts section to edit the welcome message shown when a user presses Start, along with the other interface texts your users see. Write it as a short, clear instruction — "Send us your question and we'll reply here" works better than a wall of text.
The bot itself is a one-to-one feedback channel: your audience writes to it privately. What you connect a group for is the admin side — that's where your team receives and answers messages. If you run a channel, put the bot's link in the channel description or a pinned post so subscribers know where to write.
Telegram bots can edit and delete their own recent messages, but whether Livegram exposes this in the reply flow is not documented. `
Livegram's documented feature set covers the welcome message, forwarding, replies, broadcasts and analytics. Rule-based auto-responders, ticket assignment and business-hours messages are not documented features. `
Yes. Connect a group chat as the admin destination and every member of that group sees incoming messages and can reply. This effectively turns your bot into a shared support inbox for a small team.
Create a private group with your team, add your bot to it, and make the bot an administrator of that group. Then connect that chat in your bot's settings inside @LivegramBot so incoming messages are routed there instead of to you privately.
Telegram enables "privacy mode" on every bot by default, which hides most group messages from it — but bots added as administrators always receive all messages in that group. Admin rights are therefore what let your team's replies reliably reach the bot instead of being silently dropped.
Telegram requires the bot to be removed from the group and added again before a privacy-mode change takes effect. If you toggled /setprivacy, re-add the bot to your team group and re-grant its admin rights.
There is no built-in assignment or "claimed" status. Teams normally handle this with a simple convention — react to a message when you pick it up, or agree on a rota. For anything larger than a handful of agents this is the main thing Livegram will not do for you.
Whoever is in the connected group can read and answer messages. Account-level actions — connecting new bots, buying Pro, running broadcasts — stay with the Livegram account that owns the bot. There is no per-admin permission system. `
A bot belongs to the Livegram account that connected its token. Sharing the workload is done through the connected group chat, not by adding co-owners to the account.
Messages stop being delivered there, and your users' messages have nowhere to land. Reconnect a chat in /mybots as soon as possible — Telegram will not replay messages sent while the destination was broken.
Yes. Livegram is built for this — send /addbot again with a different token, and manage everything from /mybots. Many people run one bot per project, brand, or language.
Send /mybots and pick the bot you want from the list. Settings, texts, broadcasts and statistics are all per-bot.
Livegram does not publish a per-account bot limit. Telegram's own limit on how many bots one account may register with @BotFather applies to you regardless of Livegram. `
Yes. Pro is bought per Livegram account and removes the "This bot was created with @LivegramBot" label and the ads from every bot you own on the platform, for all of their users.
Livegram has no built-in account-to-account transfer. In practice you disconnect the bot from the old account, generate a fresh token in @BotFather with /token, and connect that new token from the other account. Your subscribers keep the same bot and the same chat, but the message history and subscriber list held by the old Livegram account do not travel with it.
Yes, at the Telegram level: in @BotFather send /mybots, select the bot and choose Transfer Ownership. The bot, its username and its token stay the same — only the controlling Telegram account changes. Telegram warns that this gives the other person full control, including the ability to read the bot's messages and delete it, and it cannot be undone.
No. Each bot has its own audience — the people who pressed Start on that specific bot — and broadcasts go to one bot's audience at a time.
A broadcast sends one message to everyone who has ever written to your bot. It is the way to announce a new product, a schedule change, or a promotion to the audience you built through the bot.
Only people who have pressed Start on your bot and have not blocked it. Telegram does not allow bots to message anyone else, so you cannot import a contact list or message people who found you elsewhere.
Yes, at least by interface language — Livegram keeps track of which language each user is on, so you can announce something to just your English or just your Russian audience. Some users also report an "every Nth user" option useful for A/B testing message wording. `
Broadcasts use the same message types the bot supports, so images and attachments work. Keep them light — a single clear image with a short caption performs better than a large file people have to download.
Delivery is paced to stay inside Telegram's limits, which allow a bot roughly 30 messages per second across all recipients. A list of a few thousand users takes a couple of minutes; ten thousand takes at least six. Telegram itself recommends spreading large broadcasts over several hours, so treat a broadcast as something that lands gradually rather than instantly.
Scheduled broadcasts are not a documented Livegram feature. `
Assume you cannot recall what has already been delivered — Telegram messages sent by a bot land immediately. Always send a test to yourself first by writing to your own bot from a second account.
Sparingly. Every broadcast that feels like spam costs you subscribers permanently, because blocking the bot is one tap and there is no way to reach that person again. Most successful bots broadcast no more than a few times a month.
No, as long as people opted in by writing to your bot and the content is relevant to why they subscribed. Sending unsolicited bulk messages, promotions to people who never asked, or anything phishing-related violates both Livegram's terms and Telegram's, and can get your bot removed.
The exact per-broadcast delivery report shown by Livegram is not documented. `
Basic but useful numbers: how many users your bot has and how many messages it is handling over time. This is enough to see whether your bot is growing and how heavy your support load is.
Open /mybots, choose the bot, and open its statistics section. Figures are per-bot, not aggregated across your account.
Data export is not a documented Livegram feature. If you need portable records, your admin chat in Telegram already holds the conversation — save or forward what matters from there.
The user count includes everyone who ever pressed Start, including people who have since blocked the bot or lost interest. That gap is normal, and it widens over time on every bot.
No. Livegram works entirely inside Telegram and sees only what the Telegram Bot API provides. There is no tracking pixel, no cross-site profile, and no data sold to third parties.
There is no documented integration, API or webhook for third-party tools. `
Three things. It removes the ads shown inside @LivegramBot for you; it removes the "This bot was created with @LivegramBot" label from every bot you own; and it removes ads from all your connected bots, for all of their users. It does not add features — the free tier already includes the full bot-building and messaging feature set.
| Period | USD | RUB |
|---|---|---|
| 1 month | $2.92 | 250 ₽ · 220 ⭐ |
| 3 months | $7.30 | 625 ₽ · 550 ⭐ |
| 6 months | $13.14 | 1125 ₽ · 990 ⭐ |
| 12 months | $23.36 | 2000 ₽ · 1760 ⭐ |
| The 12-month plan works out to roughly $1.94 per month, the cheapest per-month rate. |
Send /pro in @LivegramBot and choose a period. You can also subscribe on livegram.io. Both routes activate the same subscription on your account.
Credit or debit card and Telegram Stars inside the bot, and card payment on the website. Website orders are processed by Whop.
Stars are Telegram's own in-app currency, bought through the App Store, Google Play or @PremiumBot, and used to pay for digital goods inside Telegram. Choosing Stars in /pro charges your Stars balance rather than a card. Note that Telegram treats the purchase of Stars themselves as final and does not refund them; anything refundable is handled by Livegram and returns to your Stars balance, not to your bank.
Orders placed on livegram.io are processed by Whop, so your card statement and receipt may show the payment provider rather than Livegram or Krionit Lab. Purchases made inside @LivegramBot are paid by card or Telegram Stars.
Yes. Paid subscriptions renew automatically at the end of each billing period using the payment method on file. You can turn auto-renewal off at any time.
Turn off auto-renewal in your Livegram account, or use the subscription-management link in your payment receipt email. Cancelling stops all future charges immediately and takes effect at the end of the period you already paid for.
Nothing breaks. Your bots keep running exactly as before — the ads and the "This bot was created with @LivegramBot" label simply come back.
Generally no. Livegram is a digital service activated instantly on payment, so a billing period that has already started is non-refundable, including when you did not use it. There are two exceptions: a payment-gateway error that charged you twice for the same period and account, and a confirmed outage of paid features lasting more than 48 continuous hours through Livegram's own fault.
Email admin@livegram.io within seven calendar days of the problem occurring. Include the transaction ID and your payment receipt or order ID, plus a detailed description with screenshots. Support reviews the request within five working days; if approved, the money is credited back in three to ten working days.
No. Downgrades are not prorated or compensated; the new price simply applies from the next billing cycle onwards.
Don't. A chargeback filed without contacting support first is treated as a violation, and results in your account being permanently blocked, your bots deleted, and your payment details blacklisted. Contact admin@livegram.io first — genuine billing errors are the one case that does get refunded.
Any taxes applicable in your jurisdiction are added at checkout, so the final amount charged may differ from the listed price. The checkout shows the exact total before you confirm.
Per account. One subscription covers every bot connected to that Livegram account, which is what makes it worthwhile if you run several bots.
If a bot sits inactive or unpaid for 30 consecutive calendar days, Livegram reserves the right to disconnect that bot and delete its configuration from the service. Your Telegram chats — and the messages in them — are unaffected; reconnecting the bot later means setting it up again.
Ads are what pay for the free tier. Livegram sells advertising placements to its own audience, and that revenue is why building and running a feedback bot costs nothing. Livegram Pro removes them.
Yes, on the free tier your users encounter Livegram's ads and the "This bot was created with @LivegramBot" label. Buying Pro with /pro removes both for every bot you own and everyone who uses them.
Yes. Send /ads in @LivegramBot to buy a placement. Livegram has an audience of roughly 6 million users cumulatively, so it is a realistic channel for reaching Telegram bot owners and channel admins.
Pricing, formats and available slots are quoted through the /ads flow inside the bot, since rates depend on the placement and volume you want. Start there rather than relying on third-party resale listings, which may be out of date.
Your bot, your audience, your rules — Livegram does not take a cut of what you do with your own subscribers. You remain fully responsible for the legality of whatever you promote, and Livegram's prohibited-content rules still apply.
No. Ad selection is managed by Livegram. If you need full control over what your users see, Pro removes the ads entirely.
No. Livegram works purely as a proxy: messages travel between people inside Telegram, and Livegram simply relays them from one chat to the other. Content is forwarded automatically by software and is not collected, viewed, analysed or stored for review by any employee. The conversation itself lives in Telegram — in the user's chat with your bot and in your admin chat — and nowhere else.
The bot owner's Telegram ID — that is what authorization and account management run on — plus the technical configuration of your connected bots, such as the token you provide via /addbot so the service can operate them. Message content is not stored: conversations live in Telegram and nowhere else.
The messages themselves stay where Telegram put them — in the user's chat with your bot and in your admin chat — for as long as those chats exist. Livegram does not store message history at all: the only thing kept on its side is the bot owner's Telegram ID, used for authorization and account management. Your own Telegram chat is the record.
You are. As the person who created and runs the bot, you are the data controller for your end subscribers and are solely responsible for obtaining their consent to process their data. Livegram acts only as a technical processor working within the settings you configure.
Yes. Everything your users see comes from the bot — the bot's name, the bot's avatar, the bot's messages. Your account, username and phone number are never exposed to them by the service.
You see what any Telegram bot sees: their Telegram ID, first name, last name and username if set. You never receive their phone number or email unless they deliberately share it in the chat.
Livegram stores your token because it needs it to run your bot, and protects it with encrypted transport, restricted internal database access and security monitoring. Treat the token as a password on your side too: never paste it into unknown services, and revoke it in @BotFather if you suspect it leaked.
Livegram is operated by "Krionit Lab" LLC under the laws of the Kyrgyz Republic and states that it follows international data-protection standards. Full GDPR adequacy status is not claimed in the published policy. `
Personal information is not sold, exchanged or given to third parties for marketing. Two exceptions exist: payment data handled independently by the payment provider, and disclosures to Kyrgyz state authorities or courts made only on an official written request under applicable law.
Yes. Send a deletion request to admin@livegram.io and your account and associated personal information will be deleted within 30 working days. You can also request a copy of what is stored and demand corrections to inaccurate data.
Communication channels are encrypted in transit using secure protocols. Note that bot conversations in Telegram are ordinary cloud chats, not end-to-end encrypted secret chats — that is a Telegram platform property that applies to every bot on the network, not a Livegram choice.
Server locations are not published. `
Check three things in order: that the token you pasted is the current one from @BotFather, that no other service or script is running on the same token, and that you haven't deleted or revoked the bot in @BotFather. In most cases the token is the culprit.
Copy it again from @BotFather (/mybots → your bot → API Token) and make sure no space, line break, or invisible character came along with it. If it still fails, revoke the token in @BotFather to generate a fresh one and paste the new value. A revoked token stops working instantly, so anything using the old one must be updated.
Only one program may receive updates for a given token at a time. The moment a second service — another bot builder, a script, a webhook on your own server — starts on that token, one of them stops receiving anything, and the loser is usually whichever started first. Disconnect the other service entirely, then reconnect the bot in Livegram. If you are unsure what else is using it, generate a new token in @BotFather with /token and connect only Livegram to it.
Confirm the destination is still valid: if you connected a group, the bot must still be a member and an administrator there. If the group was deleted, the bot removed, or its admin rights withdrawn, delivery breaks silently. Reconnect the chat in /mybots, then test by writing to your bot from a second Telegram account.
The most common cause is that you typed a message instead of using Telegram's Reply on the forwarded one — without a reply, Livegram cannot tell who the answer is for. The second most common cause is that the person blocked your bot, in which case Telegram refuses delivery and nothing can be done from your side.
Telegram rejects messages to users who blocked a bot, so replies and broadcasts simply do not arrive for them. You will usually notice it as a growing gap between your total user count and your broadcast reach. There is no way to message someone again unless they unblock the bot and write to you first.
Your bot lives in @BotFather under the Telegram account that created it, so recovering the Telegram account is the only route back. Livegram support cannot restore control of a bot to a different account, because ownership is determined by Telegram, not by Livegram.
All of that is done in @BotFather, not in Livegram: /mybots → your bot → Edit Bot, where you can change the name, the description (up to 512 characters), the "about" text (up to 120 characters) and the profile picture. Changes take effect on Telegram's side within moments. Livegram controls the message texts your users receive, not the bot's Telegram profile.
No. Telegram does not allow a bot's @username to be changed after creation. If you must have a different one, create a new bot with @BotFather and connect the new token to Livegram — your existing subscriber list will not carry over.
Disconnect it from Livegram in /mybots, which stops Livegram from operating it. To delete the bot account entirely, use /deletebot in @BotFather. Deleting in @BotFather is irreversible and removes the bot from Telegram for everyone.
@BotFather describes /deletebot as permanently deleting the bot and freeing its username, but the freed username is released to everyone, not reserved for you. Telegram does not document how quickly it becomes claimable again. `
Disconnect the bot in Livegram, then revoke the token in @BotFather and issue a new one for your developer. Your users keep the same @username and the same chat, so nothing changes on their side. Note that the conversation history and subscriber list stored by Livegram do not transfer.
Telegram enforces rate limits on all bots — broadly around 30 messages per second overall and much less to a single group. Livegram paces sending to stay inside them, which is why large broadcasts take time. If a bot generates an abnormal load on Livegram's servers, its speed may also be throttled deliberately until the cause is resolved.
The Telegram Bot API limits what bots can move: 20 MB for a file the bot downloads, 50 MB for a file the bot sends, and 10 MB for a photo. Anything larger fails regardless of which service runs the bot. Ask the person to send a file-sharing link, or to send a large video as a document link rather than an upload.
Telegram Premium users can switch off receipt of voice messages and video notes, and Telegram then refuses delivery to them specifically. There is nothing to fix on your side — reply with text or a file to that person instead.
That is a Telegram enforcement decision, usually for spam or prohibited content, and Livegram cannot reverse it. Telegram's bot-developer terms reserve the right to restrict a bot with no advance notice, compensation or explanation, and there is no documented appeal process — @BotSupport is the usual place to ask, but nothing is guaranteed. Livegram's terms place actions by Telegram outside its responsibility, and such events do not qualify for a refund.
Livegram may suspend an account and disable its bots immediately, without notice or refund, for violating the User Agreement. If you believe this was a mistake, write to admin@livegram.io with your account details and an explanation. Note that funds for the unused remainder of a subscription are forfeited when a block is the result of a genuine violation.
Send /feedback in @LivegramBot or email admin@livegram.io. Include your bot's @username, what you expected, what actually happened, and a screenshot — that trio resolves most cases in a single reply.
Spam and unsolicited bulk messaging, phishing, fraud, pyramid schemes, illegal lotteries and casinos, the sale of prohibited or restricted goods including drugs, weapons, counterfeits and pornography, collecting third parties' personal data without their consent, content promoting violence, terrorism or discrimination, copyright infringement, and distributing malware. Breaking any of these can get your account and bots removed without notice or refund.
Telegram's published guidance is: no more than about one message per second to a single chat, no more than 20 messages per minute in a group, and no more than roughly 30 messages per second when broadcasting. Exceeding them gets the bot temporarily throttled by Telegram. These are Telegram's limits, not Livegram's, and they apply to every bot on the platform.
Yes, if it has to. If a bot puts an abnormal load on the servers — for example mass mailings beyond the established limits — Livegram may restrict its speed or block it temporarily until the cause is resolved.
Entirely. Livegram is a passive technical provider that does not select recipients, initiate messages, or pre-moderate content. All civil, administrative and criminal liability for the content, actions, goods and services offered through your bot rests with you, including copyright clearance for anything you upload.
The terms state the service is intended for commercial, professional or entrepreneurial use, and are not governed by consumer-protection law. Nothing stops a personal project technically, but you should read the User Agreement with that framing in mind.
Yes — Telegram's terms of service apply on top of Livegram's, and Telegram enforces them independently. A bot can be perfectly acceptable to Livegram and still be removed by Telegram, which is why the safest approach is to satisfy both rulebooks.
Email admin@livegram.io with the offending bot's @username and evidence such as screenshots. Serious cases involving illegal content should also be reported to Telegram directly.
Yes. The full bot-building and messaging feature set — connecting bots, receiving and answering messages, team chats, broadcasts and analytics — costs nothing, and no card is needed to start. The service is funded by advertising, which is why the free tier shows Livegram's ads and the "This bot was created with @LivegramBot" label.
No. Livegram is independent software and is in no way affiliated with, associated with, authorized or sponsored by Telegram FZ-LLC. It is built on Telegram's public Bot API, the same way any third-party bot is.
"Krionit Lab" LLC, registered in the Kyrgyz Republic, at Office 5, Building 18, Klubny Lane, Pervomaisky District, Bishkek. TIN 00502202610356. The contact address for all enquiries is admin@livegram.io.
The interface is multilingual — send /lang in @LivegramBot to change yours. You can also set the language of the texts your own users see, and Livegram keeps track of which language each of your users is on so you can address them separately.
Yes. Livegram supports separate texts per language, and incoming conversations can be organised by language so you can broadcast to one language group at a time. This is genuinely useful for anyone running an international channel.
Write to our support bot @LivegramSupportBot for product and technical questions, or email admin@livegram.io. For billing questions, include the order ID from your payment receipt — it speeds things up considerably.
| Command | What it does |
|---|---|
/start |
Start working with @LivegramBot |
/addbot |
Connect a new bot using its @BotFather token |
/mybots |
Manage your connected bots |
/pro |
Buy or manage the Livegram Pro subscription |
/ads |
Buy advertising placements |
/lang |
Change the interface language |
/help |
Built-in reference |
/feedback |
Contact support |
Around 6 million people have used @LivegramBot cumulatively, with more than 500,000 active according to the website, and over 131,000 bots have been created on the platform. That makes it one of the most widely used feedback-bot builders on Telegram.
No. The service is provided "as is" and "as available", with no warranty of uninterrupted or error-free operation. Livegram also depends on Telegram's own availability, which is outside anyone's control.
The platform is built on Telegraf.js, a well-established Node.js framework for the Telegram Bot API. In day-to-day use this is invisible to you — everything is configured through chat.
If a bot is inactive or unpaid for 30 consecutive calendar days, Livegram may delete it and all associated data, including message history and subscriber lists, from its servers. Keep this in mind before pausing a project you intend to return to.
The User Agreement is governed by the legislation of the Kyrgyz Republic, and unresolved disputes go to the competent court at the operator's place of registration. Both parties are expected to attempt to settle disagreements through negotiation first.
Two ways in. Pick the one that matches your question and you will get an answer faster.
Write to our support bot @LivegramSupportBot — the fastest route for anything about how the product works: connecting a bot, replies not arriving, broadcasts, team chat setup, analytics, language settings. Before you write, /help in @LivegramBot answers the most common questions instantly.
Receipts and refund requests under the Refund Policy · questions about the Terms of Service · access, correction or deletion of your data under the Privacy Policy. For billing, include the order ID from your payment receipt. Please contact us before opening a chargeback — nearly every billing problem is fixable in one email.
Free products are paid for somehow. Ours is paid for by advertising, and we would rather explain it than bury it. On the free plan, ads appear inside @LivegramBot and inside the bots you connect, and every bot carries the label "This bot was created with @LivegramBot." That advertising revenue funds the infrastructure that keeps the builder free for everyone else. If you do not want that, Livegram Pro removes all of it. Advertisers can book placements by sending /ads to @LivegramBot.
We do not read your conversations. Livegram works purely as a proxy: messages travel between people inside Telegram, and the service only relays them from one chat to the other. Your correspondence lives in Telegram — in the user's chat with your bot and in your admin chat — and nowhere else. The only thing Livegram stores is the bot owner's Telegram ID, used for authorization and account management.
Livegram is independent software. It is not affiliated with, associated with, authorized, endorsed by, or sponsored by Telegram FZ-LLC or any of its subsidiaries. Livegram is built on Telegram's public Bot API and depends on that platform's availability.
Full legal documents — click to expand.
Last updated: July 1, 2026
This User Agreement, hereinafter referred to as the Agreement, is concluded between "Krionit Lab" LLC, a legal entity registered in accordance with the legislation of the Kyrgyz Republic, hereinafter referred to as the Operator, and any individual or legal entity that accesses and uses the Service, hereinafter referred to as the User.
Please read the text of this Agreement carefully. Registration on the website, launching the bot, or any use of the Service constitutes your full and unconditional consent to the terms of this Agreement. If you do not agree with the terms, you must immediately cease using the Service.
The Service is provided exclusively as a neutral technical tool. The Service allows Users to automate the receipt and sending of messages in the Telegram messenger.
The Service is intended exclusively for use within commercial, professional, or entrepreneurial activities. The terms of this Agreement are not regulated by consumer protection laws.
The Operator acts exclusively as a passive technical provider. The Operator does not initiate the transmission of messages, does not select the recipients, and does not perform preliminary moderation of the content passing through Users' Sub-bots. The Operator does not have technical access to the private correspondence of end users, and does not track, view, or store the content of messages passing through the Service.
The entire completeness of civil, administrative, and criminal liability for the content, actions, goods, or services sold through the Sub-bots lies exclusively with the User who created the respective Sub-bot.
The Service does not store the content of messages passing through Sub-bots. Messages are exchanged between Telegram users and remain solely within the Telegram platform; the Service acts exclusively as a technical relay. On its side, the Service stores only the User's Telegram identifier, used for authorization and account management, together with the technical configuration of connected Sub-bots.
The Operator has the right to unilaterally disconnect the User's Sub-bot and delete its configuration from the servers in the event of inactivity or lack of tariff payment for thirty consecutive calendar days. The Operator is not liable to the User or third parties for the consequences of such deletion.
In the event of a violation of the Agreement terms, the Operator reserves the right to immediately block the User's account and disable their Sub-bots without refunding the cost of paid subscriptions and without prior notice, as well as to transfer information to competent state authorities upon their lawful request.
The Service provides free features, as well as paid subscriptions that grant access to premium features under the name PRO. Current tariffs are published on the Service's website.
The order processing is carried out by the merchant of record Whop. Whop is the official merchant for all placed orders. Whop handles all customer support inquiries related to payments and issues refunds. All payment transactions, subscription management, and financial settlements are securely processed through Whop in accordance with their terms of service and privacy policy.
By purchasing a paid subscription, the User agrees to automatic recurring deductions of funds according to the selected billing period, either monthly or annually. The User can cancel the subscription auto-renewal at any time through their Personal Account.
Funds for an already paid subscription billing period are non-refundable. In case of subscription cancellation, it remains active until the end of the paid period. All taxes, fees, and duties, including value-added tax applicable to the purchase, are calculated and collected by the Payment Agent in accordance with the User's jurisdiction.
The Service is provided on an "as is" and "as available" basis. The Operator makes no warranties regarding the uninterrupted operation of the Service or the absence of errors.
The Service is independent software and is in no way affiliated, associated, authorized, or sponsored by Telegram FZ-LLC or its subsidiaries. The Service directly depends on the technical capabilities, stability, and availability of the Telegram messenger and its software interface.
The Operator is not responsible for any actions of the Telegram messenger administration, including changes to its software code, closure or modification of technical data transfer methods, the introduction of limits, platform suspension, or the complete blocking or deletion of the User's chatbots and accounts by Telegram. Such events are recognized as force majeure circumstances, are not the fault of the Operator, and do not give the User the right to demand a refund.
The Operator is not liable for technical failures on the part of hosting providers, the Payment Agent, or Internet providers that may affect the Service's performance. Under no circumstances shall the Operator, its directors, employees, or partners be liable for any indirect damages, including loss of profit, data, or business reputation, arising from the use or inability to use the Service.
All intellectual property rights concerning the design, software code, algorithms, logos, and interfaces of the Service are protected by law. The User is granted a limited, revocable, non-exclusive right to use the Service in accordance with its intended functional purpose. The User has no right to copy, decompile, modify, or attempt to extract the source code of the Service.
This Agreement shall be governed by and construed in accordance with the legislation of the Kyrgyz Republic. The Parties shall endeavor to resolve all disputes and disagreements arising from this Agreement through negotiations. If pre-trial settlement is impossible, the dispute shall be submitted to the competent court at the place of the Operator's registration.
The Operator reserves the right to unilaterally make changes to this Agreement. The updated version of the Agreement takes effect from the moment of its publication on the website www.livegram.io. Continued use of the Service after the publication of changes constitutes the User's agreement to the new version of the Agreement.
"Krionit Lab" LLC
Legal address: Office 5, Building 18, Klubny Lane, Pervomaisky District, Bishkek, Kyrgyz Republic
TIN: 00502202610356
Email for inquiries, complaints, and official requests: admin@livegram.io
Last updated: July 1, 2026
This Privacy Policy determines the procedure for processing, storing, and protecting personal information that "Krionit Lab" LLC (hereinafter referred to as the Operator), registered under the laws of the Kyrgyz Republic, receives from individuals and legal entities (hereinafter referred to as Users) during the use of the website www.livegram.io and the integrated Telegram bot @LivegramBot (collectively referred to as the Service).
The use of the Service constitutes the User's unconditional consent to the terms of this Privacy Policy. In case of disagreement with the conditions for processing information, the User must immediately cease using the Service.
The Operator processes Users' information in accordance with the legislation of the Kyrgyz Republic on personal data, international data protection standards, and based on the User Agreement concluded between the Operator and the User.
To ensure the operation of the Service, the Operator collects and processes only the information necessary to fulfill its obligations to the User. The User's personal information includes the following data:
During the operation of the Service, there is a clear separation of responsibility for processing the data of end users interacting with the Sub-bots:
The User who creates and administers the Sub-bot is recognized as the sole personal data operator for their end subscribers. The User is solely responsible for obtaining their subscribers' consent to process their data.
The Service Operator acts exclusively as a technical data processor. The Operator processes end users' information solely on behalf of the User and within the algorithms set by the User in the Service settings.
Since the Service operates based on the Telegram messenger software interface, the User acknowledges that data collection and processing are also governed by Telegram's official privacy policy, over which the Service Operator has no control.
The Operator processes Users' information exclusively for strictly defined purposes:
The Operator does not sell, exchange, or transfer Users' personal information to third parties for marketing or commercial purposes. The transfer of Users' information is permitted only in the following strictly defined cases:
The Operator retains the User's personal information for the entire duration of the User's account and the period of using the Service.
The Service does not store the content of messages. On its side, the Service stores only the User's Telegram identifier, used for authorization and account management, together with the configuration of connected Sub-bots.
The Operator has the right to disconnect the User's Sub-bot and delete its configuration from the servers in the event of inactivity or lack of tariff payment for thirty consecutive calendar days.
The User retains full control over their personal data and has the right to exercise the following options:
The Operator takes all necessary organizational, technical, and legal measures to protect the User's personal information from unauthorized or accidental access, destruction, modification, blocking, copying, and distribution by third parties.
Data protection measures include encryption of communication channels, secure data transfer protocols, restricting Operator employees' access to server databases, and continuous monitoring of security systems.
The Operator reserves the right to unilaterally make changes to this Privacy Policy. The new version of the Privacy Policy takes effect from the moment of its publication on the website www.livegram.io. Continued use of the Service after the publication of changes constitutes the User's agreement to the updated terms.
"Krionit Lab" LLC
Legal address: Office 5, Building 18, Klubny Lane, Pervomaisky District, Bishkek, Kyrgyz Republic
TIN: 00502202610356
Email for inquiries regarding data processing, information deletion, or complaints: admin@livegram.io
Last updated: July 1, 2026
This Refund Policy is an integral part of the User Agreement and establishes the exhaustive conditions for refunding payments for paid services provided by "Krionit Lab" LLC (hereinafter referred to as the Operator) within the use of the website www.livegram.io and the integrated Telegram bot @LivegramBot (collectively referred to as the Service). By making a payment for a subscription to the Service, the User confirms their full agreement with the terms of this Policy.
The process of order handling, tax withholding, and accepting payments for paid Service subscriptions is carried out by the international merchant of record, Whop. Whop acts as the official Merchant of Record for all transactions made on the Service platform and bears direct financial responsibility for their execution. All actual refund operations to the User's bank card, e-wallet, or other payment instrument are carried out exclusively through the secure Whop payment gateway in accordance with their internal rules, interbank clearing timeframes, and security standards.
The Service provides Users with intangible digital services consisting of providing software as a service (SaaS). Access to the premium features of the Service is granted to the User automatically and instantly after payment confirmation. Due to the immediate nature of the provision of digital services and the impossibility of their physical return, funds for an already paid and commenced subscription billing period, whether it is a monthly or annual billing cycle, are non-refundable.
The access service is considered to be provided by the Operator properly and in full at the moment of successful payment and activation of the corresponding status of the User's account in the Service database. The User has no right to demand a refund on the grounds that they did not use the paid features of the Service, did not launch the created Sub-bots, did not send messages, or did not log into the Personal Account during the paid period. Payment is charged for the fact of providing access to the functionality, and not for the actual time of its use.
When subscribing, the User agrees to automatic deduction of funds at the beginning of each new billing period. The User has the right to cancel the automatic recurring renewal of a paid subscription at any time. Cancellation can be done independently through a special subscription management section in the Service's Personal Account or by using a secure link in the email receipt received from Whop upon payment.
In case of subscription cancellation, the automatic deduction of funds for all subsequent billing periods ceases immediately. Subscription cancellation does not entail a recalculation or refund of funds for the current, already paid period. After cancellation, the User retains full and unlimited access to all paid premium features of the Service up to and including the last minute of the current billing cycle.
If the User decides to switch to a cheaper tariff plan or opt out of some additional paid options before the expiration of the current billing period, the difference in tariff costs is not compensated and is not refunded to the User's bank card. The new tariff conditions take effect from the next billing cycle.
If the User's account or their Sub-bots have been blocked, restricted in access, or completely deleted by the Operator for violating the rules of the User Agreement, sending spam, fraudulent actions, or other illegal activities, the funds for the unused remainder of the subscription are forfeited. Refunds to violators of the User Agreement are strictly not issued under any circumstances.
The Operator urges Users to resolve any financial disagreements exclusively by contacting the official customer support of the Service. If the User initiates a forced refund procedure (chargeback) through their issuing bank or payment system (e.g., PayPal), bypassing the support service of the Operator or Whop, the Operator regards this as a violation of financial discipline and potential fraud.
Upon receiving a chargeback notification, the Operator has the right to immediately and irreversibly block the User's account, delete all their Sub-bots, and add the User's payment details to an internal blacklist to prevent future purchases.
The Operator may initiate a refund through the Whop platform exclusively by individual decision of the support service in strictly limited cases. Such cases include:
Refunds are not provided if the malfunctions are caused by the actions of the Telegram messenger (including token blocking, API changes, messenger server crashes) or problems on the side of the User's internet provider.
To consider an exceptional case, the User must send a motivated written request to the official email address of the support service within seven calendar days from the moment the problem occurs. The request must necessarily include the unique transaction identifier, receipt number, or Invoice ID issued by the Whop platform, as well as a detailed technical description of the reason for the refund request with attached screenshots.
The processing time for the request by the Operator's support service is up to five working days. If the refund is approved by the Operator, the actual crediting of funds to the User's account takes from three to ten working days, depending on the regulations of the Whop platform and the issuing bank of the User's card.
"Krionit Lab" LLC
Legal address: Office 5, Building 18, Klubny Lane, Pervomaisky District, Bishkek, Kyrgyz Republic
TIN: 00502202610356
Email for sending refund requests and resolving billing issues: admin@livegram.io