Restaurants and allergen questions: the hard line

That is the shortest rule in this entire category and the one with the worst consequences if you get it wrong.

I spent sixteen years running multi-unit restaurants. Allergen calls arrive mid service, and the temptation to give a quick reassuring answer is enormous. An AI removes the last bit of human hesitation that used to slow the wrong answer down.

Why can an AI not answer an allergen question?

Because the answer depends on things the agent cannot know at the moment it speaks.

Whether the fryer is shared today. Whether the prep cook used the same board. Whether the supplier changed the bun formulation last week. Whether the chef adjusted tonight's sauce at four.

A person in the kitchen can go and look. A voice agent reads a document written in the past and describes a kitchen it cannot see.

The regulatory shape follows the same logic. The FDA Food Code 2022 puts allergen knowledge with the person in charge at paragraph 2-102.11(C)(9), a designated, present, accountable human. Paragraph 3-602.12(C), new in the 2022 edition, requires the permit holder to notify consumers of major food allergens in unpackaged food by written notification. A voice agent is neither the person in charge nor written notification. At best it can point the caller to a document.

Two details that matter for your jurisdiction. Sesame became the ninth major food allergen under the FASTER Act of 2021, so any list written before that is out of date. And the Food Code is a model code. It binds only where a state or local authority has adopted it, and editions differ. Confirm which edition your health department has adopted before you write anything into a script.

Does federal law require restaurants to disclose allergens?

Not on menus, and this is the most misunderstood point in the whole subject.

You will hear the Food Allergen Labeling and Consumer Protection Act cited as the reason restaurants must disclose. FALCPA governs labeling on packaged food. It imposes no federal menu disclosure duty on restaurants at all.

That absence is the trap, not the escape. Owners hear "no federal requirement" and conclude there is no exposure. What it actually means is that there is no federal safe harbor either. Restaurant allergen exposure is governed by ordinary negligence law and by state and local food codes, which is a far less predictable place to be than a clear federal standard would have been.

California has since moved. SB 68, the ADDE Act, was chaptered on 13 October 2025 and commences 1 July 2026. It requires a food facility subject to the federal chain nutrient disclosure provisions, which reach chains of 20 or more locations, to provide written notification of major food allergens for each menu item, either on the menu or in a specified digital format. If you operate at that scale in California, that is a document project with a deadline, and it is a question for your own counsel rather than for a marketing article.

I am not a lawyer and none of this is legal advice. The operator version is simple enough: your health department, your insurer, and your attorney each have a view, and you want all three before anyone argues you into "but it just reads the menu."

What should the agent say instead?

One line, warm, and it hands off. This is what I would put in the script.

"I want to get that exactly right for you rather than guess. Let me have our manager call you back in the next few minutes with a proper answer, or if you are close by, our team can walk you through it in person. Can I take the best number for you?"

That does four things. It refuses without sounding like a refusal. It signals seriousness, which is what an allergy caller wants to hear. It captures the callback number so the lead does not evaporate. And it sends the question to the human whose job it is.

The version that fails is "I am unable to provide allergen information." A caller with a serious allergy hears indifference, does not book, and sometimes tells people about it.

Then the callback has to happen. That is a manager routing rule, not a technology feature, and it is where most of these scripts quietly break.

Can your kitchen actually keep the callback promise?

What can a restaurant AI safely handle?

Most of the phone, honestly.

Hours, address, parking, whether you take walk ins, the current wait if you have that data, whether the patio is open, whether you have highchairs. All of that is a fact about the building.

Reservations, waitlist adds, and party size changes, if it can write into the booking system you already use rather than leaving a message somebody retypes. That is worth more than it sounds: Maple found 58% of reservations still originate from phone calls, not apps or online booking, and the average call runs 1 minute 45 seconds.

Takeout and catering inquiries, until a menu decision needs a human. Catering is where the money is on the phone for most independents, and it is the call most likely to be missed at 5:45 on a Friday.

There is a segment argument for this too. Revmo AI's analysis of 12,091 real restaurant call recordings put answer rates at 91% for full service and 59.9% for quick service. A full service operator answering nine calls in ten has a quality problem to solve. A quick service operator missing four in ten has a coverage problem. Those are different purchases.

What the agent should not do beyond allergens: quote a firm catering price for a custom menu, promise a table by a specific time, or confirm anything about a large party's setup that the floor manager has not seen.

Does this apply to dietary preferences too?

No, and the distinction is worth being precise about because staff blur it constantly.

"Is this dish vegetarian" is a menu fact. It has a written answer, it does not change with the fryer, and getting it wrong disappoints someone rather than harming them. An agent can answer it from the menu.

"Is this safe for my child's peanut allergy" is a safety question about tonight's kitchen. Different question, different rule, no exceptions.

The script needs both a whitelist of menu facts it may state and a trigger list of words that force the handoff. Allergy, allergic, anaphylaxis, celiac, epipen, and every named major allergen including sesame. Those triggers must be hard coded interrupts, not knowledge base lookups. If any of them appear, the agent stops answering and hands off, even if the question sounded casual.

Train the same rule into your humans while you are at it. In my experience the AI follows the rule more reliably than the host stand does at seven on a Saturday.

Is any of this worth doing if the phone is not your problem?

Only if you have counted. Restaurants routinely assume the phone is fine because someone is standing near it.

Before buying anything, work out what your real missed call rate is across a normal week, including the dinner rush and the hour before opening. The gap between what owners believe and what the log shows is usually large.

A cheaper first step for many restaurants is an automatic text back when a call is missed. It does not answer allergen questions either, which is fine, because it is not pretending to.

And if your online path is the problem instead, look at the pattern rather than the platform. The same above the fold discipline that a contractor site needs in its first screen applies to a restaurant homepage, and checking where people abandon your catering form costs nothing and often finds more money than the phone does.

What to do this week

Write the allergen handoff line exactly as you want it spoken. One sentence, warm, ends with a request for the callback number.

Write the trigger word list, including sesame. Put it in the script as a hard interrupt, not as guidance.

Log allergen calls for two weeks and run the six step arithmetic above. Decide the callback promise from the result rather than from optimism.

Decide who owns the callback during service. If nobody can own it, change the promise.

Then call your own restaurant at seven on a Friday and ask if the pad thai is safe for a shellfish allergy. Whatever the human says is what your script has to fix, and that is the real starting point.

Questions about your allergen script?

Email me at eric@seod.com with your allergen policy exactly as it exists today, even if it is one line on the bottom of a menu. I will tell you which parts a phone agent may state, which parts must never leave a human's mouth, and the exact handoff line I would use for your concept.

I ran kitchens for sixteen years and I will answer this one personally. Where it needs your health department or your attorney rather than my read, I will say so plainly, and on this subject that happens often.

More on phones and lead handling is in the AI phone and lead response library.