Run Your Day by Asking: TripWorks Now Works With Claude and ChatGPT

Most operators assume an AI assistant is something you use next to your booking software. You ask it to write a tour description, then switch tabs and paste the result in. But the assistant has never seen your guests, your calendar, or your call log, so it can only guess.

That changes when you connect it. TripWorks now works with Claude, ChatGPT, Gemini, and Google Antigravity, so you can ask a question about your own account and get an answer from your real data. This article explains what the connection is, what it can do for you, and how to tell whether it's the right tool for the job.

What does it mean to connect an AI assistant to TripWorks?

It means your assistant can look things up in your account, and make certain changes, on your behalf. The connection uses MCP, the Model Context Protocol, an open standard for linking AI assistants to the software you already use. You turn it on once under Setup, Integrations, paste one web address into your assistant, and approve the connection with your normal TripWorks login.

From then on you just ask. “Find guests named Rivera.” “How many customers do we have?” The assistant picks the right tool, runs it, and tells you what it found.

Which parts of my account can an assistant work with?

Quite a lot of the day-to-day back office. On the look-up side, an assistant can read your experiences, locations, customers, booking restrictions, promo codes, trip sources, team members, phone calls, and audit log. It can also search across trips, bookings, customers, gift cards, payments, resellers, and voucher codes by keyword, and it can total up or average values across your customers, experiences, and calls.

On the change side, it can create and edit experiences, locations, and booking restrictions, and edit customers. Every change starts as a preview. Nothing is saved until you confirm it.

Picture a museum manager asking for every timed-entry experience with a group minimum. Or an aquarium owner asking who changed a ticket type yesterday, and getting the person, the time, and the exact fields that changed from the audit log. Or a kayak outfitter asking for last week's phone calls, including the ones handled by the AI callbot. Those are questions that used to mean opening three screens and a report.

Should I use this, Zapier, webhooks, or the REST API?

The useful question is who, or what, is doing the work. An assistant connection is built for a person in the loop: someone asking a question or making a quick change and reading the answer. The other options are built for software that runs on its own.

If you want something to happen automatically every time a booking comes in, that's a job for Zapier if you want no code, or webhooks if you're sending data to your own system. If you're building custom software on top of TripWorks, that's the REST API. And if you just want to ask your account a question, or tidy up a handful of records, connect an assistant. Most operators will end up using more than one, because they answer different needs.

How does it keep my data safe?

The assistant runs as you. It can see and do only what your own permission group already allows, and never more. If you can't open the Locations setup screen, your assistant can't list or change locations either. Someone moved to a group with less access loses that access in their assistant too.

You also get a second control. When you approve the connection you choose Read access, Write access, or both. Leave Write unchecked and the assistant can look but never touch, even if your permissions would allow edits.

Turning it off is one switch. Disable MCP under Setup, Integrations and every connected assistant stops working right away.

There is one thing to weigh honestly. Whatever your assistant looks up is passed to that AI provider to write the answer, and is handled under the provider's own terms. Grant Read access with that in mind, and review your provider's privacy settings.

What could you actually do with it?

Picture 7:45 on a Monday morning. The first boat leaves in an hour, coffee is still hot, and you have a dozen small questions before the day starts.

So you ask. What did the team change over the weekend? Your assistant reads the audit log and tells you what changed, when, and which team member made the change. How many calls came in Saturday, including the ones the AI callbot handled? You get the list and the count. What are we charging for each experience, and how many guests does each one hold? You get it in a clean summary, starting prices and capacities side by side, no report to build.

Then the phone rings. A guest remembers only a last name, or a phone number, or half a confirmation code. You type it in, and your assistant searches trips, bookings, customers, gift cards, payments, resellers, and voucher codes all at once, then sums up what it found so you can answer while they're still on the line.

Later comes the work that used to swallow an afternoon. A new season means a new launch location, a new sunset experience, and a tighter group rule on the ropes course. Describe each one in a sentence and your assistant drafts it. It shows you a preview first, you say yes, and it's in your account. A guest sends a corrected email address? Same thing: preview, yes, done.

Before you close out, you ask which promo codes are running and where your bookings are coming from, and you get a straight answer instead of three tabs.

None of it means learning a new screen. You describe what you want in your own words, and the assistant does the clicking. And because TripWorks keeps adding to what an assistant can reach, the list of things worth asking only gets longer.

How do I get started?

Start with Read access. Turn on MCP under Setup, Integrations, connect one assistant, and ask it something you already know the answer to, like “List my experiences.” If it comes back with your real activities, you're connected, and you can decide later whether to grant Write access.

Each assistant has its own step-by-step guide: Claude, ChatGPT, Gemini, and Google Antigravity. For the full picture of what it can do and how permissions work, read Connect TripWorks to your AI assistant.