Technology AI

How many phone lines a plumbing office needs

Phone lines are sized by concurrent calls, not staff. Read your peak from call records, run the Erlang B numbers and plan for a freeze-day surge.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing9 min read

On this page
  1. Lines are a peak problem, not a headcount problem
  2. What holds a line besides a customer talking
  3. Three kinds of line, three kinds of limit
  4. Read your peak from the call records
  5. Turn the peak into a line count with Erlang B
  6. Why ten lines won't save a freeze morning
  7. Starting points by office size
  8. Busy signals hide in your reports
  9. Frequently asked questions
  10. References
Technology AI: How many phone lines a plumbing office needs$15,400: average homeowners insurance claim for water damage and freezing, 2019 to 2023TECHNOLOGY AIHow many phone lines aplumbing office needs$15,400average homeowners insurance claim for waterdamage and freezing, 2019 to 2023Ava for PlumbersInsightsTechnology AI: How many phone lines a plumbing office needs$15,400: average homeowners insurance claim for water damage and freezing, 2019 to 2023TECHNOLOGY AIHow many phone linesa plumbing officeneeds$15,400average homeowners insurance claim forwater damage and freezing, 2019 to2023Ava for Plumbers
Figure source: Insurance Information Institute, 2025[1]

Key takeaways

  • Size lines by the most calls connected at once, not by desks: callers on hold, callbacks, techs calling in and forwarded calls all hold a line.
  • Traffic in erlangs is calls in the busiest hour times minutes per call, divided by 60; the Erlang B formula turns that into the chance a caller hears busy[2].
  • Example: six lines carry a two-erlang normal peak with about 1 caller in 100 blocked, but on a five-erlang freeze morning the same six lines block nearly 1 in 5.
  • Lines beyond the people who can answer only lengthen the hold queue. Plan the surge as an overflow layer, not a bigger line count.

Lines are a peak problem, not a headcount problem

Ask most owners how many lines they need and they count desks. Two CSRs and a dispatcher, so three lines. Then a cold snap arrives. The dispatcher is on with a tech, both CSRs have callers on hold, the owner is returning an estimate call from the office phone, and the fifth caller hears a busy signal. That caller never reached the queue, so they are not on the abandoned-call report. In many setups they are on no report at all.

What matters is call paths: how many conversations, or waiting callers, can be connected to your system at the same moment. Queueing research models it exactly that way. The number of trunk lines is the upper limit on calls in the system, waiting or being served, and a caller who finds every line occupied gets a busy signal and is blocked[2].

Staff count still matters, for a different question. People decide how fast calls are answered; lines decide whether calls get in at all. The CSR staffing guide covers the first question. This one covers the second, and the two answers are rarely the same number.

What holds a line besides a customer talking

  • Callers on hold or in a queue. A waiting caller holds a path for every second they wait.
  • Callbacks and other outbound calls. The CSR returning yesterday's voicemails is on a path a new caller can't use.
  • Techs calling in. Parts questions, job updates and “can you look up the last visit” calls peak when customer calls do.
  • Forwarded calls. On many trunk-based systems a call forwarded to an outside number holds a path in and a path out for its whole length. Ask your provider whether yours does.
  • Transfers and three-way calls. Conferencing in a supplier or a property manager can tie up two paths at once.
  • Legacy devices. Fax machines, alarm panels and elevator phones count if they share the same pool of lines.

Count all of it when you measure. A shop that sizes for customer calls alone usually finds its real peak is higher once outbound calls and tech traffic are added, and the gap is widest in exactly the hour you care about: the first hour of a bad-weather morning, when every tech is phoning in about parts and every CSR is calling customers to move appointments.

Three kinds of line, three kinds of limit

Ask your provider for the concurrency limits in writing: per number, per account and for forwarded calls.
SetupWhat limits concurrent callsWhat the extra caller gets
Analog lines on copperOne call per physical line; extra lines roll over in a hunt sequenceA busy signal, or whatever busy treatment the carrier offers
SIP trunk to an office phone systemThe number of channels (call paths) you pay forBusy, or the system's all-channels-busy rule
Hosted cloud phone serviceUser licences, plan limits on simultaneous calls, and queue settingsQueue, voicemail or overflow, depending on the rules you set

Cloud systems moved the bottleneck. A hosted queue can hold many callers at once: Microsoft Teams, for example, lets 50 calls wait in a queue by default and up to 200[3]. On those systems the hard limit is usually people and the rules you write, not wires, so the useful question becomes what happens to call number six when five people are busy.

