2026-05-18

Prom night group bookings: who is really calling you

Prom parties look like a headache and book like a catering job. The callers are parents, the risk is the no-show, and the fix is a prepayment rule stated up front.

Most operators assume prom night is a service problem. Sixteen teenagers at a long table, a server running themselves into the ground, a check split every possible way, a modest tip. That is the picture, and it is why some restaurants quietly decline the business.

The picture is mostly wrong about where the difficulty lives. Prom is a booking problem. Almost everything that goes badly on the night was determined three weeks earlier during a phone call that nobody treated as a sales call.

The caller is a parent doing procurement

Students do not book prom dinners. A parent does, usually one who volunteered or got volunteered, and they are working a list. They call four or five restaurants in an afternoon with the same three questions: can you seat sixteen on May 16th, what does it cost per person, and how do we pay.

They want those answers in one call. A restaurant that says "let me have the manager call you back" is competing against one that already gave a number, and the callback often lands after the decision was made. This is the same dynamic as any group inquiry, which we cover more generally in large party reservations by phone, except the window is compressed into about two weeks of the spring.

The second thing worth understanding about this caller: they are not price-shopping in the ordinary sense. They are risk-shopping. They have committed to organizing something for other people's children and they want to know it will not fall apart. A firm price, a firm time, and a clear payment rule reads to them as competence, and competence is what they are buying.

What they will not tell you unless you ask

Party size will move. The number they give you on the first call is the number of kids currently in the group chat, and it will change at least twice. Ask directly how firm it is, and set your policy against the number they can commit to rather than the number they hope for.

They also usually have not thought about timing. Prom dinners run against a hard external deadline, because the dance starts when it starts. If they say 6:00, they mean out the door by 7:15, and if you do not surface that during the booking call you will discover it when a table of sixteen starts asking for the check twenty minutes after the entrees land. Ask what time they need to leave, then decide whether you can do it.

The no-show risk is real and prepayment is the answer

A prom group is a social arrangement, not a household. Four kids dropping out between the booking and the night is ordinary. The whole group dissolving because of a disagreement you will never hear about is uncommon but not rare.

That is why prom bookings warrant a deposit rule you would not apply to a family of twelve. Either a per-head deposit or a prepaid prix fixe, taken at booking, with a stated shrink policy: you pay for the number you commit to by a set date, and drops after that date are still charged. Say the rule on the first call, in plain language, and put it in the confirmation.

Operators resist this because it feels like it will cost bookings. It does cost a few, and the ones it costs are disproportionately the ones that were going to shrink or evaporate. The general framing sits in deposits for large catering, and the safe mechanics of taking a card during a call are in collecting payment over the phone safely.

One more thing to decide in advance: alcohol. There will be adults at some of these tables and there will be attempts at others. Have an actual stated house rule rather than leaving it to a nineteen-year-old server to enforce on a Saturday night, and know your state's position on it. The phone-order version of that question is in alcohol orders by phone laws.

A fixed per-person price fixes three problems at once

The organizing parent needs a number to tell fifteen other parents. Your kitchen needs a prep count. Your server needs to not take sixteen individual orders at a table where half the group is taking photos.

A prom prix fixe at a set price per head answers all three. Two or three entree choices collected in advance, a set starter and dessert, tax and gratuity included so the number the parent quotes is the number everyone pays. Automatic gratuity on large parties is standard practice and this is exactly the situation it exists for, but it has to be disclosed at booking rather than discovered on the check.

The argument against is that you give up check growth. Look honestly at whether that growth exists. Sixteen teenagers ordering off a full menu on a night when they are dressed up and photographing everything is not typically a high-average-check table, and the operational cost of serving it à la carte is substantial. You are trading a small amount of upside for a much shorter table time and a countable kitchen number.

If your format makes a prix fixe awkward, at least pre-collect the entree counts. The thing you are buying is a kitchen that knows what is coming, and a table that starts eating within fifteen minutes of sitting.

Where the phone system fits

Prom inquiry calls arrive in a two-week burst, often during weekday afternoons, and each one is five to ten minutes if handled well. That is a lot of manager time in a season when managers are also handling graduation parties, and the two overlap almost exactly. The graduation side of the same season is in graduation catering season.

The qualifying half of the call is bounded and repeatable: date, party size, do you have a group menu, what is the per-person price, what is the deposit, what time do we need to be out. A voice agent handles that reliably and captures it in a form somebody can act on. What it should not do is finalize a sixteen-top against your book without a person looking at it, because the seating decision usually involves a judgment about table configuration that is not in any system.

So the useful setup is: the agent catches every prom call, answers the price and policy questions the same way every time, records the details, and routes the actual booking to whoever owns your group business. The escalation logic is the same one described in catering lead qualification.

Pull your reservation records from last May and count how many group bookings of eight or more you took, how many arrived at the size they booked, and how many you lost after a callback that went out the next day. If the third number is anything above zero, the money is in answering the first call properly, not in serving the table better.

More on seasonal playbooks

All seasonal playbooks articles

Frequently asked questions

Hear it answer a real call.

Call the demo line and order like a customer would, or book time and we'll walk your team through it.