Restaurant Chatbot: Menu, Allergen and Opening Hours Questions

A restaurant chatbot on your website handles the questions you hear over and over about the menu, allergens and opening hours. It answers from your own menu and policies, so staff stay on the floor instead of on the phone. You know how it goes. Calls and messages pile up right when the dining room is fullest, and most of them ask about things already printed on the menu or posted on the site. The bot only answers from what you’ve written down. Bookings and orders still go through your usual phone line or booking page. Before you set one up, it pays to know what to ask chatbot vendors about keeping answers limited to your own menu and policies.

What can a restaurant chatbot answer for your diners?

Anything where the answer already exists in writing: dishes, menu prices, opening hours, location, parking, house rules. These are the questions guests type in before a visit, or while they’re still deciding where to eat tonight:

• which dishes are vegetarian or vegan
• gluten-free options and how they’re marked
• portion sizes and ingredients of a specific dish
• whether there’s a kids’ menu
• holiday and seasonal opening hours
• whether dogs are welcome and how accessible the venue is
• accepted payment methods

As a restaurant website assistant, it lives in a widget you add with a single script, and it answers only from the documents the owner uploads. Nothing else. Want to hear what spoken answers sound like? Try the restaurant voicebot demo.

Which questions to prepare first

Start with the handful of questions your staff get every single day. Those are the ones that eat into service. Getting the knowledge base ready doesn’t take much:

1. For a week, write down every question that comes in by phone and message.
2. Write one clear answer to each question.
3. Upload the current menu and your allergen matrix.
4. Add opening hours, including holidays and seasonal changes.
5. Test the bot with real questions from your staff and fix any weak answers.

Shop owners go through the same exercise, and the guide on the questions to cover first works just as well for a dining room. One habit matters a lot here: when the menu or seasonal hours change, update the knowledge base the same day. If you don’t, the bot will happily keep repeating last month’s information. It has no way of knowing better.

Allergen questions: what the bot may say and where it must stop

An allergen questions chatbot only repeats the allergen information your restaurant has already published. It never replaces a conversation with staff. Regulation (EU) No 1169/2011 on food information defines prepacked food and excludes food packed on the sales premises at the consumer’s request, as well as food prepacked for direct sale. That’s a summary of the text, not legal advice. Check your own duties with your local food authority.

Every allergen answer should close by asking anyone with an allergy to confirm with staff before ordering. Recipes change. Suppliers change. Cross-contact in a busy kitchen happens. So the bot is never the only source: your staff and your printed or on-menu allergen information remain the reference. It also gives no medical advice and doesn’t judge whether a dish is safe for a particular person or condition (that’s simply not its job). A lot of the same thinking shows up in guidance on bots for sensitive questions, where health topics call for the same caution.

Answering diners after hours and during the rush

The bot replies at any hour. A question sent at midnight, or right in the middle of Saturday service, gets an answer without anyone waiting for a free pair of hands. And answering diners after hours means the guest planning dinner in the evening can decide on the spot instead of calling you tomorrow. During the rush? Fewer interruptions at the pass and the bar, and the phone stays free for calls that really need a person. The first thing that late-night guest sees is your greeting, so it pays to write opening lines that invite questions about the menu, allergens or tonight’s hours.

Every answer should point to a clear next step. For bookings, orders, large groups or special requests, the bot gives the restaurant’s phone number or booking page, taken from the content you uploaded. The guest knows exactly where to go. Staff get those requests through the channel they already use. Simple.

When a chatbot for restaurants should say ‘I don’t know’

If the answer isn’t in the menu or the policies, a chatbot for restaurants should say so and send the guest to staff. No guessing. Typical cases:

• whether the kitchen can make a dish without a specific ingredient today
• whether today’s special is still available
• anything about a particular person’s diet or health

An honest “I don’t know” earns more trust than a confident mistake, and the reasoning behind declining questions it cannot answer holds for every kitchen. In my view, a restaurant chatbot does its best work as a well-fed first answer to the repeat questions, while staff keep the final word on allergens and on anything outside the written content. The same approach carries over to other businesses too, as the examples of bots in other industries show.

FAQ