Launched this week

Chat.sh
The help center I built after Intercom's search broke
107 followers
The help center I built after Intercom's search broke
107 followers
🎉 Launch day only: $200 off any lifetime deal with code PHLAUNCH ($399 → $199, $799 → $599). Ends Oct 2, 12 AM PT. Most help centers give you a subdomain, a keyword search, and a monthly bill. chat.sh is different: 🔍 AI search that writes the answer and cites the pages it used 📁 Lives in a folder on your own site (yoursite.com/help) 🤖 Every page as markdown for ChatGPT, Claude, and llms.txt 💸 Pay once, no subscription Try it at chat.sh/help. Chat messenger and a support inbox are next.








@damonchen such a cool name, and yes this was ripe for disruption. Congrats on the launch.
@socodemaker Thanks for the support.
@damonchen I love this story, congrats on your launch!
@damonchen Congrats, Damon! If a team hits their monthly AI credit cap during a traffic spike, does search fall back to direct semantic lookup or can credits be topped up?
Congrats Damon!
@german_merlo1 Thanks for support!
the yoursite.com/help part is the detail I'd want to understand before buying a lifetime deal. is that a reverse proxy you run that serves live from chat.sh, or does it actually write static files into my site's repo/folder? makes a real difference for what happens to my help center years from now if chat.sh the company doesn't make it - static files I own outright are a very different risk than a proxy pointed at someone else's server.
@galdayan short answer: reverse proxy, not static files in your repo.
You add one rewrite rule to whatever sits in front of your domain — a vercel.json entry, a Cloudflare Worker, an nginx block. We generate the snippet. It forwards /help to your help center, path unchanged. The rule lives in your infra, so you can delete or repoint it in thirty seconds without asking me.
On the risk you're actually pricing: your content isn't locked up. Articles are Markdown, each one addressable at /help/articles/your-slug.md, and /help/llms.txt indexes every article URL. A short wget loop gives you the whole help center as .md files any day, no cooperation from me needed.
So the bad case isn't "my help center is gone." It's "I repoint the rule and serve the Markdown I already have" — and since the proxy never rewrites paths, anything serving the same /help/articles/slug URLs keeps your links and rankings intact.
Happy to show you the generated snippet for your stack first.