Give the tool a menu that is actually current
People often ask when the kitchen closes, whether a dish is still available or how to reserve a table. Put your current hours, reservation method and menu in one place staff can check. A drafting tool can prepare a reply using those facts. It cannot know that a special sold out this afternoon unless someone updates its source.
For reservation enquiries, ask for the date, party size and a way to reply. Do not have a tool confirm a table from an email alone. A person or the reservation system must check capacity first. If the request includes a celebration, accessibility need or unusual timing, send it to someone who can make an informed decision.
Review answers whenever hours change for a holiday or the menu changes. An old answer can look polished and still send someone to a closed dining room. Make the update part of the same routine as changing the sign or the reservation calendar.
Describe dishes from the kitchen's own notes
Short menu descriptions help people understand what a dish is. A tool can organize the chef's notes into a concise description of ingredients and preparation. Start from the actual recipe and the words the kitchen uses. Avoid adding flavors, origins or ingredients that no one supplied just because the sentence sounds appealing.
Show the draft to the kitchen before publishing. Check spelling, portion descriptions, price and whether a dish is available at the stated time. If you offer variations, explain how to ask about them rather than promising any substitution. The printed menu, online menu and staff answers should tell the same story.
Allergen information needs a separate and stricter process. Never generate allergen claims with a tool. Staff must check actual ingredients, supplier information and kitchen practices before answering a guest. When there is uncertainty, say so and have a knowledgeable person handle the conversation directly.
Treat reviews as conversations, not templates
A public review can deserve a short thank you or a careful response to a concern. A tool may produce a first draft, but someone who knows the situation should decide whether to reply and what to say. Do not invent a visit, a refund, a conversation or a promise to change something the team has not agreed to change.
For a complaint, pause and read the full review. If there may be a food safety concern, route it to the right person promptly. Keep the public response respectful and brief. Do not reveal reservation details, payment information or anything else about a guest in public, even to defend your team.
Look for repeated questions in reviews and messages. If people keep asking how to reserve or when lunch ends, the website may need a clearer answer. That is a decision about your published information, not a reason to send the same automatic reply to every guest.
Put review and privacy rules in writing
Check the privacy terms of a tool before putting guest names, phone numbers or reservation details into it. Do not paste customer personal data into tools you have not checked. Use sample enquiries without real guest information to test the wording, then decide where approved replies should be kept.
Read each outgoing message for accuracy and tone. A tool can write confidently about a menu item that no longer exists, or make a complaint sound dismissive. Keep a person in the loop for anything sent to guests, and give staff a clear route for questions the prepared answers cannot resolve.
Begin with one common question about hours or reservations. Compare a draft with what a staff member would say today. If it needs repeated corrections, improve the source information or use a simple saved answer instead. The final decision about food, service and what to tell a guest stays with the team.