What server does VICIdial need for 100 agents?
For 100 agents dialing predictive at three lines each, one Turbo server with 32 dedicated cores carries the floor at about 58% CPU at the busiest minute; 100 inbound agents fit Velocity and 100 manual agents fit Ultimate. At this size the calculator also lays out a cluster, shown under the main table. VICIfast hosts either as managed VICIdial: the same VICIdial admin and agent screen, with the servers patched, backed up and monitored for you.
| How the floor dials | Calls at peak | Smallest server that fits | Peak CPU |
|---|---|---|---|
| Outbound, predictive 3 lines per waiting agent | 300 | Turbo · 32 dedicated cores · $1,899/mo | 58% |
| Inbound every agent on a call, 10% more waiting | 111 | Velocity · 16 dedicated cores · $899/mo | 61% |
| Manual dialing one line per agent | 100 | Ultimate · 16 shared cores · $749/mo | 58% |
- Bandwidth at peak
- 35 Mbps
- Predictive outbound, both legs
- Carrier channels
- 360
- Concurrent calls to ask your carrier for
- Recordings per day
- 30.2 GB
- 8 dialing hours
- Days of recordings on disk
- 18
- On Turbo, before offloading
| Role | Servers | Each |
|---|---|---|
| Database | 1 | Velocity · 16 dedicated cores · $899/mo |
| Database replica | 1 | Velocity · 16 dedicated cores · $899/mo |
| Web and agent phones | 3 | Surge · 8 dedicated cores · $449/mo · 34 agents |
| Dialer (Asterisk) | 2 | Pro · 8 shared cores · $399/mo · 150 calls |
The first table is one server per dialing mode. The second is the cluster layout for the predictive row. The agent counts on pricing are suggestions for a typical mix: Ultimate is listed for 100 agents and Velocity for 100, yet 100 predictive agents need Turbo, because they carry about three live calls each.
Why does the calculator suggest a cluster at 100 agents?
Because 100 agents is where we start suggesting one, even though a single server still fits: from here, the bigger question is what happens when the one server that carries every call and every report has a bad minute. The cluster splits the work by role:
- Database and replica - two servers with 16 dedicated cores each (Velocity). The replica is identical, and reports read it, so long reports stay off the live database.
- Three web servers - Surge, 8 dedicated cores each. They serve the agent screens and run the agents' phones, about 35 agents per server.
- Two dialers - Pro, 8 cores each, running Asterisk only. Each has room for about 250 live calls, and with two, losing one does not stop every call.
Treat this as a starting design. The single-server figures come from a model we check against real shifts on our servers; the cluster layout follows the rules we build VICIdial clusters by, and we confirm it with you before anything is built.
One big server or a cluster: which is better for 100 agents?
One server is simpler and costs less; a cluster costs more but spreads the risk and gives the floor room to grow past what any one server carries.
| One server (Turbo) | Cluster | |
|---|---|---|
| Servers | 1 | 7: database, replica, 3 web, 2 dialers |
| Peak CPU | about 58% of 32 cores | spread across roles |
| If a server fails | every call stops | losing a dialer or web server stops part of the floor; the database is still shared |
| Reports | run on the database the dialer uses | read the replica |
| Room to grow | resize to Hyper, which carries about 150 predictive agents at 59% | add web servers and dialers |
| Monthly cost | one plan - see the first table | the total under the cluster table |
| Set-up | ready in under 40 seconds | delivered in under 24 hours |
Neither column changes the agent's day: the agent screen, the admin and the reports are the same VICIdial either way. How many agents fit on one VICIdial server covers the single-server side in more depth.
When is a cluster worth it at 100 agents?
A cluster is worth it when an hour of the whole floor being down costs more than the extra servers, when reports run hard during dialing hours, or when you expect to pass 150 predictive agents, where one server stops being enough. One server is the better answer when:
- you run one site, and growth is flat for the next year;
- reporting is light, or runs after hours - VICIdial reports explained shows which reports your supervisors actually use;
- the floor is inbound or manual. Velocity or Ultimate carries 100 of those agents, and a cluster buys you little.
If you start on one server, one-click resize moves it to a bigger plan later, keeping its data and IP address.
Where to start
Put your floor in the capacity calculator, then change the lines per agent and the inbound calls and watch where one server stops fitting. For one server, start the 7-day free trial (card required). For a cluster, see enterprise delivery or talk to us - a person reads every message and answers by the next business day.