What Is a Wallboard?

The wallboard is the oldest piece of contact center furniture still doing useful work. Its purpose is not analysis, it is shared awareness. When the queue starts building, everyone on the floor should know without being told, and the supervisor should not have to announce it. The format follows the purpose: a small number of large figures, changing live, readable from the far side of a room.

This is why a wallboard and a dashboard are different objects even when they draw on the same data. A dashboard serves one person with a question and can afford filters, comparisons and drill-downs. A wallboard serves everybody with no question at all, and every extra element on it costs the legibility of the things that matter. The most common mistake in building one is treating the screen as free space.

What Earns a Place

• Calls waiting. The single number most likely to change behaviour immediately.
• Longest current wait. The one that catches an individual caller being badly served while the average looks fine.
• Agents available. Whether there is capacity to absorb what is arriving.
• Progress against the answer target. Where the shift stands against what it committed to.
• Audio quality. Because a sudden burst of complaints about the line is answered faster by a number than by an argument.

What Does Not

Historical trends, month-to-date totals, cost metrics and anything requiring interpretation belong in reports. They do not prompt action in the next five minutes, and their presence pushes the numbers that do into a smaller font. Individual agent rankings are a separate judgement call: they can motivate, and they can distort behaviour toward whatever the screen rewards, so many operations keep the public screen at queue level and put individual detail in a private view.

How DialerBee Handles the Wallboard

In DialerBee, queue depth and queue stats are live on the wallboard in the inbound contact center, with queue performance and inbound call reports behind them for the record afterwards. Alongside the queue, supervisors see which agents are Ready, on Break, in Manual, on a Callback or in a Meeting, and when something needs a person they can listen to the call, whisper to the agent, barge in, or force a logout from the same place.

The supervisor tools add the floor screen itself with a MOS card for live audio quality, so when agents say the line is bad the wallboard says whether they are right, alongside a live agent grid where every agent is a card showing their state, how long they have been in it, and the campaign or queue they are on. Agent activity timers show time in ready, in wrap-up, on break and on a call, on the principle that time in state is the number that tells you whether the floor is working or waiting. In the operations center, mean opinion score is captured per call and low-MOS alerts surface on the wallboard while the shift is running, with alerts you configure for a NOC, snooze so a known issue stops shouting, and a history of what fired and when. Real-time dashboards update every few seconds over WebSocket connections, so supervisors see live agent states, call activity and campaign KPIs without refreshing, across 11 languages.

Frequently Asked Questions

What is the difference between a wallboard and a dashboard?

A wallboard is read from across a room by people who are not looking for anything in particular, so it shows a few large numbers and changes continuously. A dashboard is read up close by someone with a question, so it can carry filters, drill-downs and detail. Putting a dashboard on a wall screen produces something nobody can read.

What should a wallboard show?

The handful of numbers that would make someone act in the next few minutes. Typically that is calls waiting, the longest current wait, agents available, and progress against the answer target. Anything a supervisor would investigate rather than react to belongs in a report instead.

Should wallboards show individual agent performance?

It depends on the culture, and it cuts both ways. Visible leaderboards motivate some teams and demoralise others, and they tend to push behaviour toward whatever is displayed, which is a problem if the displayed metric is speed rather than quality. Queue-level numbers are safer on a public screen; individual detail works better in a private view.

How often should a wallboard update?

Continuously enough that a supervisor trusts it. A screen refreshing on a slow interval shows a state that has already changed, and once people have seen it be wrong they stop watching. Live updating is the point of the format.

Do remote agents need a wallboard?

Yes, and it is more important for them than for people on a floor. An agent in a room can feel the queue building from the noise around them. A remote agent has no such signal, so the wallboard is the only thing that tells them the team is under pressure right now.

Related terms: service level and SLA, average speed of answer, barge, whisper and listen, MOS and agent occupancy.