Graduation catering is not a bump in your normal business. It's a six-week stretch, roughly mid-April through the first week of June, where an unusual share of your inbound calls are leads rather than orders, and where most of the money is decided in the first ninety seconds of a phone conversation.
The volume isn't the difficulty. A dozen extra calls a week is nothing. The difficulty is that each one requires a different conversation than a takeout order, arrives at whatever time is convenient for the caller, and gets handled by whoever picked up.
The dates collapse onto a few weekends
Every high school in your area graduates within a two or three weekend window, and the parties happen the same afternoon or the next day. The colleges add another weekend.
So the season is not evenly spread. It's four or five Saturdays that are effectively booked out and a lot of quiet days around them. A family calling in mid-May for the second Saturday in June is competing with every other family from the same three schools.
This has a practical consequence: your capacity per time slot matters more than your capacity per week. Three orders for fifty people at noon on the same Saturday is a harder problem than nine orders spread across the month, and your kitchen will tell you that in the least convenient possible way.
The first ninety seconds decide everything
A graduation catering call has five facts that determine whether the job exists at all:
- The date, stated as an actual date rather than "graduation weekend."
- The headcount, and whether that number is a guess or a guest list.
- The service time, meaning when food needs to be ready, not when the party starts.
- Pickup or delivery, and the delivery address if it's delivery.
- Whether they have a budget in mind, asked plainly and without apology.
Get those before discussing a single menu item. A twenty-minute conversation about tray sizes for a date you're already full on is twenty minutes you don't have in May. The full set of qualifying questions and how to sequence them sits in catering lead qualification.
Write the answers down in the same place every time. A season's worth of leads scattered across order pads, text messages, and someone's memory is how a confirmed party for eighty ends up as a surprise on a Saturday morning.
Most of these calls arrive at the wrong time
Parents call between 11 and 1, or around 5, because that's when they have a free minute. Those are your two busiest phone hours.
So the highest-value call of your week lands while your host is seating a table and two takeout orders are on hold. The predictable result is a rushed conversation, an incomplete set of facts, and a promise to call back that sometimes happens.
That mismatch is the reason many operators route catering to its own path, either a separate number or a separate handling rule on the main line, which is what a second phone line for catering covers. If you're running a voice agent, the useful configuration is not to have it close catering deals. It's to have it collect the five facts reliably, at any hour, and hand a complete lead to a human who calls back. That split is the point of AI phone answering for catering orders.
The headcount is always wrong, and you should plan for that
Graduation guest counts move. A family says sixty in April, tells you eighty in late May, and forty-five people show up because the party overlapped with two others.
Two habits handle this. First, set a cutoff date for final counts, usually five to seven days out, and say it clearly when the order is booked. Second, price and prep against the confirmed number rather than the optimistic one, and treat upward changes after the cutoff as a new conversation rather than an automatic yes.
Neither of these is unusual in catering. What's unusual about graduation season is how many first-time buyers you're dealing with. Most of these families have never ordered catering before, and they don't know that a count matters or that a Saturday can be full. Say it out loud rather than assuming.
The same inexperience shows up in how they think about quantity. A parent estimating food for sixty people at an open-house party where guests drift in over four hours will guess badly in both directions, and they'll take your word for it if you give them a number. Give them one. Telling a family "for sixty at an open house I'd build it for about forty-five eaters, and here's why" is the single most useful thing you can say on that call, and it's the reason they'll call you again next year for the younger sibling.
Deposits do the filtering for you
A meaningful share of graduation inquiries never become orders, which is fine. The problem is the ones that become orders and then evaporate.
Taking a deposit when you book the date, rather than at pickup, sorts the real bookings from the ones still shopping, and it does it without you having to guess which is which. The handling mechanics, including how to take a card over the phone without holding numbers you shouldn't, are covered in collecting payment over the phone safely and deposits for large catering.
Saying no in April is cheaper than failing in June
Once a Saturday slot is full, it's full. The fourth family who calls should get a clear no with an offered alternative, not a maybe.
This is the part operators get wrong most often, usually out of a reasonable reluctance to turn down money. But the cost of an overbooked Saturday is not one bad order. It's three late orders, a kitchen that spent the day in crisis, and a set of parents who will remember exactly whose fault it was for years.
Offer the alternative concretely. A 10:30 pickup instead of noon, or the Sunday instead of the Saturday, will be accepted more often than you'd expect if you name it rather than asking what else might work.
What to set up before mid-April
Decide your per-slot capacity in trays or covers, not in dollars, and write it on a calendar the whole team can see. Set your final-count deadline and your deposit percentage. Pick the five questions you ask on every call and put them somewhere the person answering can read them.
Then, at the end of the season, count two things: how many catering calls you took, and how many turned into booked orders. If the gap is large and you can't say why, the problem is almost never your food. It's what happened in the ninety seconds after someone picked up the phone in the middle of a lunch rush. The scaling version of that problem, for kitchens where large orders are the whole business, is in voice AI and large catering orders.