Private Events setup

Configure Private Event types

Create clear Private Event type options so guests can classify buyouts, private dining, large parties, tastings, and custom requests.

Updated 2026-06-22

Private Event types are the choices guests see on the inquiry form. They help staff understand the shape of the request before reading the notes.

Keep the list practical. Guests should be able to choose quickly, and staff should be able to route the request without guessing.

Start With Common Requests

Start with the requests the venue already receives.

Restaurants often use:

  • Private Dining
  • Full Buyout
  • Large Party
  • Corporate Event
  • Rehearsal Dinner
  • Birthday or Celebration

Wineries and tasting rooms often use:

  • Private Tasting
  • Large Group Tasting
  • Vineyard Tour
  • Club Event
  • Corporate Event
  • Full Buyout
  • Wedding Weekend Event

Avoid creating a type for every small variation. The guest notes field can capture details.

Use Guest-Facing Names

Use names guests understand.

Good names:

  • Private Dining
  • Full Buyout
  • Corporate Event
  • Large Group Tasting
  • Wedding Weekend Event
  • Custom Tasting

Avoid internal labels:

  • PE Type 1
  • Events Team
  • Manager Review
  • High Rev
  • Manual Quote

The type appears in the request, staff inbox, and notification email. Make it readable.

Keep The List Short

Most venues should start with three to six types.

Too few types can make every request feel vague. Too many types slow guests down and create duplicate categories.

If two types are handled the same way by staff, combine them.

For example, Birthday, Anniversary, and Celebration can often be one type: Celebration.

Disable Types You Are Not Ready To Sell

Only enable types the venue is prepared to discuss.

If the kitchen cannot support full buyouts yet, leave Full Buyout disabled. If vineyard tours are seasonal, disable the type outside the season or make the description clear in the website copy around the form.

The inquiry form should set expectations the team can meet.

Match Types To Staff Workflow

A good type helps staff answer:

  • Who should follow up?
  • How quickly should they respond?
  • What information is missing?
  • Does this need a quote?
  • Is this likely to become a reservation, contract, or manual booking?

If a type does not help staff act, it may not need to exist.

Review And Adjust

After a few weeks, review the requests:

  • Are guests choosing the right type?
  • Are too many requests marked Other or described only in notes?
  • Are staff changing how they triage certain types?
  • Are some types never used?

Use real request history to simplify the list.

For examples, see Recommended Private Event types for restaurants and wineries.