AI in Tour Operations: The Four Rules I Set Before CORAA Went Live
By Kay Honig
TL;DR: On October 12, 2026, the AI inside CORAA went live at LDK. CORAA is the operations platform LDK built after about six years on Peek Pro at Kay Tours. Before launch I set four rules: AI checks and my team decides, money tools only read, everything starts in pilot, and every number shows how reliable it is. Most of it is still in pilot. This is the operator's version of the story, and what I'd tell anyone running tours who is thinking about doing the same.
Read the original on Kay Tours: How AI Helps Our Team Deliver Better Private Tours. That one is written for our guests. This one is for operators.
Start with the tour, not the booking
Most reservation software is built around one event: the sale. For an operator, the sale is where the work begins.
Between the booking and the drop-off back at the hotel sit dozens of details. A pickup time. A guide who knows the route. An allergy. A birthday. A charge that has to match. If one of them slips, the guest feels it. The software vendor doesn't.
Our catalog has more than 50 tours, private, semi-private and small group, from Chichén Itzá and Tulum to Holbox and Bacalar. I wanted every team member looking at the same version of every trip. After about six years on Peek Pro, I decided we needed our own system.
That system is CORAA: Centralized Operations Reservations Affiliate Administration. It holds reservations, sales, operations, our guides and the booking engine behind our tours on kay.tours. LDK, the company I co-founded, built it.
Getting there was messy. I wrote about that phase in CORAA Update: Three Systems in Parallel. This post is about the next step: putting AI on top.
Four rules I wrote before the first feature
AI in operations can go wrong quietly. So I wrote the rules before anything shipped.
1. AI checks. My team decides. Every flag goes to a team member for review. No tool makes a call on its own. The AI does the repetitive scanning. Judgment stays human.
2. Anything touching money is read-only. Our financial tools can look. They cannot change a record, and they cannot send anything. With money, I'll take trust over speed every time.
3. Pilot before rollout. A new tool goes to a small group first. Most of CORAA's AI is still at that stage. That's deliberate, not a delay.
4. Every number shows its confidence. The tools show how reliable each figure is. An honest "check this" is useful. A wrong number delivered with confidence is dangerous.
If you're an operator evaluating AI, I'd ask these four questions before you look at any feature list.
What it actually does overnight
Launch day brought eight tools: Night Report, Smart Guide Report, Crew Copilot, Leak Radar, Margin Map, The Next Tour, SG Departures and Ask CORAA.
I won't walk through each one. The pattern matters more than the names. A lot of the checking happens at night, so the team starts the day with a list instead of a surprise.
- Tomorrow's reservations get checked. The Night Report flags what looks off, like a pickup time that's missing or two that contradict each other. We fix it the evening before, not at the hotel door.
- Special requests surface on their own. Allergies, food restrictions, honeymoons, birthdays. The guide sees them before the meeting point.
- Payments get reviewed. Duplicates, wrong currencies, forgotten or unusual charges get flagged. Read-only, per rule two.
During the day, Crew Copilot helps us assign guides by tour experience, workload and availability. After each tour, guide reports get condensed into a summary of incidents, equipment and real guest counts, with worrying feedback flagged. And guests already traveling with us can get suggestions for the tours most loved by others staying nearby, priced for their group.
None of this is magic. It's checking that used to depend on someone remembering to do it.
The notebook
On day one we showed the Night Report to Claudia from our Monitoring team.
She laughed. She had been writing that same summary by hand, in a notebook.
That one is on me. A capable team member was doing a system's job because I hadn't given her a better tool. That's the hidden cost of running on infrastructure you don't control. Your strongest team members quietly patch the gaps. And you don't notice, because the work still gets done.
Now her time goes back to the guest's day.
Why operators should own this layer
Booking platforms, OTAs and aggregators sell inventory. Operators build the experience. When an operator's whole business lives inside someone else's software, the operator becomes hard to see. Sometimes even to themselves.
I care about rebuilding trust in travel. For me, that starts with seeing my own operation clearly. You can't promise guests transparency about a business you can't see yourself.
Owning your operations data is the first step. Whether you build or buy, know where your data lives, who can read it, and what your team is still fixing by hand.
FAQ
What is CORAA? Short for Centralized Operations Reservations Affiliate Administration, CORAA is the platform LDK built to run Kay Tours Mexico, Living Dreams Mexico and Living Dreams Dominican. It covers reservations, sales, operations, guides and the website booking engine.
What did CORAA replace? Peek Pro, which Kay Tours used for about six years.
When did CORAA's AI go live? October 12, 2026, with eight tools, including the Night Report and Crew Copilot.
Does the AI make decisions? No. It flags and summarizes. A team member reviews every flag and makes the call.
Can the AI change payments? No. The financial tools are read-only. They can't edit or send anything.
Is it fully rolled out? No. Most tools are still in pilot mode with a small group.