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

# Impact Dashboard report

> Read the Impact Dashboard: automation percentage, sessions solved by AI, the conversation flow, resolutions and sentiment, and what each number counts.

The Impact Dashboard shows how many sessions your AI solves on its own, how sessions move from channel to outcome, and how customers felt. Use it to follow your automation rate over time and to open the sessions behind any number.

> [!NOTE]
>
> **Reports & Apps → Impact Dashboard** in your [OpenCX dashboard](https://platform.open.cx/reports/impact-dashboard). Requires **Reports: Read** in [Roles](https://docs.open.cx/security/roles.md). Opening the sessions behind the conversation flow also requires **Inbox: Read**. The Impact Dashboard is in the sidebar by default.

The page has four sections: **Summary**, **Conversation flow**, **Resolutions** and **Sentiments**.

## Filter the dashboard

The filters at the top apply to every section.

| Filter | What it does | Default |
| - | - | - |
| **Period** | **Rolling**: **Today**, **3d**, **7d**, **30d**, **90d**. **Calendar**: **This week** through **Last year**. Or **Custom range...** to pick dates. Sessions count on the day they were created. | **7d** |
| **Time zone** | Sets where each day starts and ends, for the period and the daily bars. Your choice is remembered per organization in this browser. | **(GMT+0:00) UTC** |
| **Channel** | **All Channels**, or one channel such as Web, Email or Phone. | **All Channels** |
| **HubSpot source** | Shown only when HubSpot is connected. **Tickets**: sessions linked to a HubSpot ticket. **Conversations**: HubSpot conversations that never became a ticket. Sessions that didn't come from HubSpot appear only under **All**. | **All** |
| **Tags** | **Includes**: sessions must carry every tag you pick. **Excludes**: sessions must carry none of them. A tag can be in only one of the two lists. Remembered per organization in this browser. | No tags |

## What each outcome means

Every number on the page is built from the AI's outcome for each session:

| Outcome | What it counts |
| - | - |
| **Resolved** | The AI closed the session as resolved in a reply, once the customer's question was settled. For an AI call, the call ended without a transfer. |
| **Assumed-Resolved** | The session closed while the AI was still handling it, without the AI marking it resolved. Most often it closed automatically after the customer stopped replying: by default after 3 hours, or 12 hours on email and WhatsApp. It also applies when the customer, a workflow or the API closes a session the AI is handling. |
| **Handed Off** | The AI handed the session to your team, for any reason, including a reached usage limit. For an AI call, the call was transferred. |
| **In Progress** | The AI is still handling the session and it has no outcome yet. |

When your organization is set to show assumed-resolved sessions as resolved, **Assumed-Resolved** disappears everywhere on the page and those sessions count as **Resolved**.

**Summary**, **Resolutions** and **Sentiments** count eligible sessions: sessions created in the period that have at least one message and one of the four outcomes above. Sessions in assist mode are left out. A session your team handles without the AI ever owning it has no outcome, so it is not counted.

## Read the summary

| Card | How it's calculated |
| - | - |
| **Total sessions solved by AI** | Resolved + Assumed-Resolved + In Progress. The line below it, **Out of … eligible sessions**, adds Handed Off. **Learn more** splits the total into **Confirmed resolutions** (Resolved + Assumed-Resolved) and **Pending confirmation** (In Progress). |
| **Automation percentage** | (Resolved + Assumed-Resolved + In Progress) ÷ (Resolved + Assumed-Resolved + Handed Off + In Progress) × 100, to one decimal. |

The automation percentage is a forecast: it already counts sessions the AI is still handling, because most of them end up resolved. It goes down if those sessions are later handed off.

**Inspect sessions** on the automation card points you to [Data Export](https://docs.open.cx/reports/data-export.md), where you filter the same sessions and download them.

## Read resolutions and sentiments

**Resolutions** shows the four outcomes as a donut, with the number of eligible sessions in the middle, and as stacked bars per day.

**Sentiments** shows the customer sentiment recorded for each eligible session when the AI resolves or hands it off: **Happy**, **Neutral** or **Angry**. **In Progress** counts sessions still with the AI. The middle of the donut shows the emoji of the most common sentiment.

## Trace the conversation flow

**Conversation flow** draws sessions as bands moving through columns. Each column is a dimension, such as channel or outcome. Each block in a column is one value, labelled with its session count and its share of all sessions in the flow. The wider a band, the more sessions moved between those two values. Hover a block or band to see its count.

The default flow is **All tickets → Channel → Resolution**: every session, split by channel, then by outcome.

**1. Change a column**

Select a dimension pill and pick another dimension. For **Contact custom data** or **Session custom data**, also pick the key to group by.

**2. Add or remove columns**

Select **Add dimension** for another column, or **×** on a pill to remove it. A flow needs at least two and at most six dimensions, and two neighboring columns can't use the same dimension.

**3. Share the flow**

The page URL carries your flow, so a copied link opens the same columns. Your last flow is also remembered per organization in this browser.

Each column shows its 12 largest values. The rest are grouped into **Other (N)**, where N is the number of values grouped.

> [!NOTE]
>
> The flow counts every session created in the period with at least one message, including assist-mode sessions and sessions only your team handled. Those have no AI outcome, so under **Resolution** they appear as **In Progress**. The flow's total can therefore be higher than the summary's eligible sessions.

> [accordion] Dimensions you can pick
>
> | Dimension | Groups sessions by |
> | - | - |
> | **All tickets** | Nothing: one block with every session. Use it as the first column. |
> | **Who replied** | **Agent replied** if a teammate replied, otherwise **AI replied** if the AI did, otherwise **No reply**. |
> | **Resolution** | The AI outcome: **Resolved**, **Assumed-Resolved**, **Handed Off** or **In Progress**. |
> | **Handoff** | **Handed off** or **Not handed off**. |
> | **Channel** | The session's channel. |
> | **Integration source** | The connected helpdesk or CRM the session came from, such as HubSpot, Zendesk, Intercom or Salesforce, or **Native**. |
> | **AI mode** | **Autopilot** or **Assist mode**. |
> | **Contact custom data** | The value of the key you pick on the contact, or **Unspecified**. |
> | **Session custom data** | The value of the key you pick on the session, or **Unspecified**. |
> | **Sentiment** | **Happy**, **Neutral**, **Angry** or **No sentiment**. |
> | **Status** | **Open**, **Resolved** or **Unresolved**. |
> | **Team** | The assigned team, or **Unassigned**. |
> | **Contact source** | Where the contact record came from, such as a form, HubSpot, Intercom, Salesforce or Slack, or **Unknown**. |
> | **CSAT** | **Positive (4-5)**, **Neutral (3)**, **Negative (1-2)** or **No CSAT**. |
> | **Handoff reason** | The reason the AI gave, such as **Insufficient knowledge**, **Insufficient tools**, **Prohibited topic** or **User requested human**. **Usage limit reached** when a usage limit sent the session to your team, **Handed off (reason unrecorded)** when no reason was recorded, and **Not handed off**. |
> | **Contact reason** | The latest contact reason assigned to the session, or **Uncategorized**. |
>
> The custom-data key pickers list the keys your organization's sessions and contacts have used. A picker shows **No keys yet** when none have been recorded.

## Open the sessions behind a number

Select a block to list the sessions with that value, or a band to list the sessions that moved between its two values. The **Sessions** panel shows how many match, newest first, 20 at a time; select **Load more** for the next ones. Each row shows the session number, channel, sentiment, status, contact, last message and when the session was created. Select a row to open the session in the inbox.

Changing the flow's columns closes the panel, because its selection no longer matches.

## How these numbers relate to billing

The Impact Dashboard is a reporting view, not your bill. It counts sessions by the day they were created, and includes sessions still in progress. Billed AI resolutions are counted when a session closes. To see the sessions behind a charge, use **View billed sessions** in [Settings → Billing](https://docs.open.cx/billing.md#review-billed-sessions-and-calls).

## Troubleshooting

| Symptom | Likely cause | Fix |
| - | - | - |
| The flow says **Add at least two dimensions to trace how sessions flow between them.** or **Adjacent dimensions must differ — change one to trace the flow.** | The flow has one column, or the same dimension twice in a row | Add a dimension, or change one of the neighboring pills. |
| The flow says **Pick a value for the custom-data dimension to trace the flow.** | A custom-data column has no key yet | Pick a key in that pill. If it shows **No keys yet**, choose another dimension. |
| Selecting a block shows **Couldn't load these sessions. Try again.** | Your role lacks **Inbox: Read**, which listing sessions requires | Ask an admin to grant it in [Roles](https://docs.open.cx/security/roles.md). |
| The flow's total is higher than **Out of … eligible sessions** | The flow also counts assist-mode sessions and sessions only your team handled | Add **AI mode** or **Who replied** as a column to see them separately. |

***

## Related Documentation

> [card] [Handoff Insights](https://docs.open.cx/reports/handoff-insights.md)
>
> Why the AI hands off

> [card] [Increase automation](https://docs.open.cx/resources/increase-automation.md)
>
> Turn the numbers into fixes

> [card] [Data Export](https://docs.open.cx/reports/data-export.md)
>
> Download the sessions

> [card] [Billing](https://docs.open.cx/billing.md)
>
> Billed AI resolutions


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