ExampleExample scenario. Not a real customer. Figures are modelled from the sources listed.

Case studyFull-service restaurants with catering and private events

Example: how a 3-restaurant group would catch catering calls

A modelled scenario: how a fictional three-restaurant group would capture catering and event calls during service and route them to its events manager.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing9 min read

On this page
  1. Scenario profile
  2. The group in this example
  3. Where the catering calls went before
  4. How the SI Employee is set up
  5. Before and after, call by call
  6. What the numbers would look like
  7. The events manager's callback routine
  8. The first 30 days in this example
  9. Lessons from the scenario
  10. Frequently asked questions
  11. References

Scenario profile

Business
Example: Tallowbrook Kitchen Group (3 restaurants)
Industry
Full-service restaurants with catering and private events
Size
Owner, one events and catering manager, three general managers and about 85 staff across three restaurants
Setting
One metro area: a downtown restaurant with a 40-seat private room, a suburban restaurant near office parks that cooks most catering, and a neighborhood restaurant for family events
Call volume
About 1,100 calls a week across three numbers, roughly 60 of them about catering or events

Key takeaways

  • In this example about 60 of the group's 1,100 weekly calls are about catering or events, and about 45 of those land during lunch or dinner service.
  • The modelled setup answers all three numbers on overflow and after closing, asks the events manager's own questions and names the restaurant on every lead.
  • A change to a confirmed order is transferred to the manager on duty while the caller is on the line; prices, dates and allergy answers stay with staff.
  • Every figure here is modelled from the sources listed or invented for the example, not measured at a real restaurant group.

The group in this example

Tallowbrook Kitchen Group is invented for this example; the setup and the arithmetic are the point. It runs three full-service restaurants in one metro area: a downtown dining room with a 40-seat private room, a suburban restaurant near two office parks that cooks most of the catering, and a smaller neighborhood place that hosts birthdays, showers and the odd rehearsal dinner.

Catering began as a favor to regulars and is now the part of the business the owner most wants to grow. The private room is the newer bet. In the National Restaurant Association's 2025 outlook, 52% of consumers expressed interest in private dinner events with a chef and 70% in tasting events[1]. One events and catering manager handles all of it, on weekdays, from a desk in the suburban kitchen office.

In this example the three numbers take about 1,100 calls a week, and roughly 60 are about catering or events: new office lunch orders, party and private-room inquiries, and changes to booked orders. About 45 of them arrive at the worst moments: between 11:30 and 1:30, when office managers line up lunches for the days ahead, and between 5 and 8, when people call about a party on the drive home.

Where the catering calls went before

Hosts answer all three phones, and a host cannot quote a catering order. In a rush the first move was to fetch the general manager, who left a full dining room for seven or eight minutes to write the details on the back of a guest check. When no manager could come, the call ended as a first name and number on the reservation pad, or as a request to email the events manager. The pad lost the headcount. The email request lost the caller.

Those minutes cost more than the P&L shows. Food service managers earned a median $33.36 an hour in 2025, and their schedules can include early mornings, nights, weekends and holidays[2]. Good ones are hard to replace: nearly three quarters of operators plan to hire in 2026 but expect difficulty finding experienced managers and chefs[3]. A manager writing on a guest check is not touching tables or watching the pass.

Event inquiries had a location problem on top. Callers ring the restaurant they found first, not the one with the room they need. A host at the neighborhood restaurant could not say how many the downtown room seats or whether it does a plated dinner, so the answer was “someone will call you back”, often with no date or guest count written down.

Then the callbacks. The events manager started each morning with three voicemail boxes and three host pads, and returned calls from a personal mobile. In a 2020 Pew survey, eight in ten Americans said they don't generally answer their cellphone when an unknown number calls[4], so the phone tag often ran into the next day. Changes were worse: a headcount moving from 30 to 42 for tomorrow's lunch, given to a host at 7:40 pm and found the next morning after prep had started.

How the SI Employee is set up

In the modelled setup an SI Employee picks up any call a host has not answered within four rings, at all three numbers, and takes every call after closing. Each number keeps its own greeting, hours, address and policies, so a caller to the neighborhood restaurant hears that restaurant's name and that kitchen's closing time. The group keeps one local number on each of its three listings, in line with Google's guidance to give a number that connects to the individual business location[5].

