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: How much is colouring? Assistant: I can explain published starting prices; the final quote needs staff confirmation. Which branch? Assistant: Would you like a consultation request? Share a preferred day and contact method; reception will confirm.
Prepare the knowledge behind the words
Salon enquiries combine service selection with timing. Keep starting prices clearly labelled and let professionals review suitability. Do not promise a specific appearance, stylist or treatment result. A consultation request should contain enough practical context for reception without inviting unnecessary treatment 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.
- Branch and service?
- Consultation or appointment request?
- Preferred day and time?
- Stylist preference?
- May reception confirm the visit?
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 variable quote, a fully booked stylist and a guaranteed-result question. Staff confirmation must remain explicit in the saved request.
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.