Key takeaways
- When a host calls out, the phone is usually the first job dropped; decide in advance who picks it up.
- Every shift needs a named phone owner, a named backup and a written overflow rule.
- A callback queue with promised times turns missed calls into bookings later the same night.
- Plan coverage before seasonal peaks, when restaurant employment and call volume rise together.
Why the phone is the first job to go
On a fully staffed night the host stand absorbs the phone without much thought. Take one host away and the same person is greeting, quoting waits, seating, bussing menus and answering calls at once. Something gives, and it is usually the phone, because the guest standing in front of you feels more urgent than the one ringing.
Short-staffed nights are not rare events in this industry. The monthly quits rate in accommodation and food services was 5.0% in September 2026, more than double the 2.3% rate across all private industry[1][2]. Recruiting and retaining employees was still a leading challenge for 77% of operators in 2025[3]. A phone plan that only works when everyone shows up is not a plan.
The one-page coverage plan
Write the plan on a single page and post it at the host stand and in the manager log. It answers one question for every shift: who answers the phone when the normal person cannot? The roster below is an example for a fictional 110-seat restaurant; your roles and times will differ.
| Daypart | Phone owner | Backup | If both are tied up |
|---|---|---|---|
| Lunch 11:00–2:30 | Lead server on the floor | Manager on duty | Ring to voicemail with a callback promise; check every 15 minutes |
| Pre-shift 3:00–5:00 | Manager | Bartender during setup | Return calls in a batch at 4:30 |
| Dinner 5:00–7:00 | Second host | Lead host | Overflow to the bar phone or a backup line |
| Dinner peak 7:00–8:30 | Lead host for bookings only | Manager for complaints and allergies | Callback queue; missed-call text with booking link |
| Late 8:30–close | Lead host | Closing manager | Voicemail with next-day callback time |
Two details make this work. First, the backup is a person, not a role description; write the name on the daily sheet. Second, the overflow rule is specific. “Someone will grab it” is not a rule. “Calls ring three times at the stand, then roll to the bar phone, then to voicemail with a callback promise” is.
Build your plan in six steps
Map when calls arrive
Pull two weeks of call logs and count calls by half hour. Most restaurants find two or three clear spikes, usually late afternoon and the start of dinner.
Match owners to spikes
Put your most reliable phone person on the busiest window, even if it means another task moves to someone else for that hour.
Choose the backup path
Decide where unanswered calls go: a second handset, the bar phone, a manager mobile, an answering service or an AI phone agent. Write the order down.
Set the short-staffed trigger
Agree what changes when you are down one person: for example, the phone owner only takes reservations and the manager takes everything else.
Script the hold and the callback
Give every person who might answer the same short scripts, so guests hear the same promise whoever picks up.
Review after every short shift
Five minutes at close: how many calls were missed, how many callbacks were done, what to change next time.
Choosing the backup layer
The backup path is the part of the plan most owners skip, and it is the part that saves the night. There are five common choices, and most restaurants use two of them together. Judge each one by three questions: will it answer when every person is busy, can it take a reservation request with the details you need, and will the details reach the host without being retyped from memory.
- A second handset at the bar or expo: cheap and immediate, but it only moves the problem to another busy person.
- A manager's mobile: good for complaints and large parties, poor for routine bookings during service, when managers are on the floor.
- Voicemail with a callback promise: always available, but every message becomes work for later, and some guests will not leave one.
- An answering service: covers volume, but scripts must be precise and details often arrive by email that nobody reads mid-shift.
- An AI phone agent: answers every call at once and can collect reservation requests and questions, but needs careful setup, testing and a clear handoff to staff.
Whatever you choose, write down the order in which calls move through the layers and test it monthly by calling your own number during service. A backup path that has never been tested is a guess.
Run a callback queue that guests trust
A callback queue is a list of people you owe a call, with a promised time next to each name. It can live in your reservation system, a shared spreadsheet or a clipboard, as long as everyone on shift can see it. The promise is what matters: a guest told “we will call you back by 8:45” will usually wait; a guest told “we'll call you back” often books elsewhere.
- Capture: name, number, party size, preferred time and what they need.
- Promise: a specific time, never “soon”.
- Prioritize: same-night bookings first, then large parties and events, then general questions.
- Work the queue in lulls: after the first seating, during the 8:30 dip, and at close.
- Close each entry with what happened: booked, waitlisted, declined, or no answer with a message left.
Complaints and allergy questions never wait in the general queue. They go to the manager immediately, by name, with the guest's number.
Scripts for a short night
- Quick hold: “Thanks for calling Copper Table, can you hold for one minute while I seat a guest?” Wait for the answer before pressing hold.
- Callback offer: “We're slammed right now. Can I take your number and call you back by 8:45 with a time for four?”
- Voicemail greeting: “You've reached Copper Table. We're with guests right now. Leave your name, number and party size and we'll call you back within the hour, or book anytime at our website.”
- Backup pickup: “Copper Table, this is Jordan at the bar. Our host is seating guests; I can take your reservation request now.”
Keep scripts short enough to say while walking. If a bartender is the backup, give them a laminated card with the three questions every reservation needs: date and time, party size, and a name with a number.
Plan for the seasonal squeeze
Restaurant staffing follows the calendar. Not seasonally adjusted, food services and drinking places employment rose from 11.88 million in January 2025 to 12.52 million in June 2025[4]. Those extra workers arrive because demand does, and so do extra calls about patio seating, graduations, tourists and private events.
Source: US Bureau of Labor Statistics, 2025[4]
Show the data
| Item | Value |
|---|---|
| January 2025 | 11.88 million jobs |
| June 2025 | 12.52 million jobs |
Part-time work is common for servers, and schedules span early mornings, late evenings, weekends and holidays[5]. That flexibility helps you staff peaks but makes the phone plan more fragile, because the backup on Tuesday is not the backup on Saturday. Refresh the roster when the summer schedule goes live, and train every seasonal hire on the phone scripts during their first week, not after the first bad night.
Example: Saturday with one host out
Example: at a fictional 110-seat restaurant, the second host calls out at 3 p.m. on a Saturday with 180 covers booked. The manager opens the plan and switches to the short-staffed rule: the lead host handles the stand and same-night bookings only; the bartender takes overflow calls between 5 and 7; the manager owns complaints, allergies and large-party requests.
Example: missed calls roll to voicemail with a one-hour callback promise, and a missed-call text sends the booking link. At 8:40, during the dip, the lead host works through the callback queue of nine entries and books four tables. At close the manager notes that most missed calls came between 6:45 and 7:30 and moves a server's side work so they can cover the phone in that window next time.
Close-of-shift review
- How many calls rang out or went to voicemail?
- Were all callbacks made by the promised time?
- Did any complaint or allergy call wait in the general queue?
- Which window was worst, and who could cover it next time?
- Does the plan need a new backup name for next week?
If you see the same gaps every week, it may be time to add a backup layer that does not depend on who shows up. Compare options in AI phone answering for restaurants and route unanswered calls to an automatic missed call text back as a minimum.
Frequently asked questions
Who should answer the phone when a restaurant is short-staffed?
Name one phone owner and one backup per shift in advance, and narrow the owner's job: for example, reservations only, with complaints and allergy questions going to the manager.
Should we stop answering the phone during the rush?
Letting every call ring out loses bookings. If you must pause, roll calls to voicemail with a specific callback promise and send a missed-call text with your booking link.
How do we make callbacks actually happen?
Keep one visible queue with a promised time for each entry, work it in planned lulls, and review completion at close.
Can a bartender or server cover the phone?
Yes, if they have the same short scripts as hosts and a card listing the details every reservation request needs.
References
US Bureau of Labor Statistics (2026). Job Openings and Labor Turnover Survey: series JTS720000000000000QUR (opens in a new tab) ↑
US Bureau of Labor Statistics (2026). Job Openings and Labor Turnover Survey: series JTS100000000000000QUR (opens in a new tab) ↑
National Restaurant Association (2025). The 2025 State of the Industry shows cautious optimism (opens in a new tab) ↑
US Bureau of Labor Statistics (2025). Current Employment Statistics: series CEU7072200001 (opens in a new tab) ↑
US Bureau of Labor Statistics (2025). Occupational Outlook Handbook: Waiters and Waitresses (opens in a new tab) ↑