Seat parties, not just slots

Released 14 October 2026

Seat parties, not just slots: set how many covers a room or coach holds, and WA.cr counts every party against it.

What's new

• Covers on a room. On the Staff step of the appointments setup, give a dining room, terrace or site-visit coach a number under Covers (seats at once). It then takes bookings side by side until the guests add up to that number. Leave it blank and the row works exactly as before, one booking at a time.
• Guests choose their party size. When a service books into a room with covers, or has a largest party, your booking page and form ask Guests first and show only the times that party fits.
• A largest party per service. Set Largest party on a service, such as "Table" up to 6. A bigger group is pointed to a service that seats them, such as a "Large party" service you approve by hand.
• How full each room is. The diary shows "Party of 4" on bookings and "54 / 60 covers" for each room at its busiest that day.
• Overbook on purpose, with a record. At the counter, Show full times lets you squeeze a party in after ticking that you know the room will be over. Every overbooking is written to your audit log.

Worth knowing

• Requests hold their covers while they wait. A large-party request keeps its covers until your approval window runs out. Approving it later re-counts the room and tells you if it no longer fits.
• Buffers still count. A time is only offered if the room keeps enough free covers across the whole booking, turnaround included.
• A table is never double-booked. Overbooking only applies to rooms with covers.
• Auto Flows can book parties too. Set Party size on the Offer times and Take the booking steps, for example to {{var.party_size}}. A WhatsApp Flow form still books one guest.