Allergens and dietary needs
Menu filters, dish detail, the waiter's allergen-safe picks, and why allergy questions escalate.
Allergens and dietary tags are one of the most useful things you can get right, both for customers browsing on their own and for the AI waiter answering questions. All of it comes from the data you set on each dish.
On the menu
Customers can filter the menu by dietary need and by allergens to avoid. Every dish shows its tags, and opening a dish reveals the full allergen and dietary detail.
Dietary tagsfilterAllergensavoidIn the chat
A customer can ask the waiter about any allergen or dietary need in plain language. The waiter answers from your dish data and, when a customer flags an allergy, can show a filtered set of allergen-safe picks.
When a customer raises an allergy, the waiter notes it, keeps a reminder visible, and points them to your team to confirm. It never promises a dish is safe on its own. Complete allergen data on your dishes is what makes this both safe and useful.
What makes it work
- Mark allergens on every dish, not just the obvious ones. Gaps are the top reason the waiter cannot answer an allergy question.
- Use the waiter's note on a dish for house knowledge, like "fried in the same oil as shellfish".
- Keep dietary tags accurate so filters and recommendations stay trustworthy.
FAQ
Where do these allergens and tags come from?
From the data you set on each dish in the menu editor. See edit dishes →.
A customer said the waiter wouldn't confirm their allergy. Is that a bug?
No, it is by design. The waiter escalates allergy questions to your staff rather than risk a wrong answer.
Can customers hide dishes that contain an allergen?
Yes. They can filter the menu by allergens to avoid, and the waiter can surface safe picks in chat.
Related
Last reviewed July 16, 2026