What is the difference between Erlang C and Erlang A?
Erlang C assumes customers will wait in queue until an agent is available. Erlang A adds abandonment, which makes it more realistic when callers may hang up after waiting too long.
Model voice, chat, and asynchronous workloads with Erlang C, Erlang A, Erlang B, and Linear staffing calculations. Estimate required agents, service levels, occupancy, hourly coverage, and FTE requirements in one place.
Operating Hours
Calculator Type
Adjust the volume distribution across hours
Volume will be distributed evenly during business hours.
Erlang C assumes customers will wait in queue until an agent is available. Erlang A adds abandonment, which makes it more realistic when callers may hang up after waiting too long.
A common benchmark is 80% of contacts answered within 20 seconds, but the right target depends on your channel mix, customer expectations, and service cost tradeoffs.
Shrinkage covers paid time agents are unavailable for contacts, including breaks, meetings, coaching, training, absence, and system downtime. Many contact centers plan for roughly 25% to 35% total shrinkage.
Use the Linear method for asynchronous work such as email, tickets, and back-office processing where customers are not actively waiting in a real-time queue.
Yes. For live chat, set concurrency to the number of simultaneous chats each agent can handle. Use Erlang for queued chats and Linear for asynchronous messaging workflows.