Understanding VICIdial Real-Time Reports

Why Real-Time Reports Matter

If you manage an outbound call center, you already know that yesterday's spreadsheet is too late. VICIdial real-time reports give supervisors a live window into agent activity, dialer throughput, and campaign health. Without them, you are guessing whether agents are on calls, in pause, or simply staring at a blank screen while your vicidial dialer burns through leads.

Whether you run VICIdial on managed vicidial hosting or maintain your own vicidial server, the reporting screens work the same way. The difference is usually performance: a properly sized server with adequate RAM and low database latency renders updates in seconds. An undersized box chokes under load and makes supervisors think agents are idle when the dashboard is simply lagging.

This guide walks through the most important real-time screens, what each column means, and the operational decisions you should make when numbers drift out of range. If you are still setting up campaigns, start with our guide on outbound calling configuration before diving into live monitoring.

Accessing Real-Time Screens in VICIdial

VICIdial exposes several live views from the admin and agent interfaces. Supervisors typically use the Real-Time Report under Reports in the admin panel, while floor managers may also watch the Campaign Detail screen and agent status panels.

1. Log in to the VICIdial admin interface with a user account that has REPORT permissions.
2. Navigate to Reports, then select Real-Time Report or Real-Time Main Report depending on your version.
3. Choose the campaign or inbound group you want to monitor from the dropdown at the top.
4. Set the refresh interval. Most teams use 5 to 10 seconds during active dialing; slower refresh reduces server load.
5. Open a second browser tab with Campaign Detail if you need hopper and dial-level context alongside agent stats.

For remote supervisors, confirm that your vicidial hosting provider has not blocked admin ports behind a VPN-only policy. Many vicidial support tickets about blank real-time screens trace back to firewall rules or expired SSL certificates on the web interface, not actual dialer failures.

Key Metrics Explained

Agent Status Columns

The agent grid is the first place supervisors look. Each row represents a logged-in agent and shows their current state: INCALL, READY, PAUSED, DISPO, or DEAD. Understanding these states is essential because misread status is the number one cause of unnecessary floor interventions.

• INCALL: Agent is connected to a live customer or prospect. Duration here should align with your average talk time.
• READY: Agent is available and waiting for the predictive dialer to deliver the next call.
• PAUSED: Agent selected a pause code. Review pause codes weekly to catch excessive break time.
• DISPO: Agent is dispositioning the last call. Long DISPO times often mean your disposition list is too complex.
• DEAD: Session dropped or phone registration failed. Check SIP connectivity before blaming the agent.

Cross-reference agent status with the monitor, whisper, and barge features when you need to coach live without leaving the dashboard.

Dialer and Hopper Metrics

Campaign-level numbers tell you whether the dialer is keeping pace with agent capacity. Watch these fields closely during peak hours.

• Calls Today: Total outbound attempts for the selected campaign. Sudden flatlines usually indicate a carrier or trunk issue.
• Answers Today: Live human connections. Compare against Calls Today to calculate your contact rate in real time.
• Dial Level: Current predictive dial ratio. We cover tuning in our dial levels guide.
• Hopper Count: Leads queued and ready to dial. A hopper near zero means agents will go idle within minutes.
• Active Calls: Live channels in use including ringing and connected states.
• Dropped Calls: Monitor against your compliance threshold. Spikes warrant immediate dial-level reduction.

A healthy hopper on a predictive campaign typically holds at least two to three times your active agent count. If hopper count collapses while agents show READY, verify that leads were imported correctly and that filters are not excluding your entire list. Our lead import guide covers the most common data issues.

Inbound and Blended Metrics

Blended campaigns add queue depth and service level to the picture. Real-time inbound panels show calls waiting, longest wait time, and agents assigned to inbound groups. When outbound is slow, some operations pull agents to inbound manually; the real-time screen confirms whether that shift actually happened or agents remain locked to an empty outbound hopper.

Building a Supervisor Routine Around Live Data

Effective floor management is repetitive by design. Top supervisors run the same checklist every fifteen minutes during a shift rather than reacting to gut feeling.

