How to read the Maximum System Stats report

The Maximum System Stats report gives you a table and a bar graph for each of the last 30 days, tracking seven peak figures across calls and agents — it is the go-to report for understanding how close your server and carrier trunks are to their limits on any given day.

The seven figures tracked each day

For every calendar day in the 30-day window, the report records:

• Total call count in and out — the combined volume of every inbound and outbound call the system processed that day.
• Total inbound call count — inbound-only volume, useful for measuring queue demand against staffing.
• Total outbound call count — outbound-only volume, which tracks your Campaign throughput.
• Most concurrent calls in and out — the single highest simultaneous combined call count reached during the day. This is the peak that sizes your server and your Carrier trunk capacity.
• Most concurrent calls inbound total — the peak simultaneous inbound call count, which sizes your inbound trunk allocation.
• Most concurrent calls outbound total — the peak simultaneous outbound call count, which sizes your outbound dialing capacity.
• Most concurrent agents — the highest simultaneous logged-in Agent count for the day, which sizes your licensing and server headroom.

The table and the bar graph

The report presents each day in two ways. The data table gives you the exact numbers so you can compare days precisely and spot the outlier with the highest peak. The bar graph puts the same data in visual form so you can see trends, seasonality, and whether peaks are creeping upward over time without needing to read 30 rows of numbers in sequence.

Use the table when you need the exact peak number for a specific day. Use the bar graph when you want to understand whether the operation is growing or whether peaks are approaching your installed capacity.

flowchart LR
  A["30-day data window"] --> B["Data table per day"]
  A --> C["Bar graph per day"]
  B --> D["Exact peak numbers"]
  B --> E["Day-level comparisons"]
  C --> F["Visual trend and seasonality"]
  C --> G["Creeping peaks toward ceiling"]
  D --> H["Size trunks and server"]
  E --> H
  F --> I["Plan capacity ahead of the breach"]
  G --> I

What this report is actually for

Every figure in Maximum System Stats except the total call counts is a peak, not an average or a total. That distinction is intentional. Hardware, trunks, and Concurrent calls capacity are all sized for worst-case simultaneous load, not for daily totals. A server that handled 4,000 calls in a day is fine; a server whose peak hit 200 simultaneous channels at 2pm may be in trouble depending on how many cores it has.

The 30-day window is long enough to capture at least four weekly cycles, so you can see whether your Tuesday peak is always higher than your Monday peak, or whether month-end calling campaigns push one week well above baseline. Once you know the pattern, you can compare new days against it and spot anomalies quickly.

The report does not show real-time data. For live monitoring use the Real-time report. Maximum System Stats is retrospective — it helps you understand what happened and plan what comes next.

How to use the report in practice

A good weekly habit is to open Maximum System Stats on Monday morning and scan the prior week. Look at the most-concurrent-calls combined column and find the single highest day. That number tells you how close to your trunk ceiling you came. If it is above 80 percent of your capacity, add a capacity review to the week's tasks. If it is above 90 percent on more than one day, that is an immediate action item.

The same scan applies to the most-concurrent-agents column. Compare it against your licensed seat count. A consistent gap between the two means you have a comfortable buffer. A gap that has been narrowing week over week is a warning that staffing growth is outpacing your current configuration.

Neither the table nor the bar graph requires any special setup — the report is available in the Reports section of any VICIdial installation that has been running long enough to accumulate data. You do not need to enable it separately the way you do with the Server Performance Report. It populates automatically as the system processes Concurrent calls each day.

For the overall framework of what to watch and when, see our guide to monitoring VICIdial server health and capacity. To understand how load and channel counts behave during a live shift, read how to read the Server Performance Report.

If you want a VICIdial box where these reports are pre-configured and available from day one, spin up a managed VICIdial box on VICIfast — it provisions in under 40 seconds with reporting enabled.