Chat.sh

Chat.sh is a help center that answers the question instead of handing back a list of titles. You type your question in your own words, and the AI search reads it, retrieves the relevant passages, writes the answer, and shows the pages it used. It is built for teams that need a public help center for their product and want it served on their own domain — either as a custom domain such as help.yoursite.com, or in a folder on the site they already run, such as yoursite.com/help. The product exists because its maker was a longtime Intercom customer until Intercom's help center search broke. The fix did not come fast enough, so he built his own. The frustration he describes is familiar to anyone who has run support documentation: most help centers give you a subdomain, a keyword search, and a monthly bill, and the old stack hands every team the same URLs, the same search, and the same page with a different logo on it. When a keyword index is handed the word "domain", it returns five titles that all contain that word rather than the one page that answers the question. Chat.sh is a deliberate response to that fixed format. The centrepiece is search that reads the question. A model retrieves the relevant passages from the knowledge base and writes an answer, then displays the pages it used, so the reader can verify where the answer came from. Answers come from published articles only, which keeps the output grounded in documentation the team has actually written and approved. The result is closer to a colleague answering than a search box listing: instead of a list of titles the reader must open one by one, they get the answer directly, with its sources attached. Underneath sits one knowledge base that feeds three ways of answering. Content goes in once as articles, web links, files, or TXT and markdown, and the help center, the messenger, and the markdown you hand to an AI assistant all come from that same source. The help center is a public site that answers rather than handing back a list of titles, reachable at yoursite.com/help, help.yoursite.com, or your-team.chat.sh. The chat messenger, shipping next, puts the same answers in a widget on your app so a stuck customer never has to leave the page they are stuck on; each AI reply in it uses one credit from the monthly allowance. The AI agent side lets you copy any page as markdown, view it as plain text, open it directly in ChatGPT or Claude to ask questions about it, or copy every published article at once for pasting into AI tools, and an agent can also start from llms.txt. Presentation is treated as part of the product. You can name a folder — /guide, /help, or whatever you call it — and the help center is served from there on the domain you already run, keeping the same domain and the same analytics with no subdomain to explain. If you prefer, you can point a domain you own at the help center instead. Article addresses are written for people: there is no numeric id wedged into the path, and the slug is the title and is yours to change. Each page draws its own preview card, so a link dropped in Slack arrives as the article rather than as your logo, and theming lets you pick the accent and the mark. Every page follows that choice and stays readable, because the colour is darkened until it is. Put together, the product's approach is to treat support content as a single source that is published to several surfaces rather than as a website bolted onto a subscription tool. You maintain one knowledge base; Chat.sh answers from it in a help center on your own domain or in a folder on your existing site, will answer from it inside an app widget, and exports it as markdown for assistants such as ChatGPT and Claude. Nothing is duplicated per channel, and the answer always cites the pages it drew on. The benefits follow from those choices. Readers get answers instead of search results, with the sources shown so they can check them. The help center lives on a domain the team already owns, so it inherits existing analytics and needs no new subdomain to explain to anyone. Documentation becomes usable inside AI tools through markdown export and llms.txt. And commercially, the product is bought once rather than rented: your own domain is $399 once, never a subscription, and the price rises by $100 each time a new capability ships, so buying early costs the least. Concrete uses follow the same shape. A team that wants docs at yoursite.com/guide names the folder and publishes there, keeping the help center alongside the rest of the site. A team that prefers a dedicated address points a custom domain at it. A support lead drops an article link into Slack and the preview card carries the article itself. A developer copies a page as markdown and opens it in ChatGPT or Claude to ask follow-up questions, or copies the whole help center into an AI tool. Live examples cited in the content are testimonial.to/guide and chat.sh/help. Chat.sh is free for 50 pages and 100 AI answers a month with no card required. Every price tier includes the help center, 1,000 pages and 1,000 AI credits a month per workspace; one credit is one answer, here or in the messenger, and when the month's credits are gone, 1,000 more cost $20 as a one-time purchase. Page counting is defined rather than vague: a link counts as one page for every 2,500 characters of its text, an article you write counts as one page, and a PDF counts as one page per page of the file. The lifetime deal adds your own domain, bigger ceilings, and your agents. The chat messenger is shipping next and the inbox is shipping after it; the inbox lets teammates take over a conversation, with three people per workspace and each person after that at $10 a month, and human replies do not use AI credits. Launch-day buyers get $200 off any lifetime deal with the code PHLAUNCH, taking $399 to $199 and $799 to $599, until October 2 at 12 AM PT. Chat.sh's value proposition is narrow and clear: a help center whose search answers the question and cites its sources, hosted on your own domain or in a folder on the site you already run, with the same knowledge base exported as markdown for AI assistants — and paid for once rather than every month.