Before anything goes live, the owner and the events manager write down four things: the catering and event questions, in the order a quote is built; the private-room basics each restaurant may share; who gets each kind of call at each location; and the topics that always go to a person. Prices, date availability and allergy answers stay with staff. The routing list fits on one page:

  1. New catering order or event inquiry, any restaurant: full intake, then a summary to the events manager naming the restaurant and the caller's callback window.
  2. Change to a confirmed order in the next 48 hours: transfer to the manager on duty at the restaurant cooking it, with the events manager as backup.
  3. Allergy or dietary-safety question: details and a callback number passed to staff, with no ingredient answers given on the phone.
  4. Complaint about a past order or event: details taken and passed to that restaurant's general manager.
  5. Pickup or delivery: the group's ordering link sent by text when the caller agrees, once the SMS sender is registered.
Example: a 12:20 pm office lunch inquiry
  • Caller
  • System
  • SI Employee
  • Your team
  1. 01Caller

    Call at 12:20 pm

    An office manager calls the suburban restaurant about lunch for 45 next Thursday.

  2. 02System

    Overflow after four rings

    Both hosts are seating the lunch rush, so the call rolls to the SI Employee.

  3. 03SI Employee

    Asks the catering questions

    Date, start time, guest count, drop-off or staffed, address and a callback window.

  4. 04SI Employee

    Flags dietary needs

    Notes two gluten-free guests and a nut allergy for staff; gives no ingredient answers.

  5. 05System

    Lead to the events manager

    Summary, transcript and restaurant land in the inbox; the events manager is notified.

  6. 06Your team

    Callback the same afternoon

    The events manager quotes from the summary instead of starting the questions again.

Example: fictional group and routing. A real setup follows the questions and rules the owner approves.

The questions are the events manager's own: date and start time, guest count, drop-off or staffed service, delivery address or pickup location, dietary needs to flag, a budget if the caller offers one, and a callback window. Events add the occasion and the restaurant the caller would prefer. Same questions, same order, every call: that is what lets the events manager quote from the summary. The guide to catering inquiry questions covers how to pick them.

Room questions get the approved basics, such as the downtown room seating 40 for a plated dinner. It never says the room is free on a date or quotes a minimum spend; it records the request and gives the house rule on callbacks: same day for weekday calls before 3 pm, otherwise the next weekday morning.

Before and after, call by call

Before and after: how catering and event calls would be handled in this example
CallBefore (hosts answer, notes on the pad)After (modelled setup)
Office lunch inquiry at 12:20 pmFirst name and number on the reservation pad, if a host has a free handOverflow answer, full intake, summary to the events manager naming the restaurant
Rehearsal dinner call to a restaurant with no private room“Someone will call you back”, usually with no date or guest countApproved basics for the downtown room; inquiry sent with the caller's preferred restaurant
Headcount change for tomorrow, called in at 7:40 pmLeft with a host and found the next morning after prep startedTransferred to the manager on duty, events manager as backup, and logged with a summary
Nut allergy question about the catering menuHost guesses from the menu or promises to ask the kitchenNo ingredient answer; details and callback number passed to staff
Caller who just wants to order pickupOn hold while the host seats a four-topOrdering link sent by text when the caller agrees
Events manager's first hourThree voicemail boxes, three host pads, callbacks from a personal mobileOne inbox: each call with a summary, the restaurant it came in on and a callback window

In this example the calls and the events manager's job stay the same. What would change is where the calls land in the middle of service, and what arrives with them.

What the numbers would look like

The worked example models manager time on catering and event calls. The hourly figure is the 2025 median pay for food service managers[2]; the volume, minutes and share are invented for this scenario.

ExampleModelled manager time on catering and event calls
Example: worked figures
InputExample
Catering and event calls a day, all three9
Manager minutes per call8
Share that no longer needs a manager75%
Manager's hourly pay$33.36
Calls a month195
Staff hours on these calls26
Hours handed off20
Monthly value of that staff time$652

How it is worked out: Calls a day × 21.7 working days × minutes per call ÷ 60 × share handled = hours; hours × hourly cost.

Assumptions

  • Hourly pay of $33.36, the 2025 median for food service managers.[2]
  • Nearly three quarters of operators plan to hire but expect difficulty finding experienced managers, so the hours matter more than the dollars.[3]
  • Nine calls a day, eight manager minutes a call and a 75% share are invented for this example. The other quarter, mostly changes to confirmed orders, still goes to a manager.

Example only: modelled, not measured. Nine calls a day over the calculator's 21.7 days gives about 195 a month, which matches the 45 a week that arrive during service. Median pay leaves out benefits, so the cost runs low.

In this example that comes to about 20 manager hours a month, roughly $650 at the median rate. Treat that as the floor. The bigger number is the orders, which this model leaves out: an office lunch for 45 or a rehearsal dinner that ends up as a first name on a pad is easy to lose to whichever caterer calls back first.

