A restaurant receptionist needs a reliable source for ordinary guest questions. Separate stable facts from time-sensitive information, and give uncertain answers a defined owner rather than filling gaps with guesses.
Build the information sheet from real front-desk work: opening hours, address, entrance, parking, reservation process, walk-ins, takeaway collection and the restaurant’s current menu source. Add recurring questions that matter to your location rather than copying an unrelated restaurant’s FAQ.
Write answers in plain language. If a street entrance differs from the mailing address, describe the guest entrance clearly. If parking is operated by a third party, distinguish the restaurant’s verified information from guarantees it cannot make about spaces or prices.
Related Loman sources: Loman’s full-service restaurant phone workflows
Hours, menu availability, event closures and outdoor seating can change. Identify the source and owner for each item. A receptionist should know whether an answer is current, not simply whether some text exists in its knowledge base.
Use effective dates for temporary changes and test that they take effect. A holiday answer should not remain active afterward. If a real-time fact is unavailable, such as the current wait for a walk-in table, the flow should explain the limitation and offer the approved path to staff.
A dish description can be shared from the approved menu, but ingredient questions and allergy concerns may require a trained team member. The receptionist should not infer that a dish is safe from the absence of an ingredient in a short menu description.
Have staff define the escalation language and destination. Capture only the detail needed to route the question, and avoid promising that a dish can meet a requirement until the appropriate person has confirmed it. The same principle applies to unusual preparation requests that the kitchen must approve.
When a caller asks a question the sheet does not cover, route the request and log the gap for review. Repeated questions are a useful signal that the approved information should be improved. Do not automatically add an unverified answer from a caller’s suggestion.
Review the sheet with the people who know the operation: the host lead, kitchen owner and manager responsible for policies. Test a sample of ordinary questions and a deliberately unknown one. Good information handling includes knowing when the answer is not available and how to get the guest useful help.
Editorial operating guidance from Loman. The checklists are planning aids, not independent performance research or legal advice. Confirm your restaurant’s current policies and provider support.
Official Loman product information ↗Use your approved policy and exception scenarios when you evaluate Loman.
Discuss your receptionist workflow ↗