How it works
Talk to us however you like.
Type it in the chat, text our skipper, or send a voice note. One AI crew member reads all three, checks the same live calendar, and books the same boat.
Three ways in
Guests get a host who never sleeps. The skipper gets an ops desk in a pocket. Same crew member either way.
For guests
Web chat
Ask in plain words — “sunset sail for four next Saturday” — and watch it check dates, quote the price, and book. Open in the corner of any page or in full view.
Answers stream in as it thinks. Live prices, live availability.
Open the chat →For the skipper
Telegram text
Our skipper runs the day from a phone: “what’s on tomorrow?”, “block Friday afternoon”, “move Priya to Sunday at 10.”
Only the skipper’s account can talk to it. Everyone else gets a polite no.
For the skipper
Telegram voice
Hands full on the dock? Send a voice note. It’s transcribed, echoed back so nothing gets misheard, then acted on like a text.
Short notes, quick turnaround, same tools underneath.
Same brain, same calendar
The assistant never touches the schedule directly. It asks for things through a short list of tools, and the calendar has the final say.
- Web chatfor guests
- Telegram textfor skipper
- Telegram voicefor skipper
One assistant
Reads every channel
Same instructions, same manners, a different brief per channel. Guests get a host; the skipper gets an ops desk.
Only through these tools
- Look up trips
- Check the calendar
- Suggest times
- Price a sail
- Book it
- Block time
Every tool hits the same live calendar the booking page uses. The database refuses overlapping bookings, so the assistant can't double-book even if it tried.
The skipper’s side
A morning on the dock, by text and by voice.
This is a scripted example of the operator bot. The real one only answers our skipper, so we can’t hand you the phone — but every line here is something it does today: read the day, block time from a voice note, and move a booking without a phone call.
- Today’s manifest — who’s sailing, when, how many
- Block time — weather, maintenance, a day off
- Cancel or move — with the guest emailed automatically
Book & Sail Ops
bot · online
What's on tomorrow?
Checked the calendar · Sat Jul 18
Two sails tomorrow: a 2-hour at 1:00 pm (4 guests, Priya) and the sunset 2-hour at 7:10 pm (2 guests, Dan). Morning is open.
- 0:06
Heard: “Block tomorrow morning until noon, engine service.”
Blocked · Sat Jul 18, 8:00 am – 12:00 pm
Done. Tomorrow 8:00 am to 12:00 pm is blocked for engine service. The 1:00 pm sail is unaffected.
Can we fit Priya's party of 4 on Sunday at 10 instead?
Checked availability · Sun Jul 19, 10:00 am
Yes — Sunday 10:00 am is free for a 2-hour sail. Want me to move Priya's booking there and email her the new time?
The guest side · live
Go on, ask it something.
This is the real thing, wired to the real calendar. Ask about a date, get a price, or book — it'll show its work as small receipts while it checks.
- Look up trips · the four trip lengths, sunset options, what’s included
- Check the calendar · real openings for a date and party size
- Suggest times · the best-fit departures when you’re flexible
- Price a sail · the exact quote, taxes in, before you commit
- Book it · a real booking, confirmation emailed in seconds
- Check our FAQ · parking, pets, what to bring, cancellations
Hi, I'm the crew chat.
I can check dates, price a sail, and book you in — no forms, no phone call.
What we promise
It can’t double-book
Overlapping bookings are refused by the calendar itself, not by good manners. Two people racing for the last sunset slot: one wins, one gets the next best time.
Same calendar as the booking page
Chat, voice, the booking form and the skipper’s dashboard all read and write one schedule. There’s no “the bot said” versus “the site said.”
Every booking gets a paper trail
Confirmation email in seconds, a link to save it to an account later, and a short recap of each conversation the skipper can read.
Around the clock, in season
The chat answers at 2 am. The skipper still gets a full night’s sleep, and the boat is still never promised twice.
For the curious: Next.js on Vercel, Postgres with a hard no-overlap rule, prompts and policies in Sanity, Claude doing the reading. Built by 88 Create.