Phones and Call Handling

How Many Phone Lines Does a Restaurant Need?

Size restaurant phone lines from your busiest fifteen minutes, call length and who can answer, with a worked Friday example and the limit of extra lines.

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

On this page
  1. Lines, call paths and people are three different numbers
  2. Start from the busiest fifteen minutes
  3. How many call paths that load needs
  4. The point where extra lines only mean more ringing
  5. Worked example: fixing a Friday at 110 seats
  6. Checks to make while you change the setup
  7. Recheck the number every quarter
  8. Frequently asked questions
  9. References
Phones and Call Handling: How Many Phone Lines Does a Restaurant Need?~75%: of all US restaurant traffic now happens off-premises, almost 3 in 4 orders taken to goPHONES AND CALL HANDLINGHow Many Phone Lines Does aRestaurant Need?~75%of all US restaurant traffic now happens off-premises,almost 3 in 4 orders taken to goAva for RestaurantsInsightsPhones and Call Handling: How Many Phone Lines Does a Restaurant Need?~75%: of all US restaurant traffic now happens off-premises, almost 3 in 4 orders taken to goPHONES AND CALL HANDLINGHow Many Phone LinesDoes a RestaurantNeed?~75%of all US restaurant traffic nowhappens off-premises, almost 3 in 4orders taken to goAva for Restaurants
Figure source: National Restaurant Association, 2025[1]

Key takeaways

  • Size the phone for your busiest fifteen minutes, not the daily total: calls per quarter-hour × 4 × average minutes ÷ 60 gives the load in erlangs[2].
  • In the worked Example, a Friday load of 2.0 erlangs means two call paths leave about 4 in 10 callers facing a busy line, and five paths bring it under 4%[2].
  • Call paths beyond the number of people free to answer do not answer anything. They turn a busy signal into ringing.
  • Give every path beyond your people a destination: a backup handset, a voicemail that sends guests online, or overflow forwarding.
  • Any multi-line system must let staff dial 911 with no prefix and notify a central point on site[3].

Lines, call paths and people are three different numbers

Most restaurants inherit their answer to the lines question. Two copper lines came with the building, the VoIP plan says calls are unlimited, or the owner's mobile has been the restaurant number since opening week. None of those tells you whether the fourth caller at 6:10 on a Friday gets through, and that caller is the one the question is really about.

Three numbers matter, and they get mixed up. The published number is what guests dial; most places need one, sometimes a second for catering. Call paths are how many conversations the system can carry at the same moment: one per copper line, a set number of concurrent calls or channels on a VoIP or SIP plan, one call plus call waiting on a mobile. People are how many staff can actually pick up at that minute. On a busy night the third number is almost always the smallest, and it decides how many calls are answered.

Getting it right matters more than it did ten years ago. Nearly 75% of all US restaurant traffic now happens off-premises, in National Restaurant Association research[1], and 94% of consumers say speed is critical when they order that way[4]. A guest who hears a busy signal at dinner time has an ordering app one tap away.

Start from the busiest fifteen minutes

Daily call counts hide the problem. Calls bunch around the moments guests plan their evening, so a day with long quiet stretches can still have one quarter-hour where calls arrive on top of each other. Size the phone for that quarter-hour. The hour-by-hour call volume method gets you the raw data from your carrier or phone system; for sizing, narrow it to fifteen-minute blocks in your two or three busiest services.

  1. Pull four weeks of call logs

    Export start time, duration and whether each call was answered. Keep the missed and abandoned calls; they are demand too.

  2. Find the busiest quarter-hour

    For each service, count calls in every fifteen-minute block and take the typical high, not the single worst night of the year.

  3. Time calls by type

    Use the log's durations or a stopwatch on twenty calls. Pickup orders, reservation calls and quick questions take very different times, and your mix sets the average.

  4. Convert to load

    Multiply the quarter-hour count by four to get calls per hour, multiply by average minutes per call and divide by sixty. The result is the load in erlangs, the unit telephone engineers size circuits with[2].

  5. Count the people

    Write down who can realistically pick up in that quarter-hour and what else they are doing at the time.

