Scenario profile
- Business
- Example: The Marrowgate Dining Room (70 seats)
- Industry
- Independent fine-dining restaurant
- Size
- 70 seats plus an 18-seat private dining room; chef-owner, general manager, maître d', part-time reservationist, part-time events manager, about 35 staff in all
- Setting
- City neighborhood; dinner Tuesday to Saturday with a tasting menu and a short à la carte list; closed Sunday and Monday
- Call volume
- About 230 calls a week: roughly 40 on each service day and 15 on each closed day
Key takeaways
- In this example most tables book online, but the phone carries the hard calls: changes, large parties, allergies and private dinners.
- The modelled setup sorts every call that needs a person into one of six request types, each with its own questions and its own owner on the team.
- Nothing is promised on the call: tables stay requests until the reservationist confirms them, and allergy questions go to the sous chef.
- Every figure here is modelled from the sources listed, not measured at a real restaurant.
The restaurant in this example
The Marrowgate Dining Room is fictional. It seats 70, with an 18-seat private room behind the bar, and serves a tasting menu and a short à la carte list, Tuesday to Saturday. The chef-owner runs the kitchen; a general manager, a maître d' and a part-time reservationist run the front, and an events manager looks after the private room two days a week.
In this example most tables book online. The phone still carries the calls that matter most: changes to existing bookings, parties too big for the online system, anniversaries and proposals, allergies and private dinners. Callers tend to want a person. In a 2012 Cornell study, about two in three surveyed diners who had never booked online said they preferred to talk to someone, and at the top independent US restaurants the researchers checked, 49% of reservations still came by telephone[1].
In this example the line takes about 230 calls a week, roughly 40 on each service day and 15 on each closed day. The reservationist answers from 11 am to 4:30 pm, Tuesday to Saturday. Before and after that, the phone rings at the host stand. On Sunday and Monday it goes to voicemail.
Where the calls went wrong
Hosts greet guests, seat them, and manage reservations and waiting lists[2]. At the podium of a full room on a Friday, those jobs collide. In this example the maître d' picks up between seatings, and a four-minute call about a table three weeks out leaves a couple standing at the door in their coats. When she lets it ring instead, the guest running late for a 7:45 table never gets through. A 2009 Cornell report described the same trap: when the person taking reservations also greets and seats, callers may be put on hold, the agent rushed and the records unreliable[3].
Closed days are worse. Sunday and Monday bring about 30 calls, and on Tuesday the reservationist spends most of her first two hours returning the ones that left a message. Some of those guests have already booked elsewhere; others don't pick up, and the phone tag runs into Wednesday. Guests don't keep the restaurant's hours: an industry estimate cited by Cornell in 2009 put a quarter of online reservations between 10 pm and 10 am[3].
Changes and cancellations leak too. In a Cornell survey of 1,230 frequent diners, respondents often found it hard to reach a restaurant when they needed to change a reservation[4]. Here, a four-top that grows to six usually just arrives as six, on the one Saturday when there is no six-top left.
Two problems cost more than the rest. Private dining inquiries go to voicemail or to whoever answers, and the events manager sees them two or three days later, by which time a rehearsal dinner may be placed somewhere else. And dietary notes travel badly. A caller says her husband has a severe shellfish allergy; it goes on the phone pad, never reaches the booking notes, and the kitchen first hears about it at the table. Crustacean shellfish is one of the nine major food allergens identified by US law[5], and on a tasting menu it can hide in the stock, the sauce and the garnish.
How the SI Employee is set up
In the modelled setup the restaurant forwards its existing number to an SI Employee in three situations: when the reservationist has not picked up after four rings, from 4:30 pm until she starts at 11 the next morning, and all day Sunday and Monday. The general manager writes and approves everything it says before a guest hears it: hours, address, parking and valet, dress code, how long the tasting menu runs, the card guarantee for larger parties, the cancellation window, and the 15-minute hold on late tables, a length the frequent diners in Cornell's survey rated fair and acceptable[4].
Questions about hours or parking are answered from that approved information. Any call that needs a person ends as one of six request types, each with its own questions and its own owner:
- New reservation, up to six guests: date, time and how flexible it is, party size, name, mobile, occasion and dietary notes. Goes to the reservationist.
- Change or cancellation: the name on the booking, the date and what is changing. Same-day changes also go straight to the host stand.
- Waitlist: party size, the latest time that works and a mobile number, sent to the host stand for tonight's list or to the reservationist for a later date.
- Large party of seven to twelve: the same questions plus seating preferences, for the general manager.
- Private dining for thirteen or more: date and a backup date, guest count, occasion, menu format, wine, speeches or AV, and dietary needs. Goes to the events manager, with the general manager as backup.
- Allergy or dietary-safety question: written down in the guest's own words and passed to the sous chef as a callback request.
The limits are written down as carefully as the questions. Every booking is labeled a request until a person confirms it, so no guest is ever told a table is held. It never says a dish is safe for an allergy. It never takes a card number on the call; the reservation system sends its own card-guarantee link when the reservationist confirms. A same-night caller who wants a person is transferred to the host stand, with the general manager's mobile as the backup.
- Caller
- SI Employee
- System
- Your team
01Caller
Call on a closed Monday
Saturday at 7:30 for four, an anniversary, and one guest is allergic to shellfish.
02SI Employee
Collects the request
Date, time window, party size, name, mobile, occasion; reads the card-guarantee policy.
03SI Employee
Records the allergy
Writes it in the guest's words, makes no promise about the menu, asks for a callback time.
04System
Request lands in the inbox
Summary and transcript in the inbox; the reservationist and the sous chef are notified.
05Your team
Tuesday: table confirmed
Reservationist books 7:15 and the reservation system sends its confirmation and card link.
06Your team
Sous chef calls back
Confirms the tasting menu can be cooked without shellfish; the note goes on the booking.
Example: fictional restaurant and policy. A real setup follows the questions and owners the manager approves.
Each call lands in the AssistCall inbox with a summary and a transcript, and the person who owns that request type is notified. In this example the reservationist copies confirmed bookings and their notes into the reservation system by hand, and those guest notes are what the kitchen reads at the pre-service lineup. The SI Employee does not write into the reservation system.
Before and after, call by call
| Call | Before (host stand and voicemail) | After (modelled setup) |
|---|---|---|
| Saturday table requested on a closed Monday | Voicemail, returned Tuesday afternoon, often after the guest has booked elsewhere | Request taken in full on the call; reservationist confirms it Tuesday morning |
| Thursday four-top grows to six | Guest tries twice, gives up, and six arrive | Change logged as a request; reservationist checks the floor plan and calls back |
| Call at 6:40 pm asking for a table at 8 tonight | Maître d' leaves the door to check the book | Waitlist request with party size, latest time and mobile sent to the host stand |
| Rehearsal dinner for 16 | Message for the events manager, seen two days later | Inquiry with date, backup date, headcount and dietary needs sent to the events manager that evening |
| Guest mentions a severe nut allergy | Written on the phone pad, missing from the booking notes | Recorded word for word and passed to the sous chef as a callback; nothing promised on the call |
| Running 20 minutes late at 7:50 pm | Rings out while the maître d' seats a table | Caller hears the hold policy and is transferred to the host stand, or a note is sent there |
In this example the number of calls stays the same. What would change is who answers during service, how fast the closed-day requests reach a person, and whether the details survive the trip from the phone to the book and the kitchen.
What the numbers would look like
The worked example counts the front-of-house minutes the SI Employee would take off the team on service days. Every request still needs a person to confirm it, so only the minutes saved on each call count. The hourly cost is the June 2026 average for accommodation and food services, benefits included[6].
| Input | Example |
|---|---|
| Calls on a service day | 40 |
| Staff minutes saved per call | 3 |
| Share the SI Employee would take | 45% |
| Hourly cost of front-of-house time | $20.03 |
| Calls a month | 868 |
| Staff hours on these calls | 43 |
| Hours handed off | 20 |
| Monthly value of that staff time | $391 |
How it is worked out: Calls a day × 21.7 working days × minutes per call ÷ 60 × share handled = hours; hours × hourly cost.
Assumptions
- Hourly cost: $20.03, the average employer cost of compensation per hour worked in accommodation and food services, June 2026.[6]
- At the top independent US restaurants Cornell checked, 49% of reservations came by telephone.[1]
- Invented for this example: forty calls on each of five service days a week (the model's 21.7 days a month); a 45% share taken in overflow, after 4:30 pm or before 11 am; three minutes saved per call, about four on the phone less one to enter and confirm the request.
Example only: modelled, not measured. Closed-day calls are left out, so the hours shown are on the low side.
In this example that is about 20 hours a month, roughly $390 at that rate. It is a modest number, and it is not the reason a fine-dining room would do this. The minutes that matter are the ones at 7:45 on a Saturday, when the maître d' would stay at the door instead of the phone, and the Tuesday mornings when the reservationist would confirm requests instead of chasing voicemails. The techniques in handling phone calls during the dinner rush still apply to the calls that reach a person.
The private room is the other side of the ledger. In this example one 16-guest dinner would be worth more than a month of those hours, and the appetite is there: 52% of consumers told the National Restaurant Association they were interested in private dinner events with a chef[7]. Every inquiry would reach the events manager the same evening with the date, headcount and dietary needs already written down, so the first callback can be about menus. Selling private dining covers what happens on that call.
The first 30 days in this example
Day 1
The general manager writes the house information, the reservation policy and the questions for each request type.
Day 4
Test calls: a sold-out Saturday, a party of 14, a severe nut allergy, a guest who insists on a person.
Day 7
Closed days and overnight go live. Daytime calls still ring the reservationist first.
Day 14
Service hours and daytime overflow go live, with a transfer to the host stand for same-night guests.
Day 30
The manager compares podium calls, Tuesday voicemails and private-dining reply times with the month before.
Example timeline; a real rollout follows the restaurant's own schedule.
In this example the general manager keeps two lists through the first month. One holds requests the reservationist had to correct after calling back: a wrong date, a party size that changed, a dietary note that was too vague for the kitchen. The other holds calls that went to the SI Employee but should have reached a person straight away. The first list shows which questions need rewording; the second shows where the transfer rules are too tight.
Lessons from the scenario
- Write down the request types and who owns each one before going live. A request with no owner is just a voicemail with better handwriting.
- Keep the word request. Guests forgive a callback; they don't forgive a table that was never booked.
- Put allergies on their own line, in the guest's words, and send them to the kitchen. Nobody on the phone should decide what the kitchen can cook.
- Give private dining a same-day owner and a backup, including the weeks the events manager is off.
- Judge the setup by podium calls during service and by the Tuesday voicemail pile, not by how many calls were answered.
The restaurant keeps its number, its reservation system, its policies and its people. What changes is that the maître d' stays at the door. For the detail behind each piece, see running a restaurant waitlist, allergy questions over the phone and guest notes and tags in your reservation system. For what an SI Employee handles on a live call today, see what it does.
Frequently asked questions
Is The Marrowgate Dining Room a real restaurant?
No. It is a fictional restaurant used to show the method, and every figure is either modelled from the sources listed or invented for the example.
Does the SI Employee book tables straight into the reservation system?
No. Booking straight into a reservation platform is planned, not live, so in this example every booking is taken as a request. The reservationist confirms it in the reservation system, which sends the guest its own confirmation.
Who answers allergy and dietary questions?
The kitchen. The SI Employee writes the allergy down in the guest's own words, makes no promise about the menu, and passes it to the sous chef as a callback request, with the general manager as backup. See handling allergy questions over the phone.
What happens to same-night calls during service?
In this example a guest running late hears the 15-minute hold policy, and anyone who wants a person is transferred to the host stand. If nobody picks up, the general manager's mobile is the backup, and a written note reaches the host stand either way.
Can it take a credit card guarantee over the phone?
No. In this example card numbers are never taken on the call. The SI Employee reads the restaurant's guarantee and cancellation policy, and the reservation system sends its own card link when the reservationist confirms the table.
References
Cornell University Center for Hospitality Research (Sheryl E. Kimes and Katherine Kies) (2012). The Role of Multi-Restaurant Reservation Sites in Restaurant Distribution Management (Cornell Hospitality Report, Vol. 12 No. 3) (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (2026). Occupational Outlook Handbook: Food and Beverage Serving and Related Workers (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2009). How Restaurant Customers View On-line Reservations (Cornell Hospitality Report, Vol. 9 No. 5) (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2008). A Consumer's View of Restaurant Reservations Policies (Cornell Hospitality Report, Vol. 8 No. 1) (opens in a new tab) ↑
U.S. Food and Drug Administration (2026). Food Allergies (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (2026). Employer Costs for Employee Compensation, Table 4: Private industry workers by occupational and industry group (June 2026) (opens in a new tab) ↑
National Restaurant Association (2025). Restaurant Industry Poised for Growth in 2025: Industry Expected to Employ 15.9 Million People and Reach $1.5 Trillion in Sales (opens in a new tab) ↑