Suprr - Customer support directly from Telegram
by•
An easy to install customer support bubble for your website that sends customer conversations to your Telegram. Tailored to small teams, respond to your customers’ requests right from Telegram, 5 min to integrate
Replies
ColdHunt
ColdHunt
@eric_ukeje The primary use case for this is customer support for smaller teams who don't want to manage the complexity of other tools (like Intercom for example) and want a simple, minimalistic on-the-go tool
IMO having Telegram as the single inbox makes life way simpler for a tiny team. I was using a makeshift Telegram workflow last year and it reduced our response time by half, so this is actually useful. Curious how they handle multi-agent context switches though, does it thread per user? It have saved me from juggling multiple tabs, so I'm keen to try the open-source self-hosted option.
ColdHunt
@shaxxd Thanks for your interest in Suprr! It's targeting small teams so there's no real agent switching yet, what it does is it creates a telegram thread in your group for each new user, and then anybody can reply to them
Nice UI, just what small teams need, IMO. The multi-language support seems handy; last holiday season we had customers in 6 locales and it was messy to route messages. My question is about edge cases: what happens if Telegram is down or blocked in some country, is there a fallback channel? Also wondering if there’s built-in tagging / SLA tracking or you rely on external tools. One tiny nit: the 5 min claim sounds optimistic, it'll depend on your webhook and DNS setup, but I'm intreiged
ColdHunt
@lyndsay_h There's no fallback, but your customers also don't need Telegram, Telegram is only used by you and your team as a CRM to answer your customers' questions. Your customers then receive the answers in the chat bubble on your website and on their email. The 7 minute integration time that's mentioned on the website is not for self hosting, but for setting up Suprr that's hosted by us :)
tbh I really like the 7-minute integration claim, seems tuned for non-technical founders. I self-hosted a similar stack before to keep control over user data and avoid vendor lockin. Quick question — how do you handle localization edge cases when a user's device language isn't set or is unsupported? The open-source angle is huge for us, and I'd love a docker-compose example or helm chart. Also, any known latency hit when bridging via Telegram for high traffic sites?
ColdHunt
@sherryje Thanks for the question, the fallback language is English in case the users' one is not supported. We have everything to host it with Docker, though no docker-compose yet :(
Telegram API is a reliable software that's powering gigantic projects so there should not be any latency problems even for bigger sites!
Interesting product, TBF I need more detail on privacy. Did you tested GDPR / data retention flows for the email fallback and message storage? My small store used Telegram + email for async replies and we ran into issues mapping emails back to sessions during refunds. Also LMK if there’s an API for exporting conversations or adding custom fields for order IDs. Overall curious, but the privacy/data flow is my main blocker.
I think you should build a npm package. A react package. If you don't have before
Do you have plans to expand this to other messaging apps (like WhatsApp) later on? A lot of small teams (especially those targeting global freelancers) use WhatsApp as their go-to comms tool, so being able to pick between Telegram and WhatsApp would make this even more flexible. Also—any thoughts on adding canned response shortcuts directly in the Telegram chat? That’d let them fire off quick answers to common questions (like “how do I reset my password?”) without typing the same thing 10 times a day.