How to Build an Asterisk Call Center Wallboard: Complete 2026 Guide

Your call center supervisor walks in at 9 AM, grabs coffee, and opens the reporting tool. Yesterday's numbers look fine. Meanwhile, 47 callers are stuck in the support queue, three agents are on extended breaks, and your SLA dropped below 60% twenty minutes ago.

Nobody noticed. Nobody acted.

That gap between "data exists" and "someone sees it in time" is exactly what a wallboard eliminates. A wall-mounted screen showing real-time queue stats, agent availability, and SLA status turns your call center from reactive to proactive.

If you run Asterisk — or any Asterisk-based PBX like FreePBX, Issabel, or VitalPBX — this guide covers everything you need to build an effective wallboard. From choosing the right metrics to picking the right tool to the exact queues.conf settings that feed your displays.

What Is a Call Center Wallboard?

A wallboard is a real-time dashboard displayed on a large screen (or multiple screens) in your call center. It shows live operational metrics — calls waiting, agents available, SLA status, average wait times — updating continuously so supervisors and agents can react to problems the moment they appear.

Think of it as the call center equivalent of an airport departure board. Everyone sees the same information. Everyone knows the current state. When something goes wrong, it's visible immediately.

The key word is real-time. A wallboard that refreshes every 5 minutes is a report on a TV screen. A real wallboard streams data with sub-second latency. When a call enters the queue, you see it. When an agent goes on break, you know.

Wallboard vs. Dashboard vs. Report

These terms get mixed up constantly. Here's the distinction:

You need all three. But the wallboard is the one that prevents fires, not the one that analyzes the ashes.

7 Metrics Every Asterisk Wallboard Must Display

The biggest wallboard mistake is cramming 30 metrics onto a screen that nobody reads. Research from the Nielsen Norman Group shows people can effectively track 5-7 data points simultaneously. More than that, and attention fragments.

Here are the seven that matter most for Asterisk call centers, ordered by urgency.

1. Calls Waiting in Queue

What: The number of callers currently on hold, waiting for an agent.

Why it's #1: This is the single most actionable metric. If calls waiting spikes from 3 to 15 in ten minutes, something is wrong — and you need to know now, not at the end of the shift.

Asterisk source: The Queue() application tracks this in real-time. The AMI QueueStatus action returns Calls for each queue.

Alert threshold: More than 2x your average concurrent calls = yellow. More than 3x = red.

2. Longest Wait Time

What: How long the caller who's been waiting the longest has been in the queue.

Why: Calls waiting tells you the quantity. Longest wait tells you the severity. Five calls waiting with a max wait of 20 seconds is manageable. Five calls waiting with someone at 4 minutes is a crisis.

Asterisk source: QueueStatus AMI event returns Wait time for each caller in the queue.

Alert threshold: Varies by industry. For most B2B: yellow at 60 seconds, red at 120 seconds.

3. Available Agents

What: Number of agents logged into queues and ready to take calls (not on a call, not paused).

Why: This metric explains why calls are piling up. If you have 20 calls waiting and only 2 available agents, the problem is capacity. If you have 20 calls waiting and 8 available agents, the problem is routing.

Asterisk source: QueueMember events via AMI. Agent states: Not in use (available), In use (on call), Paused (on break), Unavailable (logged out).

Threshold: If available agents drops to zero for more than 30 seconds during business hours, that's an immediate alert.

4. Service Level (SLA)

What: Percentage of calls answered within your target time. Industry standard: 80% of calls answered within 20 seconds (80/20).

Why: SLA is the single number that tells you whether your call center is performing. It combines staffing, agent speed, and call complexity into one metric.

Asterisk source: Asterisk tracks this in queue_log. The COMPLETECALLER and COMPLETEAGENT events include hold time, which you compare against your threshold.

Display tip: Show SLA as a large percentage with color coding. Green (>80%), yellow (65-80%), red (<65%). Update every 60 seconds based on a rolling window.

5. Abandon Rate

What: Percentage of callers who hung up before reaching an agent.

Why: Every abandoned call is a potential lost customer. At 3%, it's normal. At 8%, it's a problem. At 15%, you're hemorrhaging revenue.

Asterisk source: ABANDON events in queue_log record when callers hang up in queue. Track the position, original position, and wait time.

Display: Show as today's running percentage. Color shift at 5% (yellow) and 10% (red).

6. Average Handle Time (AHT)

What: Average time agents spend per call — talk time plus after-call work.

