> 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/feature-highlights/queue-status-report.md).

# Queue Status Report

Need to check in on your queue and see what's currently going on? The Queue status report is your go-to spot! Most of the info here updates in real time, so you can easily see what your agents are doing or how many interactions are waiting. Just head over there to get the latest scoop!

<figure><img src="/files/hogOxUHsW9LpPzHOEFoH" alt="" width="375"><figcaption></figcaption></figure>

At the top, you'll spot some quick stats for each queue, showing how many interactions are waiting and how many are being answered by agents. You'll also see the number of agents available to take interactions. Clicking on any of these queue "cards" gives you detailed info right below. The agent tab shows you all agents in the queue and their current status. The interactions tab gives you a rundown of all the interactions in queue. The Link tab takes you straight to a prefiltered report for that 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 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://cc.docs.landis.cloud/feature-highlights/queue-status-report.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.