A private chef dinner inquiry may depend on guest count, menu, service style, venue, kitchen, dietary needs, timing, equipment, travel, staffing, budget, and cleanup. A date and guest count are not enough to build a useful proposal.
Keep food, allergen, service, and availability claims current and reviewed by the chef. Explain when a menu or venue review is required.
Separate dinner formats
Explain plated, family-style, tasting, cooking class, drop-off, retreat, corporate, wedding, in-home, venue, and special event paths where supported.
Use real event proof with permission and identify guest count, menu, venue, service, and setup context.
Ask for event and kitchen context
Collect date, guest count, event type, venue, kitchen, service style, menu interest, dietary or allergen needs, equipment, staffing, travel, timing, budget context, and contact.
Let the customer request menu consultation, availability, quote, venue review, or a site conversation. An inquiry should not imply a date or menu is confirmed.
Make proposal states clear
Use inquiry, menu review, venue review, proposal, revision, deposit, confirmed, schedule change, completed, and closeout statuses.
The food truck catering inquiry guide covers guest count, menu, location, access, service window, permits, deposits, and weather in another event-food workflow.
Measure inquiry quality
Track complete event context, menu questions, response time, quote changes, venue issues, booking conversion, cancellations, referrals, and pages customers view before contacting the chef.
Need a private chef website that helps clients describe the dinner before a proposal? Ask Vertinus to map menus, venues, guest details, and booking handoffs.