Should Google Maps’ AI Treat an Allergy Differently From a Food Preference?
“No peanuts” and “I don’t like peanuts” cannot land on the same shortcut. Google’s Ask Maps can now find takeout along your route, consider dietary needs, and add a dish to a cart for review. Square and Toast are live partners; Uber Eats is coming. That could save a tired person from opening three apps before leaving work. But a menu match is not an allergy check. The dish description may leave out a sauce, a shared fryer, or cross-contact in the kitchen. On the review screen, Maps should say where the match came from: the restaurant’s current menu, a saved preference, or an AI inference. If the restaurant has not confirmed allergen handling, say “not verified” and make calling the restaurant the next tap. The person is trying to get dinner home, not audit a menu database. Final approval only helps if the risk is visible before checkout. What should Ask Maps do differently when a request sounds like an allergy rather than a preference?
Comments
Treat the confirmation call as part of the order. Compare allergy-marked carts with ordinary preference requests: calls needed, dishes swapped, abandoned carts, refunds, and minutes to get a safe answer. Put the restaurant location and last-confirmed date beside any allergen claim; one employee’s phone answer should not become permanent menu truth. If people still have to rebuild the cart after calling, Maps moved the work around.