> ## Documentation Index
> Fetch the complete documentation index at: https://www.plain.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Charts you can add to a dashboard

> Every metric in the dashboard chart catalog, the chart types it can show, what it counts, and which date places a thread in the time range.

The chart catalog is the list of metrics in the **Add to dashboard** panel when you [edit a dashboard](https://www.plain.com/docs/product/platform/dashboards/build-a-dashboard.md#add-charts-and-text). Each metric appears once. Badges under its name show the chart types it supports, and clicking it adds the default type, shown in bold in the tables below. Switch type later with **Chart type** in the [chart's options](https://www.plain.com/docs/product/platform/dashboards/configure-charts.md#choose-a-chart-type). Every metric uses the same calculation as its [metric in Insights](https://www.plain.com/docs/product/platform/metrics.md).

A **Breakdown** shows the 5 largest groups and leaves the rest off. A **Line** or **Bars** chart with a group-by shows the 10 largest groups. A **Heatmap** needs a time frame of at least 7 days, and it counts threads in each hour (UTC) and day of the week.

## Which date counts a thread in the range

Charts don't all count a thread on the same date. **New threads created** counts a thread on the day it was created, while **Resolution time** counts it on the date of its last outbound message. 2 charts side by side can cover the same time range and still count different threads. Each chart's description names the date it uses.

Durations are wall-clock time, so they include nights and weekends. Time charts show the median unless you [change the percentile](https://www.plain.com/docs/product/platform/dashboards/configure-charts.md#change-the-percentile).

## Volume

Counts of threads created, reopened, and moved, plus the size of the Todo queue.

| Chart | Chart types | What it counts |
| - | - | - |
| **New threads created** | **Bars**, Line, Breakdown, Heatmap | Threads created in the period, counted on the date each was created, whatever their status now. The breakdown ranks groups from highest to lowest |
| **Threads reopened** | **Bars**, Line | Threads that moved from Done back to Todo, counted on the date they reopened. Threads returning to Todo from Snoozed aren't counted |
| **Todo inflow** | **Bars**, Line | Threads that entered Todo, on the date of the move. Includes new threads, threads reopened from Done, and threads returning from Snoozed. Each thread counts once per bar |
| **Threads moved to Done** | **Bars**, Line | Threads that moved to Done, counted on the date of the move. A thread closed, reopened, and closed again in the same bar counts once |
| **Threads moved to Snoozed** | **Bars**, Line | Threads that moved to Snoozed, counted on the date of the move. A thread snoozed twice in the same bar counts once |
| **Queue size** | **Line**, Bars | An hourly snapshot of how many threads were in Todo. A thread joins the count when it enters Todo and leaves it when it moves to Done, Snoozed, or Ignored |

## Response and resolution

How long customers wait for a reply, a resolution, or while a thread sits in Todo or **Paused for later**.

| Chart | Chart types | What it counts |
| - | - | - |
| **First response time** | **Line**, Bars, Number, Breakdown | Time from the first customer message to the first reply from a person, for threads whose first reply was sent in the period. Bot replies and auto-replies don't count. The breakdown starts grouped by account and ranks groups from slowest to fastest |
| **Next response time** | **Line**, Bars, Number, Breakdown | The gap between consecutive replies on a thread, for threads created in the period. Bot replies and auto-replies don't count. The breakdown starts grouped by account and ranks groups from slowest to fastest |
| **Resolution time** | **Line**, Bars, Number, Breakdown | Time from the first customer message to the thread moving to Done, for threads whose last outbound message was in the period. The breakdown starts grouped by tier and ranks groups from slowest to fastest |
| **Customer waiting time** | **Line**, Bars, Number, Breakdown | Total time threads created in the period spent in Todo or **Paused for later**, across every stretch in those statuses. The breakdown starts grouped by tier and ranks groups from slowest to fastest |

The **Line** and **Bars** types also show a headline number for the whole period. See [First response time](https://www.plain.com/docs/product/platform/first-response-time.md), [Next response time](https://www.plain.com/docs/product/platform/next-response-time.md), [Resolution time](https://www.plain.com/docs/product/platform/resolution-time.md), and [Customer waiting time](https://www.plain.com/docs/product/platform/customer-waiting-time.md) for the full calculations.

## SLA compliance

The share of threads that met the first response or next response time limit. Each of these metrics has a single chart type, so **Chart type** is hidden.

| Chart | Chart types | What it counts |
| - | - | - |
| **First response SLA** | **Number** | The percentage of threads that got their first reply from a person within the SLA time limit. Each thread counts once, on the date its SLA was achieved or breached |
| **Next response SLA** | **Number** | The percentage of threads that got their follow-up replies within the SLA time limit. Each thread counts once, on the date its SLA was achieved or breached |

See [SLA compliance](https://www.plain.com/docs/product/platform/sla-compliance.md) for how Plain decides an SLA outcome.

## CSAT

Ratings customers submitted, as a count of each rating or as the share of one rating.

| Chart | Chart types | What it counts |
| - | - | - |
| **CSAT responses** | **Bars** (stacked), Line | CSAT ratings submitted in the period, split into Negative, Neutral, and Positive. Each counts on the date the survey was submitted. **Bars** stacks the 3 ratings. **Line** draws one line per rating |
| **CSAT score** | **Number**, Line, Bars | The percentage of CSAT ratings submitted in the period that match the chart's **Rating**. It starts on Positive. Each counts on the date the survey was submitted. **Line** and **Bars** draw that percentage over time |

See [CSAT scores](https://www.plain.com/docs/product/platform/csat-scores.md) for how ratings are collected.

## Team

The same outcomes, split by the user assigned to the thread. These metrics appear in the catalog for the same plans and roles as [team reporting](https://www.plain.com/docs/product/platform/team-reporting.md). Other roles see **Not available for your role** in place of the chart. See [Who can see and change a dashboard](https://www.plain.com/docs/product/platform/dashboards.md#who-can-see-and-change-a-dashboard).

| Chart | Chart types | What it counts |
| - | - | - |
| **First response SLA by team member** | **Breakdown** | The percentage of threads that got their first reply within the SLA time limit, for each user assigned to them. Each thread counts once per assignee. Shows the 5 users with the highest percentage |
| **Next response SLA by team member** | **Breakdown** | The percentage of threads that got their follow-up replies within the SLA time limit, for each user assigned to them. Each thread counts once per assignee. Shows the 5 users with the highest percentage |
| **Agent messages sent** | **Bars** (stacked), Line, Heatmap | Messages each user sent, counted on the date each was sent. Shows the 10 most active users. **Heatmap** counts threads instead: threads your team sent at least one message on, in each hour (UTC) and day of the week. Repeated replies to one thread count once in a cell |
| **Thread assignments** | **Bars** (stacked), Line | Threads assigned to each user, counted on the date of the assignment. A thread assigned to the same user twice in the same bar counts once. Shows the 10 users with the most assignments |
| **Agent CSAT score** | **Line**, Bars | The percentage of CSAT ratings that match the chart's **Rating**, for each user assigned to the rated thread. It starts on Positive. Each rating counts on the date the survey was submitted. Shows up to 10 users |

## All-time

A count that ignores the dashboard's time range. [Page filters](https://www.plain.com/docs/product/platform/dashboards/build-a-dashboard.md#filter-every-chart) still apply.

| Chart | Chart types | What it counts |
| - | - | - |
| **Customers helped** | **Number** | Every customer with a thread your team moved to Done since your workspace was created |

**Customers helped** has no time frame setting.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.