Covering the restaurant phone during the lunch and dinner rush

To cover the phone at a rush, count the calls in your busiest 15 minutes, then name who answers first, who answers second, and where a call goes when both are busy: a hold queue, an answering service or AI, or voicemail with a callback list. Set it up before service and test the overflow once.

This guide is about staffing and routing: who picks up, and what happens to the next caller. The order-taking method itself (hold rules, read-back, quote time and payment) has its own guide. For the words staff say, use our restaurant phone scripts.

When do restaurant calls peak?

In Maple's restaurant phone audit, call volume built from 10 a.m., peaked at 5 p.m. local time and faded after 9 p.m. Friday carried 20.1% of weekly calls and Monday 11.2%. Dinner-block calls ran longest. Those figures describe restaurants using Maple over a 90-day window, so use them as a prompt to count your own.

Your own call log is the number that counts. Export two weeks of calls from your phone provider, group them into 15-minute blocks, and mark the busiest block at lunch and at dinner on each day. Note the average call length too. Calls bunch inside an hour, so a 15-minute count shows the real squeeze better than an hourly total.

How many people does the phone need at peak?

Take the calls in your busiest 15 minutes and multiply by the average minutes per call. That is the phone work arriving in those 15 minutes. If it is 15 minutes or more, one person cannot keep up, however fast they are: callers arrive faster than one person can finish them.

The table uses the Erlang C formula, the standard call-center formula for the chance that a caller has to wait. We ran the sums with made-up inputs: each call takes 2.5 minutes, and the people counted do nothing but answer the phone.

Calls in busiest 15 minutes	Minutes of phone work	1 person	2 people	3 people	4 people
4	10	67% of callers wait; average wait 5 minutes	17% wait; average 19 seconds	3% wait; average 2 seconds	Under 1% wait
6	15	Falls behind	33% wait; average 50 seconds	9% wait; average 7 seconds	2% wait; average 1 second
10	25	Falls behind	76% wait; average 5.7 minutes	30% wait; average 34 seconds	10% wait; average 7 seconds
14	35	Falls behind	Falls behind	61% wait; average 2.3 minutes	27% wait; average 24 seconds

Read it with two limits in mind. The Erlang C formula assumes callers never hang up while they wait, which makes it ask for more staff than you really need. Your staff also run the counter or seat guests between calls, which pushes the other way. Treat the table as a guide to the size of the gap. If your busiest block needs three dedicated people and you can spare one, the other two people's worth of calls need an overflow route.

For how many phone lines you need so callers do not hear a busy signal, see our pizza shop phone guide. Lines and people are separate counts.

Who should answer first, second and third?

Write a coverage plan for each rush and post it at the host stand or counter. The example below is ours, for a counter-service restaurant with a lunch peak at 12:15 and a dinner peak at 6:00.

Period	First to answer	Backup	When both are busy	Who runs callbacks
11:30 to 12:00	Cashier	Manager	Hold queue with a short message	Cashier, before noon
12:00 to 1:15 (peak)	A named phone person, off the register	Cashier	Answering service or AI, or voicemail with a callback promise	Manager, at 1:15
5:30 to 7:00 (peak)	Host or a named phone person	Manager	Same as lunch peak	Manager, at 7:00
Other hours	Whoever is at the counter	Manager	Voicemail	Opening or closing manager

At the peak, take the phone person off the register. A cashier who also answers the phone makes a guest wait in one line or the other.

How should calls overflow when everyone is busy?

Your phone system decides what the next caller hears. There are three common setups.

Setup	What it does	What the provider documents	Start here if
Ring group	Rings several phones at once or in order until someone answers	Ooma's ring group guide lists simultaneous, sequential and hybrid ringing, and says a hunt group rings analog phones until it finds an open line	Two or three people share the phone and calls rarely stack up
Call queue	Holds callers in line with music or a message and hands each to the next free person	Ooma says a call queue holds up to 25 calls and can send an unanswered call to voicemail, another extension or a message. It is a Pro Plus feature, listed at $29.95 per user per month on Ooma's plans page	Callers stack up at the peak and you want them to wait in order
Queue with overflow	Sends waiting calls to a second group of people after a set time	RingCentral's overflow feature lets up to three overflow queues help, on its Premium, Ultimate, Advanced and Ultra plans	A second team, such as the kitchen office, can take calls at peak

Set a maximum wait. RingCentral's call queue overview gives 15 minutes as its longest queue wait, and Ooma lets an admin choose the wait before a call counts as unanswered. For a takeout order, offer a callback well before a caller has held for several minutes. Pick the time your team can keep, and route timed-out calls to an answering service, AI or voicemail.

Our restaurant phone system guide covers ring patterns, handsets and outage forwarding. If you forward overflow to an outside service, run the call forwarding checklist first.

What should happen when nobody can pick up?

Pick one path for a call nobody answers, and make it end with a person calling back or with the order taken. Three options, from simplest:

1. Voicemail with a callback time. A peak-hour greeting says you are busy, gives your online ordering link, and says when you will call back. Our voicemail greeting guide has example wording.
2. An answering service. People off site take a message or an order. Ask what they send you and how fast.
3. AI that answers or takes the order. It answers the overflow call, takes an order into the POS where supported, and transfers to staff when asked.

How do you run callbacks during a rush?

1. Give one person the job and a time to do it, as in the coverage plan above.
2. Work from the missed-call list in your phone app or portal, oldest first. Include voicemails.
3. Skip numbers that have already called back and ordered. Check the POS by phone number or name.
4. Open with the reason: "This is Rosa's on Main returning your call from 12:20. Can I take your order now?"
5. Mark each number called, reached or left a message, and ordered or not.
6. At the end of the week, count missed calls at each peak and how many became orders on callback. That tells you whether the plan needs another person or more overflow.

How do you test the plan before a busy night?

On a quiet afternoon, have three people call the main number at once from their own phones. Check who answers each call, what the third caller hears, how long the queue holds them, and where the call ends when nobody picks up. Then check the missed-call list shows all three. Fix one setting at a time and call again.

If the overflow goes to Maple, Voice answers questions and transfers calls for $150 a month billed monthly or $85 a month billed annually. Pro, at $350 a month billed monthly or $220 a month billed annually, takes phone orders into supported POS systems. Run the same three-phone test with the product page checklist before you route your live number.

Published by Maple. This AI-assisted guide combines Maple's published phone audit, Ooma and RingCentral help pages, and our own Erlang C calculation with made-up inputs. The coverage plan is an example we wrote. It does not report a test at any restaurant or promise a result.