For restaurants that want more event revenue.

Common questions

• We already run OpenTable, SevenRooms or Resy for everyday tables. Do we have to switch?
  No. Openevent is built as the events layer next to your reservation system, not a replacement. Your à-la-carte covers, walk-ins and waitlist stay where they are; Openevent handles the private-dining-room calendar, set menus, deposits and run sheets in a separate view so your floor team and your events workflow don't collide.
• How do we stop double-booking the private dining room when reservations live in OpenTable and events live here?
  Openevent treats the private room as its own bookable resource with its own calendar, so an events booking blocks the room and your team mirrors it back into your reservation tool as a hold. We're transparent that this is a manual cross-check today rather than a live two-way sync, many teams already do exactly this with Tripleseat, and it works once the room ownership is clear.
• Can we take a deposit at booking and the balance closer to the event?
  Yes. Set menus support a deposit (fixed amount or percentage) at booking and an automatic balance reminder before the event, both via Stripe. Stripe fees are passed through at cost, and Openevent's own fee is 1%* on processed payments. No card-on-file workarounds, no separate payment terminal.
• Dietary requirements come in scattered, email, WhatsApp, the booking form. How does this actually get to the chef on service day?
  Custom checkout questions capture allergens and dietary needs guest-by-guest at booking, and they print onto the event sheet the kitchen sees on the day. It is not a full allergen-tagged menu database, it's structured intake plus a clear run sheet, which is what most private-dining teams actually need.
• Our chef changes the set menu every season. Do we have to rebuild templates every time?
  Set menus are saved as templates with versions, duplicate the autumn menu, tweak the courses, set it live for the next quarter. Past events keep the version they were booked on, so a December booking still shows the December menu after you've moved on.
• We get a lot of inquiries overnight. Things slip. What does the AI inbox actually do?
  The AI inbox reads incoming booking emails, drafts a reply using your set menus, availability and policy, and waits for you to approve before sending. It doesn't auto-confirm bookings on its own, final say stays with your events manager. The point is response time: replies within an hour convert dramatically better than replies hours later.
• We're a group with multiple locations. Can we see private-event revenue per room, per venue and per host in one place?
  Yes, every event rolls up to a group-level dashboard with revenue by venue, by private room and by repeat host. The CRM flags returning groups across all locations, so if a corporate client booked your Zürich venue last quarter, the Geneva team sees it the moment they enquire.
• Can guests book and pay online themselves, or do we handle every enquiry?
  Both. You can send a set-menu offer the guest confirms and pays online in a couple of clicks, or keep it fully manual and handle each enquiry yourself, whichever suits the booking. Either way the deposit, confirmation and run sheet are created automatically.
• Can we send a branded offer and contract for a private event?
  Yes. Send a branded offer with your menus, pricing and terms that the host can sign digitally, and the signed confirmation is stored automatically against the event. It looks like your restaurant, not a generic PDF.
• What happens to our guest data if we leave? And what does this actually cost?
  Your data is yours, full CSV export of every booking, contact and document at any time, no exit fee. Pricing is free to register and use for most features; we take 1%* on payments processed through Openevent, and Stripe fees are separate. No per-location licence, no setup fee, no annual lock-in.