Restaurant corporate booking calls: banquets and groups

Which calls actually earn money in a restaurant

Most calls to a restaurant are short and simple: opening hours, the address, a table for two. Their value is low and automating them needs no elaborate flow — a form on the site or a chat usually solves that more cheaply.

A meaningful share of a restaurant's revenue comes from different calls: banquets, corporate events, group bookings, large orders. These enquiries are few, but one of them can be worth dozens of ordinary table reservations. That is where how the call is run changes the result.

What is worth automating in everyday table booking, and what is not, is covered in the restaurant chatbot article. This one is about the high-value enquiry: how banquet and corporate booking calls should be built.

The seven facts in a banquet enquiry

Answering a banquet enquiry takes seven things. Without them the answer stays at «prices vary, come and talk to us» and the enquiry is lost.

• Date and time: the specific day, the start and the approximate end
• Guest count: a range is fine, but a narrow one
• Event type: birthday, corporate, wedding, memorial, business meeting
• Room requirement: a private room or a section of the main one; screen, microphone, music
• Menu format: set menu, buffet, open menu, special dietary requirements
• Budget range: per head or total
• Who decides: whether the person calling decides, or approval is needed

That last line is decisive on corporate enquiries. The caller is often an office manager and the decision sits elsewhere. Knowing this determines who the follow-up goes to and when — otherwise a proposal is sent and an answer is awaited from someone who never saw it.

The price question: cost per head

The first question on a banquet enquiry is almost always about price. It is not an easy one to answer on the spot, because the figure depends on the menu, the date and the room. All the same, «we cannot say exactly» loses the enquiry.

1. 1Give a range, not a numberA per-head range and what it covers: which menu, drinks included or not, service charge or not. A range lets the customer compare and keeps the conversation going.
2. 2Name what moves the rangeThe date (weekends and holidays differ), the guest count, the menu format. With those three the customer can test their own budget.
3. 3Offer the next stepA viewing of the room, menu options sent over, or a tasting. A banquet enquiry does not close on the phone — the phone's job is to set the next step.

The third step is the key to this flow. The outcome of an enquiry should not be «we quoted, they are thinking»; it should be a meeting with a date or a proposal that has gone out.

The follow-up window follows the event date

Follow-up on banquet enquiries does not run on a fixed schedule. The window is set by how long there is until the event.

• One or two weeks to the event: answer the same day, follow up the next
• A month to the event: answer, follow up in three days, a final touch a week later
• Two or three months: answer, follow up in a week, then once a month
• Date not yet fixed: after two touches the enquiry moves to a waiting status and joins the seasonal list

The practical reason for the split: calling every day about an event two months away is pressure, and waiting three days about an event next week is late. Applying one schedule to every enquiry makes both mistakes at once.

The script: four situations

The script's purpose is not to sell but to close the enquiry with complete information and a concrete next step.

1. 1Information complete, the date is freeThe room and date are held provisionally, menu options are sent, and a deadline for confirmation is given. Result: a provisional hold and a confirmation date.
2. 2The date is takenAn alternative is offered: a nearby date, a different hour, a second room. Without that answer ready, the enquiry is lost.
3. 3Someone else decidesThe decision maker's name, role and contact are asked for; the proposal goes to both and the follow-up goes to the decision maker.
4. 4They only want a priceGive the range and offer the next step. An outcome code is written — this group is its own list for a seasonal campaign.

Two touches, before and after the event

A booked banquet is not yet fully booked. Two touches reduce the loss and lay the ground for a repeat order.

• Two or three days before: final guest count, menu, arrival time and payment terms
• Special requirements are repeated: diet, allergies, children's menu, cake
• One or two days after: a short feedback call — what went well, what was missing
• For corporate customers, the approximate date of the next event is asked for and recorded
• If there is dissatisfaction, the call goes straight to the person responsible

The third line is the one most often skipped and the one that brings the most back. A call after the event surfaces a problem early and keeps a corporate customer on the list for next year.

Corporate customers: events that repeat

A corporate customer's value is not measured by one event. Company events repeat: New Year, anniversaries, team meetings, training days. A collaboration that worked once is the simplest sales opportunity available next year.

The practical approach: call the companies that held an event last year one or two months before that same date. This is returning to a base with a seasonal segment, and the rules are the same as in retail customer reactivation — the difference is that here the segment is built from dates rather than from basket size.

Limits

What is not automated here is clear enough. Menu changes, special dietary requirements and decoration arrangements are decisions for the chef and the events manager. Discounts are not the subject of a script either.

Equally, a call about a problem during an event — a delay, a shortage, a complaint — goes to a person immediately. That call is not a sales call, and any delay in answering it raises its cost sharply.

How Vexvon supports this flow

Vexvon's AI voice agent answers and places calls from each company's own scenario, approved information and escalation rules. The parts this flow uses:

• Inbound calls are separated by time policies and routing rules: an ordinary table enquiry can go one way and a banquet enquiry to the events manager
• The scenario defines the fields to extract: date, guest count, event type, room requirement, menu format, budget range, decision maker
• Follow-up campaigns are built from a CRM filter and scheduled against the event date
• Reminders are checked every minute and night hours are protected
• A request for a discount or a menu change hands the call to an operator

How booking follow-up is built on the hotel side is in hotel booking follow up calls, and answering and routing calls on the call center page.

Measurement and where to start

Four numbers are enough for the banquet flow, and they have to be measured separately from ordinary table reservations.

• Enquiry-to-proposal rate
• Proposal-to-booked-event rate
• Average event value and average spend per head
• Share of repeat corporate customers

To start, log every banquet enquiry with the seven fields for a month — where the loss sits becomes visible after that. To build this flow, get in touch.