How does Voksha handle a large party reservation request, like a table of 12?

Large party requests are exactly the kind of call that needs judgment, not just a booking script, so Voksha is set up to follow your restaurant's actual large-party policy rather than treating a 12-top the same as a table for two. During setup, you tell Voksha your thresholds: maybe parties over 8 need a deposit, parties over 10 require manager approval or can only be seated in a private room, or large parties aren't available Friday and Saturday nights during peak hours at all.

When a caller asks for a table of 12, Voksha applies those rules, it can quote the deposit policy, explain private room availability and any room minimum, and either book it directly if it fits your standard policy or capture the details and flag it for a manager callback if it needs a judgment call, splitting into two tables, a custom prix fixe menu, AV needs for a business dinner. This is similar to how Voksha handles the $500-2,000 catering leads restaurants get: recognize the high-value, non-standard request and route it to a person rather than trying to force it into a simple booking flow.

For restaurants, this matters because large parties are disproportionately valuable, a 12-top is often $600-900 in revenue in one seating, and disproportionately likely to be mishandled by a rushed host trying to also manage the walk-in line, which is exactly the scenario Voksha is meant to catch instead of letting it go to voicemail or getting rushed through incorrectly.