1. Scan agent states: count PAUSED and DISPO rows. More than ten percent of the floor in PAUSED for over five minutes deserves a walk-by.
2. Check hopper and dial level: confirm the dialer is feeding agents. Adjust dial level in small increments if drop rate is safe.
3. Compare answers to calls: a falling contact rate may indicate list fatigue, wrong time zone filtering, or carrier blocking.
4. Review dropped calls: if above policy, lower dial level immediately and investigate trunk capacity.
5. Note anomalies in a shift log: timestamp, metric, action taken. This builds data for weekly ops meetings.

Pair this routine with lead recycling best practices so callbacks and no-answer leads re-enter the hopper on a schedule instead of flooding it unpredictably.

Customizing and Filtering Views

Large teams rarely monitor every campaign at once. Use campaign filters to isolate a single list test or a new agent training group. Some VICIdial builds support user group restrictions so team leads only see their agents, which reduces noise and prevents accidental changes to unrelated campaigns.

Color coding and column order vary by version, but the underlying data model is consistent. Export permissions are separate from view permissions. If a supervisor can see real-time data but cannot export historical reports, that is normal. Historical analysis belongs in the outbound reporting module or an external BI tool fed by the VICIdial database.

When evaluating vicidial pricing and vicidial cost proposals from vendors, ask whether real-time reporting performance is guaranteed at your agent count. A low vicidial cost quote that skimps on CPU and database I/O will show up here first as stale numbers and angry supervisors.

Troubleshooting Common Real-Time Report Issues

Dashboard Not Refreshing

When the clock on the real-time page freezes, check Asterisk and the VICIdial keepalive processes before opening a vicidial support case.

1. Confirm the web server and MySQL/MariaDB service are running on the vicidial server.
2. Check disk space on /var and the MySQL partition. Full disks cause silent query failures.
3. Review the asterisk CLI for channel buildup. Stuck channels reduce accuracy of active call counts.
4. Restart the VICIdial AST_VDauto_dial process only after confirming no regulatory risk from orphaned calls.
5. Test from another browser to rule out cached JavaScript or ad-block extensions.

Agent Count Mismatch

If real-time shows fewer agents than expected, agents may be logged into the wrong campaign, using the wrong phone login, or stuck in a dead session from a dropped VPN. Have agents log out completely and re-login. Verify phone registration in the phones panel matches the agent session.

Metrics Look Inflated or Duplicated

Duplicate agent rows often appear after browser refreshes during login storms at shift start. Clearing dead sessions from the user status screen usually resolves it. Inflated call counts can indicate retried autodial on carrier failure; cross-check with your SIP carrier configuration and look for rapid NO ANSWER cycles in the carrier CDR.

Performance and Hosting Considerations

Real-time reporting is database-read heavy. Every refresh issues queries against live agent and call tables. On a shared vicidial hosting platform, noisy neighbors or missing indexes hurt everyone. Dedicated hardware or properly isolated VPS resources scale linearly with agent count.

Recommended baselines for smooth dashboards: SSD storage, at least 4 GB RAM for deployments under fifty agents, and MariaDB tuned with innodb_buffer_pool_size set to a reasonable fraction of available memory. Enable slow query logging during peak hours to catch reports that need optimization.

If you are planning vicidial setup from scratch, provision the database on the same LAN as the dialer application server. Latency above five milliseconds between app and DB is rarely fatal but above twenty milliseconds supervisors will notice refresh lag during busy campaigns.

Conclusion

VICIdial real-time reports are not decoration. They are the feedback loop that connects dialer configuration, list quality, carrier health, and agent behavior into one screen. Supervisors who learn to read agent states, hopper depth, and drop rate together make better decisions than those who watch a single number in isolation.

Start with a consistent monitoring routine, fix infrastructure issues before blaming agents, and cross-train on related topics like dial levels and call transfers so the whole floor speaks the same language. When reports stay fast and accurate, your outbound operation stays predictable, and that is worth more than any single campaign tweak.