Kept seeing the same problem: small businesses on Telegram drowning in repetitive customer questions, but no clean solution that doesn't require a developer.
So I built Pulso Bot. The twist: each client gets their own named bot via BotFather — not a shared widget. Their customers see "ShopBot", not "Pulso Bot."
How it works technically
- My server manages multiple client bot tokens simultaneously
- Each bot is isolated — FAQ, analytics, subscription, handoff state all per-token in Supabase
- Claude Haiku reads the FAQ and answers in the customer's detected language (Unicode-priority for Hebrew/Arabic — langdetect alone fails on short phrases)
- After 2 failed answers → human handoff with full conversation history sent to the owner
- Voice messages transcribed via Whisper before hitting the same pipeline
Stack
Python, python-telegram-bot, Claude Haiku, Whisper, Supabase, Railway
Monetization
Telegram Stars subscriptions (auto-renewing) — no Stripe, no credit cards, everything inside Telegram. 250⭐/mo for 300 replies up to 1000⭐ for unlimited.
Still figuring out distribution. Product is live at pulso.tools, 14-day trial.
Top comments (0)