The phone is still where a lot of this business starts. In a Cornell survey published in 2012, about two-thirds of diners who had not booked a table online wanted to talk to someone to make their reservation[6]. That was about tables, not catering, but an office manager booking lunch for 45 is unlikely to feel differently.

The events manager's callback routine

In the modelled setup each call arrives with a summary, a transcript and an outcome. The routine stays the events manager's:

  1. 9:00 Changes first

    Open any change to a confirmed order and check it reached the right kitchen and the prep sheet.

  2. 9:10 Call back

    Return calls from a restaurant line rather than a personal mobile, inside the window each caller chose.

  3. Same day: quote

    Send the written quote while the details are fresh, and tell the client when you will follow up.

  4. 5:00 Update the pipeline

    Move each lead to its stage in the events tracker so nothing depends on anyone's memory.

Response targets follow the group's own standard, as in how fast to respond to catering leads, and the stages follow its event sales pipeline. Leads could reach catering software by webhook. For the first month the events manager types them into the tracker instead, which doubles as a check on every summary.

The first 30 days in this example

Example: a modelled first month
  1. Day 1

    Owner and events manager write the questions, room basics and routing for each restaurant.

  2. Day 4

    Test calls at all three numbers: lunch for 60, a wrong-location rehearsal dinner, a 7 pm headcount change, a nut allergy.

  3. Day 8

    Overflow goes live at all three numbers during opening hours, plus every call after closing.

  4. Day 15

    Events manager and general managers review every catering and event call from the first week.

  5. Day 30

    Owner compares time to first callback and the share of complete leads with the month before.

Example timeline; a real rollout follows the group's own schedule.

Through the first month the events manager marks two kinds of call: leads missing something the quote needed, and calls that should have reached a person and did not. The first means a question is missing or badly worded. The second means a routing rule is too narrow, and it gets fixed first, because a missed headcount change turns into a problem on the line.

Lessons from the scenario

  • Write the catering questions in the order the quote is built, and ask them the same way on every call.
  • Route by kind of call as well as by restaurant: new leads to the events manager, changes to the manager on duty, allergy questions to staff.
  • Treat a change to a confirmed order as urgent. It belongs with a person the same evening, not in tomorrow's inbox.
  • Keep prices, availability and allergy answers with staff, and have the phone agent say so plainly.
  • Judge the setup by time to first callback and by how many leads arrive complete, not by how many calls were answered.

From the outside nothing changes: same three numbers, same listings, same hosts, same events manager. Inside, the lunch-rush catering call ends as a complete lead with the right restaurant's name on it. For the wider choices behind this setup, see phone routing for multi-location restaurant groups and whether to run separate lines for takeout, catering and reservations. For what an SI Employee handles on a live call today, see what it does.

Frequently asked questions

Is Tallowbrook Kitchen Group a real customer?

No. It is a fictional restaurant group used to show the method, and every figure is modelled from the sources listed or invented for the example.

Does the phone agent quote catering prices or confirm a date?

No. In this example it asks the events manager's questions, shares only the private-room basics the owner approved and tells the caller when to expect a callback. The events manager quotes and confirms availability.

How does it know which restaurant the caller means?

Each number is set up with that restaurant's name, hours, address, policies and routing. For events it also asks which restaurant the caller would prefer, because many people ring the one they found first rather than the one with the room they need. See phone routing for multi-location restaurant groups.

What happens to a headcount change for tomorrow's order?

In this example it is transferred to the manager on duty at the restaurant cooking the order, with the events manager as backup. If neither picks up, the caller is told so, the change is taken down with a summary and the person the group chose for these calls is notified.

Can the leads go straight into catering software?

Yes, by webhook to any tool that accepts one, including through Zapier. This example keeps it manual for the first month so a person reads every summary against the call before trusting the automation.

References

  1. 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) ↑

  2. U.S. Bureau of Labor Statistics (2025). Occupational Outlook Handbook: Food Service Managers (opens in a new tab) ↑

  3. National Restaurant Association (2026). Persistent Cost Increases and Enduring Demand Will Shape the Restaurant Industry in 2026 (opens in a new tab) ↑

  4. Pew Research Center (2020). Most Americans don't answer cellphone calls from unknown numbers (opens in a new tab) ↑

  5. Google Business Profile Help (2026). Guidelines for representing your business on Google (opens in a new tab) ↑

  6. Cornell University Center for Hospitality Research (Kimes and 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) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo