> 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/analyze-kb-article-generation-results.md).

# Analyze KB Article Generation Results

There are two ways to generate Knowledge Base articles from the tickets that are attached to the specific application/bot.&#x20;

1. **From Bulk Tickets (via Knowledge Generation Job):** &#x20;

Navigate to Content Generation > Knowledge Generation Clustered Tickets, choose Job Configuration from the Settings pull-down menu and then click the Generate Knowledge button. The results for this option are returned on the Content Generation -> AI Generated Documents -> Bulk Tab&#x20;

2. **From Single Ticket:**&#x20;

Start from the Agent Assist application/bot and click the Generate Knowledge from Individual Ticket button.&#x20;

The results for this option are returned on the Content Generation -> AI Generated Documents -> Single tab.&#x20;

From **SOR -> Tickets**, you can navigate to the **Tickets** page in multiple ways:&#x20;

* Go to **SOR → Tickets**, or&#x20;
* Click on the **Ticket Count** in **Content Generation → AI Generated Documents → Bulk tab**, or&#x20;
* Click the **Data Processing Funnel** button and select any purple or grey box, which will navigate to the **Tickets List** page.&#x20;

From the **Tickets** List page, click on a specific ticket to open the Ticket Details page.&#x20;

### Purpose of Navigation via Content Generation&#x20;

Navigation through Content Generation helps you review tickets within a cluster.&#x20;

* If you are not satisfied with the automatically selected representative ticket, you can manually choose a specific ticket from the cluster and generate knowledge from that single ticket.&#x20;
* Similarly, for bad-quality tickets, you can select the ticket, add Additional Comments, and generate the document without waiting for IT agents to update the ticket in the source system and then re-ingest it into Aisera.&#x20;

This allows you to directly add comments to a single ticket and generate the document immediately.&#x20;

<figure><img src="/files/mD4zrGvuhJq6g36wItgz" alt=""><figcaption></figcaption></figure>

&#x20;

<div align="left"><figure><img src="/files/sZqtNikzIiSOKSiFNf02" alt=""><figcaption></figcaption></figure></div>

&#x20;


---

# 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/analyze-kb-article-generation-results.md?ask=<question>&goal=<endgoal>
```

`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.
