Why Geneva restaurants lose catering jobs before the callback

It is 6:40 on a Tuesday and every table is seated. The phone rings and the host picks it up with a menu still in her hand. A woman is calling about a graduation party, maybe forty people, first weekend in June, and she wants to know what that would cost. The host says the manager handles parties and asks for a name and number. She writes it on the back of a reservation slip and puts the slip under the podium so it does not blow away.

The manager comes in at eleven the next morning to a short produce delivery and a line cook who called off. He finds the slip around four. The handwriting says Kara, then a number with one digit that could be a 3 or an 8. He tries it Thursday and gets voicemail. Kara booked the place on Third Street on Wednesday, because someone there answered the phone at ten and had a package sheet in her inbox by noon.

That one call was worth more than the whole Tuesday night of covers, and it came in at the one moment when nobody could do anything with it.

What a slip under the podium costs

A private party inquiry comes in on the same line as "are you open until nine," and during service every call gets triaged by whoever is standing closest to the phone. The forty-person booking gets the same eleven seconds as the hours question.

Then there is timing. Nobody planning a rehearsal dinner calls one restaurant. They call three or four in an afternoon and compare what comes back, and whoever replies first with real numbers sets the frame everyone else has to argue with. A callback two days later is competing against a decision the host has already half made.

There is also the information you never captured. Date, headcount, start time, room or full buyout, whether they need a bar. When the record is a name and a smudged number, the callback becomes a discovery call, then a second call to send pricing, then a third to confirm. Each gap between those calls is another day.

Nothing gets counted either. Ask a manager how many party inquiries came in last June and you get a guess. Nobody knows whether the ones who passed walked on price or on the wait, so the same leak runs every graduation season and nobody can point at it.

The parties that do book live in a text thread on the manager's personal phone. Final counts, the cake being dropped off at four, the aunt who cannot have gluten, the centerpieces they are bringing themselves. The kitchen learns most of it on Friday.

What catering intake looks like when a system holds it

Every inquiry gets captured the same way and gets a real answer the same night, whether or not a manager is anywhere near a desk.

• Missed and after-hours calls get a text back within about a minute: this is the restaurant, we caught your call during service, tell us your date and headcount and we will send options tonight. Replies land in one inbox the manager actually reads.
• One short form does the capture, reachable from the website, from that text, and from a code on the check presenter. Nine fields is enough: date, time, headcount, occasion, room or buyout, bar, dietary notes, name, phone.
• The inquiry becomes a record with a timestamp, an owner, and a status. It cannot slide under a podium.
• The first real reply goes out that evening on its own: current per-head pricing, room capacities, deposit and cancellation terms, and a link to put a soft hold on the date. The manager can improve on it in the morning, but he is no longer the reason it took two days.
• Follow-up runs on a schedule and then stops. One nudge at two days, one more at five with an offer to walk the room, then the lead gets marked cold. Nobody is chasing a June party in July.
• Once it books, the details arrive on a schedule instead of by memory. Deposit link, confirmation, a request for final count and allergies two weeks out, and one event sheet that reaches the kitchen and the floor three days out in the same format every time.
• The owner gets one weekly note: inquiries in, how many were answered within the hour, how many booked.

These are the same mechanics I have built for intake elsewhere. A freight forwarding client's quote requests used to arrive as loose email and now come in structured and tracked, and a pool service client's leads are captured and followed through to the job. Something comes in, gets recorded properly, gets an immediate reply, gets nudged on a schedule, and reaches a person when there is a decision to make.

What stays human

Selling the party. The tasting, the walkthrough where the host stands in the room and pictures it, the call where someone asks for a buyout on a Saturday in June and you decide what that is worth against a normal Saturday. Menu design for a table with a serious allergy belongs to the chef, and the day itself belongs to the staff. The system answers the phone when both hands are full and gets the details into the kitchen in writing.

When it is not worth building

If you do six parties a year and the manager is usually at the desk when the phone rings, keep the slip. And if your package pricing does not exist in writing yet, that is the first job, and it is an afternoon with a calculator and last year's food cost. A system can only send what you have already decided.

When it is worth building, builds start at $500 one time, then a flat monthly from $99 after an included run-in period, cancellable. There is more on the restaurants page and on what I build for businesses in Geneva.

Where to start

The first step is a free 20 minute process audit. We walk through your last ten party inquiries, find when each one was answered and which ones never were, and put a number on the season. If a system pays for itself, build it. If it does not, you keep the map either way. Start here.