How does Voksha avoid creating liability when answering allergen or ingredient questions?

Allergen questions are one of the highest-liability call types a restaurant gets, and the standard the industry works from is the FDA's requirement to disclose the nine major allergens, milk, eggs, fish, shellfish, tree nuts, peanuts, wheat, soybeans, and sesame, added in 2023, when asked. Voksha is configured to answer allergen questions using exactly the ingredient information you provide during setup, it doesn't guess or improvise beyond what's in your menu data.

Where liability actually gets managed is in how the answer is framed, not just what's said. Voksha can tell a caller which dishes contain a listed allergen based on standard recipes, but for anything involving cross-contact risk, shared fryers, shared prep surfaces, or a customer describing a severe or anaphylactic allergy, the safer pattern is to have Voksha flag it clearly, note that the kitchen can be asked directly, and offer to have a manager confirm before the guest arrives or before an order is finalized, rather than issuing a flat guarantee that a dish carries zero cross-contact risk. This mirrors how a well-trained server should already be handling these calls, since verbal guarantees about severe allergies are a liability risk with or without AI on the phone.

Practically, restaurants should keep the allergen data Voksha references current every time a recipe changes, the same discipline you'd apply to a printed allergen chart. An outdated allergen list is a liability problem regardless of who or what is answering the phone, so this is really about your restaurant's data hygiene as much as it is about Voksha's configuration.