Group Bookings Go to Whoever Replies First
A 30-pax year-end dinner enquiry goes to five restaurants at once. The one that answers pax, price and room first gets the deposit. Here is how to be it.
Restaurant group booking enquiries are decided before anyone talks about a deposit. The company admin who asks "do you have space for 30 pax on 12 December, and how much per head?" has sent the same message to four other restaurants, and the deposit goes to whichever one answers those two questions first. Most restaurants answer last, because a group enquiry lands during service and gets left for the boss.
A group booking enquiry is worth more than a week of two-top reservations, and it is the enquiry most restaurants reply to slowest. The person sending it is usually an office admin comparing several venues in one afternoon, and they book the first place that gives them capacity, a price per pax and deposit terms without a follow-up question. A restaurant that puts those facts in a document and lets the first reply come from that document, in under a minute, wins the booking before its competitors have finished dinner service.
Why do group booking enquiries get answered last?
Because they are the only enquiry the floor staff are not allowed to answer. A message asking "are you open on Monday?" gets a reply from whoever holds the phone. A message asking about 30 pax, a private room and a set menu price gets read, marked in the person's head as "for boss", and left. The boss is expediting. The boss sees it at 11pm, decides it needs a proper reply, and sends one the next morning. By then the admin has a confirmed venue.
That pattern is not unique to restaurants. In the sales operations we have looked inside, roughly 3 in 10 assigned leads never got a first message, and nobody was answerable for it. The lead was "seen". Seen is not answered. A restaurant runs the same shape with one phone and no assignment at all: everybody saw the group enquiry, so nobody owns it.
The cost is out of proportion to the effort. Thirty pax at RM88 per head is RM2,640 in one sitting, in a private room that would otherwise seat two families. A quiet Tuesday in December becomes the best night of the week. The reply that wins it is five lines long.
That figure comes from B2B sales (InsideSales.com Lead Response Management study, via LeadAngel), and a year-end dinner enquiry is B2B sales. It is a company buying from a supplier. The buyer is not a diner in love with your char siew. It is an admin with a budget, a headcount and a deadline, and a boss who wants the venue confirmed this week.
Who actually sends a year-end dinner enquiry?
Not the person who will eat the meal. A company annual dinner or year-end party enquiry in Malaysia is almost always sent by an admin, HR executive or personal assistant who has been told to "find somewhere for the team, around RM100 a head, before the 15th". They open Google Maps, shortlist five restaurants near the office, and send the same three questions to all five within twenty minutes.
Read that from the restaurant's side. You are not competing with the hotel ballroom. Klang Valley hotel packages run RM150 to RM250 per pax for a ballroom, and December and January Saturday slots at popular hotels are gone by mid-year (Savvy Travel, 2026). A 40-person company that missed that window, or never had that budget, is looking for a restaurant with a private room. That is a lot of companies in October and November, and the admin's shortlist is your real competition.
The admin's job is to close the task, not to find the best food. Their question list is short and the same every time:
A restaurant that answers all five in the first reply has given the admin something to paste into the email to their boss. A restaurant that answers "let me check with the boss and get back to you" has given them nothing, and the admin moves on to the next reply in the thread. The counterintuitive part is that a polite, human "let me check" reply loses to an instant, complete one even when the human restaurant has better food and a better price. The admin never finds out.
What does a group booking enquiry need in the first reply?
Facts, not warmth. The first reply to a large group reservation enquiry should contain capacity, the price per pax, the deposit rule and a clear next question. Warmth comes in the second message, once the admin has a reason to keep talking to you.
Compare the two replies most restaurants actually send.
| "Let me check with boss" | Fact-sheet reply | |
|---|---|---|
| Time to first reply | 2 to 14 hours | Under one minute |
| Facts in the reply | None | Capacity, room, price per pax, deposit, cut-off |
| What the admin does next | Reads the next restaurant’s reply | Pastes your reply into an email to their boss |
| Follow-up question needed | Yes, at least two more rounds | One: the date and headcount |
| Chance of a deposit | Whoever else replied first | Yours to lose |
Here is the fact-sheet reply for a 70-seat Chinese seafood restaurant in Klang, written once and reused for the whole season:
Hi! Yes, we can take 30 to 40 pax on weekday evenings in December.
Private room: seats 40 (round tables of 10), own aircon, mic and TV screen.
Set menus: RM78 / RM98 / RM128 per pax (8 courses), vegetarian table available.
Deposit: RM500 to hold the date, balance on the night. Free cancellation up to 7 days before.
Which date are you looking at, and roughly how many pax?Five lines. Nothing in it needs the boss. Every number in it was true last week and will be true next week. That is the point: the facts that win a group booking are the facts that do not change, which means they can be answered by anyone, or by anything, the moment the enquiry lands.
This is where Raion HUB's AI chatbot earns its keep for an F&B operator without becoming an ordering system. Upload the group menu PDF and the private-room fact sheet, and the AI answers the five standard questions from those documents, in English, Malay or Mandarin, while the kitchen is mid-service. It also reads the enquiry and fills in the date, headcount, budget per pax and occasion as fields on the contact, so the manager opens a booking with the details already captured rather than a chat to scroll through. The manager still confirms the date and takes the deposit. The AI just makes sure the restaurant is the first reply, not the fifth.
Frequently Asked Questions
How to answer group booking enquiries in under a minute
The whole system is one document, one rule about who owns the enquiry, and one follow-up. It takes an afternoon to set up in October and runs through Chinese New Year.
How to Answer Restaurant Group Booking Enquiries in Under a Minute
Notice what is not in that list. No online ordering, no menu builder, no payment flow inside the chat. The manager takes the deposit the way the restaurant already takes deposits. The automation is only doing the part restaurants are worst at, which is replying to a high-value enquiry instantly with facts, and then not forgetting it. That is also the part covered in our restaurant reservation automation guide: capture the booking, confirm it, remind them. Group bookings are the same mechanism with a bigger number attached.
The follow-up step matters more for groups than for any other reservation. A two-top that goes quiet was never coming. A 35-pax enquiry that goes quiet is sitting in a comparison email waiting for a boss to pick. The day-2 message is often the one that gets forwarded to that boss, and the one that wins.
What changes for a restaurant in year-end season
The difference shows up in the quiet nights. A restaurant that answers group enquiries the next morning fills its December Saturdays anyway, because everybody wants Saturdays. The restaurant that answers in a minute fills its December Tuesdays and Wednesdays, because it was the first to say "yes, weekday evenings, RM78 per pax, private room seats 40".
Around 40 company dinner enquiries arrive between mid-October and end November, most during dinner service. The owner answered them at night or the next morning and could not tell which ones he had lost or why.
A one-page group fact sheet and three set menus were uploaded so the AI answered capacity, price per pax and deposit terms instantly. Enquiries were tagged as group bookings, assigned to the floor manager, and chased on day 2 and day 5 if unconfirmed.
That is a composite of the operators we talk to, not a single account, and the numbers are deliberately left out. The mechanism is what transfers. A restaurant that can answer the five standard questions in a minute will win more group bookings than one that cannot, and the restaurant's food has nothing to do with it.
The same fact-sheet approach fixes the neighbouring leak, which we covered in where five-figure catering orders get lost: the highest-value enquiries an F&B business receives are the ones it answers slowest, because they look complicated. They are not complicated. They are five questions with fixed answers. And once the group is confirmed, the standard no-show prevention workflow applies with a deposit already in hand, which makes it the easiest no-show you will ever prevent.
If you run a restaurant with a private room and you have not yet written your group fact sheet, write it this week, before the October enquiries start. The F&B automation page shows where it plugs in once you have it. For the wider picture on how the first reply, the capture and the follow-up fit together across an F&B operation, the WhatsApp automation guide for Malaysian businesses covers the full workflow.
The bottom line
Group booking enquiries are the highest-value messages a restaurant receives and the ones it answers slowest, because they are left for the boss. The admin sending them books the first restaurant that states capacity, price per pax and deposit terms without a follow-up question. Put those facts in one document, let the first reply come from it in under a minute, give every group enquiry a named owner, and chase the unconfirmed ones on day 2 and day 5. The deposit follows the first complete reply, not the best food.
