# AI chat on a tour booking website: what it should answer and when it hands off to you

What an AI chat on your tour booking website should answer, when it passes a guest to a person, what that message says and how each answer leads to a booking.

Published 2026-11-21. By [Drew Sainte Marie](https://tourboss.ai/about-us/).

AI chat on a tour booking website should answer from the trip details and policies you've approved, then point the guest to the right booking page. When a question needs a person, the chat says who will reply and when, and passes along everything the guest has already typed.

At 9 pm, a guest asking a kayak shop's chat where to park can get the directions and a link to the trip they asked about. If the chat can't help, they shouldn't be left staring at the screen for a reply that won't come until morning.

## Find the page behind each answer

Pull your last 50 guest messages and, for each routine question in them, find the page or written reply you'd want the chat to answer from.

Meeting instructions have to come from the tour named in the conversation. Two of your food tours might mention the same neighborhood, and the chat still can't borrow directions from one for a guest asking about the other.

Parking goes in that same reply, with enough detail to get the guest from the car to the meeting spot.

Departure times take more care, since the seats left to book won't always match the published schedule. Label the timetable as a schedule when you load it, and if the vendor says the chat reads live availability, have them show you.

Put your approved cancellation wording with these answers too, word for word as the confirmation email has it, so guests read the same terms in the chat and in their inbox.

For questions your material doesn't cover, write the exact message the chat sends when it offers to bring in a person.

## Answers you'd sign off on at the desk

The vendor claims in this post come from each vendor's own page, as of November 21, 2026.

[Tidio's Lyro page](https://www.tidio.com/lyro/) says Lyro works only with content you provide and passes a question to a human when that content doesn't have the answer. In the demo, test that with a question you know is missing from your notes.

[FareHarbor's agent page](https://fareharbor.com/scale/fareharbor-agent-ai-powered-guest-communication/) says it uses real-time availability, tour details and policies. FareHarbor also says you set the rules for which complex or sensitive questions get passed along.

Before you shop for a new tool, ask your booking provider what your account already has.

### Write it the way your front desk would say it

Work from the replies you already trust and cut each one to two or three sentences.

For a boat tour, put the meeting spot and the arrival time ahead of any welcome speech.

Say each answer out loud. Anything you'd trim on the phone can come out of the chat version too, as long as the guest still has what they need to get there. Where leaving out the tour name could cause a mix-up, keep it in.

### When a departure time changes

A chat can keep giving last month's start time long after you've fixed the page. So pick one page or document as the home of each current answer, and on the day a departure time changes, update every other place that uses it.

Then ask the chat for the new time yourself, because a corrected page won't help if the reply still gives the old one.

Check that answer against checkout and the confirmation email as well. Settle any difference before a guest has to ask which one is right.

The [website design guide](/travel-website-design/) covers the page itself. The chat's answers need to match the wording guests find there once they leave the conversation.

## What the guest sees when your team takes over

Group quotes and private-trip requests go to your team. So do complaints, safety questions and anything about money owed, like refunds or a payment that didn't go through. We cover which decisions to keep with people in [AI agents for tour operators](/digital-marketing-for-tourism/ai-agents-for-tour-operators/).

### Write the message on the screen

Write this message before anyone sets the chat up, and once they have, ask to see it in the real chat window. Here's a draft to adapt. Fill the brackets with details you'll stand behind, and only use it once you've confirmed the request reaches the right person:

> “I've passed your request to [staff role], along with this conversation. You'll hear back by [day and time, with time zone] through [how you'll reply]. You don't need to send those details again.”

If all that arrives on your end is a name and a phone number, that last sentence is false, so fix what gets sent before the message goes live.

If the reply will come by email, the chat should say so, and the guest will know it's safe to close the window. If you're going to call, have the chat confirm the number.

### Promise a time you can keep

“Someone will be with you shortly” sounds fine until nobody is at the desk. After hours, the message needs to give the next time you can actually reply.

Agree on that time with your team, and allow for the hours they're out on trips.

Send the chat a test question after closing. Any wording that makes it sound like someone is about to join needs to change, because that request will sit until you're back.

### Ask for missing details once

A group request needs the date, how many people are coming and a way to reach the guest. Anything they've already given in the chat travels with the request, and the chat only asks for what's missing.

To test it, ask for 14 places on a food tour. Put the date in your first message and the group size in the next, and watch for a form or reply that asks for them again.

With a private trip, only ask about the occasion if knowing it helps you prepare the answer.

Once the request is in, the chat should show the guest a line confirming it went through. On your side, the whole conversation comes with it, including any change the guest made along the way.

### Open the request where it lands

[Fin's own description](https://fin.ai/) says it passes customers to your human team with their context intact. Ask to see where that conversation lands and what your team can read when it gets there.

Log in on the account your team answers from and open the request from the alert they'd get, so you see exactly what arrived.

Look for which tour was discussed, the guest's own question and how to reach them. Read far enough to catch any correction to the date or party size.

Then reply to the test request from that account, and check that it reaches you the way the chat promised.

## A useful answer still needs a way to book

End each reply the way you'd end it if the guest were standing at your desk. After the parking directions, that could be a short line inviting them to pick a departure.

### Link the tour they asked about

A home page with every trip on it is the wrong place to send someone who just asked when the food tour starts. They've told you what they want, so offer that tour's booking page and put the tour's name in the link.

Follow it from the chat and make sure the page it opens shows the same tour name.

### Name open departures only from the live calendar

If the chat can't see your live calendar, it shouldn't offer a specific open time. In the demo, ask for the next opening and compare the answer with your booking calendar. If there's no live connection, have the reply send guests to the tour's dates so they can pick a time themselves.

### If they gave the number, use it

Asking “How many people?” makes sense when the next step depends on party size, and only if the guest hasn't already said.

Once a guest has what they need to book, send the link. Another question between them and checkout is only worth asking if the answer changes where you send them.

Ask the vendor whether the chat can take a payment or hold a seat, and have them show you. If the chat stops at the link, its reply should tell the guest to finish the booking in checkout, and leave out anything that suggests their places are held before then.

Sort the questions from your 50 messages the way this table does.

| Guest question | Chat answers | Hand to your team |
|---|---|---|
| What time do you start? | Posted time, verified openings | Anything it can't verify |
| Where do we park? | Approved directions | Gaps in the notes |
| Is it running tomorrow? | Policy and update time | Departure decision |
| Can my 5-year-old come? | Posted age limits | Exceptions or safety |
| Can I get a refund? | Written policy | Every refund request |
| We're 14 people. | Collect date and group size | Price and space |
| This wasn't what we booked. | Acknowledge receipt | Whole conversation |

## A guest asking what to wear has mostly decided

Before Tour Boss, Drew Sainte Marie ran his own tour boat company. One question for him: when a guest asks something simple, like parking or what to wear, what should the reply say next?

> "When somebody asks what to wear, they've already pictured themselves on the boat. That's a person who's mostly decided, so I'd answer it like they're coming. 'Bring a light jacket, it gets breezy once the sun goes down.' Then I'd ask one easy question about their trip, like, 'Are you thinking about tonight or later in the week?' Their answer tells you which departure to point them to. If you can see the calendar, give them a real time and the link. If you can't, send the link to that trip's dates and stop there. The mistake I'd watch for is the answer that ends with a period. The guest got what they asked for, said thanks and went off to look at someone else's tour. I'd want a chat to do what a good person at the desk does. Answer the question, then help them pick a time."
>
> Drew Sainte Marie, founder of Tour Boss

## Test the reply after the easy answer

Run these on your own phone before guests ever see the chat, and keep each conversation going past its first reply.

1. Ask for meeting and parking instructions and check the whole reply against the right tour page. It should close with one easy question about your plans, so answer it and follow whatever next step it offers.
2. Send a group request after hours and read the exact message that comes back, which should say when and how you'll reply without hinting that someone is about to join the chat.
3. Give the date and group size before you ask for a person. Both should already be there when you open the request on your end.
4. Close the chat and come back later to see what's still on the screen and what it remembers. If the earlier exchange is gone, take out any wording that promises the conversation will pick up there.
5. Halfway through, switch from one tour to another, then follow the booking link through checkout and confirm the tour and any date offered match the latest part of the conversation.
6. Have your team answer the test request. Look for that reply where the chat said it would come, then go back to the chat and make sure nothing there still has you waiting for another response.

Fin says its testing tools include simulations and manual inspection before settings go live. Use something like that if your tool has it, and still read the replies on your own site.

For the first two weeks, read every conversation, even the ones that ended with a correct answer and no booking step. Where a reply leaves the guest with nowhere useful to go, rewrite its last line.

For each request you took over, compare the reply time the chat promised with when the answer actually went out. Look for guests who had to repeat things they'd already typed.

After those two weeks, put a weekly review on your calendar, and add any changed prices and policies to the next round of test questions.

## Get the replies ready before the chat goes live

The person setting up the chat needs two things from you: the message guests see when you take over from the chat, and the reply times you've agreed on. Ask them to walk you through one after-hours request all the way to the answer.

If your provider's chat can't do this, our [tools for operators](/tools-for-operators/) page has other options.

## Questions

### Can an AI chat book tours for me?

Only if the vendor can show you a finished booking on one of your own tours, with the booking sitting in your calendar afterward. A chat that only sends a link leaves the guest to finish in checkout.

### What should the chat never answer?

It should never decide a refund, approve a safety exception or make the weather call. Send complaints and group pricing to your team too.

### Will a chat bot hurt my reviews?

It can, if it gives wrong directions or leaves a request sitting with no reply. Before launch, test what it tells guests when it passes them to you, and keep reading conversations after that.

### How do I teach it my own policies?

Give it your approved wording, the same wording your confirmation emails use. Then check its replies against that wording, and make sure the requests that need your team actually reach them.

## Keep learning

- [AI agents for tour operators: what to automate first and what to keep human](https://tourboss.ai/digital-marketing-for-tourism/ai-agents-for-tour-operators/): Which jobs to hand an AI agent first at a tour company, from missed-call texts to review reply drafts, and which guest messages to keep with a person.
- [Will booking software get you more tour bookings? What it does and what fills the calendar](https://tourboss.ai/digital-marketing-for-tourism/will-booking-software-get-more-tour-bookings/): Booking software takes bookings and payments, but it doesn't bring guests. See what it does well, where bookings come from and how to get more direct ones.
- [SEO for Tour Operators: A Plain Guide for Tour Companies](https://tourboss.ai/digital-marketing-for-tourism/grow-tour-business-seo/): How a tour company gets found on Google: keywords, tour pages, your Google listing and links. It has a checklist and what to ask an SEO company.

Drew Sainte Marie. Drew has spent 26 years running guest experiences, 15 of them owning his own tour companies. [About Drew](https://tourboss.ai/about-us/)

## Want us to handle your SEO and AI search?

That's what we do for tour, charter and adventure companies.

[See how we work](https://tourboss.ai/digital-marketing-for-tourism/)

Ready to talk? [Book a free call](https://tourboss.ai/strategy-session/)

---

Tour Boss is a digital marketing agency for tour, charter, activity and adventure companies, specializing in SEO and AI search. It was founded by Drew Sainte Marie, a tour operator with 26 years running guest experiences. We serve boat charters, boat rentals, helicopter and aerial tours, adventure experiences, horseback riding, RV rentals, snowmobile tours and private jet charters. We start with Month One, a 30-day fix with a before-and-after report and no long-term contract. After that, you pick a month-to-month plan or stop and keep everything we built. Based in Austin, TX 78702. Not affiliated with tourboss.app.
