How Small Tour Operators Use AI for Bookings and Itineraries

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How Small Tour Operators Use AI for Bookings and Itineraries.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How Small Tour Operators Use AI for Bookings and Itineraries.

Let your booking system handle availability, payments and waivers, and use AI for the conversation around it: answering pre-booking questions so more people book direct, drafting private-tour itineraries from your own route notes, and writing pre-trip messages. Check every time, opening day and drive time in an AI itinerary before it reaches a guest.

Most small operators run two businesses under one name. Scheduled departures are a fixed product: the same walk or boat trip at set times, where AI's job is answering questions and sending messages. Private and custom tours are bespoke, and each one needs an itinerary and a quote. That second business is where AI saves the most time, and also where an invented detail can strand a group outside a closed museum.

Follow me on Instagram@sagnikteaches

Scheduled departures versus private tours: where AI helps

JobScheduled departuresPrivate and custom tours
Availability and paymentBooking system, alwaysBooking system or a payment link once agreed
Pre-booking questionsAI answers from your FAQ; hands over group and access questionsAI collects the brief: dates, group size, interests, mobility
ItineraryFixed; written onceAI drafts from your route library; a guide checks
QuoteFixed priceYour pricing sheet; AI writes it up
Pre-trip messagesScheduled templatesTemplates plus a personal note
On the dayWeather and meeting-point messagesSame, plus changes to the plan

Bookings: what the reservation system does and what AI adds

Your reservation system is the source of truth for what's available. Never let an assistant confirm a place that the system hasn't booked. The main systems are adding AI of their own. FareHarbor announced FareHarbor Agent in April 2026, an assistant that answers guests across phone, email, chat, SMS, Facebook, Instagram and WhatsApp, checks live availability, sends booking links and hands conversations to staff with the context attached; at announcement it was rolling out to a select group of operators. Peek Pro offers an assistant called Peek Copilot for content and back-office tasks, along with AI dynamic pricing. If you're on one of these systems, ask your account manager what's switched on for you before buying anything separate.

Connect on LinkedInSagnik Bhattacharya

The commercial case is direct bookings. Online travel agencies such as Viator and GetYourGuide bring volume, but take a commission on each sale, commonly reported in the 20% to 30% range; check your own supplier agreement for the actual figure. Many guests find you on an agency, then visit your website with a question before booking. If the question gets answered in minutes, they often book direct. That's the job for a website assistant trained on your FAQ, with a clear hand-over for groups, accessibility and private tours; adding a chatbot that captures leads on your website covers the set-up.

Subscribe on YouTube@codingliquids

Set the assistant's limits in writing before it goes live. It can answer from the FAQ, share booking links and explain the cancellation policy in your exact words. It hands over anything involving groups above your largest standard size, private tours, access and mobility, refunds, changes to an existing booking, and complaints. It never confirms a place, a pickup or a price that isn't in the booking system. Operators who skip this step usually discover the gap when a guest turns up quoting a promise nobody on the team made.

A typical version of that gap: a guest asks at night whether they can bring their dog on the coastal boat trip. The FAQ says nothing about dogs, so the assistant fills in from general knowledge ("well-behaved dogs on leads are usually welcome") and the family arrives with a spaniel for a boat that doesn't take animals. Two fixes, both needed. Add a line to the instructions: "If the FAQ doesn't answer the question, say you'll check with the team and hand it over." Then look at the handed-over questions each week and turn any that come up twice into a new FAQ entry, so the assistant can answer it properly next time. Dogs, buggies, toilets on board and card payment on the day are the ones that tend to appear first.

An illustrative before and after for a common question arriving at 10pm:

Question: is the harbour walk ok for a 9 year old and do we need to
book or can we just turn up

Before (answered next morning): Yes it's fine. Booking recommended.

After (assistant, within a minute): Yes, children from 8 are welcome
on the harbour walk, and under-12s are half price. It's 2.5 hours
with one steep section, and there's a coffee stop halfway. We do
recommend booking, as summer departures often fill: here's the link
to see tomorrow's times.

