# Analytics

Track ticket volume, resolution and response times, automation rates, categories, tools, sources, and requester feedback

The **Analytics** page shows how Risotto and your team handle tickets over a period. It is the first item in the sidebar. The header has the page filters and a **Force refresh** button. Below them are the summary cards, then the charts and tables.

*Product example: The Analytics page: Department, Assignee and date range filters with Force refresh in the header, above nine summary cards.*

You see **Analytics** when you are an Agent or a Supervisor of at least one department. The page counts only the tickets of your departments and their sub-departments. If you are not a member of any department, the sidebar has no **Analytics** item, and the dashboard opens **Knowledge** instead.

## Filters

The header has three filters. Each one applies to every card and chart on the page:

- **Department**: shows tickets from the departments you pick. The list has the departments you are a member of. When you pick none, the page covers all of them. If you are in only one department, it is always selected.
- **Assignee**: shows tickets assigned to the people you pick. You can search by name and pick more than one person. A ticket counts when its assignee is any of the people you picked. Tickets with no assignee are not included while this filter is set.
- **Date range**: shows tickets created in the period you pick. The page opens on the last 30 days.

When you set more than one filter, a ticket must match all of them. The filters are saved in the page URL, so you can share a filtered view.

To filter by department:

1. **Open the department filter**

   Click **Department** in the header. The list of your departments opens.

2. **Pick the departments**

   Check each department you want. The page reloads its numbers after each
   click. To show all your departments again, click **Clear filters**.

   *Product example: The Department filter open on the Analytics page, with IT checked and People ringed.*

To change the period:

1. **Open the date range**

   Click the date range in the header. A calendar opens with a list of
   presets.

2. **Pick a period**

   Click a preset (**Today**, **Yesterday**, **Last 7 days**, **Last 30
   days**, **This month**, or **Last month**), or click a start day and then
   an end day in the calendar.

   *Product example: The Analytics date range picker open: presets beside a calendar, with Last month ringed.*

The period can be at most 90 days. If you pick a longer one, Risotto moves the start date to 90 days before the end date and shows "Date range limited to 90 days. The start date has been adjusted."

Risotto calculates the numbers in the background and shows placeholders until they are ready. It reuses a result for the same filters for up to 10 minutes. To recalculate now, click **Force refresh** (the circular arrow icon) in the header.

## Summary cards

The cards at the top of the page summarize the period. Point to a card with a question mark icon to see how it is calculated.

