VICIfast

Free tool

Agent capacity calculator

Outbound, inbound or blended: tell it your agents and calls at the busiest minute. It picks the server that carries them, prices it in your region and shows the bandwidth, carrier channels and recording storage around it. Bigger floors get a cluster design. Sized from real VICIdial traffic on our servers, not a spec sheet.

Campaign type

How they dial
3

VICIdial’s dial level. 2 to 4 is typical; lists full of voicemail and no-answers often run 8 or more. That’s 60 outbound calls at once.

Record every call?

VICIdial records the part of each call that is connected to an agent.

Prices and core counts differ a little by region.

Advanced

Used for dial attempts per minute.

Used for monthly traffic and recording storage.

Recommended for your floor

Pro

$399/mo in Ashburn

8 shared cores · 16 GB RAM · 240 GB disk

CPU at your busiest minuteabout 38%
our 60% limit
Live calls
60
Channels
182
Agents it holds
29
working like this

Dialing all day? Surge puts you on 8 dedicated cores for $449/mo, with no neighbours sharing them.

Around the server

What else to plan for

Bandwidth, each way
7.0 Mbps
G.711 audio for 80 streams; about 0.55 TB a month of the 20 TB included.
Carrier channels to ask for
80
Your peak is 60 calls at once; this adds a fifth for spikes.
Dial attempts
up to 120/min
About 2.0 calls per second at a 30 s ring timeout. Check your carrier allows it.
Recording storage
6.0 GB/day
At 8 h a day with agents talking 60% of the time. Pro’s disk holds about 33 days before they move off.

Every plan in Ashburn

How each server handles your floor

20 agents, 60 outbound calls at once, recording on.

  • Launch$49/mo

    2 shared cores · 2 GB · up to 5 agents

    Over its 5-agent seat guide
  • Scale$99/mo

    3 shared cores · 4 GB · up to 10 agents

    Over its 10-agent seat guide
  • Growth$219/mo

    4 shared cores · 8 GB · up to 16 agents

    75%
  • Pulse$249/mo

    4 dedicated cores · 16 GB · up to 18 agents

    75%
  • ProBest fit$399/mo

    8 shared cores · 16 GB · up to 29 agents

    38%
  • Surge$449/mo

    8 dedicated cores · 32 GB · up to 33 agents

    38%
  • Ultimate$749/mo

    16 shared cores · 32 GB · up to 53 agents

    19%
  • Velocity$899/mo

    16 dedicated cores · 64 GB · up to 61 agents

    19%
  • Turbo$1,899/mo

    32 dedicated cores · 128 GB · up to 119 agents

    9%
  • Hyper$3,249/mo

    48 dedicated cores · 192 GB · up to 176 agents

    6%

The tick on each bar is that plan’s limit: 70% of its cores on dedicated plans, 60% on shared ones. Amber is over it.

The method

How we size it, in plain English

  1. Live calls are the outbound lines (agents times dial level; manual and one-line dialing count one per agent) plus the inbound calls talking or waiting in queue.
  2. Each live call uses about 2.2 phone-system channels, and each logged-in agent about 2.5 (their phone, their conference and the dialer’s leg).
  3. On a small floor about 75 channels keep one core busy, with a little on top for the database, web server and VICIdial’s background jobs. Past about 150 channels each one costs more, about 47 to a core, because they all compete for the same cores.
  4. We pick the cheapest plan whose busiest minute stays under 70% CPU (60% on shared cores, which a neighbour can borrow), within the plan’s seat guide. The rest is headroom for spikes.
  5. Clusters split the work by role and are sized from how we run VICIdial clusters, not from the single-server numbers above: a database with an identical replica, one web server per 35 agents carrying their phones, and an Asterisk-only dialer per 250 live calls.
  6. Answering-machine detection isn’t counted: on VICIfast it runs off the dialer. If you use VICIdial’s built-in AMD instead, go one size up.

Fitted in October 2026 from about 7,700 busy minutes on four production VICIdial servers, and refitted from two full shifts on a 16-core dedicated server dialing about 10 lines per agent, where 166 live calls and 17 agents kept 7.5 cores busy. Its agents spent about 60% of their time talking and its recordings took about 63 MB per recorded hour. Bandwidth assumes G.711 audio (87 kbps per stream each way). It’s an estimate, so ramp a new floor up in steps; if you outgrow a plan, you can move to a bigger one from your dashboard.

Questions

Capacity, answered

How many agents can one VICIdial server handle?
It depends more on how many lines each agent dials than on the agent count. At 3 lines per agent with recording on, the calculator puts Pulse (4 dedicated cores) about 18, Surge (8 dedicated cores) about 33, Velocity (16 dedicated cores) about 61, Turbo (32 dedicated cores) about 119, Hyper (48 dedicated cores) about 176 agents, keeping the busiest minute under 70% CPU.
How many concurrent calls can a VICIdial server handle?
Each live call is about 2.2 Asterisk channels and each logged-in agent about 2.5. On a small floor about 75 channels keep one core busy; past about 150 channels each one costs more, about 47 to a core, as we measured on a busy predictive floor. So a 16-core dedicated server with 25 agents stays under 70% CPU up to roughly 220 live calls.
How do I size a server for inbound calls?
Count the calls at your busiest minute: callers talking to agents plus callers waiting in queue. Each one loads the server like an outbound line, so a blended floor adds its inbound calls to its outbound lines.
When do I need a VICIdial cluster?
From about 100 agents or 500 live calls, or as soon as one server can't carry the floor. A cluster splits the work by role: a database server with an identical replica, web servers for the agent screens and the agents' phones, and two or more Asterisk-only dialers for the calls, so losing one doesn't stop every call. For example, 300 agents at 3 lines each comes out at 1 Velocity database server, 1 Velocity database replica, 9 Surge web servers with the agents' phones, 4 Pro dialers. Past about 1,000 agents, one database is the limit and it becomes two clusters.
Does call recording need a bigger server?
Rarely. VICIdial only records calls that are connected to an agent, so even a floor dialing ten lines per agent has one recording per agent at most. On a busy server recording and its MP3 encoding came to about 5 to 8% of the CPU.
Do I need dedicated CPU for predictive dialing?
Not for a small floor. Shared cores are fine, but a neighbour can borrow them, so the calculator keeps shared plans under 60% at peak instead of 70%. For a floor that dials all day, dedicated cores keep audio steady at the busiest minute.