Boat, kayak and other activity operators have a different balance. Weather decides far more departures, capacity is fixed by the vessel or the number of boats, and minimum ages, swimming ability and waivers matter. Keep all of those rules in the booking system, not in the assistant's instructions: minimum age as a booking restriction, waivers signed at checkout, capacity set per departure. The assistant then explains the rules and points to the right departure, while the system enforces them. It also makes the weather messages more important than any itinerary, so drafting weather messages in advance, covered under pre-trip and on-trip messages below, matters most for these operators.

Collecting the private-tour brief

A private-tour enquiry usually starts with "we're four people, what would you suggest?" Before any itinerary can be drafted, you need a brief. Ask the assistant to reply to every private enquiry with the same short set of questions, and to summarise the answers in a standard format for you:

  • Dates, and how fixed they are. Opening days and seasonal closures depend on them.
  • Group size and ages. Children and older guests change the pace and the route.
  • Mobility and health. Steps, distances, time on feet, seasickness on boats.
  • Interests and must-sees. Food, history, nature, photography; anything they'd be disappointed to miss.
  • Pace. Full days or half days, early starts or late ones.
  • Where they're staying, for pickups and to keep travel time down.
  • Budget, or at least whether they're after a standard private tour or something special.

Enquiries rarely arrive in that order. Here is a real-sounding one, and the summary the assistant produced from it (both illustrative):

Enquiry: Hi, we're coming for my parents' anniversary end of April,
4 of us, would love something with good food and boats maybe? Dad
isn't great on hills. We're at the guesthouse by the market. Mon/Tue
probably but could do Wed.

Summary:
Dates:     late April, Mon-Tue preferred, Wed possible (confirm which)
Group:     4 adults, two older (anniversary: worth a personal touch)
Mobility:  "not great on hills" - ASK: walking stick? steps ok?
Interests: food, boats
Pace:      not stated - ASK
Staying:   near the market square
Budget:    not stated - ASK standard private tour or special

The useful part is the "ASK" lines. The assistant drafts the follow-up with only those three questions, so the guest isn't asked to repeat what they've already said. The anniversary detail is worth keeping in the brief even though it isn't a requirement: a guide who knows it can book the table by the window.

The brief in the itinerary prompt below came from exactly these questions. The mobility answer, one guest with a walking stick, is the one that changed the plan most, and it's the one guests often forget to mention unless asked directly.

A route library: the raw material for every itinerary

AI itineraries go wrong when the assistant fills gaps from general knowledge. The fix is to give it your own knowledge in a form it can use. Write one entry per route, stop or activity you offer. A filled-in illustrative entry:

ROUTE R-04: Harbour and old town walk
Duration:       2.5 hours including a 20-minute coffee stop
Distance:       4 km; one steep section (the stepped lane up to the church)
Start / finish: Harbour office / market square
Stops:          fish market (mornings only), lifeboat station, church
                tower (extra fee, closed Mondays Nov-Mar), old town gate
Seasonal:       fish market closed Sundays; lifeboat station open Apr-Oct
Accessibility:  two flights of steps; step-free alternative adds 15 min
                and skips the church tower
Good pairings:  R-07 (boat trip) in the afternoon; lunch at 1pm fits both
Guide notes:    busiest 11am-2pm on cruise-ship days; start at 9.30
Last checked:   March, by the lead guide

Twenty entries like this take a day or two to write, and they're the most valuable document in the business. They also make it easier to train new guides.

Keeping the library current is a once-a-year job the assistant can make shorter. Each spring, paste in the whole library and ask: "List every entry whose last-checked date is over 12 months old, every stop with a seasonal or day-of-week restriction, and every price mentioned. Group them by who should check them." An illustrative answer might list six stale entries, eleven seasonal stops and four prices, grouped into "lead guide to walk it", "phone or check the venue's website" and "owner to confirm". That's an afternoon's checking instead of a vague sense that the library might be out of date. Update the last-checked line as each entry is confirmed.

Drafting a private itinerary with AI

With the library in hand, a prompt like this produces a solid first draft:

