Key takeaways
- One inquiry is worth your median event value for that type of event multiplied by your booking rate for similar inquiries.
- Count slow replies as well as missed ones: in one audit, almost half of companies took more than a day to reply or never replied[1].
- Use the median event, not the average, and work out booking rates by channel; phone, form and email rarely match.
- A written 24-hour personal-reply rule and a monthly lost-inquiry log recover more than new menus or photos.
An inquiry is worth a share of an event
A missed private event inquiry is not worth the full check of the party that never happened. It is worth that check multiplied by the chance you would have booked it, and that chance is something you can measure from your own records. Get the number right and it settles most arguments about who answers the phone, how fast the events manager replies and whether an events hire pays for itself.
The demand is there to lose. In National Restaurant Association research published in 2025, 52% of consumers said they were interested in private dinner events with a chef and 70% in tasting events[2]. Private dining is a sales business with a long gap between the first call and the deposit, and the inquiries that slip through that gap are usually the ones nobody counted.
Two kinds of inquiry leak. Some are missed outright: the call rings out, the voicemail is never returned, the web form lands in an inbox nobody opens until Tuesday. Others are answered slowly, two or three days later, after the host has already seen two other rooms. Both belong in the same calculation.
The formula and the numbers it needs
Value of one inquiry = typical booked event value × booking rate for inquiries like it. Monthly exposure = value of one inquiry × inquiries missed or answered late each month.
Typical event value
Pull every booked event from the last 12 months and take the median total: food, beverage, room fee and service charge, before tax. Use the median, not the average. One wedding buyout drags the average up and makes every inquiry look richer than it is.
Booking rate
Divide booked events by real inquiries over the same months. If your event sales pipeline records the source, work it out separately for phone, web form and email.
Share of real inquiries
Strip out vendor pitches, booked clients changing a headcount and questions that were never events. The share varies a lot between restaurants, so count it rather than guess.
Missed and late inquiries
Count the inquiries that never got a personal reply, plus those whose first personal reply came more than a day later. The phone log, the events inbox and the form tool each hold part of the answer.
Do not rely on your Google listing for the phone side. Google switched off call history in Business Profiles on July 31, 2024, so calls placed from the listing no longer show up there[3]. The record has to come from your own phone system, or from whoever answers your forwarded calls. The guide to measuring missed calls at your restaurant covers pulling a week of logs and reading them.
Example: what one inquiry is worth, by event type
Example. A fictional 110-seat bistro with a 40-seat private room pulls a year of events and splits them by type. The booking rates come from its own pipeline; the spend per guest is its median for each type, drinks included.
| Event type | Guests | Median spend per guest | Event value | Booking rate | Value per inquiry |
|---|---|---|---|---|---|
| Weekday business dinner | 20 | $95 | $1,900 | 35% | $665 |
| Birthday dinner, private room | 16 | $70 | $1,120 | 45% | $504 |
| Rehearsal dinner | 40 | $110 | $4,400 | 25% | $1,100 |
| December holiday party | 60 | $85 | $5,100 | 20% | $1,020 |
| Weekday lunch meeting | 25 | $40 | $1,000 | 50% | $500 |
Read the last column, not the event value. In this example a rehearsal dinner inquiry is worth about twice a birthday inquiry, even though it books less often, because the event is four times the size. A weekday lunch meeting looks small, but it books half the time and, if it goes well, comes back every quarter.
That repeat value is not in the table, so treat the figures as a floor. A company that books a holiday party and two client dinners a year is worth far more than any single event in it. Building an annual calendar of repeat events is how that value gets collected, and it starts with the first inquiry being answered.
Late counts as partly missed
Restaurants that track anything track unanswered calls. Very few track slow replies, and slow is the more common failure. The best-known audit of response times is not about restaurants, but the shape fits: when researchers sent a web inquiry to 2,241 US companies, 37% replied within an hour, 16% within a day, 24% took longer than a day and 23% never replied at all. Companies that did reply within 30 days took 42 hours on average[1].
- Within an hour 37%
- 1 to 24 hours 16%
- More than 24 hours 24%
- Never responded 23%
Source: Harvard Business Review, 2011[1]
Show the data
| First response | Share of companies |
|---|---|
| Within an hour | 37% |
| 1 to 24 hours | 16% |
| More than 24 hours | 24% |
| Never responded | 23% |
The same article reported a second study: firms that tried to reach a lead within an hour were nearly seven times as likely to qualify it as firms that tried an hour later, and more than 60 times as likely as firms that waited 24 hours or more[1]. Someone comparing three restaurants for a client dinner behaves the same way. The first one to come back with availability, the right room and a clear next step sets the bar the others are measured against.
So count late replies as partly lost. A workable rule for the calculation: a first personal reply after 24 hours counts as half missed, and after 72 hours as missed. Those cut-offs are a judgment call, not a research finding, but they stop slow replies hiding inside the answered column.
Your monthly exposure
Put your own numbers into the calculator. The worked example covers phone inquiries only, because that is where most restaurants have the least visibility; run it again for the web form and the events inbox.
| Input | Example |
|---|---|
| Event inquiry calls a week | 8 |
| Share unanswered or returned after a day | 30% |
| Share that are new events | 75% |
| Booking rate when answered promptly | 30% |
| Median booked event value | $2,400 |
| Unanswered calls a month | 10 |
| From new customers | 7.8 |
| Bookings that would have followed | 2.3 |
| Monthly value at risk | $5,612 |
How it is worked out: Calls a week × 4.33 weeks × unanswered share × new-customer share × booking rate × average value.
Assumptions
- Missed or late share of 30%: in an audit of US companies, 23% never answered a web inquiry and another 24% took more than a day.[1]
- Call count, new-event share, booking rate and event value are invented for this example. Use your own pipeline and phone log.
Example only. The result is the event revenue riding on calls nobody handled in time, not revenue you would all win back.
Example. At eight event calls a week, with three in ten unanswered or returned after a day, three-quarters of them new events, a 30% booking rate and a $2,400 median event, the bistro has roughly $5,600 a month of event revenue riding on calls nobody handled in time. It would not win all of that back. What changes is the booking rate on those calls, which moves toward the rate on calls answered well. That gap is the number to track.
The 24-hour reply rule
The cheapest fix is a written standard: every event inquiry gets a personal reply within 24 hours, seven days a week, and within two hours when it arrives during office hours. An autoresponder does not count. A personal reply answers three questions (is the date open, does the space fit the group, what happens next) and contains these five things.
- Availability: the date is open, open with a tentative hold until a named day, or taken, with the two nearest alternatives.
- Fit: the room or section that suits the guest count, with one line on the layout.
- Price frame: the minimum or per-person range for that night, in writing, so the host can check it against the budget.
- Next step: a tour time, a call slot or a proposal by a named day.
- A name and a direct number, sent from the restaurant’s address rather than a personal phone.
Callbacks need a written partner. In a 2020 Pew Research Center survey, eight in ten Americans said they do not generally answer cellphone calls from unknown numbers[4], so leave a short voicemail and send the email in the same minute. The private event inquiry response templates have wording for an open date, a taken date and an inquiry with half the details missing.
Who keeps the rule on days off decides whether it holds. Food service managers often work evenings, weekends and holidays[5], and planning carries on after close: an OpenTable estimate cited by Cornell researchers put about a quarter of online reservations between 10 pm and 10 am[6]. An events manager who works Tuesday to Saturday days cannot see the Sunday-night inquiry until Tuesday morning. Decide who covers each gap; who should answer private event calls compares the options.
Keep a lost-inquiry log
A log turns opinions into numbers. Keep one row per inquiry, whatever the channel, and fill in the outcome when it closes.
| Field | What to record | Why it matters |
|---|---|---|
| Received | Date, time and channel: phone, form, email or walk-in | Shows when inquiries arrive and who was on |
| Event | Event date, guest count, occasion, room wanted | Lets you value it with your own table |
| First personal reply | Date, time and who replied | The number the 24-hour rule is judged on |
| Estimated value | Guests × median spend for that event type | Turns lost inquiries into dollars |
| Outcome | Booked, lost, no response, not a fit | Feeds the booking rate |
| Reason lost | Date taken, price, slow reply, chose another venue, unknown | Shows which leaks you can fix |
event inquiries by phone, form and email
real events, after vendors and changes are removed
got a personal reply within 24 hours
received a written proposal
booked with a deposit
Example, modelled for illustration. Your own log gives the real funnel.
In the example funnel, nine of the 31 real inquiries never got a personal reply within a day. At the bistro’s numbers that is the line to work on first, ahead of new menus, new photos or a price change. The reason-lost column tells you the second line: if “date taken” dominates, the answer is pricing quieter nights, not answering faster.
Closing the gap on the phone
Most of the fixes are habits: the 24-hour rule, a capture card at the host stand, one shared inbox for event mail. The hard gap is the phone at the moments nobody can take a long call, such as Friday service, Sunday night and the events manager’s day off. One option is to forward those calls to an SI Employee, which asks the event questions you set, answers the room basics you approve and emails the summary to the events manager; it never confirms a date or a price.
The fine-dining example shows that setup on an 18-seat private room, and a second example on a busy takeout and catering line shows it where event calls compete with orders. Whatever closes the gap, rerun the log after a month. If the share answered within a day goes up and the booking rate on those inquiries holds, the number in your calculator is turning into deposits.
From there, the follow-through matters as much as the first reply. Selling private dining covers packages and minimums, and post-event follow-up and rebooking covers turning one booked event into the next.
Frequently asked questions
How do I put a value on a private event inquiry?
Multiply your median booked event value for that type of event by your booking rate for similar inquiries. In the example above, a $4,400 rehearsal dinner that books one time in four is worth about $1,100 per inquiry.
Should slow replies count as lost?
Partly. In one study, firms that tried to reach a lead within an hour were more than 60 times as likely to qualify it as firms that waited 24 hours or more[1]. Counting a reply after 24 hours as half lost keeps slow replies visible.
Where do I find missed event calls?
In your phone system's call log, or in the call records from whoever answers your forwarded calls. Google Business Profile stopped showing call history on July 31, 2024[3].
Does the value include repeat business?
Not in the basic formula, so treat the result as a floor. Corporate clients who rebook several times a year are worth more; track them as accounts, not single events.
What reply time should we promise event inquiries?
A personal reply within 24 hours every day of the week, and within two hours during office hours, covering availability, fit, a price frame and a next step.
References
Harvard Business Review (2011). The Short Life of Online Sales Leads (opens in a new tab) ↑
National Restaurant Association (2025). Restaurant Industry Poised for Growth in 2025 (2025 State of the Restaurant Industry) (opens in a new tab) ↑
Google Business Profile Help (2024). Changes to Google Business Profile chat and call history (opens in a new tab) ↑
Pew Research Center (2020). Most Americans don't answer cellphone calls from unknown numbers (opens in a new tab) ↑
US Bureau of Labor Statistics (2025). Occupational Outlook Handbook: Food Service Managers (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2009). How Restaurant Customers View Online Reservations (Cornell Hospitality Report, Vol. 9, No. 5) (opens in a new tab) ↑