- **Solved**: the percentage and count of tickets with the status **Resolved**, out of all tickets in the period (for example "90%" and "371 of 412"). Click the card to open **Tickets > All** filtered to resolved tickets.
- **Solved automatically**: the share of solved tickets Risotto resolved without a human. A ticket counts when it has the **Auto-Solved** tag and not the **Escalated** tag. This card divides by solved tickets. The rate on [Insights](https://www.tryrisotto.com/docs/dashboard/insights) divides by all tickets in the last 90 days, so it is lower. Click the card to open those tickets.
- **Solved with knowledge**: the share of solved tickets that have the **Knowledge** tag and not the **Escalated** tag, out of all solved tickets. Click the card to open those tickets.
- **Responses approved**: shown only when proofreading is on. The share of responses that someone on your team approved, out of the responses sent for proofreading.
- **Average first response in**: the mean time from ticket creation to the first response.
- **Average time to resolve (TTR)**: the mean time from ticket creation to resolution. Time the ticket spent paused does not count.
- **Average tickets per day**: the mean number of tickets created per day.
- **Average AI TTR**: the mean time from creation to resolution for auto-solved tickets.
- **Average Human TTR**: the mean time from escalation to resolution for escalated tickets.
- **Approximate Time Saved**: (**Average Human TTR** − **Average AI TTR**) × the number of auto-solved tickets.

Times show in hours and minutes. A time longer than 8 hours shows in whole hours.

## Charts and tables

Below the summary cards:

- **Solved tickets**: a donut chart that splits solved tickets into **Auto solved** and **Manually solved**.
- **Escalated tickets**: a donut chart that splits escalations into **Instant escalation**, **Chat with team**, and, when there are any, **Eventual escalation** for the other escalations.
- **Trends**: a stacked bar chart of the tickets created each day, by their status: **Open**, **Awaiting response**, **Awaiting support**, **Awaiting approval**, **Resolved**, and **Closed**.
- **Weekly summaries**: a table with one row per week, Sunday to Saturday, and columns for **Total**, **Open**, **In Progress**, **Waiting for Response**, **Waiting for Support**, **Resolved**, and **Closed**. Each cell shows the change from the week before in parentheses, for example "(+5)", before the count. The table is hidden on narrow screens.

*Product example: The Solved tickets and Escalated tickets donuts, the Trends chart of ticket statuses by day, and the Weekly summaries table.*

- **Category distribution**: a donut chart of tickets by category. A ticket without a category counts under the category that Risotto suggested.
- **Top tools**: a ranked table of the ten tools most often mentioned in tickets, with **Rank**, **Tool**, and **Tickets** columns. The badge in the corner shows **All categories** or the category you picked.
- **Ticket sources**: a donut chart of tickets by Slack channel, with direct messages as **DM**. The seven largest sources show by name, and the rest are grouped as **Others**.
- **Ticket feedback**: a donut chart of rated tickets by ⭐, 👍, and 👎. See [Ticket feedback](#ticket-feedback).

*Product example: Category distribution with Access Requests selected, Top tools narrowed to it with Okta expanded and ringed, Ticket sources, and Ticket feedback.*

To see the tools of one category:

1. **Pick a category**

   Click a slice of the **Category distribution** chart. The slice is outlined,
   and **Top tools** shows the top tools of that category.

2. **See the tools used with a tool**

   In **Top tools**, click a tool that has a chevron. The rows under it list
   the other tools mentioned in the same tickets. Click it again to hide them.

3. **Show all categories again**

   Click the **×** on the category badge in **Top tools**, or click the same
   slice again.

## Ticket feedback

In Slack, Risotto asks the requester to rate a ticket when Risotto closes it. The prompt has three buttons: ⭐, 👍, and 👎. Risotto shows the prompt when:

- Risotto resolves the ticket. The prompt says **Did this run do what you expected?**
- Risotto auto-resolves a ticket that waited too long for the requester, the ticket was not escalated, and only the requester replied in the thread. The prompt says **Did this resolve your issue?**
- Risotto grants an access request, or extends an access grant.

Risotto does not ask for a rating when a request is denied, canceled, or expires. Microsoft Teams and email requests do not get the prompt. You cannot turn the prompt off.

Only the requester or someone with a Risotto dashboard account can rate the ticket. Anyone else who clicks a button sees "This request was not made by you, so I can't process your response." After one click, Risotto removes the buttons, so the rating cannot be changed. Risotto then sends that person a DM that asks why they gave that rating. Risotto records the reply, but the dashboard does not show it. A 👎 does not reopen or escalate the ticket.

To see the ratings:

- **Analytics page.** The **Ticket feedback** card at the bottom of the page is a donut chart of the rated tickets by ⭐, 👍, and 👎. Tickets without a rating are not in the chart. The date range, department, and assignee filters apply to it.
- **Tickets > All.** Click **Filter** and pick **Feedback**. Pick ⭐, 👍, 👎, or **No feedback**. For example, filter on 👎 to review the tickets that requesters rated low.
- **Ticket details.** The ticket's side panel shows a **Feedback** row with the rating. The row is not there when the ticket has no rating.

> **Note:** The rating is not in the CSV download from the ticket table, in the public
> API, or in the MCP server ticket tools.

## Other reports

Org Admins and Org Managers see an **Other reports** link at the bottom of the Analytics page. It opens the **Reports** page, which has two reports:

- **Year in Review**: click **Generate Report** to build a CSV of the past 12 months of ticket activity: totals, auto-solved and knowledge-applied counts, time-to-resolve metrics, and weekly and monthly breakdowns. When it is ready, click **Download CSV**.
- **Response Simulator**: runs a batch of Slack messages through your indexed knowledge and gives you the answers as a CSV file. See [Testing methods](https://www.tryrisotto.com/docs/guides/risotto-poc/testing-methods).

## Sharing and exporting

The Analytics page has no download of its own, and Risotto doesn't post these metrics to Slack or email on a schedule. To share the numbers with people who don't have a Risotto dashboard login:

- **Print to PDF.** Use your browser's print dialog to save the page as a PDF and share it wherever your leadership updates live.
- **Download the Year in Review.** Org Admins and Org Managers can download a CSV of the past 12 months from [Other reports](#other-reports).
- **Build a custom view with the Assistant.** Ask the [Assistant](https://www.tryrisotto.com/docs/dashboard/assistant) to build an Artifact that pulls the ticket data you care about (for example, tickets created and resolved by department over a date range). An Artifact is a reusable dashboard page you can revisit each week, and the Assistant can also return the underlying numbers as a table you can copy into another tool.

> **Note:** Tools like the Assistant and the [MCP server](https://www.tryrisotto.com/docs/integrations/mcp-server)
> read ticket records, not the pre-computed analytics page, so the numbers they
> produce may be grouped or rounded differently from the page above.

Source: https://www.tryrisotto.com/docs/dashboard/analytics
