Answers, at the length they deserve

Kapuli is in closed beta. We onboard a small number of operators at a time so each one gets real attention, and so we build the right things. That means a conversation first.

No. It is thirty minutes of looking at how you run departures. Plenty of calls end with us saying we are not the right fit yet.

Use the contact form, or email support@kapuli.ai. We answer within a day.

We migrate your existing site for you on Boutique and Enterprise, and agree the schedule with you on the first call. Your content, your URLs and your search ranking all come across intact.

The founder. Kapuli is built by Kapuli, Inc. in the United States, and the founding cohort gets a direct line to him.

No. On Boutique and Enterprise you connect your own Stripe account and every dollar goes to you. On Solo, payments run through Kapuli and carry a 2% booking fee, because you are not bringing your own processor.

A dated departure that is open for booking or currently running. Trips you have finished or archived do not count against your plan.

No. Solo includes one user, Boutique includes five, and Enterprise is unlimited. We do not charge per seat.

A forward deployed engineer who looks after your booking site and builds the improvements your operation needs. Boutique gets 20 hours a month, Enterprise gets 160.

Yes. Most operators start on Boutique and move to Enterprise when they cross 50 active departures or add a second brand.

You cannot, yet. Kapuli is in closed beta and we onboard by conversation. Book a 30-minute call and we will tell you honestly whether you are a fit.

We move it across for you and keep your content, your URLs and your search ranking intact. After that you get a self-service editor, so changing words and photos never needs a developer again.

Yes. If you are happy with your site, connect it to Kapuli through our bring-your-own-website API and keep the front end exactly as it is.

You do. Your travellers and bookings sit in your own space, kept separate from every other operator on the platform. Nothing is pooled and nothing is resold.

Any time, as CSV or Excel. Travellers, bookings, revenue, the lot. Including on the way out, if it comes to that.

No. The booking experience runs on your own domain, under your own brand. There is no Kapuli branding anywhere your customers can see.

Yes. Capacity, price, deposit amounts, due dates and cancellation terms are set per trip, and you can override them on a single departure.

They can, according to the policy you set. Kapuli applies your rules rather than ours.

Kapuli reads your policy and works out the refund or the credit due. You approve it, and the guest gets the email automatically.

Yes. Staff can create a booking on a guest's behalf, take an offline payment and record it against the same departure.

Everyone in a shared booking can pay their own share, or cancel on their own, without disturbing the rest of the group.

On the traveller's profile. IDs, waivers and insurance certificates upload once and stay linked to every trip they take with you.

Yes. Paid add-ons attach to the trips you choose, and pre-trip or post-trip extensions can be booked alongside the main departure.

Yours. On Boutique and Enterprise you connect your own Stripe account and the money goes straight to you. Card payments are broadly supported, and Enterprise can add Plaid and others.

Never on Boutique or Enterprise. Solo carries a 2% booking fee because payments run through Kapuli on that plan.

Yes, from their own account, without needing to email you about it.

Yes, on Enterprise. You decide how credits are earned and spent, and they can be combined with discounts.

Room types are real inventory. You keep a room library, assign rooming on the departure itself, and price a private room upgrade there too. Anything else you need from a traveller is set up as a pre-trip requirement, so it gets asked for, submitted and reviewed rather than sitting in somebody's inbox.

A shared space for a single departure. Guides post sightings and voice notes from the field, travellers add photos and reactions, and at the end it becomes something the guest keeps and shares.

No. The journal is there if they want it. Plenty of travellers just read along, and the trip works the same either way.

Yes. Comments and reactions on any entry, from guides and guests alike.

Yes. Every guide on a departure writes into the same journal, so guests see one story instead of four.

Only the people on that trip, until the trip ends. After that the guest gets a link they can share with whoever they like.

Yes, and the tip can be split separately between guides, drivers and hotel staff.

Nothing. It is free on iOS and Android, and every Kapuli plan includes it in full.

Everything keeps working. Photos, notes and sightings save on the phone and upload themselves the moment a bar of signal comes back.

No. Anyone can download it and try it. The full platform is a separate conversation, and that one starts with a call.

Species identification works wherever you are. Naming individual animals is live at Panna Tiger Reserve in Madhya Pradesh, India, and is invite only while we add more reserves.

Camera for field photos, gallery for journal uploads, and location for the features that need it. You can refuse or withdraw any of them in your device settings and the app keeps working.

Bookings by trip and date, revenue by payment method, occupancy against capacity, and your customer data. Everything exports to CSV or Excel.

You do, using Kapuli's built-in tools. Enquiries from your website become trackable cases linked to the right booking, payment and trip.

Of course. Kapuli never stands between you and your travellers. Custom requests reach you exactly as they do today.

Boutique and Enterprise come with a dedicated forward deployed engineer: 20 hours a month on Boutique, 160 on Enterprise. Email support@kapuli.ai and we reply within a day.