Key takeaways
- A telephone SOP writes the decisions down once: who answers by which ring, what gets logged, what goes to a manager and how anyone checks.
- Restaurant teams turn over fast[1], so the procedure, not the longest-serving host, has to hold the standard.
- Name a primary and a backup for every shift and a fixed overflow when both miss; the phone never just rings out.
- Allergy questions, complaints, large parties, press and anything involving money go to a manager by rule, not by judgment.
- A manager checks the SOP weekly with test calls, the call log and a ring report, and revises it every quarter.
Why the phone needs a written procedure
Ask three hosts how the phone works at your restaurant and you will often get three answers. One picks up on the first ring and puts everyone on hold. One lets it ring while finishing with the party at the stand. One assumes the bar has it. None of them is wrong by the rules they were given, because nobody wrote the rules down. A telephone standard operating procedure fixes that by making the decisions once: who answers, by which ring, what gets written down, what goes to a manager, and how anyone knows it happened.
The case for writing it down is turnover. Workers in food services and drinking places had a median of 2.2 years with their current employer in January 2026, against 3.9 years across the private sector[1], and the monthly quits rate in accommodation and food services was 5.0% in September 2026[2]. The host who knows that catering calls go to Maria on Tuesdays will not be there next spring. The procedure will.
Source: US Bureau of Labor Statistics, 2026[1]
Show the data
| Industry | Median years |
|---|---|
| Food services and drinking places | 2.2 years |
| All private sector | 3.9 years |
The phone also competes with the job hosts were hired for. Hosts greet guests, seat them and manage reservations and waiting lists[3], and the phone sits on top of all three. An SOP doesn't add work. It removes the decisions that make a ringing phone stressful, so a host in their first week can handle a call the way the general manager would.
The one-page SOP, section by section
Keep it to one page so it can be posted at the stand and read aloud in a pre-shift. The wording below is an example to adapt; replace the brackets with your names, numbers and times.
- Purpose. Every call to [restaurant] is answered in the restaurant's name, handled to the end or handed to a named owner, and recorded in the call log if anything was promised.
- Scope. The main line, the catering line and any handset in the building, during open hours, prep hours and closed hours.
- Roles. The daily sheet names a primary phone person and a backup for each shift. The manager on duty owns escalations. The owner owns press and anything legal.
- Ring rules. Primary answers by ring 3. Backup answers by ring 5. After ring 6 the call goes to overflow. Nobody lets a call ring out because they assume someone else has it.
- Call handling. Greeting script, read back every booking and order, ask before any hold and come back within 30 seconds, close with the next step and the caller's name.
- Logging. Any call not finished on the spot goes in the call log with time, name, number, call type, what was promised, the owner and a deadline.
- Escalation. Allergy, complaint, injury, large party, press, money and anything off-script go to the manager on duty, then the backup manager, then the owner.
- Checks. The manager reviews the log at close, makes two test calls a week and pulls a ring report every Monday. The SOP is revised every quarter and signed by every front-of-house hire.
The call-handling line is deliberately short, because the detail lives elsewhere: tone and manners in phone etiquette rules, the words themselves in the host phone script. The SOP only says which standard applies and who is accountable for it.
Ring rules and coverage by shift
Write ring limits as rings, because that is what staff hear, and check them in seconds, because that is what the phone system logs. Ring timing varies by carrier and system, so time three rings on your own line and write the seconds next to the count. The right target varies by daypart, and how fast a restaurant should answer the phone covers setting one. What the SOP adds is the backup: a named person, not a role description, and an overflow that takes the call when both of them miss.
| Shift | Primary | Backup | Overflow after ring 6 |
|---|---|---|---|
| Prep, 10:00 to 11:30 | Opening manager | Prep lead | Greeting with hours, then voicemail |
| Lunch, 11:30 to 2:30 | Host | Bartender | Overflow line or answering cover |
| Afternoon, 2:30 to 5:00 | Host on side work | Manager on duty | Voicemail, cleared at 4:30 |
| Dinner, 5:00 to 9:30 | Second host, phone only from 6:30 | Lead host | Overflow line or answering cover |
| Close, 9:30 to 11:00 | Closing host | Closing manager | Greeting with hours, then voicemail |
| Closed hours | None | None | After-hours greeting and overflow; swept at opening |
- Caller
- Your team
- System
01Caller
Main line rings
Rings at the host stand and the bar handset at the same time.
02Your team
Host answers by ring 3
The primary phone person named on the daily sheet.
03Your team
Backup picks up by ring 5
Bartender or lead host; nobody assumes someone else has it.
04System
Overflow takes the call
After ring 6: voicemail, an answering service or an SI Employee.
05Your team
Unfinished calls logged
Anything promised gets an owner and a deadline.
06Your team
Manager clears the log
Checked before dinner and at close; nothing carries over unowned.
Example. Ring counts are illustrative; set yours by daypart and check them against the phone system's logs.
Short-staffed nights bend the table, not the rule. When the second host calls out, the backup column moves up and somebody else is named, as laid out in the phone coverage plan for short-staffed shifts. The ring limits stay where they are.
What every call must include
- The restaurant's name and the person's first name in the greeting, so the caller knows they reached the right place and who they spoke to.
- A read-back of every reservation and order: name, date, time, party size or items, callback number.
- Permission before a hold, and a return within 30 seconds or an offer to call back.
- A clear next step at the end: “You're booked”, “Our manager will call you by four”, or “Here's where to find that”.
- The recording notice in the greeting if calls are recorded. Federal law allows recording with one party's consent[4], but some states are stricter; check yours in call recording laws by state.
- Relay calls treated like any other call. Businesses covered by the ADA must accept calls through relay services[5], and a relay operator's introduction is not a sales call.
Two things are never done on the phone, by anyone, whatever the caller says: reading a code sent to the restaurant's phone or email, and paying or refunding money because of an incoming call. The patterns behind that rule are in phone scams that target restaurants.
What gets logged, and where
The call log is the SOP's memory. It doesn't need to capture every call, only every call that left something unfinished or that a manager needs to know about. Keep it in one place: a tab in the manager log, a shared tablet note or a printed sheet at the stand that goes into the log at close. Three places means nobody checks any of them.
- Columns: time, caller name, number, call type, what was promised, owner, deadline, done.
- Always logged: callbacks promised, complaints, allergy questions, large parties and events, press, anything involving money, suspicious calls.
- Never logged in the open: card numbers, security codes, or health details beyond what a manager needs to call back.
- Closed out: the owner writes the outcome and initials it, so the closing manager can see at a glance what is still open.
The log feeds the shift record. What belongs in the manager's end-of-shift notes, and how the phone entries fit with the rest, is covered in the manager log book.
Escalation rules
Escalation is where judgment goes wrong under pressure, so the SOP replaces judgment with a list. If a call matches a line, it goes to the person on that line. No host is ever wrong for escalating; a host is wrong for guessing.
- Allergy or dietary safety question: manager on duty, live. When FALCPA passed, eight major allergens accounted for 90% of food allergies and serious reactions in the US[6], and a kitchen's answer can change with the menu. Detail in allergy questions over the phone.
- Complaint: manager on duty within ten minutes, or a callback promised for a time the manager confirms.
- Injury, illness or a guest reporting a reaction: manager on duty, live, and an incident note the same shift.
- Large party or private event: manager or events lead, the same day.
- Press, lawyers, government agencies: the owner, with the caller's name, organization and deadline.
- An emergency in the building: anyone calls 911 directly from any phone. FCC rules require multi-line systems to allow direct 911 dialing without a prefix[7].
- Manager unreachable: backup manager, then the owner. The chain and the numbers are printed on the SOP.
The same list applies to whatever answers your overflow. If you forward the line to an SI Employee when it is busy, not answered or closed, the SOP gets one more row: it answers from the information you approve, takes reservation requests for the host to confirm, sends catering leads to the catering manager, texts your ordering link when a caller wants it and agrees, and hands complaints, allergy questions and anything off-script to the manager path you choose, with a backup. Each call lands in the AssistCall inbox with a summary and transcript, and the person you choose is emailed, so overflow calls enter the same log review as the rest. When an AI phone agent should hand off to staff covers how to draw those lines, and a restaurant phone orders and catering example shows the setup end to end.
How a manager checks the SOP is followed
A procedure nobody checks drifts back to habit within a month. The checks below take about fifteen minutes a week once they are routine, and they rely on what the phone system already records rather than on watching hosts.
Every close: clear the log
The closing manager reads every open line, confirms an owner and a deadline for each, and initials the sheet. Anything without an owner gets one before the manager leaves.
Twice a week: test calls
Call your own line from a mobile at a busy time and a quiet time. Note the ring count, the greeting, the read-back and the close. A structured version is in mystery calling your own restaurant.
Every Monday: the ring report
Pull last week's calls by hour from the phone system: answered, rang out, sent to overflow. One bad hour repeated across several days is a coverage problem, not a host problem.
Monthly: listen to five calls per host
If calls are recorded, score five per host against the call-handling line of the SOP and share one thing done well and one to fix.
Quarterly: revise and re-sign
Update names, numbers, hours and escalation contacts, re-read it at pre-shift and have every front-of-house employee sign the new version.
The fine-dining example shows these rules in a room where the maître d' should stay at the door: the reservationist owns the line in the afternoon, overflow takes the call after four rings and during closed days, and every request still ends with a person confirming it.
Frequently asked questions
What should a restaurant telephone SOP include?
Purpose, scope, named roles for each shift, ring limits with a backup and an overflow, the call-handling standard, what gets logged, escalation rules and how a manager checks it. Keep it to one page so it can be posted and read aloud.
How many rings before someone else should pick up?
A common pattern is primary by ring 3, backup by ring 5 and overflow after ring 6, adjusted by daypart. The point is that the backup is a named person and the phone never simply rings out.
Which calls should always go to a manager?
Allergy and dietary safety questions, complaints, injuries or reported reactions, large parties and events, press, legal or government callers, and anything involving money. Allergy calls matter most because a small set of major allergens accounts for most serious reactions[6].
How do we keep the SOP from being ignored?
Check it with data the phone system already has: a weekly ring report, two test calls a week and a nightly log review. Turnover is high in restaurants[2], so re-read and re-sign it every quarter and on every new hire's first shift.
Do we need to mention call recording in the SOP?
Yes, if you record. Federal law allows recording with one party's consent[4], and some states set a stricter rule, so the SOP should put the recording notice in the greeting for every recorded line.
References
US Bureau of Labor Statistics (2026). Employee Tenure, Table 5: Median years of tenure with current employer by industry (opens in a new tab) ↑
US Bureau of Labor Statistics (2026). Job Openings and Labor Turnover Survey: quits rate, accommodation and food services (opens in a new tab) ↑
US Bureau of Labor Statistics (2025). Occupational Outlook Handbook: Food and Beverage Serving and Related Workers (opens in a new tab) ↑
Legal Information Institute (Cornell Law School), US Code (2026). 18 U.S. Code 2511: Interception and disclosure of wire, oral, or electronic communications (opens in a new tab) ↑
US Department of Justice, Civil Rights Division (ADA.gov) (2026). ADA Requirements: Effective Communication (opens in a new tab) ↑
US Food and Drug Administration (2004). Food Allergies: What You Need to Know (opens in a new tab) ↑
Legal Information Institute (Cornell Law School), eCFR text (2026). 47 CFR 9.16 General obligations of multi-line telephone systems (opens in a new tab) ↑