The enquiry that arrives call-ready: catering and private-event intake

Why does the highest-value phone call get answered last?

A catering or private-event enquiry is usually not a menu question. It is closer to a done deal than almost anything else that reaches a restaurant — a $1,200 office lunch, a $6,000 rehearsal dinner — and it tends to arrive at the two worst possible moments: by phone in the middle of Friday dinner service, when nobody is free to take full details, or through a website contact form at 11 p.m., when nobody is watching at all. Restaurants that run these programs seriously treat them as a distinct line of business rather than a favor for a regular's friend — but almost none of that potential is captured by design. It is captured, if at all, by whoever happens to be standing near the phone.

What actually happens to a catering enquiry today

Two failure modes cover almost every case. The phone version: a call comes in mid-service, the host or a server takes a partial note — a name, maybe a headcount — and promises a callback that competes with forty other things that night. The form or email version: the enquiry sits in an inbox or a voicemail box that nobody has a standing job of checking, and by the time someone does, the planner has already heard back from the next restaurant on their list.

That second failure is not a restaurant-specific problem, and there's real research on how much it costs generally. Dr. James Oldroyd's Lead Response Management study, later extended in a Harvard Business Review analysis covering 2,241 firms and more than 100,000 web-generated leads, found that businesses contacting an inbound enquiry within five minutes were roughly 100 times more likely to make live contact — and about 21 times more likely to actually qualify the lead — than those who waited 30 minutes. The same research found the average business took 42 hours to respond at all. That study is B2B and general-business, not restaurant-specific — nobody has run the equivalent study on catering enquiries alone — but there is no reason to think restaurants beat that average when the enquiry usually lands on someone already running a dining room.

What "call-ready" actually means

A callback that starts with "sorry, remind me what you were looking for again?" has already lost momentum. A callback that opens with the date, the headcount, and the occasion already in hand feels like the restaurant has been expecting the call — because, on paper, it has. Six things separate a half-caught enquiry from a call-ready one:

1. The occasion — birthday, rehearsal dinner, office lunch, wake. This alone shapes tone, room, and menu.
2. Headcount — even a range ("25 to 35") is enough to start pricing.
3. The date, and how firm it is — a real reservation to plan around versus a planner still comparing three restaurants.
4. A way to reach them, and when — a phone number is only useful with a window; "evenings after 6" turns a missed call into a scheduled one instead of a guessing game.
5. Anything already volunteered about food, budget, or theme — the planner said it once; nobody should have to ask them to repeat it.
6. How they found you — not essential to the booking, but the cheapest marketing data a restaurant will ever collect, and almost nobody asks.

Everything below is about capturing those six things reliably, whether or not you ever touch a piece of software built for it.

How to build a call-ready intake system with what you already have

None of this requires new technology. It requires deciding, once, that these enquiries get a system instead of a scramble.

1. Put one short form on your own website, on whatever page currently says "call us for catering" or nothing at all. Most website builders (Squarespace, Wix, even a free Google Form linked from the page) can collect the six fields above in under a minute of a planner's time. The form doesn't need to be clever — it needs to exist.
2. Write the same six questions on an index card by the host stand or the phone, for the calls that come in live. A server or host who is handed a script asks better questions under pressure than one asked to remember them.
3. Assign the follow-up to a specific person, not "whoever's free." An enquiry with no owner is an enquiry nobody feels responsible for. This can rotate by shift; it should never be nobody's job.
4. Acknowledge receipt the same day, even before you have an answer. A one-line reply — "got it, we'll call you back by tomorrow afternoon" — is often enough to stop a planner from moving to the next restaurant on their list, and it costs thirty seconds.
5. Set an internal response-time target and hold it. It does not need to be five minutes. It needs to be a number smaller than "whenever someone remembers," and someone needs to check it got hit.

A restaurant that does only steps 1 and 3 — one form, one owner — will out-respond most of the local competition it's actually losing these bookings to.

What a slow or half-caught intake actually costs

The honest answer is that nobody has published a clean, restaurant-specific figure for what one mishandled catering enquiry is worth — the research that exists (the Oldroyd/HBR study above) is general business data, not a restaurant study, and we're not going to borrow its multiplier and dress it up as ours. What is measurable: catering and private events are a real, sizable line of business — the standalone U.S. catering services industry is valued at roughly $15.7 billion in 2026 across some 13,700 businesses (IBISWorld). And private parties aren't a fringe case to plan for: a 2026 survey of over 1,000 food and beverage operators found private parties are the single most common event type these businesses book, at 54.4% of events surveyed (FLIP / Veracity Insurance Solutions). Every one of those bookings started as an enquiry that either got a fast, complete response or didn't.

Where Brief First fits

Brief First's events door is free on every page, for every restaurant, whether or not you ever subscribe to anything: a guest planning something can leave the enquiry and a way to reach them right on your page, and it lands on your dashboard the same way a website form would — a plain capture, no AI involved in catching it. That much costs nothing and never will.

What the paid tier adds is an AI host that does the gathering itself: instead of a name and "call me," a guest talking to the host about a birthday dinner gets asked the occasion, the headcount, and the date in the conversation, the way a good host would ask in person — so what lands on your screen is the call-ready version, not the half-caught one. Free tells you someone asked. Paid gets you the details before you've dialed the number.

Either way, the enquiry reaches a screen instead of a voicemail box, and the next step is a phone call your restaurant makes on its own terms — Brief First never books, quotes, or takes payment on your behalf.