Why: Rising AHT is an early warning signal. If your AHT jumps from 4 minutes to 7 minutes, agents might be dealing with a new issue (system outage, product defect, confusing policy change). The wallboard catches this before anyone files a report.

Asterisk source: COMPLETECALLER and COMPLETEAGENT events in queue_log include holdtime and talktime fields.

Display: Show today's rolling average vs. your target. A graph showing the trend over the last 2 hours is even better.

7. Agent Status Overview

What: A visual breakdown of agent states — on call, available, on break, in after-call work.

Why: This answers "where is everyone?" at a glance. If half your team is on break simultaneously, you see it instantly. If three agents have been in "after-call work" for 20 minutes each, something's off.

Asterisk source: QueueMemberStatus AMI events. The Status and Paused fields give you real-time state for every agent in every queue.

Display: A row of colored dots or a compact table. Green = available, blue = on call, yellow = paused, gray = offline.

4 Ways to Build an Asterisk Wallboard

Not all wallboard solutions are equal. Here's an honest breakdown of your options in 2026, from DIY to purpose-built.

Option 1: DIY with Grafana + Custom Data Pipeline

How it works: You set up a data pipeline that reads Asterisk's queue_log or AMI events, stores them in a time-series database (InfluxDB, Prometheus, or TimescaleDB), and visualize with Grafana dashboards displayed on a TV.

The appeal: Free tools, full customization, you own the stack.

The reality:

Here's what "just set up Grafana" actually involves:

1. —Write a parser for Asterisk's queue_log format (undocumented edge cases guaranteed)
2. —Set up InfluxDB or Prometheus with proper retention policies
3. —Create a data ingestion service (Python/Node/Go) that runs 24/7
4. —Configure AMI for real-time events (edit manager.conf, handle reconnections)
5. —Build 7+ Grafana panels with the right queries
6. —Handle data gaps, timezone issues, and agent name mapping
7. —Set up alerting rules
8. —Maintain it all when Asterisk updates or your parser breaks

Time estimate: 40-80 hours for a senior engineer. Ongoing maintenance: 2-5 hours/month.

Best for: Teams with strong DevOps skills who want extreme customization and are comfortable maintaining infrastructure.

My take: I've seen teams spend three months building a Grafana wallboard that shows 70% of what a purpose-built tool provides on day one. The remaining 30% — real-time streaming, agent management, heatmaps — never gets built because the engineer who set it up moved on and nobody else understands the pipeline.

If you have the expertise and a specific reason to own the stack (compliance, integration with internal systems), go for it. Otherwise, the ROI doesn't justify the effort.

Option 2: FOP2 (Flash Operator Panel 2)

How it works: FOP2 is a web-based switchboard and operator panel for Asterisk. The wallboard is a plugin that shows queue statistics using data from Asternic Call Center Stats PRO.

Pros:

• —Integrates directly with Asterisk via AMI
• —Wallboard plugin is template-based (HTML/CSS/JS)
• —Shows real-time agent status and queue stats
• —Relatively affordable license

Cons:

• —Requires Asternic Call Center Stats PRO for full statistics
• —Template customization requires coding (Dust.js templates)
• —Statistics refresh every 30 seconds — not true real-time
• —The wallboard is a plugin, not the core product — limited capabilities
• —UI looks dated by 2026 standards
• —No heatmaps, no trend analysis, no KPI tracking

Best for: Teams already using FOP2 as their operator panel who want basic queue stats on a screen. Not ideal if the wallboard is your primary monitoring tool.

Cost: FOP2 license starts at $40 (one-time) + Asternic license if you want full stats.

Option 3: QueueMetrics Wallboards

How it works: QueueMetrics is a Java-based call center reporting tool that has included wallboard functionality since version 17.06. You build wallboards using drag-and-drop widgets — circular panels, bar charts, tables for live calls, live agents, and live queues.

Pros:

• —200+ metrics available
• —Drag-and-drop widget builder
• —Multiple views that auto-rotate (presentation mode)
• —Color-coded alerts when thresholds are breached
• —Mature product with 15+ years of development

Cons:

• —Per-agent pricing at CHF 8/agent/month — a 50-agent center pays ~$450/month just for monitoring
• —Java/Tomcat stack — heavy, requires Java expertise to install and maintain
• —Not true real-time — reads from queue_log at intervals, periodic refresh
• —50-agent minimum for on-premise licensing
• —Legacy UI — functional but not what you'd call modern or intuitive
• —Complex licensing — counts every agent ever tracked, not concurrent users

