Skip to main content
Back to blog

Supervisor wallboards: real-time queue monitoring on a shared screen

What a supervisor wallboard actually does, why a live shared surface beats per-agent views, and how Devotel Orbit's dedicated wallboard surface is set up — tiles, alarm rules by queue, TV mounting, and drill-down into the quality loop.

Orbit Editorial Team

Quick answer

A supervisor wallboard is the live, shared view of a contact center's queues and agents — the numbers a team lead needs right now (calls waiting, wait times, service level against target, agents available, SLA breaches) rendered on a screen everyone can see rather than buried in a per-agent view. The shared part is the point: a per-agent dashboard tells one person what's happening; a wallboard makes the queue state a room-level fact, so a floor reacts to the same numbers at the same time. When the board also fires configurable alarms, it stops being something a supervisor has to watch and becomes the system that tells supervisors when to look.

What Orbit ships: a dedicated wallboard route

Devotel Orbit ships the Wallboard page in the dashboard as a dedicated, shareable route (/wallboard), alongside the queue-level voice wallboard (/voice/wallboard). The WEM primer only names wallboards inside the workforce-management context — this post is the dedicated walkthrough of the surface itself. What the shared route renders live:

  • Headline KPI tiles — Messages Sent, Delivery Rate, Queue Depth, Active Agents, SLA Breaches, and API/Messages volume, each color-coded against a health threshold (healthy / warning / critical), with a neutral "no data" state when a metric has nothing honest to render instead of a misleading zero or a fabricated 100%.
  • The omnichannel queue panel — per-channel live / unassigned / assigned / waiting breakdowns so digital queues sit next to voice on the same board.
  • Live operations band — live calls now, waiting, service level, and agents available in one fused strip, with the most recent active and queue-waiting calls (caller and callee numbers masked by default, so a floor-mounted TV never shows a raw phone number) and a per-agent state strip with color-coded chips (available / on-call / wrap-up / unavailable).
  • Top performers leaderboard — sortable by calls handled, handle time, or CSAT, embedded next to the tiles.

The board streams over the live event channel and falls back to polling only while that channel is down, so a TV-mounted tab stays current without hammering the network. Every role sees it scoped to their own workspace: owner, admin, and supervisor roles get the org-wide view, while a lower-privilege agent role fails closed to their own row instead of seeing the org numbers. Access and thresholds are entirely tenant-owned, all the way down.

Alarm rules: set thresholds by queue, channel, and agent

Tiles answer "what is happening"; alarm rules answer "when do we react." A rule watches one metric against a comparator and threshold, evaluated on the live five-second tick, and can apply to a single queue or tenant-wide across every queue. The available metrics: calls waiting, longest wait, average wait, predicted wait, agents available, agents logged in, service level, and abandoned rate.

Three fields keep the alarms honest:

  • `duration_seconds` — how long the breach must persist before the alarm fires. A zero hits on the first breaching tick; anything up to 24 hours is accepted. This is the filter between "one burst" and "the floor is actually backed up."
  • Delivery channel — an in-app banner on the live feed (sse), banner plus browser notification (sse+notification), a signed webhook for paging tools, or admin email.
  • `enabled` — mute a rule without deleting it during a storm.

Creating and editing rules requires the owner or admin role; the page lists, toggles, and deletes them. Alarms clear automatically on recovery, so nobody has to acknowledge a resolved condition. The full contract, including the API shape, is in the wallboard alarm rules guide.

TV mounting and links a supervisor shares

The header carries everything a display needs: fullscreen on F, an auto-rotating cycle through tile pages every 10 seconds, a Space (or button) pause that persists across refreshes so a TV tab does not silently resume, arrow-key navigation, and a live clock so the board is safe to leave unattended. Casual keyboard input (Space in a search box, for instance) is ignored. Mounting is a dedicated browser profile signed into a supervisor-level account on the TV — the _Wallboard_ guide covers the full setup. Because the wallboard is a plain route, bookmarking or sharing its URL is a valid way to hand a supervisor the surface; permission scoping decides what any signed-in viewer actually sees.

Worked example: three alarm rules that catch the common failures

Grounded in the queue metrics the board actually shows, three rules cover most of what escalates on a floor:

  1. Wait-time rule — longest_wait > 120 seconds on the Support queue, firing after a 30-second sustained breach. Catches a caller stranded in queue before abandonment, not after the CSAT damage.
  2. Abandonment rule — abandoned_rate ≥ 5% tenant-wide. The action is staffing or callback, but the alarm is the thing that turns a drifting ratio into a supervisor reaction while it still counts. Service-level and abandoned-rate metrics run over a rolling 30-minute window; a rule on them is skipped on any tick where the window carried no traffic, instead of firing on a meaningless zero.
  3. Idle-agents rule — agents_available < 1 tenant-wide, fired instantly. When the live operations band reads zero available agents, the board's service-level tile flips to critical; this rule is the alarm version of that same tile — nobody is stranded with no one to answer.

Where the live numbers meet the quality loop

A wallboard answers "right now"; the quality program answers "getting better." The two meet on one surface — the embedded leaderboard pulls from the same QA, call, and CSAT data the Quality suite scores, and from a leaderboard row or a CSAT chip the drill-down is one click into the evaluations behind the aggregate. For the quality-side mechanics — how evaluations, recordings, and practice combine with leaderboard mechanics that credit development rather than raw output — see the quality-leaderboard post. For the full category breakdown (monitoring, QM, WFM, adherence), the WEM primer places the wallboard in the workforce-engagement stack it grows out of.

Open the wallboard

Open the Wallboard page in the dashboard, press F to strip the chrome, and leave it on a shared screen. Add one alarm rule per queue to start — a wait-time rule against your own SLA target — and let the board tell you when to look again.

Frequently asked questions

Does a small team need a wallboard?

Yes, sooner than they think. Any queue with more than a handful of agents benefits from making queue state a room-level fact. The per-agent view is for coaching; the wallboard is for acting on the queue while the customer is still in it.

What is the difference between /wallboard and /voice/wallboard?

The shared /wallboard is the cross-channel operations surface — message-level KPIs, the omnichannel queue panel, and a fused live-operations band. The dedicated voice wallboard (/voice/wallboard) keeps the full per-queue and per-agent state grid and is the surface to open when a supervisor needs to un-mask call rows or drill into the agent grid.

How do alarm rules avoid being noisy?

Two mechanisms: a duration_seconds gate that demands the breach persists before firing, and a rolling 30-minute window on the percentage metrics so that "no traffic" reads as "no evaluation" rather than a fabricated zero. Tune a rule's threshold and duration once, then let the recovery auto-clear close the loop.

Supervisor wallboards: real-time queue monitoring on a shared screen — Orbit by Devotel