> ## Documentation Index
> Fetch the complete documentation index at: https://docs.get2dial.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use the wallboard

> Read live queue depth, agent state counts, and service-level status across every queue, all in one place.

The wallboard shows what's happening across your queues right now. It's read-only — for
taking action on a live call, see [Monitor, whisper, and barge](/supervise/live-call-monitoring).

## Before you start

* You need at least one [queue](/inbound/queues/create-a-queue) with calls flowing through
  it for the wallboard to show anything meaningful.

## Steps

<Steps>
  <Step title="Open the wallboard">
    In the left navigation, select **Wallboard**.
  </Step>

  <Step title="Read the agent-state tiles">
    Five tiles show how many agents are currently **Available**, **Busy**, **Wrap-Up**,
    **Break**, and **Offline**.
  </Step>

  <Step title="Check the SLA banner">
    A banner appears when any queue is over its service-level target — it names the queue so
    you know where to look first.
  </Step>

  <Step title="Check the longest-waiting caller">
    A spotlight tile shows the caller who has been waiting longest, with a live timer.
  </Step>

  <Step title="Read each queue's tile">
    Each queue has its own tile showing how many calls are waiting and its current
    service-level percentage.
  </Step>
</Steps>

## Verify

<Check>
  The tiles update as calls arrive and are answered — place a test call into a queue and
  confirm its waiting count changes.
</Check>

## Common problems

* **A queue shows no data.** Confirm it has at least one member agent and a routing rule
  pointed at it.
* **Numbers look wrong.** See [Metric definitions](/reference/metric-definitions) for exactly
  how each figure is calculated.

## Next steps

<CardGroup cols={2}>
  <Card title="Monitor, whisper, and barge" href="/supervise/live-call-monitoring" />

  <Card title="Metric definitions" href="/reference/metric-definitions" />
</CardGroup>