Best for: Large call centers (100+ agents) with budget for enterprise tooling and IT staff comfortable with Java infrastructure. QueueMetrics is the legacy market leader for a reason — it's comprehensive, if expensive.

Cost: From ~$90/month (10 agents) to $4,500+/month (500 agents). Cloud option (QueueMetrics-Live) available.

Option 4: Astervis — Purpose-Built Real-Time Analytics

How it works: Astervis is a next-generation analytics platform built specifically for Asterisk PBX. Unlike tools that parse log files on a timer, Astervis uses event streaming (Kafka + Debezium) for Change Data Capture, delivering sub-second dashboard updates.

Pros:

• —True real-time — sub-second latency, not periodic refresh
• —30+ pre-built charts including heatmaps, trend analysis, and operator leaderboards
• —One-command installation — curl -fsSL https://api.astervis.io/api/releases/install.sh | bash and you're running in 5 minutes
• —Flat pricing — $119/month for Starter, $449/month for Professional, both with unlimited agents. No per-agent cost surprises
• —Modern stack — Next.js, TimescaleDB, Kafka. Designed for 2026, not 2006
• —Self-hosted — your server, your data, your control
• —Operator management — KPI tracking, leaderboards, scheduling built in
• —CRM integration — native Bitrix24 and AmoCRM connectors
• —Call recording playback directly in the dashboard

Cons:

• —Newer product (less legacy market presence)
• —No cloud-hosted option yet (coming soon)
• —Doesn't support Yeastar or Grandstream UCM (Asterisk/FreePBX/Issabel/VitalPBX/Sangoma only)

Best for: Any Asterisk-based call center that wants real-time wallboard capabilities without the Java overhead, per-agent pricing, or 40-hour DIY setup time.

Cost: $119/month (Starter), $449/month (Professional), $1,199/month (Business), custom pricing (Enterprise). Unlimited agents on every tier. 14-day free trial, no credit card required.

Quick Comparison

Configuring Asterisk for Wallboard Data

Regardless of which wallboard solution you choose, Asterisk needs proper configuration to provide the data. Here are the key settings.

queues.conf — Queue Configuration

Your queues.conf settings directly affect what data is available for wallboard display:

manager.conf — AMI Access for Real-Time Data

Your wallboard tool needs AMI (Asterisk Manager Interface) access to get real-time events:

Security note: Never expose AMI port 5038 to the internet. Use bindaddr = 127.0.0.1 and connect only from localhost. If your wallboard tool runs on a different server, use an SSH tunnel or VPN.

queue_log — Historical Data

Asterisk writes queue events to /var/log/asterisk/queue_log. This file is the source for historical metrics, SLA calculations, and trend analysis.

Key events in queue_log that feed wallboard data:

Testing Your Configuration

After configuring, verify events are flowing:

Make a test call to a queue and confirm you see ENTERQUEUE, CONNECT, and COMPLETECALLER/COMPLETEAGENT events in the queue_log.

Hardware Setup: Displaying Your Wallboard

A wallboard is only useful if people can see it. Here's how to set up the physical display.

Screen Options

Large TV (recommended): A 43-55" 4K TV mounted on the call center wall. Almost every modern smart TV has a built-in browser. Cost: $300-$500.

Multiple monitors: For larger centers, use 2-3 screens showing different views — one for queue metrics, one for agent status, one for daily trends.

Existing monitors: You don't need a big TV to start. Open the wallboard URL in a browser on any monitor visible to the team.

Display Computer Options

Raspberry Pi 4/5: The most popular choice. $35-$80, runs Chromium in kiosk mode. Power consumption: 5W. Set it to boot directly into the wallboard URL.

Intel NUC / Mini PC: More powerful, handles complex dashboards with many widgets. $150-$300.

Smart TV browser: Free — just open the URL in the TV's built-in browser. Downside: most smart TV browsers are limited and may not render complex dashboards well.

Fire TV Stick: $30-$50, runs Silk browser in full-screen mode. Good enough for most wallboards.

Network Considerations

• —The display device needs reliable network access to your wallboard server
• —For self-hosted solutions (Astervis, QueueMetrics), ensure the device can reach your PBX network
• —Use a wired Ethernet connection for the display device if possible — WiFi drops mean blank screens
• —Set up auto-restart: if the browser crashes or the device reboots, it should automatically reload the wallboard

Best Practices for Wallboard Design and Usage

Keep It Scannable

