Product Thumbnail

Suprr

Customer support directly from Telegram

Telegram
Customer Communication
GitHub

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

Top comment

Hey there! Thanks for checking out Suprr! During one of my previous ventures I found that people love having a little CRM within Telegram for handling customer support - so I decided to fully focus on this aspect of the product. That's why I'm building Suprr - to allow small teams to handle their support tickets gracefully, without bloated CRMs and unnecessary complexity :) I have already launched some time ago with a waitlist and after now I'm happy to say it's now up and running!

Comment highlights

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.

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?

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

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.

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.

@artemy_medvedev Congrats on the launch! Really love the clean vibe — especially the Telegram-based customer support angle. One thing I noticed while checking it on mobile: some sections have a bit of spacing/layout inconsistency and the chat bubble overlaps content in a few spots. Totally normal for early launches, and if you ever explore more mobile polish or edge-case testing, I’ve worked on a lot of similar setups and happy to share a few insights. Great work so far!

I think you should build a npm package. A react package. If you don't have before