> 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 1: Conversations by Date and Channel — Full Sub-View (Total Contacts: 27, Daily Average: 2)*

### 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):


Date	Observations
Wed 3/11/26	Blue channel: 2 conversations. Orange channel: not yet active.
Mon 3/16/26	Blue channel drops to 1. Gap period follows.
Tue 3/17/26	Blue channel: 3 conversations.
Wed 3/18/26	Blue channel: 1 conversation.
Thu 3/19/26	Blue channel: 1 conversation.
Mon 3/23/26	Blue channel: 1. Orange channel appears at 1 — indicating a second channel becomes active.
Wed 3/25/26	Blue channel peaks at 5. Orange channel: 1.
Thu 3/26/26	Blue channel: 2. Orange channel: 1.
Fri 3/27/26	Blue: 1. Orange continues.
Mon 3/30/26	Blue: 1. Orange: 3 — orange channel surpasses blue on this date.
Wed 4/1/26	Blue: 4 (second peak). Orange: 1.
Thu 4/2/26	Blue: 1. Orange: 1.

### 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.
--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` 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=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.