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 consultation tomorrow? Assistant: Which department and clinic location? Please do not share medical reports here. Assistant: What time range would you prefer? Reception will confirm the appointment request. Assistant: For an emergency, contact local emergency services directly.
Prepare the knowledge behind the words
The task is reducing administrative uncertainty about location, hours and the next reception step. Do not diagnose, interpret reports, recommend treatment or decide urgency from a general website conversation. Collect minimal scheduling details and establish an appropriate retention process before deployment. A helpful administrative reply should not require a patient to disclose sensitive history.
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 or department?
- New appointment or administrative question?
- Preferred day or time range?
- Contact method for reception?
- May reception confirm availability?
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 urgent symptoms, a pasted medical report and an unavailable specialist. The assistant should avoid medical conclusions, explain the appropriate contact route and never confirm an unverified slot.
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.