Hosted calls also need internet capacity. Cisco's figures put one call on the G.711 codec at 87.2 kbps on Ethernet, or 31.2 kbps with the compressed G.729 codec[4]. Eight simultaneous G.711 calls need roughly 0.7 Mbps in each direction. That is small next to most business connections, but upload is where cheap plans and busy offices run short. Test call quality at 8 a.m. on a Monday, with the cloud backups and tablet syncs running, not at 4 p.m. on a Friday.

Read your peak from the call records

  1. Export the call detail records

    Four to eight ordinary weeks of every call, inbound and outbound, with start and end times. Most phone systems export this as a spreadsheet.

  2. Count overlaps, not calls

    For each call, count how many others were connected when it started. The highest number in each 15-minute block is that block's concurrency.

  3. Find the busy normal hour

    Take the busiest weekday hour that wasn't a storm or a holiday. That is the hour you size for every day.

  4. Measure line-holding time

    Average minutes from connection to hang-up, including time ringing in the queue and on hold, not just talk time.

  5. Pull your worst day

    Find the freeze, rainstorm or holiday Monday in the last two years and run the same count. The ratio to the normal peak is your surge factor.

If your system only shows daily totals, ask the provider whether it keeps a concurrent-calls or peak-channels figure; some do for billing even when it isn't on the dashboard. The same export also builds the hour-of-week profile described in forecasting plumbing call volume.

Turn the peak into a line count with Erlang B

Telephone engineers size trunks with the Erlang B formula, which gives the chance that a caller finds every line busy for a given amount of traffic and number of lines[2]. Traffic is measured in erlangs: calls in the hour multiplied by average holding minutes, divided by 60. One erlang is one line busy for a whole hour. A helpful property for a plumbing office is that the blocking figure depends on the average call length, not the mix, so a morning of two-minute status calls and fifteen-minute booking calls is no problem for the math[2].

Example: 24 calls arrive in the busiest normal hour, and each holds a line for 5 minutes including ringing and hold. That is 24 × 5 ÷ 60 = 2.0 erlangs. On a freeze morning the same office sees 60 calls in that hour, which is 5.0 erlangs.

Example: callers who would hear busy, by number of linesModelled with the Erlang B formula. Normal peak: 24 calls an hour; freeze morning: 60 calls an hour; 5 minutes per call including hold.
Example: callers who would hear busy, by number of linesColumn chart. 2 lines: Normal peak (2.0 erlangs) 40%, Freeze morning (5.0 erlangs) 67.6%; 3 lines: Normal peak (2.0 erlangs) 21.1%, Freeze morning (5.0 erlangs) 53%; 4 lines: Normal peak (2.0 erlangs) 9.5%, Freeze morning (5.0 erlangs) 39.8%; 5 lines: Normal peak (2.0 erlangs) 3.7%, Freeze morning (5.0 erlangs) 28.5%; 6 lines: Normal peak (2.0 erlangs) 1.2%, Freeze morning (5.0 erlangs) 19.2%; 7 lines: Normal peak (2.0 erlangs) 0.3%, Freeze morning (5.0 erlangs) 12.1%; 8 lines: Normal peak (2.0 erlangs) 0.1%, Freeze morning (5.0 erlangs) 7%.0%20%40%60%80%2 lines · Normal peak (2.0 erlangs): 40%40%2 lines · Freeze morning (5.0 erlangs): 67.6%67.6%2 lines3 lines · Normal peak (2.0 erlangs): 21.1%21.1%3 lines · Freeze morning (5.0 erlangs): 53%53%3 lines4 lines · Normal peak (2.0 erlangs): 9.5%9.5%4 lines · Freeze morning (5.0 erlangs): 39.8%39.8%4 lines5 lines · Normal peak (2.0 erlangs): 3.7%3.7%5 lines · Freeze morning (5.0 erlangs): 28.5%28.5%5 lines6 lines · Normal peak (2.0 erlangs): 1.2%1.2%6 lines · Freeze morning (5.0 erlangs): 19.2%19.2%6 lines7 lines · Normal peak (2.0 erlangs): 0.3%0.3%7 lines · Freeze morning (5.0 erlangs): 12.1%12.1%7 lines8 lines · Normal peak (2.0 erlangs): 0.1%0.1%8 lines · Freeze morning (5.0 erlangs): 7%7%8 linesExample: callers who would hear busy, by number of linesColumn chart. 2 lines: Normal peak (2.0 erlangs) 40%, Freeze morning (5.0 erlangs) 67.6%; 3 lines: Normal peak (2.0 erlangs) 21.1%, Freeze morning (5.0 erlangs) 53%; 4 lines: Normal peak (2.0 erlangs) 9.5%, Freeze morning (5.0 erlangs) 39.8%; 5 lines: Normal peak (2.0 erlangs) 3.7%, Freeze morning (5.0 erlangs) 28.5%; 6 lines: Normal peak (2.0 erlangs) 1.2%, Freeze morning (5.0 erlangs) 19.2%; 7 lines: Normal peak (2.0 erlangs) 0.3%, Freeze morning (5.0 erlangs) 12.1%; 8 lines: Normal peak (2.0 erlangs) 0.1%, Freeze morning (5.0 erlangs) 7%.2 lines2 lines · Normal peak (2.0 erlangs): 40%40%2 lines · Freeze morning (5.0 erlangs): 67.6%67.6%3 lines3 lines · Normal peak (2.0 erlangs): 21.1%21.1%3 lines · Freeze morning (5.0 erlangs): 53%53%4 lines4 lines · Normal peak (2.0 erlangs): 9.5%9.5%4 lines · Freeze morning (5.0 erlangs): 39.8%39.8%5 lines5 lines · Normal peak (2.0 erlangs): 3.7%3.7%5 lines · Freeze morning (5.0 erlangs): 28.5%28.5%6 lines6 lines · Normal peak (2.0 erlangs): 1.2%1.2%6 lines · Freeze morning (5.0 erlangs): 19.2%19.2%7 lines7 lines · Normal peak (2.0 erlangs): 0.3%0.3%7 lines · Freeze morning (5.0 erlangs): 12.1%12.1%8 lines8 lines · Normal peak (2.0 erlangs): 0.1%0.1%8 lines · Freeze morning (5.0 erlangs): 7%7%
  • Normal peak (2.0 erlangs)
  • Freeze morning (5.0 erlangs)

Source: Gans, Koole and Mandelbaum, Manufacturing & Service Operations Management (INFORMS), 2003[2]

Show the data
LinesNormal peak (2.0 erlangs)Freeze morning (5.0 erlangs)
2 lines40%67.6%
3 lines21.1%53%
4 lines9.5%39.8%
5 lines3.7%28.5%
6 lines1.2%19.2%
7 lines0.3%12.1%
8 lines0.1%7%

Read it across. On the normal day, four lines block about 1 caller in 10 and six lines about 1 in 100. On the freeze morning, six lines block nearly 1 in 5, and it takes ten lines to get back to about 2 in 100 (Example, modelled with the Erlang B formula[2]).

Write a target down. A sensible one for a plumbing office is about 1 caller in 100 hearing busy in a normal peak hour. Then decide what you will accept on the worst day, because buying lines for the worst day has a catch.

Why ten lines won't save a freeze morning

Lines without people only make longer queues. If three people can answer and ten lines are open, seven callers can sit on hold at once. Some hang up, some redial, and some ring the next plumber on the list. Large call centers choose that trade on purpose, running with ample lines and accepting abandonment rather than busy signals[2]. A plumbing office on a freeze day has less room for it: the caller with water running down a wall will not hold for nine minutes.

Freeze surges are predictable in kind, if not in date. The Red Cross lists the pipes that freeze most often: those exposed to severe cold, such as hose bibs and sprinkler lines, those in unheated spaces like basements, crawl spaces, attics, garages and kitchen cabinets, and those against exterior walls with little insulation[5]. The calls arrive together because the cold arrives everywhere at once, and the stakes are high for the caller: the average homeowners claim for water damage and freezing was $15,400 over 2019 to 2023[1].

So size lines for the normal peak plus a margin, and plan the freeze in layers: who answers when every line and person is busy, and what the caller hears. The aim is that call number six reaches somebody or something that can take the job, instead of a tone.

Example: the sixth caller on a freeze morning
  • Caller
  • System
  • SI Employee
  • Your team
  1. 01Caller

    Caller dials main number

    Five calls are already connected: three answered, two on hold.

  2. 02System

    System reaches its limit

    The line pool or queue is full, or the hold timer runs out.

  3. 03System

    Call forwards on busy

    The carrier or phone system sends it to the overflow answerer, not a busy tone.

  4. 04SI Employee

    SI Employee takes the job

    Address, ZIP code, problem, urgency and callback number, read back to the caller.

  5. 05SI Employee

    Urgent calls go on-call

    Burst pipes transfer to the on-call path; routine work is booked or left as a request.

  6. 06Your team

    Office works the list

    Summaries arrive by email, urgent ones marked, for the team to follow up.