A wallboard should be readable from 10-15 feet away. That means:

• —Large numbers for key metrics (60pt+ font)
• —Color coding for status (green/yellow/red)
• —Maximum 7-8 data points per screen
• —No tables with 20 columns — save that for the desktop dashboard

Use Color Intentionally

Red means action needed. Yellow means attention. Green means normal. Be consistent:

• —🟢 Green: SLA > 80%, abandon rate < 5%, all agents available
• —🟡 Yellow: SLA 65-80%, abandon rate 5-10%, staffing getting tight
• —🔴 Red: SLA < 65%, abandon rate > 10%, no agents available

Don't use red for informational items. If everything is always red, people stop looking.

Rotate Views for Large Operations

If you have more metrics than fit on one screen, use auto-rotating views:

• —View 1 (30 seconds): Queue overview — calls waiting, SLA, abandon rate
• —View 2 (30 seconds): Agent overview — status breakdown, leaderboard
• —View 3 (30 seconds): Trends — hourly call volume, AHT trend, SLA trend

Position the Screen Where People Look

Mount the wallboard where supervisors naturally look during their shift. Common placements:

• —Above the supervisor's desk (most common)
• —Center of the call center floor (visible to agents)
• —Near the entrance (management visibility)
• —In the break room (agents check on return)

Update the Thresholds Quarterly

What counts as "red" should evolve. If your SLA consistently hits 90%, a yellow threshold at 80% is too generous — you'll miss the early warning when it drops to 82%. Tighten it to 85%.

Common Mistakes That Kill Wallboard Effectiveness

Mistake 1: Showing Too Many Metrics

Thirty metrics on one screen means nobody reads any of them. A cluttered wallboard is worse than no wallboard — it creates the illusion of monitoring without actual awareness.

Fix: Stick to 5-7 metrics on the main view. Put everything else in a secondary dashboard for desktop use.

Mistake 2: Data That's Minutes Old

If your wallboard updates every 5 minutes, it's not a wallboard — it's a slideshow. During a call surge, 5 minutes is an eternity. You need sub-minute updates at minimum, sub-second ideally.

Fix: Use a solution with real-time event streaming, not log file polling. This is where tools like Astervis (CDC-based streaming) have a fundamental architectural advantage over tools that parse queue_log on a timer.

Mistake 3: No Alert Thresholds

A wallboard that always looks the same — green numbers on black background, never changing color — trains people to ignore it. The whole point is that visual changes trigger human attention.

Fix: Configure meaningful thresholds. When SLA drops, the number turns yellow, then red. When calls waiting spikes, the display changes. These visual triggers are what make wallboards work.

Mistake 4: Displaying Individual Agent Metrics Publicly

Showing "Agent #47: AHT 12:30" on a wall where everyone can see it creates shame, not motivation. Research consistently shows that public shaming reduces performance, not improves it.

Fix: Show team-level metrics on the wallboard. Show individual metrics in private supervisor dashboards. Exception: positive leaderboards ("Top 3 agents this week") can be motivating when done right.

Mistake 5: Set It and Forget It

Installing a wallboard and never changing what it displays. The call center evolves — new queues, new teams, seasonal patterns — but the wallboard stays frozen in time.

Fix: Review wallboard configuration quarterly. Are these still the right metrics? Are thresholds still meaningful? Does the team still look at it?

Getting Started: From Zero to Wallboard in Under 10 Minutes

If you run Asterisk, FreePBX, Issabel, VitalPBX, or Sangoma PBX and want a real-time wallboard without the DIY complexity or legacy tool overhead, here's the fastest path:

1. —

   Install Astervis on your PBX server (one command, 5 minutes):

   curl -fsSL https://api.astervis.io/api/releases/install.sh | bash
2. —

   Open the dashboard in any browser — you'll see live queue data immediately.

3. —

   Put it on a screen. Open the wallboard URL in a browser on your TV, Raspberry Pi, or any display device.

4. —

   Configure alerts. Set SLA, abandon rate, and wait time thresholds.

You now have a real-time wallboard with 30+ charts, heatmaps, agent status tracking, and operator leaderboards. No Java, no log file parsers, no 40-hour DIY project.

The 14-day trial is free and requires no credit card. You can run it alongside your existing monitoring to compare.

Start your free trial at astervis.io →

Astervis is a real-time call center analytics platform for Asterisk PBX. Self-hosted, 30+ charts, operator management, CRM integration. Start monitoring in 5 minutes at astervis.io.