This is the part nobody tells you: your support bot came from @BotFather, so it's yours. Moving from SUCH 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 SUCH 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 SUCH (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 SUCH stays with SUCH — we can't read their database. If you need those transcripts, export them there before you cancel.
Almost always the AI. SUCH bills AI as separate per-use credits you top up, so every reply is a small decision about whether it's worth spending one. EzSuppBot includes 10,000 AI responses a month in the flat £9.99 Pro price — and unused ones bank forever — plus a knowledge base that trains the AI on your own FAQs and smart escalation that pauses the AI and pings a human when someone says "refund" or "urgent". Our free plan also includes 50 AI replies a month, which SUCH's free plan doesn't offer at all. SUCH is a good product with a longer track record and 37,000+ bots behind it; we're the cheaper, AI-included option.
We're not affiliated with SUCH. Nothing here connects to their service or touches your account with them — you're simply pointing your own bot somewhere else.