The Catering Inquiry Workflow: Stop Chasing Incomplete Requests

Carlos and his partner Priya run a small restaurant that handles private events and off-site catering. They've been building the catering side for two years. It now accounts for roughly a third of revenue, and the enquiries are regular enough to feel like a real pipeline — five or six a month, sometimes more in the run-up to Christmas and summer party season.

That pipeline is the good problem. The bad problem arrived with it.

Almost every catering enquiry that comes in is incomplete. "Hi, do you do catering? We're thinking of having an event." That's it. No date, no headcount, no location, no idea whether they want drop-off or full service, no indication of budget. Carlos replies asking for details. Sometimes he hears back the same day. More often it takes a day or two, and he has to send a second message before he gets an answer. And sometimes — more often than he'd like — the enquiry just goes quiet after the first follow-up and never becomes anything at all.

Here's the thing: the drop-off isn't always because the potential client went elsewhere. Sometimes they got busy and forgot to reply. Sometimes the back-and-forth felt like effort and they put it off. An incomplete enquiry isn't just a chore to chase — it's a lead with a much higher chance of going cold.

An Incomplete Enquiry Is Not a Lead

Think of it this way. An enquiry that arrives without the basic information needed to quote isn't yet a lead. It's the opening move in a process that only becomes a lead once Carlos has a date, a headcount, a service type, and some indication of budget. Until he has those four things, he can't do anything except ask for them.

Multiply five incomplete enquiries a month by the three to five messages it takes to extract the necessary information. That's somewhere between fifteen and twenty-five messages per month of pure overhead — before Carlos has written a single quote. Add the two or three enquiries that go quiet mid-thread every month, and that overhead is being spent on conversations that produce no revenue at all.

The structural problem? An open-ended channel — an email address, an Instagram DM, a Google Business Profile message — invites open-ended messages. When someone sees "contact us for catering enquiries," they contact you. With whatever information is top of mind at that moment. Which is usually just the opening question.

A structured intake changes what arrives.

What to Collect in a Catering Intake

A catering enquiry workflow doesn't need to be long. It needs to collect exactly what Carlos needs to reply with a quote — or ask one specific clarifying question — and nothing more. Seven things. That's all.

Event date. Or, if the date isn't fixed yet, an approximate timeframe ("mid-July," "Q4"). Without a date, Carlos can't check availability and the enquiry can't progress.

Headcount. An approximate number works fine. "Around 40 guests" is enough to rough out a quote. Without it, the quote can't exist.

Event type. Corporate lunch, birthday dinner, wedding reception, informal gathering? The nature of the event shapes every other element of the quote.

Service type. Drop-off and set-up only, buffet service with waiting staff, or full service including set-up, service, and clear-down? This is one of the highest-impact variables in a catering quote and it's almost never included in an open-ended enquiry.

Dietary requirements or restrictions. Even a broad indication — "several vegetarians, one nut allergy" — changes what Carlos needs to price in.

Rough budget range. This is the one most restaurant owners feel awkward asking directly. But it's the one that saves the most time. A client with a £500 budget for 40 guests needs a completely different proposal than a client with a £3,000 budget for the same headcount. Knowing this upfront prevents the situation where Carlos spends an hour building a proposal the client immediately says is too expensive.

Best contact email. So the quote goes somewhere it'll be read and can be found again.

Seven questions. The whole workflow takes two to three minutes to complete.

The Economics of a Complete First Enquiry

When an enquiry arrives with all seven pieces of information, Carlos can reply with a quote — or a near-quote pending one small clarifying point — within minutes of reading it. Response time goes from "two days plus three messages" to "same afternoon, one reply."

That speed difference has a real effect on conversion. An enquiry that gets a substantive, quote-ready response the same day feels like dealing with a professional operation. An enquiry that gets "Thanks for reaching out, could you tell me the date and how many guests?" — and then waits — feels like the start of a laborious process. That's often when the prospective client decides to try the caterer down the road instead.

Plus, the complete intake filters the pipeline. Potential clients who genuinely want to book take two minutes to fill in a structured form. Those who were tentatively browsing and not ready to commit rarely do. That sounds counterintuitive — fewer responses might feel like a problem — but the enquiries that come through the workflow are warmer, more specific, and much more likely to convert to an actual booking.

Where to Put the Entry Point

A catering enquiry workflow is only useful if potential clients find it. Three placements generate the most traffic for restaurants.

Instagram bio. For restaurants with an active Instagram presence, the bio link is where food-motivated potential clients look first. A link that says "Enquire about catering →" drops them into the workflow at the exact moment of intent — someone who just scrolled through event photos and thought "I wonder if they do private events."

Google Business Profile. The catering enquiry link belongs in the Google Business Profile description and as a custom button. People searching for caterers in a specific area who land on a Google Business Profile and see a clear "Enquire about catering" button are already pre-qualified.

Host desk card. A small card at the host desk — "We do private events and off-site catering" with a QR code — catches diners who enjoy the restaurant and are quietly wondering whether it could work for their company lunch or birthday dinner. This is one of the highest-quality entry points. The person's already having a positive experience.

This Captures the Enquiry — Not the Booking

It's worth being clear about where the workflow ends. It captures the enquiry. The quote, the negotiation, the deposit, and the booking confirmation all happen in the DM thread that follows.

That's the right division. Catering is a bespoke service. The intake collects what's needed to start the conversation properly; the conversation is still where the deal gets made. Carlos isn't being replaced by a form — he's being given better information to work with when he sits down to respond.

Once the quote is agreed and Carlos is ready to secure the booking with a deposit, that step happens separately — a payment request sent through the same messaging thread, keeping everything in one place. The enquiry, the quote, the deposit, and any event-day communication all live in the same conversation record.

Getting Started

The shift that makes the biggest immediate difference is simple: make the intake the default entry point for catering enquiries. Not the email address, not the DM opener, not the website contact form.

Replace "email us about catering" with "use this link to tell us about your event." Publish the QR code in the three placements above. When someone does send an open-ended DM, reply with a single message: "Happy to chat — the quickest way to get a quote is to fill in this short form, takes about two minutes." That converts the open-ended DM into a structured intake without friction.

For Carlos and Priya, the result wasn't a dramatic increase in enquiry volume. It was a dramatic improvement in enquiry quality. The same number of potential clients, arriving with complete information, producing quotes that could be written and sent the same day. The three hours of monthly overhead that used to go into chasing incomplete requests went elsewhere.

---

Read more about collecting payment once a quote is agreed in the guide to how to charge a deposit before an appointment, or visit the restaurant page to see how Blinko works for food and hospitality businesses.

See how Blinko works for restaurants → · View plans and pricing → — no credit card required.