Example: a 90-seat restaurant's phones during the dinner rush

The situation in this example

Corner Hearth Kitchen is a fictional 90-seat neighborhood restaurant used to show how the calls and the numbers would work. The owner is also the chef, a general manager runs the floor, a part-time catering lead handles off-site events, and about 30 hourly staff cover lunch and dinner six days a week. Nothing about that shape is unusual: 7 in 10 US restaurants are single-unit operations, and 9 in 10 have fewer than 50 employees^[1].

The phone sits at the host stand, and the host's job already covers seating guests, reservations and the waiting list^[2]. In this example it rings about 55 times a day, and roughly half of those calls arrive between 5 pm and 8 pm, exactly when the host is seating tables, quoting waits and handing out takeout bags. The general manager is running food or settling a check, and the catering lead has gone home for the day. So the phone either rings out, or the host answers with “Can you hold?” and the couple standing at the stand waits too.

Two things make those calls worth answering. Takeout matters even at a sit-down place: across the industry nearly 75% of restaurant traffic now happens off-premises, 41% of full-service operators say off-premises brings in a larger share of their sales than it did in 2019, and 94% of consumers say speed is critical^[3]. And the phone is still how a large share of guests book. When Cornell researchers got figures from 55 of the country's top 100 independent restaurants in 2012, 49% of reservations came in by telephone, about twice the share from the leading online booking site, and diners who had never booked online most often said they preferred to talk to someone^[4]. Frequent diners in a 2008 Cornell survey also said they often found it hard to reach a restaurant when they needed to change a booking^[5].

How the calls would be handled

In the modelled setup an SI Employee takes calls in two modes. During lunch and dinner service it answers on overflow: the host stand phone rings three times, and if nobody picks up, it answers. Before opening and after close it answers every call. Before it goes live, the general manager approves the house information: hours, holiday closures, address and parking, kitchen close, the reservation policy, private-room basics and the restaurant's official ordering link.

• Hours and directions: answered from the approved house information, including holiday hours and the time the kitchen stops taking orders.
• Reservations: party size, date, time, name, occasion and a callback number, logged as a request. The host confirms by text or call; no table is promised on the phone.
• Takeout: no orders or payments by voice. When the caller agrees, a text with the official ordering link. Order-status calls go to the takeout counter, because in this example the setup has no view of the kitchen's tickets.
• Catering and parties above the reservation limit: the catering lead's intake questions, then an email summary to the catering lead. No menu or price is quoted.
• Allergy and dietary-safety questions, and complaints: straight to the manager, with a named backup if the manager doesn't pick up, or a callback request.

The allergy rule is deliberately blunt. Sesame is now the ninth major food allergen, and when the federal allergen labeling law passed, the original eight accounted for 90% of US food allergies and serious reactions^[6]. Whether the fryer oil is shared or tonight's pesto has pine nuts in it is a kitchen question that changes with the menu, so no phone script should answer it. In this example the caller hears that a manager will call back before they order, and the manager gets the question in writing.

What the numbers would look like

The worked example below models the phone time the host stand would hand back each month. The hourly cost is the national median wage for restaurant hosts^[2]. Wages are the small part of the cost here; the bigger part is who gets pulled away from guests. The call volume, the minutes per call and the share of calls the setup would finish without a person are invented for this example.

In this example that comes to about 27 hours and $410 a month. It is the smallest number in the scenario. The larger one is what those minutes interrupt: a host on the phone isn't seating the couple at the stand, and a manager pulled to the phone isn't checking on the table that has waited 20 minutes for entrées.

Catering is where the money would sit. Example: one catering or large-party inquiry a day, six days a week, is about 26 a month. If the average order were $1,500, roughly $25 a head for lunch for 60, and taking the details on the first call with a next-morning callback turned two more of those inquiries a month into booked events, that would add $3,000 a month in sales before food and labor. Those figures are invented for this example; the catering lead's own record of inquiries won is the number to plug in.

The first 30 days in this example

The texting step needs groundwork: the restaurant's sending number is registered for business texting before any ordering link goes out. Approval is not instant, so in this example it is filed on day 1, and if it has not cleared by go-live, takeout callers get the web address from the house information until it does. After that most callers can open the link on the phone they are calling from: 91% of US adults own a smartphone^[7].

Each week in this example the general manager would read ten transcripts from Friday and Saturday service and check three things: that every reservation request got a confirmation or a polite no from the host, that every allergy callback happened before the guest ordered, and that every catering inquiry got its callback the next morning. Anything that went wrong becomes a new line in the house information or a new handoff rule, rather than a rewrite of the greeting.

Lessons from the scenario

• Answer on overflow during service, not instead of the host; guests at the stand still come first.
• Treat every phone reservation as a request until the host confirms it.
• Keep allergy and dietary-safety questions with people, every time.
• Capture catering details on the first call so the callback can come with a quote.

The scenario also shows what would not change. The reservation book stays the single source of truth, and the setup in this example has no view of live table availability. Menus, prices and event quotes stay with the team. For restaurant-specific setups covering reservation requests, catering intake and ordering links, see the restaurant version on avaforrestaurants.com.