How to Structure the Enquiry Process on Your Private Chef Website

A visitor considering a private chef hesitates longest at the enquiry form. Not at the photos, not at the menu, but at the moment they have to fill something in and don't know what happens next. That moment is the enquiry process, and on most private chef websites it gets treated as an afterthought.

This article isn't about the general trust signals a visitor has already seen earlier on the site. For that, read what clients expect from a private chef website. Here we look specifically at the mechanics of the enquiry moment itself: which questions the form asks, how the response time is communicated, and what happens after it's submitted.

Which fields should an enquiry form include?

A private chef enquiry form needs different information than a standard contact form. Ask at minimum for date, number of guests, occasion, location and any dietary preferences. Without those fields, the conversation still has to start with basic questions that needlessly delay the enquiry.

Date and flexibility

Ask for a preferred date, but also whether it is fixed or still flexible. A chef often plans weeks ahead. Someone who states upfront that they are flexible makes it easier for the chef to find a suitable slot.

Number of guests and occasion

The number of guests determines logistics, menu structure and pricing. The occasion, a birthday, a business dinner or an intimate evening, helps the chef set a direction before the first conversation even begins. A form that doesn't ask about this leaves that context unused.

Dietary preferences and allergies

Dietary preferences deserve their own field, not a free text box at the bottom. Allergies, religious restrictions and preferences aren't a detail for a chef, they are a precondition. Asking early prevents a second round of emails later.

Budget direction rather than an exact price

An open question about budget direction, for example across three or four ranges, helps without the chef having to publish a full price list. It also avoids an awkward conversation where price only comes up late.

How do you set the right expectation about response time?

A response time that isn't mentioned feels like uncertainty to a visitor. State a concrete window, for example within 24 or 48 hours, right after the enquiry is sent. That one sentence prevents someone from wondering whether the message arrived.

Place this promise both above the form and on the confirmation page. Someone who has just sent an enquiry reads that confirmation with more attention than the text that came before it. Repetition at that moment works better than a single mention.

“

An enquiry form without a response time promise leaves the visitor guessing whether the chef is taking the message seriously. A short, concrete promise right after submission removes that uncertainty without extra effort.

What happens after an enquiry is submitted?

After submitting, an enquirer deserves a confirmation page that explains what comes next, not just a notice that the message was received. Describe the next step in two or three sentences: a proposal, a phone call to align, or a menu suggestion by email.

The confirmation page as a next step, not an endpoint

A plain "thank you for your message" closes the conversation at the wrong moment. Better is a brief explanation of what the chef will do now: reviewing the enquiry, drafting an initial proposal, or scheduling a short call.

Automatic email confirmation

An automatic email that repeats the submitted details gives the enquirer something to refer back to. It confirms the enquiry arrived correctly and what information the chef already has, without needing a personal reply for that.

How do you avoid the enquiry feeling like a generic contact form?

A form that only asks for name, email and message treats a private chef enquiry like any other quote request. Adjust the fields, language and order to match the kind of decision being made here: an evening, a party, an occasion.

Language that fits the occasion

Replace generic labels like "message" with specific questions: "What occasion are you planning this evening for?" or "Do you have specific wishes for the menu?" That small adjustment shows the form was designed for this type of enquiry, not reused from another template.

An order that feels logical

Start with date and party, end with budget and any remarks. That order follows how someone naturally thinks about the evening and prevents the form from feeling like a checklist with no coherence.

“

An enquiry form that speaks the language of the occasion rather than generic field labels gives a visitor the feeling the chef is already thinking along before the first conversation has even happened.

Frequently asked questions about the enquiry process

Question: Should I show a fixed price indication in the enquiry form on my private chef website?

Answer: No, an exact price isn't necessary. A choice between a few budget ranges gives enough direction without publishing a full price list.

Question: How long can an enquiry form be before it puts people off?

Answer: Limit it to the fields you genuinely need: date, guests, occasion, dietary preferences and budget direction. More than six to eight fields often becomes discouraging.

Question: Is a phone number required in the form?

Answer: Not required, but worth including as an optional field. Some enquirers prefer to call after an initial email contact, especially for occasions that need to be arranged quickly.

Question: What should the confirmation page say after the enquiry is sent?

Answer: Briefly describe the next step and the response window, for example "You will receive a proposal by email within 48 hours." That removes uncertainty during the wait.

In closing: the enquiry process as part of the experience

The enquiry form is the first moment a visitor genuinely connects with the chef, even before the first conversation. A form that asks the right questions, states a response window and describes a clear next step makes that transition smaller.

Want to know first which broader signals already convince visitors before they reach the form? Then read what clients expect from a private chef website for that context.