# Stats

**Stats** on the left rail works its numbers out from events that really happened in conversations. Viewing stats needs the permission to view stats, which only admins and owners have by default; the **Usage** view is for admins and owners. The API is in [Tickets, stats and team](api-team.md#team-stats).

## Views and periods

- Views: **Me**, **Team** and **Usage**.
- Periods: today, yesterday, 7 days, 30 days, this month, last month, or a custom range of up to 90 days.
- Turn on **Compare to previous** to see the change from the previous period next to each number.
- Filter by **Site**; all sites by default. A "day" follows the time zone of the organization's default business hours, or UTC when none is set.

How each card is counted is in the tooltip on its title.

## Overview

| Card | How it is counted |
| --- | --- |
| New conversations | Conversations started in the period |
| Specialist first response | Time from a Specialist starting to serve to their first reply, median |
| CSAT | Helpful ÷ all ratings, credited to whoever was serving when the customer rated |
| Wait time | Time from transfer to start serving, median |

## Resolution rate

Resolution rate = resolved ÷ (resolved + unresolved), in three parts: **Resolved by Ailo**, **Resolved with a Specialist** and **Unresolved**.

- Each conversation's outcome is worked out from its events; teammates and Ailo correct it only when it is wrong. See [Serving a conversation](conversation.md#ending-a-conversation-and-its-outcome).
- Resolved by Ailo is split into **confirmed resolution** and **assumed resolution**: only those the customer clearly confirmed count as confirmed.
- Corrected outcomes and no action needed are counted too, plus the repeat visit rate.

## How teammates joined

- **Specialist involvement rate**: ended conversations a Specialist took part in ÷ ended conversations.
- **By reason**: Ailo asked, customer asked, site rule, action not completed, Ailo couldn't reply, Specialist stepped in, reason not recorded.
- **How Specialists joined**: Assist, To specialist and Specialist-led.

## Speed, tickets and satisfaction

- **First response time**: medians for Ailo and for Specialists, separately.
- **"Ailo asks you" response time**: excluding ones auto-sent on timeout.
- **Transfers**: counted by result.
- **Assist tickets**: excluding "Ailo asks you"; handling time is the median from claim to resolve.
- **CSAT**: Ailo and Specialists separately, with the rating rate; selecting a customer's comment opens the conversation.
- **Specialist performance**: each Specialist's conversations served, first response, handling time, resolutions, satisfaction and tickets resolved.
- **Conversation volume**: by day or by hour.

The **Me** view counts only conversations you took part in: resolution rate, transfers you started serving, first response time, assist tickets, satisfaction and handling time.

## Usage

**Usage** lists, per UTC day, the models Ailo used, what for, input and output tokens, and cost, for today or 7 days.

## Related

- [Desk overview](overview.md#five-ways-a-conversation-is-served)
- [Tickets, stats and team](api-team.md)
