Erlang B Calculator

Work out how many phone lines, SIP trunk channels or IVR ports you need for your busiest hour, and how many calls get a busy signal at the count you have now.

Sizing agents rather than lines? Use the Erlang C calculator. Connecting your own trunk to a voice agent? See the SIP trunk docs.

How do you want to enter traffic?

Inbound and outbound calls that need a line at the same time.

min

Decimals are fine: 2.5 is two and a half minutes.

Leave at 0 to skip.

Lines needed

18

for 1% blocking or less

Busy-hour traffic

10.00 erlangs

Blocking at that count

0.71%

Share of calls that find every line busy

Blocked calls per busy hour

1.43

Lines needed at each blocking target

Target blockingLines neededActual blocking
0.1%210.09%
0.5%190.37%
1%180.71%
2%171.29%
5%153.65%

Assumptions

  • Traffic:Calls x average minutes / 60, for the single busiest hour
  • Blocked calls:Are lost, not queued or retried (the Erlang B model)
  • Arrivals:Random and independent; a line is either busy or free

If callers wait in a queue for an agent instead of hearing a busy tone, that is Erlang C. Use the Erlang C calculator to size agents, then this one to size the lines they need.

Erlang B or Erlang C?

Both start from the same busy-hour traffic in erlangs. They answer different questions.

  • Erlang B sizes lines: SIP trunk channels, PRI channels, IVR ports, or concurrent calls on a voice agent. A call that arrives when every line is busy is blocked and lost. The output is the blocking probability, also called grade of service.
  • Erlang C sizes agents: callers who find every agent busy wait in a queue. The output is service level and average wait. Use the Erlang C calculator for that.

A contact center usually needs both: Erlang C for the agents, then Erlang B for the lines, with extra lines for the callers waiting in the queue.

How to read the result

Traffic in erlangs is calls in the busy hour times average minutes, divided by 60. 200 calls of 3 minutes is 10 erlangs. At 1% blocking, 10 erlangs needs 18 lines, not 10, because calls do not arrive evenly. With 15 lines, about 3.65% of calls would be blocked.

Use your busiest hour, not a daily average. If you only have daily calls, look at an hourly report for the peak, or the talk time calculator for minutes.

Run it on Edesy

  • IVR: an Edesy IVR answers every busy-hour call with menus, keypress input and call routing. Start free: INR 20 credit on sign-up, no card needed. Estimate the running cost with the IVR cost calculator.
  • AI voice agent concurrency: a voice agent takes many calls at once, so the line count here is the concurrency to plan for. Try Edesy Voice Agent, or bring your own trunk with the SIP trunk docs.

More on trunks: SIP trunk providers in India for AI calling.

Erlang B calculator FAQ

How many SIP trunks do I need?

Enter your busy-hour calls and average call length. The calculator finds the fewest SIP trunk channels that keep blocking at or below your target. For example, 200 calls of 3 minutes (10 erlangs) needs 18 channels for 1% blocking. Each channel carries one call at a time.

What is an erlang?

One erlang is one line in use for a full hour. 60 one-minute calls in an hour, or 20 three-minute calls, is 1 erlang. Traffic in erlangs is busy-hour calls times average minutes, divided by 60.

What blocking target should I pick?

1% is a common choice for business lines and IVRs. Pick 0.1% or 0.5% when a lost call is expensive, such as sales or emergency lines, and 2% to 5% for low-priority outbound lines. Lower blocking needs more lines; the table shows the count for each target.

What is the difference between Erlang B and Erlang C?

Erlang B assumes a call that finds every line busy is lost, so it sizes lines and trunks. Erlang C assumes the caller waits in a queue, so it sizes agents. Use the Erlang C calculator for agents and this one for the lines they use.

Does it account for callers who redial?

No. Erlang B assumes blocked calls are lost and not retried. If many blocked callers redial at once, real traffic is higher than you entered, so add some margin or pick a lower blocking target.

Can I use it for an AI voice agent or IVR?

Yes. The line count is the number of calls that must be handled at the same time, which is the concurrency you plan for on an IVR or a voice agent, and the channel count on the SIP trunk behind it.

Features

  • Lines needed for 0.1% to 5% blocking

  • Enter calls and minutes, or erlangs directly

  • Blocked calls per busy hour

  • Check the lines you have now: short or spare

  • Side-by-side table of every blocking target

  • Runs in your browser, no signup

When people use it

Buying SIP trunk channels

Find the channel count to order before a campaign or a switch to a new provider.

Sizing IVR ports

Check how many simultaneous calls an IVR or voice bot must answer in the busy hour.

Auditing existing lines

See how many callers hit a busy tone today and how many lines close the gap.