Copy this conversation flow
This text can be copied and adapted. It is not a one-click imported bot or an automated connection to a booking, order or CRM service.
Visitor: A table for six on Saturday? Assistant: Which location and preferred time? I can collect a request; it is not confirmed. Visitor: One guest has an allergy. Assistant: Discuss the requirement directly with staff before dining. May they contact you?
Prepare the knowledge behind the words
Distinguish a simple hours answer from a request requiring capacity approval. Group meals need enough context for a manager to assess arrangements. Menu wording is not an allergen safety guarantee. Do not collect unnecessary health details or claim the widget operates an order or reservation system that has not been connected.
Fields to consider for the enquiry
Remove any question that is not needed for the promised follow-up. Explain who will contact the visitor and let them decline without losing access to ordinary information.
- Which location?
- Dining, event or takeaway question?
- Guest count and date?
- Would you like a reservation request?
- May staff contact you?
Branch rules to write down
- If the visitor asks a supported factual question, answer before requesting contact.
- If essential information is missing, ask one clear question at a time.
- If the visitor declines contact, acknowledge the choice and offer the public information route.
- If the request needs approval, label it as a request and explain who confirms it.
- If knowledge is missing, say so and offer the appropriate team contact.
Acceptance checks before you use the template
Test a closed day, a full dining room and a request for an allergy guarantee. A reservation request must not receive a fictional confirmation number.
Read the resulting enquiry from the perspective of the person replying. Does it show the latest requirement and the promised next step? Test on a narrow phone screen and check that a person can close the widget and use the alternative contact route.
Maintain the flow when your business changes
Review the approved knowledge after a policy, service or schedule change. Keep one current version of the template and remove contradictory examples. Record the purpose of each question so future edits do not turn a short request into unnecessary data collection.