This is the part nobody tells you: your support bot came from @BotFather, so it's yours. Moving from Mava 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 Mava 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 Mava (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 Mava stays with Mava — we can't read their database. If you need those transcripts, export them there before you cancel.
Focus. Mava is a capable multi-channel tool, and if you need Discord and Slack too it's the right choice. If all your support happens on Telegram, EzSuppBot is less to configure and less to pay for, with AI included in a flat price.
We're not affiliated with Mava. Nothing here connects to their service or touches your account with them — you're simply pointing your own bot somewhere else.