> 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/wallboards.md).

# Wallboards

Alright, let's talk wallboards! These handy reports show real-time data for queues, laid out in a grid. You'll see cool info like the number of interactions waiting, connections to agents, and more. You can check out data for one or several queues at a glance. And just so you know, the historical totals or percentages update daily, so they're fresh every day!

<figure><img src="https://1039569329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lm5wszNs6c24n4NZ30U%2Fuploads%2FKYZ3ExWDHEbLDVuNtdkN%2FWallboards%20Resized.gif?alt=media&amp;token=133150e3-0606-4763-bdae-a334925858b8" alt="" width="375"><figcaption></figcaption></figure>

Want to set up a wallboard? Just head over to configuration, hit Wallboards, and click add. Give your wallboard a cool name, maybe a description if you feel like it, and pick some queues to display. You can also choose which data columns to include—just drag and drop them to get the order you like. Don’t forget to select an OU and throw in a logo if you want, then just hit save. All done!


---

# 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/feature-highlights/wallboards.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.
