> For the complete documentation index, see [llms.txt](https://docs.ixhello.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ixhello.com/ix-hello-reporting/premium-reporting/total-conversations-with-contained-and-transferred-dedicated-sub-view.md).

# Total Conversations with Contained & Transferred (Dedicated Sub-View)

This is the expanded, full-page version of the Total Conversations with Contained and Transferred stacked bar chart. It provides the same filter panel as the Containment & Transfer Rates sub-view, enabling granular analysis of absolute conversation volumes.

<figure><img src="/files/w3VKAQK5IuHc5nXqhYah" alt=""><figcaption><p><em>Figure 1: Total Conversations with Contained &#x26; Transferred — Full Sub-View</em></p></figcaption></figure>

### 1. Chart Details

**Visualization Type:** Stacked bar chart with daily granularity.

**Legend:** Contained (blue), Successful Transfers (orange), Unsuccessful Transfers (red).

**Dashed Reference Line:** A horizontal dashed line near the 5,000 mark indicates the average daily conversation volume across the selected period, providing a quick visual benchmark for identifying above-average and below-average days.

Each bar is labeled with the exact conversation count for that day. The data clearly reveals a consistent weekday/weekend pattern: weekdays average 6,500–8,000 conversations while weekends drop to 800–2,500.

### 2. Business Value

While the Containment Rate chart (Section 9) shows relative performance as a percentage, this view shows absolute volumes. This distinction is critical: a 100% containment rate on a day with 862 conversations tells a very different operational story than 100% containment on a day with 8,065 conversations.

The absolute volume view supports capacity planning (identifying peak days that require more infrastructure), weekend/holiday staffing decisions, and trend analysis over time. Filtering by assistant name enables volume comparison across different bots, helping teams understand which assistants drive the most traffic.

The presence of Unsuccessful Transfers (red) in the legend — even when zero — serves as a constant reminder to monitor for failed transfer attempts, which represent some of the worst customer experiences: the AI could not help, and the handoff to a human also failed.


---

# 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.ixhello.com/ix-hello-reporting/premium-reporting/total-conversations-with-contained-and-transferred-dedicated-sub-view.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.