This is the part nobody tells you: your support bot came from @BotFather, so it's yours. Moving from Livegram to EzSuppBot means pointing that same bot at a different dashboard. Same @handle, same subscribers, same chat history on their side. Your customers notice nothing.
Only one service can poll a bot at a time. Telegram hands each update to whoever asks first, so if Livegram and EzSuppBot are both running your bot, messages will appear in one dashboard or the other at random. Nothing is lost, but it's confusing.
So: get set up here first, then remove the bot from Livegram (or stop its bot there), and you're clean. If you'd rather test without touching production, make a second bot in @BotFather, connect that one to EzSuppBot, and try it side by side before you move the real one.
Your ticket history inside Livegram stays with Livegram — we can't read their database. If you need those transcripts, export them there before you cancel.
Volume, usually. Livegram forwards messages to admins and stops there — no ticket history, no AI, no team roles. Once more than one person answers, or once you want the same twenty questions answered without you, you've outgrown it. EzSuppBot keeps the same bot and adds the desk around it.
We're not affiliated with Livegram. Nothing here connects to their service or touches your account with them — you're simply pointing your own bot somewhere else.