What Cactus does

Cactus reads connected product repositories and can connect existing help material. It maps product behavior, starts documentation work from that map, and gives your team places to answer product questions.

Cactus maps your product from connected repositories and ties each map version to the repository commits it read. It starts documentation builds from that map, so your team can trace help back to product code. When repository changes affect mapped evidence, Cactus updates affected map entries and documentation; if it can’t safely update the map, it draws the map again. For details, read Keep product knowledge current.

Sources

Connect brings together where Cactus answers, what it reads, and where handoffs go. Answer surfaces include your Help Center, Messenger, AI clients over MCP, Slack, and Discord. You can set handoffs to Email, a Slack channel, or a Discord channel.

Customers can ask questions in a published Help Center, in Messenger on your product site, through an AI client over MCP, or in Slack and Discord. In Messenger, Cactus answers in the conversation. For details, read Answer customer questions.

You can set Email, a Slack channel, or a Discord channel as a handoff destination. When a teammate handles a Messenger thread, Cactus doesn’t generate an automatic reply, and the customer’s message is recorded in the Inbox. For next steps, read Resolve or escalate customer conversations.

For team access, read Join and manage your teamspace. For product setup, read Create and set up a product.

For watched products, your team can use Visibility to review AI answers, whether models name or cite the product, naming trends, keyword positions, recommendations, and follow-up actions. Read Monitor AI visibility for details.