Using ONLY the routes and stops in the attached route library, draft a
2-day private itinerary for this group:
[4 adults, two in their seventies, one uses a walking stick; interested
in food and maritime history; staying near the market square; dates:
a Monday and Tuesday in late April].
Include start and finish times, travel time between stops with a
15-minute buffer, lunch timing, and the step-free option where needed.
For every stop, note any day, season or opening restriction from the
library. If something isn't covered by the library, say so rather than
suggesting it.

An illustrative extract of what comes back:

DAY 1 (Monday)
09:30  Harbour and old town walk (R-04), step-free route, 2h45
       incl. coffee stop. Skip the church tower (closed Mondays).
12:30  Lunch near the market square
14:00  Boat trip along the coast (R-07), 1h30
16:00  Visit to the maritime museum (not in route library - suggested
       because of the group's interest in maritime history)

Three things to fix. The church tower note is wrong in the group's favour: it's closed Mondays only from November to March, so in late April it's open, though the step-free route skips it anyway. The fish market, which is the highlight for a food-loving group, is mornings only, and the draft doesn't mention it. And the maritime museum isn't yours to promise: the assistant flagged it, as instructed, but you'd still need to check its opening days and whether a tired group wants a fourth activity. For a deeper list of what to verify, what a travel agent must check in an AI itinerary applies almost line for line to operators.

The fact-check pass every itinerary needs

Before any itinerary goes to a guest, one person runs through a checklist. Filled in for the draft above:

[x] Every stop is in the route library or independently checked
[ ] Opening days and times checked for the actual dates  <- tower, museum
[x] Seasonal restrictions applied (lifeboat station open from April)
[ ] Travel times realistic on those days, with buffer    <- cruise-ship day?
[x] Mobility needs met on every stop (step-free route chosen)
[x] Lunch and toilet stops at sensible intervals
[ ] Weather alternative for each outdoor activity         <- boat trip
[x] Prices match the pricing sheet
[x] Meeting point, times and contact number correct

The unticked boxes are the work. The cruise-ship question is a good example of something only a local guide thinks to check: on those days the harbour walk runs slower and the lunch spots are full.

Turning the itinerary into a quote the guest can accept

Once the plan is checked, the quote comes from your pricing sheet, never from the assistant's sense of what tours cost. Paste in the sheet and the final itinerary, and ask it to write the quote with each line priced from the sheet and a total. For the two-day plan above, with illustrative rates:

LineFrom the pricing sheetAmount
Private guide, 2 days$380 per full day$760
Private boat trip, 1.5 hours$260 per boat, up to 6 guests$260
Fish market tasting$18 per guest$72
Total$1,092

In one illustrative draft, the assistant added a line "Senior discount (2 guests): -$36". The pricing sheet has no senior discount; the child rate for the scheduled walk had been generalised into a rule that doesn't exist. Guests remember a discount they were offered in writing, so catching it matters more than catching a typo. The check takes a minute: every line in the quote must match a line on the sheet, and anything else is deleted or becomes a deliberate decision by you. Ask for the deposit and cancellation terms to be pasted in word for word at the bottom, not summarised.

Pre-trip and on-trip messages

Scheduled messages from the booking system cover most of this: a confirmation, a reminder with the meeting point two days before, and a morning-of message. AI helps with wording and with the messages that can't be scheduled. A before and after for a meeting-point reminder:

Before: Reminder: your tour is tomorrow. Meet at the harbour office.

After: See you tomorrow at 9.30 for the harbour and old town walk.
We meet outside the harbour office: look for the guide in the green
jacket with the flag. Wear comfortable shoes (there's one steep lane)
and bring a layer; it's breezy by the water. Running late? Message
this number and we'll wait up to 10 minutes.

On the day, weather is the big one. The guide decides whether to run, move or cancel; the assistant drafts the message for each outcome in advance, so the guide sends the right one in seconds. The operator's cancellation policy should be quoted word for word, not paraphrased by the assistant. A "move" message prepared in advance for the boat trip might read (illustrative):

Tomorrow's 2pm boat trip can't run safely: the forecast wind is
too strong for the coast. We can move you to Thursday at 2pm or
Friday at 10am at no cost, or refund you in full. Reply 1, 2 or 3
and we'll sort it straight away. [Cancellation policy, verbatim]

Numbered replies matter when you're messaging 30 guests at once; you can process "1", "2" and "3" in minutes, whereas "maybe Thursday if my sister can come?" needs a conversation. The awkward case is the tour that runs in marginal weather while one family asks for a refund because they'd rather not. Decide your answer before the season, write it into the policy, and give the assistant that exact wording, so the reply on the day matches what the next family is told.

If you reply to lots of enquiries on your own, how a one-person travel agency replies to enquiries instantly has a workable routine.

A season's numbers for a two-guide operator

Say an operator with two guides runs a daily walking tour and a boat trip, plus private tours, and sells about 60% of scheduled places through online travel agencies. Over a season, roughly 3,000 guests book scheduled tours at $40 each.

Direct bookings. A website assistant answers questions within a minute, day and night, and hands private-tour enquiries to the owner. If the agency share drops from 60% to 50%, that's 300 guests moving to direct booking. At an illustrative 25% commission on $40, each direct booking keeps $10 more: about $3,000 over the season.

Private tours. Itineraries used to take the owner about 90 minutes each. With the route library and the prompt, a draft takes 10 minutes and the fact-check 20. Over 40 private tours, that's around 40 hours saved, and quotes go out the same day instead of later in the week.

How the operator knew it was working. Most reservation systems record where each booking came from. Pull the channel split every fortnight and compare it with the same fortnight last season, not with last month, because tour demand swings with school holidays and weather. Alongside it, count how many website conversations ended with a booking link clicked and how many were handed over. If hand-overs stay high after a month, the FAQ has gaps; if links get clicked but direct bookings don't rise, the problem is the booking page itself, often a checkout that asks for too much before showing a price.

Costs. A general assistant at about $20 a month for ChatGPT Plus or Claude Pro, the website assistant's own fees, and two days writing the route library. If you're weighing up the wider budget, what AI costs a small travel agency gives a comparable breakdown.

Five ways tour bookings and itineraries go wrong

  • Invented stops. Without a route library, assistants add attractions that sound right, some of which have closed or never existed. Restrict drafts to the library.
  • Stale opening times. The library is only as good as its "last checked" date. Recheck seasonal entries every spring.
  • Overbooking across channels. If agency availability doesn't sync live with your system, an assistant sending booking links can compound the problem. Check the connection before blaming the AI.
  • Promises the guide can't keep. "Private boat to the island at sunset" reads beautifully and may not be possible. Guides should read itineraries before guests do.
  • Drive times from a map on a quiet day. Add buffers, and ask a guide about the days that are never quiet. How independent travel agents draft itineraries faster covers more of the drafting habits that prevent this.

Tour operator questions about AI

Can AI translate itineraries and messages for international guests?

It does a good first draft in most major languages, and it's far better than no translation. For anything safety-related, such as meeting points, what to wear, cancellation terms and emergency contacts, have a fluent speaker check the translation once, then reuse the checked version. Keep place names and times exactly as in the original.

Should I let AI change my tour prices automatically?

Some booking systems now offer AI dynamic pricing that adjusts prices by demand. It can help fill quiet departures and lift busy ones, but set a floor and a ceiling, keep private-tour pricing under your control, and watch how it interacts with online travel agency rates. Try it on one tour for a season before switching it on everywhere.

Can AI decide whether to cancel a tour for weather?

No. It can summarise the forecast and draft the messages for either decision, but the call belongs to the guide or owner who knows the route, the group and the conditions. What AI does well is speed up the part after the decision: messaging every guest with clear options within minutes.

Further reads

Sources: FareHarbor announcement of FareHarbor Agent (April 2026); Peek Pro product pages; operator-facing guides on online travel agency commission, checked September 2026.

Want your tour bookings and itineraries sorted?

On a 1:1 call we'll look at how bookings reach you, what your reservation system already automates, and set up a route library and itinerary prompt your guides can trust.

Book a 1:1 call with me