Group Booking & Event Software for Restaurants
A party of thirty is not a reservation with a bigger number in it. It's a negotiation that runs for weeks, holds half your floor, and is worth more than the rest of the night combined.
Why it matters
Most venues run their biggest bookings in the least reliable place they own: a WhatsApp thread, a notebook by the phone, and one manager's memory of what was promised. The enquiry that never got answered is invisible. The tables held for a party that quietly went elsewhere stay held until somebody notices. And nobody can say afterwards which of these actually made money.
Here a large booking is a pipeline with a paper trail, holding real tables on the same floor plan the host is working, priced from set menus that know what their own ingredients cost.
Enquiry to service, on one board
Every enquiry lands somewhere
From the public form, the phone, a walk-in, social, or a birthday campaign — all onto the same board, tagged with where it came from and what kind of occasion it is: birthday, corporate, wedding, tour, private dinner.
Ten guests and up
Below ten it belongs in normal reservations, and it goes there. This board is for the bookings that need a conversation.
Hold the tables, with an expiry
Pick the actual tables and hold them for a set number of days. The hold releases itself if the booking is lost or cancelled — the tables that quietly stayed blocked for a party that never came are the whole reason this exists.
Nothing double-books
Group holds, ordinary reservations and event floors all check each other. Confirming re-checks the floor before it makes the hold permanent, because five days is long enough for something else to have taken the table.
Send one to three options
A proposal carries up to three package choices with a deposit percentage. The guest opens their own page and picks one.
A guest list that fills itself in
The host shares one link and their guests RSVP against it — going, maybe, or no — so the final count comes from the party rather than from one person's estimate.
Everything that happened is written down
Every status change, proposal and reply on one timeline, so the manager who wasn't there can still answer what was agreed.
Set menus that know their own margin
Build a package as courses — starters, mains, desserts, drinks — where each option points at a real dish from your menu, with an upcharge if it's a step up. Either the party chooses a set number per course, or every option is served.
Price it as food per head, drinks per head and a one-off service fee, with a minimum party size. The quote is then arithmetic rather than a guess.
The part that's harder to find elsewhere: because every option is a real dish with a real recipe, the composer shows you the actual ingredient cost and the margin as you build — costed at worst case, so a choice course is priced on the guests picking the most expensive things. Quoting a party menu at a number that turns out to lose money is a specific and common way to have a busy, unprofitable December.
Events are a different thing, and work differently
A group booking is somebody asking you for a table. An event is you announcing an evening and inviting people to it — a tasting, a supper club, a live set. Same venue, opposite direction, so it's a separate tool rather than a bigger booking.
Two ways to use the room
Either guests are seated at tables — you pick which tables, capacity is the sum of their seats, and everyone who says yes gets a real reservation that shows up on the floor plan — or the room is rearranged and you set the headcount yourself. Both block the floor; only one hands out tables.
A waitlist that behaves
When the room fills, further replies join a waitlist. If two seats free up, a pair further down gets them rather than the whole queue stalling behind a party of four — and the positions re-compact afterwards.
Party size has a ceiling
Someone trying to book more seats than an event allows is sent to the group-booking form instead, which is where a party that size actually belongs.
A door list, not a guest list
Staff check people in as they arrive. Who said yes and who turned up are stored as different facts — and the second one is what a later campaign can target.
Who gets invited, and what stops you
Invitations go by email to guests who are verified at your venue and have opted in — not to an imported list, and not to an address typed in by hand. The audience screen shows each candidate's segment, visit count, lifetime spend and last visit, and tells you plainly why anyone is unreachable: no consent, no email address, already invited, or recently mailed.
The same platform-wide cap applies as everywhere else in guest marketing — two emails per guest per rolling thirty days, counted across every venue and every campaign type together. Your own staff are excluded from every audience.
Afterwards you get the honest version of how it went: invited, opened, going, declined, waitlisted, no reply, and the conversion rate — plus every message that was sent, skipped or failed, with the reason.
Common questions
Do you take the deposit?
No. A proposal records the deposit percentage and amount and the guest accepts it, but no money moves — there is no payment processor connected today. You collect it however you collect it now; the system records that it was agreed.
Does the platform email the proposal to the guest?
Not yet. Proposal and guest-list links are real pages, but a staff member copies the link and sends it themselves. Event invitations, by contrast, are sent by the platform.
Can guests browse my upcoming events?
No. There's no public events listing or "what's on" page inside the product. A guest reaches an event through a link — either one you emailed them, or the public link you posted yourself. That link is unguessable, which is deliberate, but it does mean events don't get discovered by accident.
Do you sell tickets?
No. An event can show a price per person, but nothing is charged and nothing is refunded. Taking money would turn a cancellation from an email into a refund, and that was a deliberate decision rather than an omission.
Can I set up a recurring event?
No — each event is created individually. Recurring events were considered and decided against rather than deferred.
What happens to orders placed at a group booking?
Orders on the held tables are tagged to the booking automatically while it's in service, so the party's spend can be seen together afterwards.
Is there reporting across all my events?
Not yet. Each event has its own invitation stats and message log; there's no cross-event or cross-booking dashboard comparing them over a year.