Meal planning becomes difficult when replies are split between chat messages, reactions, and private notes. MealReply keeps one menu, one participant link, and one organiser view. Guests identify themselves, select one option, record a dietary status, and receive a private receipt for later changes.
Name one recognisable event
Use a title guests will recognise, such as “Saturday wedding dinner” or “Team lunch · August 8.” Keep the optional note short and include only context that affects the choice.
List only orderable meals
Add between two and twenty real choices. Give similarly named dishes a brief description so guests can distinguish them. An “I will not eat” option is useful when the organiser still needs a complete headcount.
Use the count and guest list together
The manager view shows totals per option and the corresponding guest responses. Counts support the order, while the named list helps resolve late changes and dietary notes without searching old messages.
Treat dietary notes as operational information
MealReply records what a guest reports but cannot guarantee that a dish is allergen-safe or that a venue prevents cross-contamination. Confirm serious allergies directly with the guest and food provider.