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: Five days in Thailand for two. Assistant: Which month, departure city and budget range? Assistant: Packages are examples; price and availability need confirmation. Please do not share passport details. Assistant: May an adviser contact you?
Prepare the knowledge behind the words
Preserve dates, party size and itinerary priorities for an adviser. Explain published inclusions without inventing fares, hotel availability or entry permission. A date change can alter the applicable quote. Existing-booking changes need the verified support route, while a new itinerary request needs a clear proposal process.
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.
- Destination and dates?
- Party size and duration?
- Leisure, business or group trip?
- Budget and priorities?
- May an adviser 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 last-minute travel, an expired promotion and a visa guarantee. The assistant should acknowledge knowledge limits and avoid requesting sensitive travel documents.
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.