Example: a fictional 110-seat restaurant with a pickup counter logs ten calls between 6:00 and 6:15 on a typical Friday. That is a rate of 40 calls an hour. Its calls in that window average three minutes, because the quarter-hour is heavy with pickup orders. Forty calls times three minutes, divided by sixty, is a load of 2.0 erlangs: on average two calls are in progress at every moment of that window. On a Tuesday the same quarter-hour brings about three calls of two and a half minutes, a load of 0.5 erlang.

Example call lengths at a full-service restaurant with pickup. Time your own; the mix moves the average more than any single call type.
Call typeTypical lengthWhat drives the length
Pickup order3 to 5 minutesMenu questions, modifiers, the read-back, payment questions
Reservation or change1.5 to 3 minutesChecking the book, party size, special requests
Hours, directions, parkingUnder 1 minuteNothing, if the answer is on the stand sheet
Catering or private event5 to 10 minutesDate, headcount, menu and budget; often better as a booked callback
Complaint4 minutes or moreListening first; usually needs a manager

How many call paths that load needs

Telephone engineers size trunks with the Erlang-B formula. Given the load and the number of channels, it estimates the chance that a new call finds every channel busy, assuming blocked callers give up instead of waiting[2]. Cellular networks are typically provisioned so that about 2% of calls in the busiest hour are blocked[2]. Restaurant callers behave much as the formula assumes: a busy signal at dinner time rarely earns a patient redial.

Example: calls that find every path busy, by number of call pathsErlang-B estimates for a Tuesday quarter-hour (0.5 erlang) and a Friday quarter-hour (2.0 erlangs). Modelled, not measured.
Example: calls that find every path busy, by number of call pathsColumn chart. 1 path: Tuesday, 0.5 erlang 33.3%, Friday, 2.0 erlangs 66.7%; 2 paths: Tuesday, 0.5 erlang 7.7%, Friday, 2.0 erlangs 40%; 3 paths: Tuesday, 0.5 erlang 1.3%, Friday, 2.0 erlangs 21.1%; 4 paths: Tuesday, 0.5 erlang 0.2%, Friday, 2.0 erlangs 9.5%; 5 paths: Tuesday, 0.5 erlang 0%, Friday, 2.0 erlangs 3.7%; 6 paths: Tuesday, 0.5 erlang 0%, Friday, 2.0 erlangs 1.2%.0%20%40%60%80%1 path · Tuesday, 0.5 erlang: 33.3%33.3%1 path · Friday, 2.0 erlangs: 66.7%66.7%1 path2 paths · Tuesday, 0.5 erlang: 7.7%7.7%2 paths · Friday, 2.0 erlangs: 40%40%2 paths3 paths · Tuesday, 0.5 erlang: 1.3%1.3%3 paths · Friday, 2.0 erlangs: 21.1%21.1%3 paths4 paths · Tuesday, 0.5 erlang: 0.2%0.2%4 paths · Friday, 2.0 erlangs: 9.5%9.5%4 paths5 paths · Tuesday, 0.5 erlang: 0%0%5 paths · Friday, 2.0 erlangs: 3.7%3.7%5 paths6 paths · Tuesday, 0.5 erlang: 0%0%6 paths · Friday, 2.0 erlangs: 1.2%1.2%6 pathsExample: calls that find every path busy, by number of call pathsColumn chart. 1 path: Tuesday, 0.5 erlang 33.3%, Friday, 2.0 erlangs 66.7%; 2 paths: Tuesday, 0.5 erlang 7.7%, Friday, 2.0 erlangs 40%; 3 paths: Tuesday, 0.5 erlang 1.3%, Friday, 2.0 erlangs 21.1%; 4 paths: Tuesday, 0.5 erlang 0.2%, Friday, 2.0 erlangs 9.5%; 5 paths: Tuesday, 0.5 erlang 0%, Friday, 2.0 erlangs 3.7%; 6 paths: Tuesday, 0.5 erlang 0%, Friday, 2.0 erlangs 1.2%.1 path1 path · Tuesday, 0.5 erlang: 33.3%33.3%1 path · Friday, 2.0 erlangs: 66.7%66.7%2 paths2 paths · Tuesday, 0.5 erlang: 7.7%7.7%2 paths · Friday, 2.0 erlangs: 40%40%3 paths3 paths · Tuesday, 0.5 erlang: 1.3%1.3%3 paths · Friday, 2.0 erlangs: 21.1%21.1%4 paths4 paths · Tuesday, 0.5 erlang: 0.2%0.2%4 paths · Friday, 2.0 erlangs: 9.5%9.5%5 paths0%5 paths · Friday, 2.0 erlangs: 3.7%3.7%6 paths0%6 paths · Friday, 2.0 erlangs: 1.2%1.2%
  • Tuesday, 0.5 erlang
  • Friday, 2.0 erlangs

