Product-grounded Messenger answers New
Sep 2–3, 2026 · Support customers in Messenger
Messenger answers draw on your product knowledge, so customers can get product-specific help directly on your site.
A visitor's turns stay in one conversation, which appears in the Inbox with their email if they leave one. When they ask for a person, it moves to Waiting on you and the team gets an email they can reply to. Teammate replies and customer feedback stay with the thread.
Combine questions into one help page
Choose Combine into one page at the end of a thread with two or more answer pages. Cactus folds the questions and answers into one page, labels how many questions it covers, and shows that page when you share the thread.
Customize Messenger for each product
Each product has its own Messenger key, saved design, and list of allowed website addresses. Cactus keeps the settings with the product and checks the key and site when Messenger loads or handles a request, so a release won't wipe the setup.
Improvements
- Help pages see every planned page in a build and open pages as they publish
- Help Center browse a quieter Help Center with a clearer home, navigation, and audience controls
- Product sources index large repositories with fewer false file errors
- What's New browse What's New by shipped release and date range
- Product setup continue product setup where a teammate left off
- Product settings see a product's logo and open Product settings from its row
- Inbox assistant-side implementation comments use plainer wording
Fixes
- Help pages opening a page no longer shows the catalog through it, and titles and step numbers appear once
- Repositories GitHub connection checks report the correct reason when a connection fails
65 commits