> For the complete documentation index, see [llms.txt](https://docs.aisera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisera.com/aisera-platform/content-generation-from-tickets/why-extract-solutions-from-the-ticket-comments.md).
# Why extract solutions from the Ticket Comments?
Human IT Serice Agents frequently disregard resolution notes for closed tickets.
.To address this concern, the Aisera GenAI platform extracts vital information from diverse ticket comments. This capability empowers us to create precise and elaborate solutions that form a sturdy knowledge base. This resource can then be utilized by other agents to efficiently resolve similar issues in less time.
This feature was created to enhance overall knowledge coverage. Granting access to a wide range of solutions and information, simplifies the process of creating a knowledge base from scratch. This, in turn, improves your knowledge serach.
You no longer have to rely solely on resolution notes. The valuable information extracted from comments offers a holistic view of the ticket resolution process. When you extract comments from tickets, you reduce the time spent on information retrieval and knowledge base creation. Instead, you gain access to a diverse repository of knowledge encompassing various issues and resolutions.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.aisera.com/aisera-platform/content-generation-from-tickets/why-extract-solutions-from-the-ticket-comments.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.