How to Respond to Catering Enquiries Faster (Without Living in Your Inbox)

A catering enquiry is a person who has an event, a date and a budget, and who is talking to you right now. They are usually talking to someone else too.

The first reply has one job. It is not the quote. It is to show that a real business saw the enquiry, that the date is possible, and what happens next.

The problem is that catering teams are rarely at a desk. They are cooking, loading vans, running service or asleep after one. The enquiry sits. By the time someone replies, the client has moved on or is already halfway through a conversation with a caterer who answered first.

You do not fix this by checking email more often. You fix it with a process that does not depend on anyone checking email.

Here is the four-step method.

Step 1: Map the path your enquiries take today

Before you change anything, find out what actually happens.

Open your own website on your phone and submit an enquiry the way a client would. Use a real-looking event: a wedding for about 120 guests next June.

Then write down:

• Where did it land? A shared inbox, a personal Gmail, a form tool nobody logs into?
• Who saw it first? And did anyone get a notification, or did it wait until someone opened a laptop?
• How long did the first reply take? Start the clock when you pressed send.
• What did the reply say? Did it move the conversation forward, or just say "thanks, we'll be in touch"?

Do the same for the other ways enquiries come in: phone calls that go to voicemail, Instagram DMs, Facebook messages, marketplace listings. Most caterers find at least one channel that nobody owns.

That map is your starting point. Everything else is about shortening it.

Step 2: Ask only the questions that decide the price

Slow replies are often not slow because nobody saw the enquiry. They are slow because the enquiry was too thin to answer. "Do you cater weddings? How much?" cannot be quoted, so it gets parked until someone has time to write a long email full of questions.

The fix is to ask for the details that decide the price, and nothing else, in the first exchange:

1. Event date — if you cannot do the date, nothing else matters.
2. Venue or location — travel, kitchen access and load-in all change the price.
3. Guest count — a range is fine.
4. Event type and service style — plated, family style, buffet or drop-off.
5. Budget range — offered as per-head ranges so nobody has to name a number.
6. Dietary needs and allergies — how many, not just yes or no.

Colour preferences, the full timeline and the playlist can wait until after they have seen a proposal.

Ask these one at a time if you are replying in a chat or DM. A wall of twelve questions feels like homework; one question feels like a conversation. If you use a website form, see the seven fields every catering enquiry form needs.

Step 3: Route every enquiry into one pipeline

If enquiries arrive in four places, you have four inboxes to check and four places for one to be forgotten.

Pick a single list where every enquiry lives, whatever channel it came from. It can be a CRM, a shared board, or a spreadsheet if that is honestly what your team will open. What matters is the rule: if it is not in the list, it does not exist. A phone enquiry gets typed in before the call ends. A DM gets copied in before you reply.

Each row needs, at minimum: the client's name, the event date, the guest count, the status (new, quoted, won, lost) and the date of the next follow-up.

If you are weighing up a spreadsheet against a proper tool, we compared the two in catering CRM vs spreadsheet.

Step 4: Set the next follow-up before you close the tab

Most lost catering leads are not rejected. They drift. A proposal goes out, the client goes quiet, and nobody is sure whose turn it is.

So make it a habit: every open enquiry has a date for its next touch. Before you close the email, the DM or the CRM record, set that date. When it arrives, you send something short and useful: a question about the menu, a note that the date is still free, or a tasting slot.

A follow-up is not nagging when it moves the event forward.

Where automation helps

Everything above works with a notebook and discipline. The hard part is the first reply at 9pm on a Saturday, when the whole team is on-site.

That is the gap we built Collaborative Kitchens AI for. The chat on your website replies straight away, asks the date, venue, guest count, style, budget and dietary questions one at a time, and puts the lead and the whole conversation into one pipeline. It can then draft a menu from the brief, which goes to the chef for approval before the client can accept anything. The chef stays in control.

You can try the chat on a real enquiry and see what your clients would see.

Your free 10-minute enquiry response audit

Run this on your own business this week. Tick each line when it is true.

• ☐ I submitted a test enquiry on my own website and know where it landed.
• ☐ The first reply arrived within one working hour.
• ☐ The first reply asked for date, venue, guest count, style, budget and dietary needs.
• ☐ Every channel (web, phone, DM, email) has a named owner.
• ☐ Every enquiry lives in one list.
• ☐ Every open enquiry has a next follow-up date.

If you ticked all six, your enquiry handling is in good shape. If not, start with the first unticked line and fix only that this week.