A free-forever contact layer for the "first 100 users" stage
Hey Indie Hackers đź‘‹
I've been working on Knocket — a 100% free contact layer built for the exact stage most of us are in: still hunting for the first 100 users, and every visitor who shows up on the landing page matters.
 Why I built this
Every “cheap” chat tool eventually gates you: it shows ads, charges per seat, and is designed for support teams with ticket queues. What I actually needed was:
 - A live chat widget on my landing page
 - A contact page I could paste into my Twitter bio
 - One inbox that catches everything — including messages coming through Telegram/Email
 - Something I could reply to from Telegram, without opening yet another dashboard
 None of the free options did all four. So we built it.
 What it does
 - Live chat widget: one line of <script> on your site
 - Mobile Widget: embed via WebView in iOS / Android / Flutter / React Native apps
 - Shareable contact page (Linktree-style with socials + booking links + blog)
 - Unified inbox: Live Chat, Telegram, Email — all in one place
 - Reply directly from Telegram — no context-switch, no dashboard
 - Companion open-source AI auto-reply agent (github.com/fangxinmoon/knocket-inbox-agent-EN)
 Free forever, and here's why
 Full disclosure: Knocket is built on top of Tencent RTC infrastructure. The goal isn't standalone monetization — it's giving indie makers a real free contact tool while Tencent RTC's paid business lives elsewhere. So no ads, no seat limits, no paid tier — because there isn't one to upsell you to.
 One thing I want feedback on
 The unified inbox routes three channels (Live Chat / Telegram / Email) through one webhook, then dispatches replies back through the original channel. If you've built or hated multi-channel inboxes before — what did we get right? What did we miss?
 Landing page: https://trtc.io/solutions/knocket
 Longer technical writeup: https://dev.to/maryinging/knocke-connect-with-customers-online-with-just-one-click-1bhb
Would love to hear if this fits into your stack, and any use case I haven't thought about.
 Disclosure: I'm on the Knocket team.
