Content Writer
When solved tickets capture new docs-worthy answers, Inkeep Content Writer opens a pull request on your docs repo, pings Slack, and your team reviews the update before merge.
Duration: 1:33
How to automatically update your docs from resolved support tickets
1. Identify new information in a ticket
A customer asks a question like "What is the recommended model to use?" and your team replies with new information that isn't yet reflected in your documentation.
2. Leverage Inkeep's content writing system
Because Inkeep has already indexed your entire docs knowledge base, it knows how your documentation is structured and where any new information needs to go.
3. Mark the ticket as solved
To kick off the update process, simply mark the ticket as solved in your ticketing platform. This triggers Inkeep to evaluate the conversation for novel information.
4. Detect novel information
Inkeep automatically analyzes the answer provided in the ticket and determines whether it contains information that isn't already covered in your docs.
5. Generate a pull request
If new information is detected, Inkeep creates a pull request to your docs repository with the proposed changes.
6. Get notified via Slack
The Inkeep Content Writer posts a notification to the appropriate Slack channel, letting your team know that a new PR is being processed.
7. Review the changes
The PR includes a clear header summarizing the update, highlights the modified files, and lets you review all proposed changes before merging.