When group booking differs
Large parties change turn time, kitchen load, and staffing. Standard slot rules are not enough, set higher minimum party and manual approval.
Corporate dinners or birthdays may require fixed menu and mandatory deposit.
Rules and approval settings
In booking rules, route parties of 8+ to approval queue. Extend turn time by size. 120 minutes for 10 guests is common.
Deposits may be full amount, not symbolic; require confirmation 7 days before event.
How do merged tables work for group bookings?
Define mergeable tables per the floor map article; the system suggests merges for group bookings. A merged block locks as one booking. Hosts can change the suggestion on approve but should watch capacity warnings.
Release the merge on the map after service. Label group tables separately to speed host guidance.
Guest communication and CRM
Store group contact in profile notes. Confirmations and deposit messages go to that person.
Corporate or Event tags in CRM power filters and reporting.
Special days and cancel policy
Group cancel cutoff should be earlier than singles. 48 or 72 hours. Deposit rules in faq-cancellations apply.
For fixed-menu events add closure days in special-hours calendar, kitchen prep differs.