Large party calls are widely treated as manager work. They are not, mostly. The manager is required for maybe one question in five, and treating the whole call as escalation means the caller waits on hold at 7pm, gets a voicemail, and books the place that picked up.
What a group inquiry actually needs is five questions asked in a fixed order by whoever answered the phone, and a clear line past which the call stops and becomes someone else's. That is a training document, not a staffing problem.
The five questions, in this order
Headcount first, because it determines everything after it. Get a number, not a range. "Fifteen to twenty" is a party you cannot seat, and the difference between those two figures is often a different section of your room.
Date and time second. Check it against the book before continuing, because there is no point qualifying a party you cannot host.
Occasion third. This sounds like small talk and is the highest-value question on the list. A birthday dinner, a rehearsal dinner, a wake, and a corporate team offsite have completely different spend, duration, and tolerance for a shared table. It also tells you whether they will want a cake brought out, which is the thing that gets forgotten and generates the complaint.
Set menu fourth. For parties past a certain size you should be requiring one, and asking early avoids the conversation where someone discovers at booking confirmation that they cannot order à la carte.
Payment last. One check or split, and whether a deposit applies. Say the deposit number out loud on this call. A deposit that surfaces in a follow-up email reads as a fee that appeared later, and those cancel at a noticeably higher rate than ones stated in the first ninety seconds.
Find your own threshold before writing any rule
"Large party" has no universal definition and borrowing one from another restaurant will produce rules that do not fit your floor.
Your threshold is the headcount at which normal seating stops working: where you have to combine tables, where a section stops turning, where the kitchen has to fire a block of covers together. In a forty-seat room that might be eight. In a room with a private back area it might be eighteen, with a second threshold at whatever fills that space.
Walk your floor plan and write the number down. Everything downstream, from who can confirm to when a deposit applies, is defined relative to it.
Give the host stand real authority
The common failure is a policy that says every group over eight needs a manager. In practice this means the call arrives during a seating rush, the manager is in the walk-in, the host takes a name and number, and someone calls back four hours later. By then the party has booked.
Set a size below which whoever answers can confirm outright, using the standard terms. Set a second size above which they collect all five answers and promise a callback within a stated window, then actually make that call. Anything genuinely unusual, a buyout, a room closure, a custom menu, goes to a manager, and that should be a small fraction of the volume.
The point is that the caller should never hear "I'm not able to help with that." They should hear either a confirmation or a specific next step with a time attached.
Where large parties stop being reservations
Somewhere above your second threshold, a group booking becomes an event, and events have a different sales process. Someone asking about forty people on a Saturday with a set menu and a private space is not making a reservation, they are buying something, and handing that conversation to a host who is also seating a four-top will lose it.
The tell is usually the combination of a private space request and a set menu. When both appear, take the details and route the call to whoever handles events, the same way you would route a catering inquiry. The qualification logic is close to identical, and it is worth reading catering lead qualification alongside this, since the questions overlap almost completely.
The details that actually cause problems later
Three things get skipped on the call and cause the complaint on the night.
Arrival timing for a large group is rarely what was booked. Ask whether everyone arrives together, and tell them plainly what happens if they do not. Most rooms will not seat a partial party at a combined table during peak, and that policy has to be said on the phone rather than discovered at the door by someone who brought their in-laws.
Duration matters and nobody mentions it. If your Saturday depends on turning that section, the party needs to know they have the table until a specific time. Stated upfront it is a normal condition. Mentioned at dessert it is being rushed out.
Outside items, a cake, decorations, a slideshow, a toast. Ask. These are all fine, generally, and all annoying when they arrive unannounced during service.
What automation does here, and what it should hand off
An automated phone system is genuinely good at the qualification half of this. It asks all five questions in order, every time, without shortcuts, and it does it at 7:20 when the host stand is three deep. It writes the answers into a structured record rather than onto a napkin. For a restaurant losing group inquiries to voicemail, that alone is most of the value.
Where it should stop is the floor judgment. Whether a party of twenty-two fits Saturday at 7:30 given what is already on the book is a decision made by someone looking at the room, and a system that confirms that booking on its own will eventually confirm one you cannot honor. The right configuration collects everything and hands off, which is a policy decision covered in human handoff and failover.
Whether the agent should touch your reservation platform at all depends on how your table management works. That distinction is worth understanding before you buy anything, and it is laid out in reservations versus ordering and in more depth in table management integration.
Test it on your own line this week
Call your own restaurant at 7pm on a Friday and ask about a party of sixteen for the following Saturday.
Time how long before a person picks up. Count how many of the five questions you get asked. Note whether anyone mentions a deposit, a set menu, or a table duration, and whether you leave the call with a confirmation or a promise. Then find out whether that promise was kept.
Most operators who run this test find the call went to voicemail. That is a revenue answer, not a service one, and it is worth knowing what a party of sixteen would have spent. The holiday version of this problem is worse and more concentrated, as Valentine's and Mother's Day reservation calls tend to show.