> 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/conversations-by-date-and-channel-dedicated-sub-view.md).

# Conversations by Date and Channel — Dedicated Sub-View

This sub-view provides the full-page, filter-enabled version of the Conversations by Date and Channel line chart. It separates conversation volume by communication channel, allowing analysts to compare traffic across different entry points (e.g., chat vs. phone) over the selected date range.

<figure><img src="/files/bvw1NVJmOjU0xhBjotPd" alt=""><figcaption><p><em>Figure 1: Conversations by Date and Channel — Full Sub-View (Total Contacts: 27, Daily Average: 2)</em></p></figcaption></figure>

### 1. Chart Details

**Visualization Type:** Multi-line time-series chart. Each line represents a distinct communication channel. The X-axis plots Day of Conversation Date; the Y-axis plots Contacts count.

**Header KPIs:** Total Contacts: 27 | Average Conversations (Daily): 2

Data observations from the visible period (03/08/2026 – 04/09/2026, STG stage):

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Date</td><td valign="top">Observations</td></tr><tr><td valign="top">Wed 3/11/26</td><td valign="top">Blue channel: 2 conversations. Orange channel: not yet active.</td></tr><tr><td valign="top">Mon 3/16/26</td><td valign="top">Blue channel drops to 1. Gap period follows.</td></tr><tr><td valign="top">Tue 3/17/26</td><td valign="top">Blue channel: 3 conversations.</td></tr><tr><td valign="top">Wed 3/18/26</td><td valign="top">Blue channel: 1 conversation.</td></tr><tr><td valign="top">Thu 3/19/26</td><td valign="top">Blue channel: 1 conversation.</td></tr><tr><td valign="top">Mon 3/23/26</td><td valign="top">Blue channel: 1. Orange channel appears at 1 — indicating a second channel becomes active.</td></tr><tr><td valign="top">Wed 3/25/26</td><td valign="top">Blue channel peaks at 5. Orange channel: 1.</td></tr><tr><td valign="top">Thu 3/26/26</td><td valign="top">Blue channel: 2. Orange channel: 1.</td></tr><tr><td valign="top">Fri 3/27/26</td><td valign="top">Blue: 1. Orange continues.</td></tr><tr><td valign="top">Mon 3/30/26</td><td valign="top">Blue: 1. Orange: 3 — orange channel surpasses blue on this date.</td></tr><tr><td valign="top">Wed 4/1/26</td><td valign="top">Blue: 4 (second peak). Orange: 1.</td></tr><tr><td valign="top">Thu 4/2/26</td><td valign="top">Blue: 1. Orange: 1.</td></tr></tbody></table>

### 2. Business Value

Channel-level volume tracking enables teams to understand which communication channels are driving conversation load and whether usage patterns differ between channels. The appearance of the orange (second) channel from 3/23 onwards suggests a new channel was activated or began receiving traffic mid-period. Comparing channel volumes helps justify channel-specific investments in bot optimization and infrastructure capacity.

<br>

&#x20;


---

# 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/conversations-by-date-and-channel-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.
