TripWorks' AI assistants can take a complete booking on their own. Both the website chatbot and the phone callbot check your live availability, collect the guest's details, create a draft booking, and text the guest a payment link they pay through your normal TripWorks checkout. The assistant never handles the money itself — it hands the guest to the same secure checkout as any other online booking.

This page explains what happens under the hood, why it's safe, and how AI bookings show up in your account.

What "an AI booking" actually is

An AI booking is a reservation that a customer starts and completes by talking to an assistant — typing in the website chat, or speaking to the callbot on the phone — instead of clicking through your booking widget.

Both assistants run on the same booking engine, so the mechanics are identical no matter which one the guest uses:

• The assistant reads your live experiences, availability, and pricing straight from your account.
• It creates the reservation as a draft — held, not paid.
• The guest pays with a link, through your standard checkout.

The only real differences are the channel (web chat vs phone) and how the booking is labeled afterward, covered below.

The booking flow, step by step

1. The guest states intent. "I'd like to book the sunset kayak tour for two this Saturday."
2. The assistant checks live availability. It looks up real times and prices from your account for that experience and date. Closed timeslots, sold-out times, and slots you don't sell online are filtered out automatically, so it only ever offers something a guest could actually book.
3. The guest chooses. They pick a time and the number of guests; the assistant confirms what's available at that size.
4. The assistant collects details. Name, email, and phone number — the minimum needed to hold the reservation and send a payment link.
5. TripWorks creates a draft booking. The reservation is written to your account in draft status — it's holding the spot's intent but isn't confirmed, because no payment has happened yet.
6. The guest gets a payment link by SMS. TripWorks texts the guest a link to complete payment.
7. The guest pays, and the booking confirms. Payment runs through your normal checkout; on success the booking is confirmed and appears alongside your other reservations.

A worked example

A guest tells the chatbot they want a private fishing charter for four on July 12. The bot checks availability, sees the 7:00 AM charter is open, and confirms the price for four. It collects the guest's name, email, and phone, creates a draft, and texts a payment link. The guest taps it, pays, and the charter is confirmed — with no staff involvement and no back-and-forth email.

Chatbot vs callbot: how the booking differs

The booking flow is the same; three things differ by channel.

Because the two are tagged separately, you can always tell — and report on — which assistant drove a booking. See set up the chatbot and set up the callbot.

Why AI bookings are safe

Letting AI take a booking sounds risky until you see where the guardrails are. The design keeps the assistant away from anything it could get wrong.

• The AI never processes payment. It creates a draft and sends a link; the guest pays through your standard TripWorks checkout. Every protection you already have — CVV, AVS, 3D Secure, and fraud monitoring — applies exactly as it does for a direct website booking. There is no path that bypasses them.
• The final price is calculated at checkout, not by the AI. The assistant quotes from live data, but the amount the guest actually pays is computed by your checkout when they pay — so a stale or misread number can't turn into a wrong charge.
• Live data, never cached. Availability, pricing, and experience details are pulled from your account in real time, so the assistant can't offer a sold-out slot or an old price.
• No made-up answers. The assistants are instructed never to invent pricing, availability, dates, or details. If they don't know something, they say so and point the guest to you.
• Scoped to your account. Every conversation only sees your account's data — never another operator's or another customer's.

What happens if the guest doesn't pay

Nothing is charged until the guest completes the payment link, so an unpaid booking simply stays a draft. That draft follows your standard abandoned-cart flow, so you can follow up the same way you would with any half-finished online booking. Any contact details the guest shared are attached to it. For the callbot, callers who never book can also be captured as leads in Lead Center (if you enable that capability), so a missed booking still becomes a follow-up opportunity rather than a lost one.

What the AI can and can't do

• Can: answer questions from your Knowledge Base and live experience details, check real-time availability and pricing, and create new bookings with a payment link.
• Can't: modify or reschedule an existing booking. If a guest wants to change a reservation, the assistant directs them to your team. It also can't take payment itself or override your checkout rules.

How AI bookings appear in TripWorks

AI bookings are ordinary reservations in your account, with one extra signal: a source tag of AI Chat Bot or AI Call Bot. That means you can filter, report, and reconcile them like any other booking, while still seeing exactly how much revenue your assistants are generating. Chat conversations are reviewable under chatbot history, and calls under callbot call history.

Frequently asked questions

Related

• Set up your AI Chatbot
• Set up your AI Callbot
• AI Chatbot & Callbot FAQ