A Party of Twelve Asked on Instagram. Who Replied?

It is 10:40 on a Tuesday night and the kitchen is breaking down. A message arrives on the restaurant's Instagram: "Hi! Do you take groups of 12 for a birthday dinner on the 14th? Roughly what would it cost?" The person who reads the Instagram account is off until Thursday. By Thursday, the organizer has asked three other places, and the first one that answered with something useful probably has the booking.

Nothing went wrong in that story, exactly. Nobody was rude and the room could have seated twelve. The request arrived in a place nobody was watching at that hour, and it asked questions nobody had written the answers to.

Group and private-dining requests deserve their own handling because one message is a whole table. The person writing is also doing a job for other people: they need something they can forward to the group chat before anyone agrees. On our restaurants page, the Growth plan lists an AI SDR for reservation and event inquiries next to event and private-dining campaigns. Before you pay anyone for that, it is worth seeing how much of the problem you can fix with a page of writing and a rule about who answers.

Find out where the requests actually arrive

Ask the team where the last few group requests came from, and you will usually get several different answers. A regular mentions a birthday to a server. Someone fills in the contact form on the website. A message comes into Instagram or Facebook. An email reaches an address only the owner checks. A voicemail is left after close. A note turns up inside a reservation made through a booking platform, where it sits in a field nobody opens until the night itself.

Write every one of those channels down, and next to each, the name of the person who reads it and how often. The gaps are usually obvious once they are on paper. An inbox checked twice a week is a slow no, even when the answer would have been yes.

Write the answers before the questions arrive

Most group requests ask the same handful of things, and the fastest reply is one that was written in advance. Put the answers on a short page on your website, something like "Groups and private dining", and keep a copy as a saved reply in every inbox you use. It should answer:

• How many you can seat, and where: a private room or a section, or the whole place on a quiet night if you do that.
• What they will eat. A set menu or the full menu. If large groups must order from a set menu, say so up front.
• How money works. Your own price per head or minimum spend, whether you take a deposit, and what happens to it if the group shrinks or cancels.
• How to hold a date, and how long a hold lasts before you release it to someone else.
• Dietary needs. How far ahead you need to know, and what the kitchen can and cannot do.

Write your real numbers into that page, the ones your manager would quote on the phone. A page that says "contact us for details" sends the organizer back to the start, and they will keep asking the other places while they wait.

The page also gives search engines and AI assistants something specific to read when someone asks where a group can eat together in your area. That is a side benefit. The main one is that your own staff stop improvising answers at 10:40 pm.

The first reply, the same night

The first reply has two jobs: prove that a human business received the message, and move the organizer one step forward. It does not need to confirm anything. It can be automatic, as long as it sounds like you and does not pretend to know the answer yet.

Thanks for thinking of us for the birthday. Our group menus and deposit terms are on this page. Send me the date, the number of guests and any dietary needs, and I'll confirm availability tomorrow by noon.

Then someone has to actually confirm by noon. An automatic reply that promises a callback nobody makes is worse than no reply, because the organizer has now been let down twice.

One thing an automatic reply should never do is confirm availability or quote a custom price on its own. Those need a person who can see the book. Keep the automation on acknowledging, sending the page and collecting the details, and keep the yes with a manager.

Holding the date, and letting it go

Once you have the details, send a hold with an expiry: "I've penciled you in for twelve on the 14th until Friday. To confirm, reply here and I'll send the deposit link." A hold with an end date is clearer for both sides than an open maybe, and it stops a tentative booking from blocking a real one.

If the organizer goes quiet, send one reminder the day before the hold ends. After that, release the table and say so kindly. People who organize dinners are used to herding a group chat, and a clear message is a relief to them.

The organizer is the contact worth keeping

The person who booked a table for twelve is not an average guest. They are the one in their circle who organizes things, from birthdays to the end-of-year dinner for the office. After the event, thank them, and ask separately whether you may get in touch before the next occasion. Keep the answer, with the date and what they celebrated, somewhere that will still exist next year.

That record is what makes a well-timed note possible eleven months later: "Last year you brought twelve people in for a birthday. Our group menu for the season is up, and the 14th is a Saturday this year." It works only if the organizer said yes to hearing from you. Without that yes, leave them alone.

This is also where a CRM earns its place in a restaurant, and it is a modest job. The pricing page lists the FracMO CRM in every plan from $249 a month, and the restaurants page lists CRM for loyalty and email campaigns on the entry plan. Whatever you use, it needs the organizer's name, the occasion, the date, the size of the group and whether they agreed to be contacted.

What this will not fix

Some requests are shopping around with no intention of booking, and a fast, complete answer will not change that. A written groups page also takes away some room to negotiate on the phone, which a few managers will miss. If your room genuinely cannot take groups on the nights people ask for, the most useful thing the page can do is say so, so nobody waits two days for a no.

And none of it works if the Thursday person is still the only one who reads Instagram. The channel list and the saved reply exist so that the answer does not depend on who is on shift.

What I would do this week

1. List every place a group request can arrive, and put a name and a checking schedule next to each one.
2. Write the groups page with your real capacity, menu options, deposit terms and hold rules.
3. Save the first-reply message in every inbox, with a promised time for a human answer that someone will actually keep.
4. After the next group dinner, ask the organizer whether you may write before their next occasion, and record the answer.

If you would rather have help with the reply flow and the guest records, the NetWebMedia restaurant plans cover them, and the page offers a free 48-hour written audit that shows where your requests go unanswered before you change anything.

← Back to all articles