A travel agency chatbot should collect six things before handing over to an agent: travel dates (or flexibility), who is travelling, a budget range, the kind of trip or interests, how the visitor wants to be contacted, and one open line about anything the agent must know. It should not quote prices, promise availability or take payment details.
The aim is to give the agent a half-finished brief, not a cold lead. An agent who opens a message that says "two adults, 10 nights in late May, around $4,000, beach with some walking, reply by email" can start working. An agent who opens "interested in holidays, call me" must start from nothing, and by then the visitor has probably messaged a competitor.
The fields, in the order to ask them
Order matters because visitors drop out. Ask what the agent needs most, and what is easiest for the visitor to answer, first. This is the order I would use, with the reason for each.
| # | Field | Why the agent needs it | How to ask |
|---|---|---|---|
| 1 | Destination or kind of trip | Decides which agent or supplier list applies | "Do you have somewhere in mind, or a kind of trip?" |
| 2 | Dates, or how flexible they are | Peak weeks change everything | "Roughly when, and could you move by a week?" |
| 3 | Who is travelling | Room types, transfers, family fares | "Who is going: how many adults, and any children and their ages?" |
| 4 | Budget range | Filters out options that cannot work | "Do you have a total budget in mind, even a rough range?" |
| 5 | Interests and must-haves | Shapes the proposal | "What would make this trip great? Anything you want to avoid?" |
| 6 | Contact and best time | Makes the hand-over possible | "What's the best email or number, and when should we reach you?" |
Move contact details up to the second question if your chat tool allows the visitor to leave at any point. A partial brief with a contact is worth more than a perfect brief without one.
Why ask for a budget at all
Visitors dislike this question, and agents need it. "What is your budget?" feels like a sales screen. Reframe it as a range, as a choice among bands, or as what the trip includes. For example: "Roughly what would you like to spend for everyone, including flights? Even a band helps: under $2,000, $2,000 to $4,000, or more." Offering bands lowers the effort and the discomfort.
If the visitor declines, the bot should accept that without pressing. Record "budget not given" and move on. An agent can ask on the phone, where the conversation is warmer.
Be clear about currency. If you serve visitors who may quote their own currency, ask for it: "In which currency?" A figure with no currency produces wrong proposals.
A worked example: a honeymoon enquiry
An illustrative case for a small agency specialising in beach and island holidays. A visitor opens the chat on a Sunday evening when nobody is in the office. The conversation, simplified:
Bot: Hi, I'm the agency's AI assistant. I can take down your trip ideas so one of our agents can come back to you with options. Do you have somewhere in mind?
Visitor: Honeymoon, somewhere warm, not too touristy
Bot: Congratulations! Roughly when are you thinking of going, and is there any flexibility?
Visitor: Late September, maybe 10 days
Bot: Lovely. Is it just the two of you?
Visitor: Yes
Bot: Do you have a total budget range in mind, including flights? Even a band helps.
Visitor: About 6 to 7 thousand dollars
Bot: Thank you. What would make it perfect, and is there anything you'd like to avoid?
Visitor: Quiet beaches, good food, snorkelling. No big resorts.
Bot: That's very helpful. What's the best email, and when should an agent reach out?
Visitor: [email], mornings
Bot: Thank you, [first name]. I've passed this to the team. An agent will email you with ideas on Monday morning. I can't confirm prices or availability myself, so they'll check that for you.The hand-over note the agent receives, built from the same conversation:
| Field | Captured |
|---|---|
| Type of trip | Honeymoon, warm, quiet |
| Dates | Late September, about 10 nights, flexibility not stated |
| Party | 2 adults |
| Budget | $6,000 to $7,000 total including flights |
| Interests | Quiet beaches, food, snorkelling; avoid large resorts |
| Contact | Email, mornings; reply promised Monday morning |
The agent can open this and send a first proposal without a question back, apart from flexibility on the dates. That one missing field is a useful thing to notice: the bot did not ask a follow-up on flexibility because the visitor gave dates without being prompted. Add a rule: if dates are given, ask once whether they can move by a few days.
Hand-over rules: when the bot stops collecting
A chatbot that keeps asking questions after someone has asked for a person is a way to lose enquiries. Write explicit hand-over rules and test them.
- Visitor asks for a person. Hand over at once with whatever has been collected, and say so plainly: "I'll pass this on now with what I have."
- Visitor mentions a deadline. A trip in under 14 days, a flight they must change, a booking they already have. Flag it as urgent and, if an agent is on, escalate immediately.
- Existing booking. Any message about a booking they have already made goes to the service team, not the sales hand-over. Ask for the booking reference and the name it is under, nothing else.
- Complaints, cancellations and refunds. No bot answer. Collect the booking reference and hand over.
- Health, visas and entry rules. The bot does not advise. Say that requirements depend on the traveller and the destination, and that the agent or the official source will confirm.
- Group, corporate or event requests. Mark as a group enquiry and hand over, collecting size and dates only.
- Visitor frustrated or stuck. Hand over after two failed exchanges.
If nobody is available at the moment of hand-over, state the next working time in the bot's last message, not a vague "soon". Promises you cannot meet are what turn a convenient chatbot into a complaint.
No price promises: the rule and the wording
This is the part I would put in capital letters in the setup. Travel prices move constantly, depend on supplier availability and often include taxes and fees added late. A chatbot that says "that trip costs around $3,000" has made a statement the agency may have to honour, or has at least set an expectation that the agent then has to undo.
Instruct the bot with specific bans, not general caution:
You never state, estimate or imply a price, a discount or a "from" price for any trip, hotel or flight.
You never say a trip, flight, room or date is available, confirmed, guaranteed or "sold out".
If asked about prices or availability, say: "Prices and availability change quickly, so one of our agents will check this for you. Could I take a few details so they have what they need?"
You may repeat a budget the visitor gave you, as their budget, not as what a trip costs.The last line avoids a quiet trap: if a visitor says "I have $5,000" and the bot replies "that should cover it", it has implied a price. Teach it to say "I've noted $5,000 as your budget" and nothing about whether it is enough.
The same applies to recommendations. If the bot names a hotel or destination, the visitor reads that as a suggestion from the agency. Either forbid recommendations or limit the bot to a short list the agency has chosen to promote, with each item written by a human. For wider guidance on stopping a bot over-promising, see the guardrails tutorial.
Five more conversations and what to capture
The six fields flex across trip types. Here is how the questions change for five different visitors, as illustrations.
A family of five in the school holidays
Ages of the children matter more than the number. Ask for each child's age at the time of travel, because it changes rooms, fares and some activities. Dates are usually fixed by school, so ask "are the dates fixed?" instead of "are you flexible?".
A retired couple booking a river cruise
Mobility and pace matter, and many want to phone. Offer a call as the first choice for contact, ask gently about mobility needs as a "does anyone in the party need step-free access or a slower pace?" and mark the lead as phone-first.
A business traveller adding leisure days
Fixed meeting dates, company policies and a booking tool come into it. The bot should collect only the meeting dates and the extra days wanted, and hand over; the agent decides what the policy allows.
A group of eight friends for a birthday weekend
This is a group enquiry. Collect group size, rough dates, a rough per-person budget and a lead contact. Ask whether everyone has agreed dates, because the agent needs to know whether this is a firm plan or a conversation.
A visitor who asks only "how much is a city break?"
Do not answer with a price. Ask what they want from the trip, how many nights and how many people, then hand over. The visitor who asks about price first is often the one who values a quick, honest reply the most.
The opening message and the consent line
The first thing a visitor reads decides whether they answer six questions or close the window. Keep it short, say what it is, say what it will do with the answers, and let them out.
Hi, I'm the agency's AI assistant. Tell me a little about the trip you're planning and I'll pass the details to one of our agents, so you don't have to repeat yourself. You can skip any question, or ask for a person at any time.Three things are packed in there: it is an AI, it has a purpose that benefits the visitor, and it has an exit. Before asking for contact details, add a plain line about use: "I'll share your details only with our agents, to reply to this enquiry." Check the line against your own privacy notice, and ask your data-protection adviser if you are unsure what you must say. If your chat tool stores transcripts, say so in the privacy notice and decide how long you keep them. A year-old chat with a phone number in it is a liability, not an asset.
Keep personal detail to a minimum. The planning fields above do not need a date of birth, an address or a passport number. If a visitor volunteers special needs or a medical condition, the bot should pass it to the agent as typed and not repeat it back or comment on it.
A mistake that cost a lead, and the fix
An illustrative failure, built from the kind of thing that happens when the flow is not tested. A small agency's bot asked for contact details last. A visitor answered four questions, got to the fifth, saw "Could you share your email?" and left because they wanted to see options first. The agent received a transcript with no way to reply. Nothing in the logs flagged it as lost.
The fix was two changes. First, the bot asks for contact after the second answer, with a reason: "So an agent can send you ideas, what's the best email?" Second, a rule that any conversation with at least dates and a party size but no contact is flagged for the weekly review, so someone can see how many near-leads are disappearing. Within a few weeks the rate of leads with contact details rose, which is the figure to watch.
This is the general lesson: a chatbot funnel loses people at specific points, and you only see where if you read the conversations. Looking at ten drop-offs teaches more than any setting.
One filled-in instruction to adapt
Below is a complete instruction for the collection job, written for a fictional small agency. Replace the bracketed parts and keep the structure. It sits inside whichever chat tool you choose, in the box usually called instructions or system prompt.
You are the website assistant for [agency name], a small travel agency. You are an AI. Say so if asked.
Your only job is to collect trip details for an agent. Ask one question at a time, in this order: type of trip or destination ideas; dates and flexibility; who is travelling (adults, children and ages); total budget and currency; interests and things to avoid; best email or phone and when to reach them. Ask for contact after the second answer if the visitor seems ready to leave.
Never ask for something the visitor has already told you. Let them skip any question. Accept a rough budget band.
Never state, estimate or imply a price, availability or a recommendation. Never advise on visas, health, insurance or safety.
Hand over immediately if the visitor asks for a person, mentions an existing booking, a complaint, a trip within 14 days, or a group of 8 or more. Collect only a booking reference, name and contact for existing bookings and complaints.
When finished, summarise what you have noted in a short list and say an agent will reply by [next working time]. Never promise anything else.Read it as a test of your own business: if any line is wrong for the way your agency works, change the line. The 14-day rule, for instance, depends on whether your agents can handle short-notice bookings at all.
Out-of-hours and weekend cover
The strongest case for a travel chatbot is the visitor who plans a trip on a Sunday night, when nobody is in the office. For that visitor the bot's job is narrow: capture the brief, set a time for the reply, and keep that promise. Decide three things in advance. Who checks the hand-over queue first thing on a Monday, and by what time they will have replied. Whether weekend enquiries get a different promise, such as "by the end of Monday" rather than "within two hours". And what happens on public holidays, when your normal rota does not apply.
It helps to send an automatic acknowledgement email straight after the chat, with the summary the bot collected. The visitor sees their own brief, can correct a wrong date, and has a written record of who will reply and when. Keep that email free of prices, offers and links to specific trips for the same reason the bot avoids them.
A small agency might also decide that some enquiries are not worth chasing in the same way. A one-line "how much is a holiday" with no dates, no party and no contact is a different animal from a full brief. Give the first kind a polite reply and a link to the agency's main enquiry form, and spend the agents' Monday mornings on the second kind.
Turning the conversation into a record
A transcript is not a lead. The value comes when the answers arrive in your inbox or CRM in the same shape every time. Aim for a structured summary with fixed field names, plus the full transcript attached.
If your chat tool can send a form-like summary, set its fields to match the table earlier. If it can only email a transcript, you can still ask an AI assistant to produce the summary. A prompt for this, to use inside a ChatGPT Project, a Claude Project or whatever assistant your agency uses:
Below is a chat transcript from a travel enquiry. Extract these fields and return them as a list: type of trip, destination ideas, dates and flexibility, number of adults, children and ages, budget and currency, interests, must-avoids, contact method and best time, urgency, and anything unclear. If a field was not given, write "not given". Do not guess or add suggestions.
[Paste transcript]Always keep the agent reading the transcript as well as the summary, at least in the first month. Summaries sometimes tidy away the detail that matters, such as "not too touristy" turning into "quiet". The human review tutorial shows a light way to keep that check in place.
Name the owner for each enquiry within the first minute. A shared inbox where "somebody will pick it up" is where leads go cold. Even a simple rule such as "the agent whose initial matches the visitor's destination region takes it" is better than none.
Testing the collection flow before launch
Run the bot yourself, then have a colleague run it as a difficult visitor. Score these cases.
- The cooperative visitor. Answer everything. Check that all six fields land in the summary.
- The one-word visitor. Reply with "beach", "May", "2", and nothing else. The bot should keep asking politely but let you leave after two refusals.
- The price demander. Ask "how much for a week on an island in August?" three times. The bot must never name a number.
- The over-sharer. Paste a long paragraph with all the details at once. The bot should extract them and ask only for what is missing, not start again from question one.
- The urgent traveller. Say you fly in five days. The record should be flagged urgent.
- The existing customer. Say you want to change a booking. The bot should route to service and not start a new lead.
- The sensitive question. Ask about visa rules and vaccination needs. The bot should decline and hand over.
- The identity check. Ask "are you human?" The bot should say it is an AI assistant. The disclosure tutorial has wording for the opening line.
The over-sharer test catches the most irritating failure: a bot that ignores what you already said and asks for dates after you gave them. If it does that, add an instruction: "Never ask for something the visitor has already told you in this conversation."
Measuring whether the hand-overs are good
You do not need a dashboard. Keep a simple tally for four weeks and review it with the agents.
- Completeness. Of the hand-overs received, how many had all six fields? If under half, shorten the flow or reorder the questions.
- Contact rate. How many left a way to reach them? A low figure means the ask comes too late or the reason is unconvincing.
- Time to first agent reply. The bot's advantage disappears if the reply takes three days. Set a target such as the next working morning.
- Agent corrections. Ask agents to mark hand-overs where the bot had something wrong. Each is a new rule.
- Conversion. Of the enquiries the chatbot passed on, how many became bookings? Compare with enquiries from the contact form, being careful that the two groups differ in size.
Say a small agency receives 30 chatbot enquiries a month and 18 leave contact details. If agents turn 4 of those into bookings with an average margin of $350 each, that is $1,400 of margin for the month from the chatbot channel. Illustrative numbers, but the sum shows what to compare against the tool's monthly cost and the agent time involved. If the cost is higher, the fix is usually fewer, better questions or a faster reply, not a cleverer bot.
If you want help deciding what your own agents need from a hand-over and how it should reach them, that is what the AI implementation consultation is for. For the step after hand-over, the tutorial on drafting itineraries with AI picks up where this one stops, and the itinerary checks tutorial covers what the agent must verify before anything goes to the customer.
Questions about travel chatbot hand-overs
How many questions is too many for a visitor?
Five to seven is a reasonable ceiling for a first conversation. Ask the fields in order of how much they help the agent, let the visitor skip any of them, and stop the moment they ask for a person. Contact details matter most, so ask for them early rather than last.
Should the bot ask for passport details?
No. Passport numbers, dates of birth and payment details do not belong in a chat on the first contact. Tell the visitor an agent will ask for what is needed through your normal booking process, and keep the bot to planning questions.
Can the bot say a trip is available?
No. Availability and prices change by the hour and depend on suppliers. The bot can say what it has noted and that an agent will check availability. Give it a ban on words such as available, guaranteed, confirmed and from-prices.
What if the visitor will not give a phone number?
Accept an email address, or a messaging handle if you use one. Offer a reason: an agent will reply with options rather than the visitor having to wait on the line. If they give nothing, the bot should still record the trip details and give your direct contact page.
Further reads
- How a One-Person Travel Agency Can Reply to Enquiries Instantly — Reply fast when one person runs the whole agency.
- How to Add an AI Chatbot That Captures Leads on Your Website — Add a lead-capturing chatbot to any website.
- Travel Agency CRM: What a Small Agency Needs and Where AI Helps — Choose the CRM the hand-over notes should land in.
- Best AI Tools for Travel Agents: Itineraries, Emails and Research — Other tools an agency can pair with a chatbot.
- What AI Costs a Small Travel Agency and What It Saves — What the full set of AI tools costs an agency.
- Travel Agent Follow-Up Emails: Chase Silent Quotes With AI — Chase enquiries that go quiet after the first proposal.
- AI Marketing for Travel Agents: A Month of Posts and Emails — A four-week content calendar, a destination fact-check table, a supplier claims check and a four-email sequence for travel agents.
- ChatGPT Prompts for Travel Agents: 10 for Quotes and Follow-Ups — Ten prompts for briefs, quotes and follow-ups, each built around your supplier figures, with worked output and the fact-checks to run first.
- How to Get Clients for a Travel Agency: Niche Content, AI Follow-Up — A niche scoring grid, a monthly content plan, lead capture and an AI-drafted five-email follow-up sequence for a small travel agency.
- Travel Agent Checklist: Pre-Departure Document Packs With AI — Build a pre-departure pack from booking data with AI: a grouped checklist, official-source pointers for visas, health and insurance, and checks before sending.
- Travel Industry AI Chatbot: What a Tour Operator Website Should Answer — What a tour operator's website chatbot should answer, look up and hand to staff: meeting points, cancellation wording, availability, refunds and safety.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: general travel-agency enquiry practice; vendor pricing pages were not needed for this tutorial.