It's 7:30 on a Saturday, the dining room's full, and the phone rings at the host stand. A party wants to come in, but first they've got a question: their daughter has a tree-nut allergy, the serious kind, the kind that travels with an auto-injector. Is anything on your menu safe for her?
The host covers the phone and calls toward the pass. The line's buried in tickets, so somebody shouts back "the chicken's probably fine," and that "probably" sails out over the phone as a yes. Nobody meant to promise anything. You just did.
Here's the thing about the allergy question: it's the one call you can't answer by guessing, and it's also the one most likely to get guessed at, because it always lands when the kitchen's slammed. The fix isn't turning every server into a chef. It's writing the answer down once, yourself, so the only words that leave the building are words you already checked.
Write the answer once, at a quiet hour
Pick a slow afternoon, that dead stretch between lunch and dinner, and go through your menu dish by dish with the one question that matters: if a guest with a real allergy ordered this, what would I honestly tell them? Do it when you're calm, not when the phone's ringing off the hook.
Sort every dish into three buckets for the big allergens: shellfish, nuts, gluten, dairy, egg, soy. In a quahog-and-calamari state like ours, that first one comes up a lot, so start there. The buckets are simple:
- Safe as served. No change needed, no risky neighbors on the plate. The grilled chicken, the house salad without croutons.
- Safe with one swap. Fine if you hold the walnuts or sub a gluten-free bun. Write down the exact swap so it's the same whether you make it or your newest server does.
- Can't promise. Shared fryer, flour in the air, a sauce that starts from a base you buy in. Say so plainly.
The honest line that protects everyone
That third bucket is the one owners want to skip, and it's the most important thing you'll write. If your fries share a fryer with the calamari, no amount of careful plating makes them shellfish-free, and a guest with a severe allergy needs to hear that before they order, not after.
Say it straight: "We cook in a shared kitchen, so we can't guarantee any dish is free of a given allergen. Here's what we can tell you." Cautious diners aren't scared off by honesty. They're scared off by a vague yes that falls apart at the table. A clear "here's what's safe, here's what we can't promise" is what actually books them.
Give your front desk the words, not the burden
Your host and your servers shouldn't be inventing answers at the pass. Print the three buckets on a single sheet, tape it by the phone, and keep the same thing in a note on the host-stand tablet. When the allergy question comes, they read the pre-approved answer instead of relaying a shout from the line.
Tell them the one rule that overrides everything: when in doubt, it goes in the "can't promise" bucket. A missed booking is a Tuesday problem. A guest in an ambulance is a different kind of night, and in a state this small, it's the kind everybody hears about.
Put the same answer where guests look first
Most cautious diners check before they ever call, so meet them there. Your website menu can carry a short allergen note on each dish, or at least a line at the top that tells people exactly who to ask and what you can and can't guarantee.
Set up a text auto-reply too (a canned message that sends the second someone texts your business line). Something like "Thanks for texting! For allergy questions, here's our current safe list," with a link. That link points to the same owner-written answer, so the guest texting at 9 PM on a closed Monday gets the right words without anyone picking up.
Consistency is the whole game here. The answer on the phone, the answer on the website, and the answer in the text all need to match, because a guest who hears three versions trusts none of them. Write it once, point everything at that one source.
Keep it true as the menu moves
An allergen list is only as good as its last update. The day you change a supplier, swap a fryer oil, or run a special with a new sauce, the list can quietly go wrong. Build the check into the work you already do:
- Every menu change gets an allergen pass before it goes live.
- New specials get sorted into the three buckets before the first one's plated.
- When a vendor swaps a product, re-check anything that uses it. A "gluten-free" bun from a new bakery isn't gluten-free until you've read the new label.
Worth doing this week
- Block one quiet hour and sort your top 20 dishes into the three buckets. Don't wait for a slow week; a slow hour is enough.
- Write your "shared kitchen" line in plain words and read it out loud. If it sounds honest, it's right.
- Tape the list by the phone and save it on the host stand, then tell every server the "when in doubt, can't promise" rule tonight.
- Add an allergen line to your website menu and set a text auto-reply that points to it.
- Put a standing reminder on every menu change: allergen pass before it's served.
None of this takes fancy software, just an afternoon and the discipline to keep it current. If you'd rather have the website note, the text auto-reply, and the whole thing wired together for you, that's the kind of quiet setup we do for Rhode Island kitchens at RI AI Agency. Either way, write the answer down before the next Saturday rush asks for it.