Show HN: Syntro.io
syntro.io
TLDR: Some time ago we started providing Slack connect support to our own customers and we ended up building a simple Slack app for this. The goal was to have an AI embedded in the Slack connect channels to help us answer questions and solve support tickets. We then built it as a separate product namedSyntro (https://syntro.io).
The background: we and many of our customers noticed the same pattern of support requests increasingly coming in through Slack Connect channels. It’s faster and more natural for customers than opening a Zendesk or Email ticket. But it creates visible problems such as:
Having no structure - so there are messages scattered across threads and DMs. Manual overhead - like copying into another ticketing/product feedback system.
We wanted to turn Slack itself into a support platform, and we found some alternatives in the market but they were a bit expensive and over complicated - so, knowing that at DailyBot we’re quite expert on Slack integrations - why not build it out?
Syntro does five things very well:
* Detects new requests in Slack by turning threads into tickets automatically. * Maintains a board (kanban/list) for prioritization and tracking via web app. * Suggests replies from your knowledge base or past tickets (you edit before sending). * Keeps Slack and the ticket board in sync, so agents can work in either. * Broadcast feature for announcements to multiple Slack Connect channels.
Technically, the tricky parts were:
1. Thread detection & context sync: Slack messages aren’t structured like tickets. We had to build logic to consolidate messages into coherent “requests.” 2. Two-way sync: Ensuring replies in Slack update the ticket system (and vice versa) without duplication. 3. Knowledge base ingestion: We support file uploads + URLs, then use embeddings for AI reply suggestions. 4. Slack Connect quirks. Permissions and visibility differ across shared channels; making the app feel native took time.
Current stack: Django backend, Next.js frontend, Postgres (with pgvector) for embeddings, Redis for state, LangChain + OpenAI/Claude for LLMs, and a Python bot for Slack integration.
Limitations / things we’re still working on: - Better SLA tracking and reminders. - More granular analytics for managers. - Expanding to email perhaps.
We may open source it in the future - we have to clean up code first and decouple it from some DailyBot underlying infrastructure.
Product + demo here: https://syntro.io (completely free for launch)
We’d love your feedback - especially from folks who’ve hacked together their own Slack support workflows. What’s missing? What’s overkill? What do you wish someone had built instead?
Thanks HN, Mauricio