Source: Ed Casas, lecture notes hosted by the University of British Columbia, 2013[2]

Show the data
Call pathsTuesday, 0.5 erlangFriday, 2.0 erlangs
1 path33.3%66.7%
2 paths7.7%40%
3 paths1.3%21.1%
4 paths0.2%9.5%
5 paths0%3.7%
6 paths0%1.2%

Read the chart left to right. At the Example Friday load of 2.0 erlangs, two paths leave about 40% of calls in that quarter-hour facing a busy line, three paths about 21%, four about 9.5% and five about 3.7%. The Tuesday load barely needs more than two: two paths block about 7.7% and three about 1.3%. These are Example figures from the formula, not measurements, and they rest on one quiet assumption: that somebody answers every path that rings.

Most restaurants land between three and five call paths once they do this sum. The assumption that every path has a person behind it is the one that breaks on a Friday.

The point where extra lines only mean more ringing

The formula counts paths, but each path needs a person. Hosts greet guests, seat them and manage reservations and waiting lists[5], and during the rush those jobs come first. If only two people can pick up at 6:10, the restaurant behaves like a two-path system however many lines the plan includes. Run the same arithmetic with people in place of paths and the Example Friday answer does not move: roughly four in ten calls in that quarter-hour reach nobody.

What changes is what the caller hears. With two paths, the third caller gets a busy signal straight away and can try again or order online. With six paths and two people, the third, fourth and fifth callers hear ringing. Ringing is worse: the guest waits half a minute, decides you are closed or ignoring them, and the host stand listens to phones it cannot reach while seating a four-top. Paths bought without people or a destination turn a clear busy signal into unanswered ringing.

A sensible ceiling is the number of people who can answer in the peak, plus one path so a call can sit on a short hold or be transferred. Every path beyond that needs somewhere to go when nobody picks up: a backup handset in the office, a voicemail greeting that sends guests to the ordering link, an answering service, or forwarding on busy or no answer to an SI Employee that answers in the restaurant's name and handles the routine calls.

Example: where Friday calls go with three paths and overflow
  • Caller
  • Your team
  • System
  • SI Employee
  1. 01Caller

    Guest dials the number

    One published number; the plan carries three calls at once.

  2. 02Your team

    Host takes the first call

    The host stand rings first and answers between seatings.

  3. 03Your team

    Pickup counter takes next

    The ring group moves the second call to the takeout counter handset.

  4. 04System

    No pickup after four rings

    Busy or unanswered calls follow the carrier's overflow forwarding.

  5. 05SI Employee

    SI Employee answers

    Hours, reservation requests for the host to confirm, ordering link by text.

  6. 06System

    Summary reaches manager

    Summary arrives by email; recording and transcript stay in the account.

Example setup. Forwarded reservation requests still need the host to confirm them, and complex calls still need a callback from staff.

Worked example: fixing a Friday at 110 seats

Example: the fictional restaurant runs two copper lines in a rollover, a host, a pickup-counter person and a general manager who floats. Its busiest Friday quarter-hour carries 2.0 erlangs. Guests mention the busy signal, so the owner's first instinct is a VoIP plan with six call paths. The table compares that with the alternatives, using the same Erlang-B arithmetic with people as the limit.

Example: calls in the busiest Friday quarter-hour that reach nobody, at a load of 2.0 erlangs. Modelled, not measured.
SetupPathsPeople freeCalls reaching nobodyWhat the caller hears
Today22About 4 in 10Busy signal
Six-path plan, same staff62About 4 in 10Ringing, then nothing
Three paths, manager on phones 5:45 to 7:0033About 2 in 10Mostly a person, sometimes busy
Three paths, two people, overflow forwarding32 plus overflowNone unanswered; complex calls returned laterA greeting in the restaurant's name
Three paths, three people, overflow forwarding33 plus overflowNone unanswered; fewer handoffsA person most of the time

