> For the complete documentation index, see [llms.txt](https://cc.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cc.docs.landis.cloud/reports/queue-calls-by-hour.md).

# Queue Interactions by Hour

Navigate to Analytics & Reports | Queue Interactions By Hour

Displays a matrix of queue statistic by hour.

For report options (e.g., filtering), See [Report Options](/appendix/report-options.md)

| Row   | Description                                                                |
| ----- | -------------------------------------------------------------------------- |
| 00-23 | Hour Number. For example, 00 includes interactions from 12:00am to 12:59am |

| Column                                 | Description                                                                                                                             |
| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Total Count                            | Number of queue interactions                                                                                                            |
| Unaccepted Count                       | Number of unanswered interactions. Includes abandoned and timed out interactions.                                                       |
| Accepted Count                         | Number of interactions handled by an agent.                                                                                             |
| Abandoned Count                        | Number of interactions where the contact disconnected when waiting in queue.                                                            |
| Timeout Count                          | Number of interactions that timed out in the queue.                                                                                     |
| Timeout With No Available Agents Count | Number of interactions that timed out immediately because no agents were either signed into the queue or had an available agent status. |
| Callbacks Count                        | Number of interactions that requested a callback.                                                                                       |
| Breakout Count                         | Number of interactions that requested to breakout while waiting in queue.                                                               |
| Outside Business Hours Count           | Number of interactions that were outside business hours based on a business hours set assigned to the queue.                            |
| On Holiday Hours Count                 | Number of interactions that were during holidays based on the holiday hours set assigned to the queue.                                  |


---

# 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://cc.docs.landis.cloud/reports/queue-calls-by-hour.md?ask=<question>&goal=<user_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.