Kapuli is built alongside the operators in the founding cohort, so most of what is below started as somebody's Tuesday-morning problem. Every release has its own link, pick a date and send it on.
Ask every guest exactly what a departure needs to know, and handle the answers without a spreadsheet.
Forms you build yourself, assemble a requirements form from text, date, time and dropdown fields, as a simple list or split into sections for longer questionnaires.
Assigned where they belong, attach a form to a whole trip or to a single departure, and guests fill it in from their own portal.
Reviewed in one place, approve or reject what comes back, or complete a form on behalf of a guest who would rather do it by phone.
Rooms are real inventory now, picked by the guest at booking and counted down as they sell.
Inventories connected to departures, build an inventory once, with details and photographs for each room, then attach it to the departures that use it.
Guests choose their own room, room selection becomes part of booking the trip instead of an email exchange afterwards.
No double bookings, availability updates in real time as bookings arrive, so the same room cannot be sold twice.
Credit becomes something you award on purpose, not only something you refund.
Loyalty credit you configure, reward guests for completing trips and for reaching the milestones you decide matter.
Cancellation credit against future bookings, issue credit when a guest cancels and let them spend it on the next departure, so the conversation is not only about refunds.
Everything it takes to stand up a trip, now one guided flow instead of three disconnected tools.
One flow, start to finish, creating a trip used to mean bouncing between separate steps for the page, the itinerary and the scheduled departure. Now it is a single guided flow: build a trip and publish it live to your site in one sitting.
Itineraries, inventory and departures, together, the full setup flow now covers day-by-day itinerary details, room and seat inventory, and departure scheduling in one place, instead of scattered across separate tools.
Photos that just work, upload trip photos as-is and Kapuli automatically resizes and formats them for your site. No more prepping images by hand before every upload.
The whole booking lifecycle now bends to how groups actually travel, together, but never all-or-nothing.
Book on behalf of your guests, your team can create a booking directly from the platform for guests who call, email or book in person, with no separate manual process.
Every guest pays and cancels on their own, when several travellers share a booking, each one can pay their share or cancel independently. It is no longer all-or-nothing for the whole group.
Verified guest accounts, guests verify their email and get their own account to view bookings and manage their trip, automatically as part of registration.
Money moves and the right message goes out, automatically, at every step of the journey.
Card payments for deposits and balances, guests can pay deposits and remaining balances by credit card, with automatic payment confirmation emails sent the moment a charge clears.
Cancellations that calculate themselves, cancel from Kapuli or the guest portal and the credit or refund due is calculated automatically against your cancellation policy. No manual math.
The right email, every time, verification, account credentials, trip welcome messages and payment confirmations now go out automatically at each step of the booking journey.
Streamline your tour operations today
We will look at how you run departures and tell you whether Kapuli fits.