In this example the owner keeps three paths, puts the floor manager on the phones from 5:45 to 7:00 on Fridays and Saturdays, and turns on forwarding for calls that find every path busy or ring four times unanswered. Pickup callers who reach the overflow get the ordering link by text when they agree to one, which also keeps the calls that do reach staff short. The pizzeria Friday rush example models the same idea at a shop where nearly every call is an order.

Notice where the money goes. The third path is usually the cheap part of a phone plan; the manager's hour and a quarter on the phones is the real cost, and it only pays off because the peak is short and predictable. Restaurant employees averaged about 25 hours a week in September 2026[6], so whoever covers the phones this Friday may not be the person who did it last Friday. Write the phone role into the shift plan, by role and by time, not into someone's memory.

Checks to make while you change the setup

  • Direct 911 dialing. FCC rules for multi-line telephone systems require that anyone can dial 911 without a prefix such as 9, that the system notify a central point on site where it can be configured to, and that fixed phones send a dispatchable location[3]. Ask your provider to confirm the setup and how to test it safely.
  • Relay calls. Guests who are deaf, hard of hearing or speech-disabled may call through a relay service, and staff must accept those calls and handle them like any other[7]. They run longer, so count them in your average call length rather than treating them as slow calls.
  • Internet failure. VoIP call paths go down with the internet connection. Decide in advance where calls forward when it fails; the POS offline and internet backup guide covers the router side.
  • Copper you forgot about. Older alarm panels, fax machines and some card terminals still use a phone line. Check what is plugged into each line before cancelling one in a migration.
  • Hold that means something. A short hold with a promised time beats ringing out. A hold queue during service with no end in sight does not.

Recheck the number every quarter

Paths, people and load all drift. A new online ordering link can cut pickup calls; a catering push lengthens them; a holiday menu changes the mix for six weeks. Every quarter, pull the busiest quarter-hours again, recalculate the load and compare answered, busy and rang-out calls. If rang-out calls rise while busy signals fall, you bought paths without people. If both fall, the plan works.

Measuring missed calls explains how to count the calls that never reach anyone. When one number is no longer enough, the guide to separate lines for takeout, catering and reservations covers when a second published number earns its place, and the phone systems comparison covers the hardware and plans. If overflow forwarding is part of your answer, check what an overflow answering setup covers today before you choose the forwarding rules.

Frequently asked questions

Are two phone lines enough for a small restaurant?

Often, if your busiest quarter-hour carries well under one erlang and two people can answer. In the Example Tuesday load of 0.5 erlang, two paths block about 8% of calls in that window and three about 1%[2]. Work out your own load before deciding.

Does an unlimited VoIP plan stop busy signals?

It stops the busy signal, not the missed call. When more calls arrive than people can answer, the extra callers hear ringing instead. Pair extra paths with a short hold message, a ring group that reaches a second person, or overflow forwarding.

Should callers wait in a hold queue instead of hearing busy?

A short queue with a message works when someone will be free within a minute or two. A long queue during service usually ends in hang-ups, so give the queue a time limit and a destination after it.

Do the FCC 911 rules apply to a restaurant phone system?

They cover multi-line telephone systems, the kind many restaurants use when several handsets share lines. They require direct 911 dialing without a prefix, on-site notification where the system supports it, and dispatchable location[3]. Ask your provider to confirm your setup.

How often should we resize the phone setup?

Quarterly, and after anything that moves call volume: a new online ordering link, longer hours, a catering push or a big holiday.

References

  1. National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑

  2. Ed Casas, lecture notes hosted by the University of British Columbia (2013). Trunking and Grade of Service (ELEX 7860 lecture 15) (opens in a new tab) ↑

  3. Legal Information Institute (Cornell Law School), eCFR text (2026). 47 CFR § 9.16 - Requirements for multi-line telephone systems (opens in a new tab) ↑

  4. National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑

  5. US Bureau of Labor Statistics (2025). Occupational Outlook Handbook: Food and Beverage Serving and Related Workers (opens in a new tab) ↑

  6. US Bureau of Labor Statistics (2026). Current Employment Statistics: series CES7072200002 (opens in a new tab) ↑

  7. US Department of Justice, Civil Rights Division (ADA.gov) (2026). ADA Requirements: Effective Communication (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