Collect a first catering inquiry without taking an order

The decision this workflow supports

A first-time catering caller may not know what the restaurant needs to assess an event. Start with the event itself rather than reading a menu or assembling a quotation during the call. The output is a qualified inquiry for staff.

Put the review process in place

Collect a preferred date, approximate attendance and service format, then ask who should receive follow-up. Let the catering manager decide whether the request fits the operation. Describe all menu choices, availability and prices as matters that staff will confirm.

Worked example for your team

A fictional organizer is considering a lunch for around thirty colleagues next month but has not chosen a menu. The first callback should be possible from the date, attendance estimate, requested format and contact details alone. The intake does not need to choose dishes or collect a payment method to become useful. Have the catering manager read the resulting note and state the next question they would ask. If the note says confirmed lunch or contains an invented package, the test fails even if every basic field was captured correctly.

Sample wording to approve

“I can collect an inquiry for the catering team. What date are you considering, about how many guests are involved, and is this collection, delivery or service at a venue?” This wording is a draft for the restaurant owner to approve before use.

Fields for the staff handoff

Staff need event date, approximate guests, requested service format, organizer contact, and catering reviewer. Mark uncertain details explicitly and keep the requested action separate from anything restaurant staff have already confirmed.

Acceptance tests before use

An inquiry is not labeled an order. An unknown guest count is accepted as approximate. The team receives enough information to decide its next question. Record the observed result, assign any mismatch, and repeat the affected scenario after correction.

Related guides