Turn private dining inquiries into a proposal the manager approves

IntermediateA design, not yet run for a business

For:RestaurantsBars and breweries

Post this as a projectFree to post. We call you within 2 working days to scope it with you.

The job

Inquiries for the private room, a rehearsal dinner or an office party arrive through the website form, the phone and the general inbox. Each needs the same details: date, guest count, budget, time, food and drink preferences. The manager answers between services, often days later, and by then the planner has booked elsewhere. The owner's question: "How many event inquiries did we lose because we answered too slowly?"

Trigger and outcome

Trigger: a new inquiry by form or email. Outcome: within the hour, a draft reply for the manager that answers what it can from the room and menu sheet, asks only for the missing details, and holds the date as tentative on the events calendar. Once details are in, a draft proposal from the set menus with a minimum spend, deposit and cancellation terms copied from the owner's template.

Tools

  • OpenClaw watches the form and the events inbox and checks the events calendar.
  • Hermes holds the private dining sheet: rooms, capacities, set menus, minimums by day, the deposit and cancellation wording the owner approved.
  • Jev decides which set menus fit the guest count and budget and drafts the proposal.

Steps

A new private dining inquiry arrives, the agent checks the calendar and the room sheet, drafts a reply asking only for missing details, builds a proposal from set menus, the manager edits and sends it, and the date is held for the planner

Fast drafts from the owner's own sheet; the manager sends every one.

  1. Write the sheet. The manager writes the room sheet: capacities, set menus, minimum spend by day, deposit and cancellation terms. The owner approves the wording.
  2. Read the inquiry. The agent pulls out date, time, count, occasion, budget and dietary needs, and marks what is missing.
  3. Check the date. It checks the events calendar. If the room is free it pencils a tentative hold that expires on a date the manager set.
  4. Draft the reply. It answers from the sheet and asks only for missing details. The manager edits and sends.
  5. Draft the proposal. With details complete, Jev picks two set menus that fit, fills the owner's template and lists any special requests for the chef.
  6. Manager sends. The manager checks prices and terms, then sends from their own account. Signed proposals move to the events calendar as confirmed.

Human checks

  • Every reply and proposal is sent by the manager; prices, minimums and terms come only from the approved sheet.
  • Dietary and allergy requests are confirmed with the chef before the menu is final.
  • Deposits are taken through the restaurant's payment link; the agent never handles card numbers.
  • Discounts or changes to terms are the owner's decision.

Data needed

The room and menu sheet, the proposal template and the events calendar. For practice, write synthetic inquiries: a complete one, a vague one ("party for about 30 in spring"), and one for a date already booked.

Variations

  • Bars and taprooms: the same with buyouts and drink packages.
  • Follow-up: a gentle check-in draft if a proposal sits unsigned past a date the manager sets.
  • Reporting: a monthly count of inquiries, proposals and bookings.

Where to find more

Further reading, not the source of this design:

Sources

Further reading

More workflow libraries elsewhere

Further reading, not part of our programme: other people's takes on the same jobs.

  • n8n workflow templates ↗

    Community-built automation flows, filterable by sales, marketing, support, document work and AI.

    Read a template for the order of its steps and the apps it touches, then design the approval points yourself.

  • Make templates ↗

    Ready-made scenarios grouped by business area, including invoicing, inventory, HR and email marketing.

    Useful for seeing which systems a small business already connects, before you pick what your agent reads.

  • Zapier templates ↗

    Short trigger-and-action recipes for lead management, support tickets, forms and campaigns.

    Most recipes are one trigger and one action; notice where an agent would add a judgement step and a human check.

  • Claude Cookbooks ↗

    Code notebooks for classification, summarising, extracting data from forms and PDFs, and tool use.

    Open it when a step needs code, such as pulling fields out of a receipt; the ideas carry over to other models.

  • Building effective agents cookbook ↗

    Minimal examples of chaining, routing, parallel calls, orchestrator and workers, and evaluator loops.

    Read it to name the shape of your workflow before you build it; the patterns matter more than the code.

  • Hermes Agent Skills Hub ↗

    Searching skills other people have written for Hermes Agent, from built-in to community sources.

    Read a community skill before you install it, and never give one access to an owner's accounts without review.

  • ClawHub ↗

    The public registry of OpenClaw skills and plugins, including email, calendar, sheets and chat connectors.

    Check who published a skill and what it can touch; treat it as a starting point you read, not a black box.

  • Agent Skills ↗

    The open format for packaging a workflow as a SKILL.md folder that many agents can load.

    Use it when you want to hand a workflow over as a skill file the owner's agent can reuse.