Allergy questions should be handled carefully on a restaurant phone. The right move is simple: answer only what you know from the menu, and hand off anything uncertain or allergy-sensitive to staff.
For a busy pizza shop, deli, or family restaurant, that means the phone host needs a clear rule. ROAL does this by answering menu questions it can support, and sending allergy-sensitive questions to staff with a summary so the team can review the order before it goes to the kitchen.
Key takeaways
- Answer ingredient questions from the menu, but hand off allergy-sensitive questions to staff.
- Use a short script that tells callers you are reviewing the question, not guessing.
- Make sure the handoff summary includes the dish, the concern, and the caller’s contact info.
- Keep the kitchen loop clear so the team can confirm before prep begins.
- Update menu notes often so the phone host stays accurate.
In this post
- What should the phone host say when a caller asks about allergies?
- Which allergy questions can be answered, and which ones need a person?
- How do you train the host to stop and hand off the right calls?
- What should staff see in the handoff summary?
- How do you avoid mistakes on the kitchen side?
- How do allergy calls fit into your phone and ordering setup?
- Questions owners ask
What should the phone host say when a caller asks about allergies?
The safest approach is to keep the answer short, clear, and honest. The host should not make guesses about hidden ingredients, cross-contact, or kitchen prep. It should answer only from the menu and any notes the restaurant has provided.
A good script line is: "I can help with menu details, but for allergy-sensitive questions I’m going to send this to the restaurant team." That tells the caller what is happening without sounding stiff.
For a real call, use this simple flow:
- Identify the dish the caller wants.
- Check the menu for the listed ingredients and modifiers.
- State only what is known, such as sauce, cheese, bread, or toppings.
- If the caller mentions a food allergy, hand it to staff.
Example: a caller asks, “Does the chicken wrap have dairy?” The host can say, “I can see the wrap includes ranch unless removed. For allergy-sensitive details, I’m sending this to the restaurant team.” That is better than guessing.
ROAL is built to do exactly that kind of handoff. It can take the rest of the order, but allergy-sensitive questions go to staff with a summary so nothing gets lost.
Which allergy questions can be answered, and which ones need a person?
Not every question needs the same response. Some are simple menu questions. Others are safety questions that should go straight to staff. A good rule is to answer ingredient questions from the menu, but hand off anything about allergy risk, shared equipment, or custom prep.
| Question type | Example | Best response |
|---|---|---|
| Menu ingredient | “Does the salad have cheese?” | Answer from the menu |
| Modifier question | “Can I get no mayo?” | Answer if your menu supports it |
| Allergy-sensitive | “Is this safe for a peanut allergy?” | Hand off to staff |
| Cross-contact | “Do you fry fries in the same oil?” | Hand off to staff |
| Custom prep | “Can the kitchen make this separately?” | Hand off to staff |
If you want a quick script for staff, keep it plain: "Caller asked about a peanut allergy on the chicken sandwich. Please review ingredients and prep before confirming." That gives the kitchen a clear task.
A practical restaurant rule is to keep the host helpful, but not overconfident. If the answer is not on the menu page, menu PDF, or store notes, the host should stop and hand it off. That is especially important for mixed dishes, sauces, breading, soups, and anything prepared in-house.
This also helps during rush periods. The phone host can keep the line moving while the kitchen or manager handles the higher-risk question.
How do you train the host to stop and hand off the right calls?
The host needs a simple playbook. The best setup is not complicated. You tell it what it may answer, what it must not answer, and who should get the handoff.
Use a short internal checklist like this:
- Answer regular menu questions from the live menu.
- Answer hours, address, parking, and pickup details.
- Take the order if the caller is comfortable.
- Stop and hand off if the caller mentions an allergy, intolerance, or special medical concern.
- Include the dish name, the ingredient concern, and the caller’s contact info.
A useful script is: "I want to make sure I get this right, so I’m sending this to the restaurant team now." That sounds calm and professional.
For example, say your restaurant sells a $24 pasta dinner and a caller asks whether the sauce has shellfish. The host should not try to infer the answer. It should collect the caller’s name, phone number, and the dish name, then send the question to staff. If the manager already knows the answer, the next time that same question comes in, the host can use the updated note.
ROAL supports this pattern. Questions it cannot answer land in an inbox, and once the owner answers them, the host knows it from then on. That makes the phone flow cleaner without pretending the host can safely judge every ingredient situation.
What should staff see in the handoff summary?
A good handoff summary should be short and useful. Staff do not need a transcript dump. They need the facts that matter so they can respond fast and correctly.
A strong summary includes:
- Caller name
- Phone number
- Menu item requested
- The allergy or ingredient concern
- Any modifiers already requested
- Whether the caller wants pickup or delivery
Example summary: "Maria, 555-0100, wants two chicken wraps. Asked whether the wrap or sauce contains dairy. Would like pickup at 6:30."
That is better than a vague note like “caller had a question.” It gives the manager enough context to call back or answer right away.
If your team wants a printed rule, use this line near the phone or prep station: "All allergy questions go to staff before confirmation." That keeps everyone aligned.
For restaurants that do a lot of phone orders, this matters because the host is often handling several tasks at once. It can take the order, collect the ready time, and still move the allergy question to staff. ROAL sends a clean ticket to the kitchen screen, and the handoff summary helps staff spot the issue before prep begins.
If your team uses a kitchen screen, make the allergy note easy to see. If not, the manager should be the one to confirm the answer before the order is finalized.
How do you avoid mistakes on the kitchen side?
The phone side is only half the job. The kitchen side needs a clear way to see the allergy note and act on it. The goal is not to make the host responsible for food safety decisions. The goal is to make sure the concern reaches the right person.
A simple kitchen checklist works well:
- Read the ticket as soon as it appears.
- Look for any allergy note or staff handoff flag.
- Confirm the item and modifiers before cooking.
- If the note is unclear, pause and ask the manager.
- Do not assume a standard build is safe for every caller.
Example: a caller orders a sandwich with no onions, but says they have a sesame allergy. The kitchen should not treat that as a routine modifier. Even if the bread is normally used, the team needs to review it before confirming.
This is where a clean ticket helps. ROAL sends orders to the kitchen screen and includes the details the restaurant needs, so the phone and kitchen stay aligned. If your menu changes often, keep the menu editor updated so the host is working from current items and prices.
A practical owner rule is: if a question could change how the kitchen prepares the food, it belongs with staff. That protects the caller and keeps the team from having to fix confusion later.
How do allergy calls fit into your phone and ordering setup?
If your restaurant forwards calls to an AI phone host, allergy questions should be part of the same call flow as orders and hours. The host can answer simple menu questions, take pickup or delivery orders, and pass sensitive questions to staff without breaking the call.
A basic setup looks like this:
- Forward all calls, or only busy and unanswered calls, to the host.
- Let the host handle normal menu and order questions.
- Route allergy-sensitive questions to staff.
- Keep your existing number.
- Review the inbox for any unanswered items.
If you want to compare the cost of different phone setups, Pricing and the AI phone host cost calculator can help you plug in your own numbers. That is useful when you are deciding whether to rely on delivery apps, staff, or a phone host.
A worked example: say your average phone order is $28 and you get 40 completed phone orders in a month. That would be 40 x your per-order cost. Plug in your own order count and average ticket size to see what the phone channel costs you. The point is not to guess. The point is to compare clearly.
ROAL is set up for this kind of call flow. It answers the restaurant’s phone, takes orders from the live menu, and hands allergy-sensitive questions to staff with a summary. If you want to try it, build a free test host from your website or menu pages and see how it handles your own menu language.