The CRM for private dining venues
Private dining & banquet software.
Every party, inquiry to BEO.
Private event and group inquiries land mid-service and get handled between rushes. Centralize them, send a proposal built from your real menu and collect the deposit, without asking the floor team to handle inquiries during service.

Centralized inquiries
Website, email, phone, concierge partners: every group inquiry enters a single queue, qualified on arrival (date, covers, budget). Nothing sits forgotten in the floor manager's inbox.
Menu proposals in minutes
Set menus, drink packages, room rental fees, food and beverage minimums: the proposal is built from your menu, with sales tax and service charges calculated, and goes out by email for e-signature.
Groups that come back
Preferences, allergies, spend history: every organizer is recognized from their second inquiry. The win-back follow-up is prepared at the right date, without anyone having to note it down.
The essentials: private dining and groups in restaurants
Private dining software helps a restaurant sell its private dining rooms, buyouts and group tables; it does not seat tonight's covers. Joinways is venue management software that restaurants use for that side of the business: inquiries arriving by email, website form or platform are read on arrival and their details extracted, a proposal is prepared from your menu with the deposit tracked, each private dining room has its own calendar with holds and confirmations, and every organizer's history is kept for the next booking. The floor team handles inquiries between services. Private dining rooms are set up as spaces, all included in the venue's price. Pricing is public: $69 to $199 per venue per month billed annually depending on venue size ($86 to $249 monthly), users unlimited. The 30-day trial needs no credit card.
- Every inquiry in one place: website form, email, Instagram, phone calls
- Menu proposals built from your real menu and your real prices, ready to send between services
- Online deposits and balance tracking, with no follow-up written by hand
- Allergies, dietary needs and house notes carried onto the BEO sent to the kitchen
- A calendar for your private dining rooms and buyouts, with holds kept for a few days
- A CRM that keeps the history of each group so they come back
What Joinways structures for your groups
Private dining inquiries centralized, qualified and prioritized on arrival.
Menu proposals, deposits and service run sheets gathered on the same booking.
A clear view of live bookings and the organizers to follow up.
The private dining and group business challenges for restaurants and rooftops
A private dining booking is won between two services: wait too long to reply and many organizers have already moved on.

Inquiries that land mid-service
Between the website form, the contact inbox and the phone during service, everyone takes their own notes and the reply goes out two days later. Joinways gathers it all into a single queue you can work through in a quiet moment.
Endless back-and-forth on menus
Three menu options across successive emails, and nobody is sure which one still stands. One proposal (menus, add-ons, terms) settles it. The client chooses from a single document, and the signed version is the only one that counts.
Deposits tracked from memory
An uncollected deposit is a room blocked on a Saturday for a group that can still cancel. Joinways tracks the status of every booking and prepares the follow-ups on outstanding amounts.
Regulars treated like strangers
The assistant who books every quarter for the same leadership team starts from zero with every email. With account history, you recognize the organizer, their constraints and their budget the moment the inquiry arrives.
What the team uses between services
Group inquiries, menu proposals, deposits and repeat business brought together in one system.
A qualified inquiry queue
Every detail is extracted from each inquiry on arrival. You see at a glance what to handle first before evening service.
Proposals built from your menu
Your menus and add-ons in a catalog, per-person pricing, sales tax and service charges handled, discounts kept within rules: the proposal is prepared from your catalog instead of being rebuilt by hand.
Private dining rooms and full buyouts
Private dining room, wine cellar, patio or the whole restaurant: capacities, food and beverage minimums and availability per space, with booking conflict detection.
Organizer & guest CRM
Allergies, preferences, past events and spend stay in the organizer's history, shared between floor and kitchen, then reused at the next inquiry.
Deposits and payments tracked
Deposit invoices issued via Stripe, payment status tracked on the booking, and prepared follow-ups on outstanding balances. The room only gets blocked for committed bookings.
Post-event follow-up
Thank-you note, feedback request, follow-up at the right date: so the private dinner leads to the next booking.
The private dining process, from first email to repeat booking
Capture, propose, collect and bring back: the path of a profitable private booking.
Capture and qualify
Every inquiry lands in the queue with every detail already extracted. Between services, the team handles the higher-value bookings first. The acknowledgment is prepared on arrival, and the queue shows the next reply to send.
Propose and secure
The menu proposal is built from your menu, goes out by email with read tracking and e-signature, and the deposit confirms the date. The back-and-forth happens on one document, not across a long email thread.
Serve and bring back
The run sheet and service notes reach the kitchen without retyping. After the event, the thank-you and follow-up are prepared for the right date. When the next inquiry arrives, the organizer's history is already there.
Use cases for restaurants and rooftops
From the team dinner to the full buyout, one way to sell and to serve.
Recurring corporate dinners
The same leadership team returns every quarter: the proposal is reactivated in minutes from the history, at the right price and with known preferences.
Rehearsal dinners and private celebrations
Rehearsal dinners, birthdays, engagements, family dinners: dietary needs, the cake and service timing are written into the booking and picked up by the kitchen.
Wine pairing dinners
Guest list, restrictions, course-by-course run sheet: each edition builds on the last, and its attendee list feeds the next invitations.
Full buyouts
Capacity, food and beverage minimum, a larger deposit, hour-by-hour run sheet: every detail of a high-value booking is settled before the night.
What makes private dining profitable: minimum spend, deposit, cutoff
The minimum spend, the deposit and the cutoff decide whether a private event stays profitable. Set those rules before the inquiry arrives and write them into the proposal.
Set the minimum spend per room and per night, and let it answer for you: a Saturday buyout has a different price than a Tuesday in the private dining room, and the proposal should say so without a negotiation.
No deposit, no booking: the date is blocked when the deposit lands. A signed proposal with a payment link makes that rule painless for everyone.
Close the booking for the kitchen on time: final guest count, menu choices and allergies confirmed at a fixed cutoff and handed over as a BEO, not as a verbal brief at the pass.
Group-business numbers a manager should know by heart
- Proposal turnaround: out before the next service starts
- Share of confirmed private bookings with the deposit collected before the date
- Group revenue per private-event seat versus the service it replaces
Saturday night's price is set before the inquiry arrives
An owner who makes groups profitable almost never negotiates: the minimum spend per room and per night is already in the proposal, and the deposit link goes out with it. Friday's phone call only confirms terms that are already written. The kitchen works the same way: the final guest count lands on a known date, and the team preps a banquet it was expecting.
A bistro with a private dining room that fills its slow weeks
Starting point
A Chicago bistro with a 30-seat private dining room takes group requests by phone mid-service and by email read late at night. Proposals go out two or three days later, deposits are requested inconsistently, and the room sits empty through the slow season.
What they put in place
Inquiries centralized and qualified on arrival, menu proposals built from the catalog with a minimum spend by night of the week, a deposit link attached to every signed proposal, and a BEO for the kitchen generated from the booking.
What the scenario illustrates
Proposals go out before the evening service. A deposit is requested on every proposal, so the private dining room is only held for committed bookings. The floor team no longer handles group emails mid-rush.
Owner-manager
Illustrative scenario: Chicago bistro with a private dining room
Illustrative scenario based on typical venue outcomes, not an actual named customer.