Chat.sh

Chat.sh is a help center that answers questions instead of simply returning a list of titles. According to the website, search reads the question and answers it, with the pages it used. It can be served on your own domain, or in a folder on the site you already run. The product is presented as a help center built after Intercom's search broke, and it is aimed at teams that want a public support site, an AI search experience, and content that AI assistants can consume. The main purpose is to let visitors ask anything in their own words and receive an answer drawn from published articles, while the team keeps the help center on a domain or path they control. It is free for 50 pages and 100 AI answers a month with no card, and your own domain costs $399 once rather than a subscription. The background is stated directly on the site: I was a longtime Intercom customer until its help center search broke. The fix didn't come fast enough, so I built my own. That story frames the problem the product addresses. Most help centers, according to the launch description, give you a subdomain, a keyword search, and a monthly bill. Chat.sh positions itself differently by offering AI search that writes the answer and cites the pages it used, living in a folder on your own site, making every page available as markdown for ChatGPT, Claude, and llms.txt, and charging once instead of a subscription. The problem matters because a help center that only hands back a list of titles can leave customers searching for the right page, while an answer that shows its sources can resolve the question directly. For teams already paying for support software, the monthly bill and the subdomain are also friction points that chat.sh explicitly calls out. One of the central features is search that reads the question. The website explains that a model retrieves the passages and writes the answer, then shows the pages it used. It is not a keyword index handing back five titles that all contain the word 'domain'. Answers come from published articles only, which means the help center is grounded in the articles the team has published. The site shows live examples at testimonial.to/guide and chat.sh/help. This approach is useful because a customer can ask in their own words and still receive a response that points back to the source article. The interaction is designed around a simple prompt: ask anything, or search for a page. When a person asks a question such as whether the help center can be put under /guide, the system answers and shows the page it used. The product is built around one knowledge base that can answer in three ways. Articles, links, and files go in once, and the help center, the messenger, and the markdown you hand to an assistant all come from that same knowledge base. The content types explicitly listed include articles, web links, files, and TXT and Markdown. The help center is a public site that answers instead of handing back a list of titles. The chat messenger is marked as coming soon; it will put the same answers in a widget on your app, so a customer who is stuck never has to leave the page they are stuck on. The AI agent capability is available now: on each article, you can copy the page as markdown, open it in ChatGPT or Claude, or copy the whole help center. An agent can also start from llms.txt. The copy options include Copy page as Markdown for LLMs, View as Markdown, Open in ChatGPT, Open in Claude, and Copy all docs as Markdown. This matters because it turns the help center into a source that AI tools and agents can use directly, rather than leaving the content trapped in a proprietary format. A key differentiator is hosting. The help center can live at yoursite.com/help, at help.yoursite.com, or at your-team.chat.sh. It can also be hosted in a folder on the site you already run: name it /guide, /help, or whatever you call it, and the help center is served from there on the same domain, with the same analytics, and no subdomain to explain. A custom domain can be added by pointing a domain you own at the help center. The site contrasts old-style URLs such as /en/articles/8341022-add-a-custom-domain with readable addresses that contain no numeric id wedged into the path. In chat.sh, the slug is the title, and it is yours to change. Another detail is that each article draws its own preview card, so a link dropped in Slack arrives as the article rather than as your logo. The visual design is also configurable: you can pick the accent and the mark, and every page follows and stays readable, because the colour is darkened until it is. Overall, the product works from a single knowledge base and exposes it through the help center, the forthcoming messenger, and markdown for AI assistants. The website frames this under the heading One knowledge base, three ways to answer. The search methodology is retrieval combined with answer generation: a model retrieves passages and writes the answer, then shows the pages it used, and answers come from published articles only. The site also asks what a fixed format can't give you, arguing that the old stack hands every team the same URLs, the same search, and the same page with a different logo on it. Chat.sh claims to differ in hosting, addresses, preview cards, and theme control. The commercial approach is described as Get all three. Pay once. It is free on a chat.sh address. The lifetime option adds your own domain, bigger ceilings, and your agents. The site says what you get never changes, and only the price does: it goes up $100 each time we ship. At every price, the help center is live now and includes AI answers on your domain or in a folder, 1,000 pages, and 1,000 AI credits a month per workspace. A link counts as one page for every 2,500 characters of its text, and an article counts as one page. A PDF counts as one page per page of the file. One credit is one answer, here or in the messenger. When the month's credits are gone, 1,000 more are $20, paid once. The chat messenger is shipping next, and each AI reply uses 1 credit from the monthly allowance. The inbox is shipping after; teammates take over a conversation, with 3 people per workspace, and each person after that is $10 a month. Human replies don't use AI credits, and buying another person does not move the lifetime onto a subscription. Benefits follow from those features. Customers get an answer with the pages used, which can reduce the back-and-forth of a keyword search that returns titles only. Teams can keep the help center on a domain or folder they already run, preserving their own analytics and avoiding a subdomain to explain. Because every article can be copied as markdown and the whole help center can be copied or accessed through llms.txt, the same content can feed ChatGPT, Claude, and AI agents. The card preview for every article makes shared links more useful in tools like Slack. The free tier lets teams start with 50 pages and 100 AI answers a month without a card. The lifetime option adds a custom domain, 1,000 pages, and 1,000 AI credits a month per workspace, and it is a one-time payment rather than a subscription. The site emphasizes that human replies in the inbox don't use AI credits and that adding a person does not convert the lifetime into a subscription. For teams tired of a monthly bill for a fixed-format help center, these outcomes are the stated value: a help center that answers, lives where they want it, and can be handed to AI assistants. Concrete use cases appear throughout the content. A customer can ask a question in their own words and receive an answer that shows the page it used. A team can host the help center in a folder such as /guide or /help on the site it already runs, keeping the same domain and analytics. A team can add a custom domain by pointing a domain it owns at the help center. A user can copy a single page as markdown, view it as plain text, open it in ChatGPT, open it in Claude, or copy all published articles as markdown for pasting into AI tools. An AI agent can start from llms.txt to access the help center. When the chat messenger ships, it will place the same answers in a widget on an app so a stuck customer does not leave the page. When the inbox ships, teammates can take over a conversation. The site also shows live examples at testimonial.to/guide and chat.sh/help, and the launch description points to chat.sh/help as a place to try it. The target audience is implied by the story and the product framing: teams that run a help center or support site, particularly SaaS and customer success teams. The launch metadata lists topics such as Customer Success, SaaS, and Artificial Intelligence. The product is for people who want answers served on their own domain or in a folder on an existing site, and who want content available as markdown for ChatGPT, Claude, and llms.txt. Pricing is stated clearly. It is free for 50 pages and 100 AI answers a month, no card. Your own domain is $399 once and never a subscription. A launch-day offer gives $200 off any lifetime deal with code PHLAUNCH: $399 becomes $199, and $799 becomes $599, ending Oct 2, 12 AM PT. The lifetime includes 1,000 pages and 1,000 AI credits a month per workspace. Extra credits are 1,000 for $20, paid once. The chat messenger is shipping next, and the inbox is shipping after with 3 people per workspace and $10 a month for each additional person. No specific tech stack is named, but the product explicitly works with markdown, ChatGPT, Claude, and llms.txt. Chat.sh's primary value proposition is a help center that answers the question. It combines AI search that reads the question and cites the pages it used with hosting on your own domain or in a folder on the site you already run. One knowledge base powers the help center, the coming messenger, and markdown for AI assistants. It is free to start, and the lifetime plan adds your own domain, bigger ceilings, and agents for a one-time payment. For teams frustrated by keyword search, subdomains, and monthly bills, chat.sh presents a different model: answers instead of titles, your site instead of a subdomain, and a pay-once lifetime instead of a subscription.