Connect an AI assistant
Your AI assistant can read this documentation directly, so it answers from the current content instead of guessing. Add one of the servers below to your client — they use the Model Context Protocol (MCP). Each one covers a different body of content, so add the one you need.
The catalog did not load. Refresh the page to try again.
Loading…
{{server.name}}
{{server.summary}}
{{server.documentCount.toLocaleString()}} pages Not published to this site
- Name
-
{{server.name}} - URL
-
{{mcpServerUrl(server.path)}}
| Tool | What it does |
|---|---|
{{tool.name}} |
{{part.text}}{{part.text}} |
How can we help?
Searching in {{docApp.searchFilterBySpecificBookTitle}}
Searching for:
{{docApp.searchResultFilteredItems.length}} results for:
{{docApp.currentResultsSearchText}}
in {{docApp.searchFilterBySpecificBookTitle}}
Found {{docApp.searchResponse.totalResultsAvailable}} matches. Showing the top {{docApp.searchResponse.results ? docApp.searchResponse.results.length : 0}}. Use a more specific search to further narrow down the results.
No documentation pages match this search, so all content types are shown.
Most matches are in {{docApp.searchDocTypeRescue.best.name}}.
There is no book with the ID "{{docApp.searchBookRescue.bid}}", so the book filter from this link was ignored and results from all books are shown.
You have an odd number of " characters in your search terms - each one needs closing with a matching " character!
-
{{resultItem.title}} {{resultItem.matchedBy === 'semantic' ? 'semantic' : (resultItem.matchedBy === 'both' ? 'keyword + semantic' : 'keyword')}}
{{resultItem.url}}
{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}
{{docApp.libraryHomeViewProduct.description}}
{{group.title || group.id}}
{{group.description}}
Automatically generate user-friendly request resolutions from technical updates from team members.
Benefits to you
- Agent assistance: Save time producing user-friendly resolution content that can be presented to the customer.
- Agent deflection: Reduce inbound calls. Reduce tickets/backlog. Reduce stress. Cut staff churn.
- User experience: Empower users to do more, faster. No waiting. Customers get back to being productive faster.
What you can do
- Simplify very technical request resolutions into content that’s suitable for end-user consumption.
- Generate request resolutions from a post in a ticket timeline (top level; not comments to posts).
- Or simply paste a block of text into the Request Resolution box and click Suggest Resolution to generate user-friendly content.
Where to find it
In any request record. Accessible as a drop-down menu option in the Request Resolution field and any timeline posts.

How to use it
-
Open a request record. Identify a ticket timeline post that contains the resolution information. Click Suggest Resolution.

-
HAi generates a user-friendly how-to solution. Click the tick to accept the resolution content.

- Version {{docApp.book.version}}
- Node {{docApp.node}} / {{docApp.build}}