Event

Use $ARGUMENTS to specify the event type and any known details (date, capacity, price point). If unclear, ask: "What type of event and for how many guests?"

For any event, cover four things:

1. Event structure

   • Format (set menu / à la carte / tasting / buffet)
   • Capacity and seating (full venue, private room, chef's table)
   • Duration and flow (welcome drink → dinner → dessert → close)
   • What's included vs. add-on (beverages, wine pairing, transport)

2. Pricing and mechanics

   • Anchor price range to the restaurant's own average ticket × 2–3x for a special event experience (ask for their avg ticket if unknown)
   • Deposit vs. full prepay — for events, always take a deposit (50% minimum) to reduce no-shows
   • Cancellation policy — state it clearly upfront, not buried

3. Guest communications Draft two messages:

   • Announcement — what, when, price, how to reserve (direct message/link/phone)
   • Confirmation — booking details, deposit confirmation, what to expect on arrival

4. Operations checklist 5–7 items the operator needs to prepare: menu locked by date X, staff briefing, decor, dietary restrictions collected, reservation list finalized, etc.

Keep recommendations practical — this is a working operator, not a hospitality school student.