Import help and support history New

Sep 8–11, 2026 · Import existing help

Bring an existing help site and Intercom conversations into Cactus, so their topics and past questions can guide help pages grounded in your product.

Turn imports into product evidence

Cactus turns help-site topics into open questions, and brings past conversations and replies in as dated evidence. When an import surfaces unanswered questions, Cactus can draft pages for those gaps and check them against the pages you already have.

Pages changed

Import existing help and support knowledge Generate and manage help pages Keep product knowledge current Answer customer questions with Cactus Choose who can read a help page Review and correct what Cactus knows

Review build runs in Settings

Build history and Rebuild are in Settings, where you can review each run's stages and published-page count. Repository pushes start one build per day, with later pushes folded into a scheduled run.

Pages changed

Build history and repository sync Generate and manage help pages Keep product knowledge current What Cactus does Answer customer questions with Cactus Connect repositories and product sources

Preview writing-rule changes

Before a batch rewrites pages, you can preview it, cancel it, or start generation. Rule changes also update pages for the chosen audience, and Settings reflects the result of applying or retiring a rule.

Pages changed

Generate and manage help pages Manage product writing rules Review and correct what Cactus knows Answer customer questions with Cactus Customer conversations in the Inbox Browse and ask questions in the Help Center

Set teamspace join rules

Choose whether people join by domain policy, invitation, or owner approval. Owners can invite any email address, manage domains, and rename the teamspace. Failed invite emails appear on the member row.

Pages changed

Join and manage your teamspace Customer conversations in the Inbox Sign in to Cactus

Hide a concept from customers

When you hide a concept, Cactus withholds it from external surfaces. A shared answer page that cites it is also hidden from visitors, while your team can still see the thread.

Pages changed

Review and correct what Cactus knows Answer customer questions with Cactus Set up your Help Center and domain Agent-friendly help Browse and ask questions in the Help Center Keep product knowledge current

Improvements

Help pages each page is published as soon as its own writing job finishes
Appearance unbranded products keep sage accents, and the signed-in app uses a consistent charcoal background
Customer answers share links show the visitor's question and answer again, with a separate spoken reply and sentence-case page and author headings
Product knowledge selected text gets a brush-stroke marker, and Add a note is the single available action
Product sources large repositories are handled in pages, and provider errors are shown once as reported
AI clients AI clients can search owner notes, page through code results, distinguish failures, and handle longer tool sessions
Product updates release notes list only the concepts they name, and knowledge changes link to their release
Onboarding finishing onboarding opens a fresh conversation
Sign in the sign-in page says Cactus publishes and uses a coral cursor on its cream field
Help pages help pages reflect your team's tone, learned from its replies, existing pages, and site
Help pages presence bubbles stack beside the idle cursor

Fixes

Help pages the presence chip stays within the screen on unknown and unpublished pages
Product knowledge the note action appears beside the highlighted line, and text-selection controls stay within the screen
Product sources repository views stay isolated during indexing
Customer answers answer citations match the revision used for the reply, and failed provider turns are saved
Docs llms.txt won't return an HTML shell, and the sitemap stays valid if the Markdown file can't be read
Onboarding your first regular question is separate from the pinned setup conversation
Home the welcome text sits at the bottom of the reading column
Help pages page slugs stay unique when concepts are omitted or renamed

97 commits