Example overflow path. Forward-on-busy and no-answer forwarding are set in your phone system or with your carrier.

Starting points by office size

Example starting points only. The peak concurrency in your own call records overrides this table.
OfficeNormal peak (calls at once)Lines to start withFreeze-day plan
Owner-operator, one van1 to 22, or a cloud number allowing 2 calls at onceBusy and no-answer forwarding to an answering option
2 to 5 trucks, one office person2 to 34Owner as first overflow, then outside answering
6 to 12 trucks, 2 to 3 CSRs4 to 66 to 8Dispatcher in the first layer; forward on busy at the line limit
13 or more trucks with a call desk7 or moreRun Erlang B on your own dataPriority queue for emergencies, overflow by written rule

Most plumbing offices sit in the first three rows: about 77% of plumbing, heating and air-conditioning establishments had fewer than 10 employees in 2023[6]. That is why one or two lines too few hurts so much. There is no second team down the hall to pick up.

Seasons move the baseline under you as well. Employment at plumbing, heating and air-conditioning contractors ran about 4% higher in August 2026 than in January[7], a hint of how demand shifts through the year, though a freeze peak is far sharper and shorter than any monthly average. Recheck your concurrency each season. However many lines you choose, every route should end with someone picking up; the overflow plan sets out the layers, and hunt groups vs call queues covers how the group rings before overflow begins.

Busy signals hide in your reports

Blocked calls are the hardest to see. A caller who heard busy never reached the queue, so many dashboards don't count them as missed or abandoned. Ask your carrier for an all-trunks-busy or blocked-calls count. If nobody can produce one, a crude check works: on your next busy morning, ring the main number from a mobile every 15 minutes and write down what you hear.

Calling those people back is a weak rescue. Only 19% of US adults say they generally answer calls from unknown numbers[8], so ringing a busy-signal caller from a number they don't recognize rarely connects. The call you can still win is the one you answer the first time.

Putting an SI Employee at the end of the line pool means the sixth caller gets a conversation, not a tone, and the office gets a written job instead of a lost one (what it does on a call). The eight-truck example shows how the urgent calls in that stream get sorted from the ones that can wait for morning.

Frequently asked questions

Is a phone line the same as a phone number?

No. A number is what callers dial; lines, channels or call paths decide how many calls can be connected at once. One number can sit on many paths, and several numbers can share one pool of paths.

How many calls at once can a cloud phone system take?

It depends on the provider and plan, so ask for the limit per number, per account and for forwarded calls in writing. Queues on hosted systems can hold many callers at once; Teams lets 50 wait by default[3]. People still have to answer them.

How much internet bandwidth does each VoIP call use?

Cisco puts a G.711 call at about 87.2 kbps on Ethernet and a G.729 call at about 31.2 kbps[4]. Multiply by your peak number of simultaneous calls and check the upload speed on your plan, not just the download speed.

Should we buy enough lines for our worst storm day?

Usually not. Extra lines without people to answer them just hold more callers on hold, and many hang up[2]. Size for the normal peak with a margin, then forward busy and unanswered calls to an overflow answerer for the surge.

What should callers hear when every line is busy?

Ideally a person or an answering system, not a busy tone. Set forward-on-busy and no-answer forwarding to your overflow layer, and test it by calling in while every line is in use.

References

  1. Insurance Information Institute (2025). Facts + Statistics: Homeowners and renters insurance (opens in a new tab) ↑

  2. Gans, Koole and Mandelbaum, Manufacturing & Service Operations Management (INFORMS) (2003). Telephone Call Centers: Tutorial, Review, and Research Prospects (opens in a new tab) ↑

  3. Microsoft Learn (2026). Setup: Call queue (Microsoft Teams) (opens in a new tab) ↑

  4. Cisco (2026). Voice Over IP - Per Call Bandwidth Consumption (opens in a new tab) ↑

  5. American Red Cross (2026). Frozen Pipes (opens in a new tab) ↑

  6. U.S. Census Bureau (2023). County Business Patterns 2023, U.S. national file (cbp23us) (opens in a new tab) ↑

  7. U.S. Bureau of Labor Statistics, Current Employment Statistics (2026). All employees, plumbing, heating, and air-conditioning contractors, not seasonally adjusted (CEU2023822001) (opens in a new tab) ↑

  8. Pew Research Center (2020). Most Americans don't answer cellphone calls from unknown numbers (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo