Most of the calls a restaurant gets don't need judgement. Are you open, can we get a table at eight, is there parking. Anyone can answer those correctly — and increasingly, software does.
Allergy questions are different. "Can your kitchen do a nut-free meal for my daughter?" isn't a question about the menu. It's a question about what happens in your kitchen — shared fryers, shared prep surfaces, what goes into the sauce base, who's on the line tonight — and the answer carries consequences that no other call does.
That makes it the one call worth routing deliberately.
Why a quick "yes" is the dangerous answer
The failure usually isn't refusing. It's reassuring.
A host who wants to be helpful says "oh yes, we can do nut-free" without checking the dessert station. A menu calls a dish gluten-free when it shares a fryer with battered fish. An answering system reads the menu and confirms a dish contains no dairy, because the menu didn't list any.
Every one of those answers sounds right, and every one rests on less information than the question needs. The person asking is often planning their evening — or their child's — around what you tell them.
Route it to someone who can check
Decide, and write down, who answers allergy questions:
- During service: the manager or a senior member of the kitchen — someone who can actually look at the prep, not someone reading the menu.
- When nobody qualified is free: take the caller's name and number, the allergy, and the date of their visit, and promise a call back. Then make the call back.
The message to front-of-house is simple: you're allowed to not know. "I want to check with the kitchen so I can give you a proper answer — can I call you back within the hour?" is better than any quick yes.
The same goes for whatever answers your phone. If it's software, one of the most important things to check is what it does with a question it can't safely answer. The right behaviour is to take the details and say someone will call back — never to answer from the menu. We built SeasonX's phone handling on that principle: when it can't give a safe answer, it takes the details and says the team will follow up, rather than guessing. It's one of the first calls to make before you trust an AI receptionist.
What to write down
When an allergy comes up on the phone — even in passing, while booking — it should end up on the reservation, where the kitchen will see it:
- The allergy or intolerance, in the guest's own words
- Who it affects, if it's a group
- What they were told the kitchen can and can't guarantee
- Who took the call
"Table of four, 7:30, one guest with a severe peanut allergy — spoke to Sam, kitchen can prepare separately, told them the fryer is shared" is a note that protects the guest and your staff.
Be honest about limits
No kitchen that handles an allergen can promise zero cross-contact, and saying so isn't a failure of hospitality. Guests with serious allergies generally know this, and would far rather hear "we can prepare it separately, but we do use peanuts in the kitchen" than a cheerful guarantee.
What they need from the call is accurate information and a clear record, so the kitchen isn't learning about the allergy from the ticket at nine o'clock.
Take the pressure off the rest of the phone
Allergy calls get rushed because they're queued behind a dozen easy ones. If the easy calls — hours, parking, simple reservations — are handled without pulling a person off the floor, that person is free for the call that needs them.
That's the argument in why your phone rings hardest when you can't answer, and it's what SeasonX is for: taking the routine calls, so the important ones reach a person.