How Phone Aliases Balance Agents Across Servers

In a multi-dialer call center, you want agents spread evenly across servers so no single box carries the whole floor. Doing that by hand is tedious and falls apart the moment shifts overlap. Phone aliases do it automatically: every alias login is steered to the dialer that is currently the least busy.

What the load-balancer actually counts

When an agent logs in with an alias and submits their campaign, the system looks at every active server in the cluster and counts the non-remote agents attached to each one. It then connects the call from the server with the lowest count. A real Remote agent on a phone line elsewhere is not counted toward a server's local load, which is why the count is specifically of the agents physically homed on that dialer.

Because the agent's Softphone already holds a registration to every dialer behind the alias, the winning server can ring its line immediately. No re-registration, no re-login.

flowchart LR
  A[Alias login submitted] --> B[List active servers]
  B --> C[Count local agents on each]
  C --> D{Lowest count}
  D --> E[Place call from that dialer]
  E --> F[Agent is live and balanced]

Why evenness matters

Spreading agents evenly keeps any one Server trunk from saturating and keeps call quality consistent across the cluster. It also makes capacity planning honest: you can add a dialer and watch new logins flow to it without touching a single agent profile.

• Overlapping shifts no longer pile onto one server
• Adding a dialer rebalances new logins automatically
• Admins stop hand-assigning agents to servers

This is also the foundation for failover: if a server drops out of the active list, it stops receiving logins and existing agents can rejoin elsewhere. For the full mechanism, see the phones and aliases guide, and how to set a phone's server IP, since the server IP is what makes each alias phone unique.

VICIfast can scale your cluster horizontally and let aliases distribute the floor for you — see pricing.