Answer your customers' support mail from your own help docs

Your ventures get customer email too. Kitty can draft the replies — but only from facts you have published, and never sending on its own.

Where it lives

Venture → Support tab. The tab unlocks once the venture's offer is live; before that there is nobody to support.

You get filters (Open / Drafts / Waiting / Closed / All), search, and a Draft replies button.

The rule the whole feature exists to enforce

The AI may answer only from help articles you wrote and published for that venture. It is instructed that those documents are the only facts it has, and told explicitly never to invent prices, refund windows, timelines, features or policies, and never to hedge with "typically" or "usually".

A drafted answer that cites no source, or cites a document that does not exist, is rejected server-side and regenerated. A guessed answer sent to a real customer — an invented refund policy, a feature that does not exist — is the worst thing this product could do, and it is worse than silence.

What happens when you press Draft replies

Up to ten unanswered messages are processed. For each one:

• The docs cover it → a reply is written as a draft, headed "Waiting for your yes", with the articles it drew on named underneath.
• The docs don't cover it → nothing is drafted. The message stays visibly open and a high-priority task appears on your todo list saying exactly what is missing: "Your help docs don't cover this: …".

Then you get a summary: "Drafted N replies from your help docs; N questions the docs don't cover went to your tasks instead of being guessed at."

Nothing is ever sent automatically. A draft waits for you to press Send, and you can edit it first — editing the draft and sending replaces it.

Writing the help articles

Right now this is the rough edge, and here is the honest state of it: there is no editor screen for venture help articles yet. They are created through the API:

POST https://kitty.build/api/ventures/<ventureId>/kb
{ "title": "Refund policy", "contentMd": "...", "isPublic": true }

Authenticate with an API key as described in automating with the API. There is also POST .../kb/suggest, which reads your last 30 days of support mail and proposes up to five articles — with the questions that prompted each — writing nothing itself.

If you want the editor screen, say so. That is how it gets prioritised.

Where published articles appear

On the venture's own website, not on kitty.build: a help/ index page listing every published article, one page per article, styled with the site's own stylesheet, and a Help link added to the site nav.

They go live at the next Publish — publishing an article does not deploy the site by itself.

One safety rule: a document marked sensitive cannot be published. Copy the shareable parts into a new article instead.

Response times

The Support tab shows a median first-response time only once at least three conversations have been answered. Below that it shows a dash, because a median of two is not a number worth showing.