Connect Let's Book (boat rentals)

If you run boat rentals with Let's Book, your chatbot can work directly against your account: it checks real availability, puts the booking in your Let's Book, and handles questions, changes and cancellations under the rules you set. Let's Book stays your booking system — the chatbot is what answers for it in chat, 24/7. This guide covers connecting it and, above all, choosing how the booking lands, which is the decision that changes your team's day the most.

Before you start

• You need the Pro or E-commerce plan. On Free or Basic you can switch from Billing in your dashboard.
• Your Let's Book account, with access to its dashboard to create an API key.
• One chatbot connects to one Let's Book account. If your key covers several, the dashboard asks which one to connect.

Step 1 · Create an API key in Let's Book

In the Let's Book dashboard (dashboard.letsbook.app), go to the integrations / API section and create a key named ChatME. Being a dedicated key, you can revoke it whenever you want without touching anything else.

Step 2 · Connect it in your ChatME dashboard

1. In your dashboard, go to Appointments → Let's Book and paste the key.
2. ChatME validates it and, if you manage several businesses, lets you pick which one to connect.
3. Within seconds you'll see your fleet loaded: docks, boat models with their capacity, and add-ons.

The key is stored encrypted and never shown again. ChatME also registers a webhook called «ChatME» in your Let's Book, so payments, expiries and changes reach your dashboard in real time.

Step 3 · Choose how the booking lands

It is the first field in Assistant policy: "How the booking lands in Let's Book". There are three modes, and the difference is who creates the booking and who sets the price.

"Booking link" (the default, and the recommended one). The assistant checks real availability and sends the customer a link to your own Let's Book booking form with boat, day, time, length and party already filled in. The customer picks extras, sees the final price and pays on your form; the booking lands in your Let's Book like any other. ChatME creates nothing and your team touches nothing. It is the only mode that does not depend on Let's Book's API pricing the booking.

"Expiring hold". ChatME creates a draft and Let's Book emails the customer the payment link. If they don't pay within your Let's Book's window (normally 10-15 minutes), the draft expires on its own and the boat is free again. Until they pay, the booking doesn't appear in Let's Book's normal bookings view — you see it in your dashboard's activity log.

"Confirmed, payment pending". The booking lands confirmed and unpaid, exactly like one your team adds by hand: it never expires and it blocks the boat. Let's Book emails the customer nothing; ChatME alerts your notification address and your team prices it and sends the payment link when they can.

Which one to choose today. Bookings created through the API reach Let's Book in "Override mode" (ignore settings), and in that mode Let's Book does not calculate the price: they arrive at €0. An unpriced booking has nothing to charge, so the payment email never reaches the customer. That is why the recommended mode is "Booking link": the price, the extras and the payment come from your own form, which does work — and the customer goes through your usual add-on upsell. The two API modes remain for anyone who prefers the assistant to create the booking; between them, while Let's Book does not apply your pricing, the better one is confirmed-payment-pending. We are asking Let's Book to honour pricing on API bookings. Switching modes is one click and changes nothing already created; the assistant recognises a confirmed-unpaid booking as its own only while the confirmed mode is still on.

Saving the confirmed mode requires a notification address. It is the trigger for the whole mode: without it nobody would know a booking is waiting to be priced, so the dashboard refuses to save it and warns you beforehand with an amber message under the selector. You set it in Forms → Notification emails (several addresses allowed, separated by ;). That same address receives form submissions, appointments and group requests.

Step 4 · Set the rest of the policy

The policy defines what the chatbot may do on its own. Anything outside it becomes a note on the booking or a request for your team — never an action of its own:

• Allow moving / cancelling: both off by default. While they are, the assistant only records the request as a note for your team to resolve.
• Minimum notice (hours): below that notice the assistant doesn't touch the booking; it leaves a note for the team. Careful: it only governs changes and cancellations, it does not limit how late someone can book. If you don't want last-minute departures, close them in Let's Book.
• Max party size self-service: above it, no booking — it collects the details, emails them to you and creates nothing in Let's Book.
• When moving, keep the same duration: if ticked, a time change preserves the original duration.
• Usual rental length (minutes): what it assumes when the customer doesn't say how long they want.
• Default dock: appears when your fleet has more than one dock. Leave it on "Ask the visitor" and the assistant asks; pick one and it stops asking.
• Fixed departures: if a boat only sails in set windows, write them as 09:00-13:00, 13:00-17:00, 17:00-21:00 (dock local time, 12 max). The assistant will offer and book only those windows. Careful: anything not in that exact format is dropped on save, silently, so check the field afterwards. With several models, a list appears to tick which ones it applies to.
• Rental lengths you offer (hours): for example 1, 2, 3, 4, 5. The assistant offers only these lengths and pre-fills them in the booking link. Let's Book's API does not expose your lengths, so this field is the only rule there is. Empty = any length.
• Price list per boat and length: a table with your models as rows and your lengths as columns, tax included, in the currency you set. The assistant quotes exactly these figures and never computes or extrapolates — an hourly price doubled is not the two-hour price. Whatever you leave blank, it refers to the Let's Book form.
• Price note: a sentence of yours the assistant takes into account when prices come up.
• Partner code: stamped on every booking created from the chat, so you can spot them in Let's Book's reports.

Step 5 · Put your prices in

The assistant doesn't invent prices. The main source is the price list per boat and length from the previous step: it quotes those figures as they are. Anything not in the list it looks up in your knowledge base (your website or the documents you upload) and gives as indicative. The final amount is always set by Let's Book — on your booking form, with the payment link Let's Book emails, or with the payment request your team sends if you work in confirmed mode. It also does not add extras to the booking (barbecue, ice, skipper…): it describes them if they are in your knowledge base, and your team adds them in Let's Book. Make sure your knowledge base includes the price list, departure times and FAQs (licence requirements, what to bring, cancellation policy). What isn't there, the assistant won't invent.

How a booking works

The customer agrees a boat, date, length and party size in chat and the assistant checks real availability. From there it depends on the mode.

In "Booking link":

1. Link. The assistant sends the link to your Let's Book form with everything filled in and says clearly that the booking is completed there; it asks for no name or email.
2. Booking and payment. The customer picks extras, sees the final price and pays on your form. The booking lands in your Let's Book like any other, and since ChatME did not create it, it appears in your dashboard's activity log only once Let's Book confirms it.
3. Afterwards. The customer can check, move or cancel that booking from the chat like any other, with their reference and email.

In the two API modes the assistant also asks for a name and email and puts the booking in your Let's Book itself, with a reference.

In "Expiring hold":

1. Hold. The customer gets their reference and, if the booking came back priced, Let's Book's payment email.
2. Payment. Until they pay, the booking is a draft: it doesn't appear in Let's Book's normal bookings view — you see it in your dashboard's activity log. If unpaid, the draft expires on its own (10-15 minutes, your Let's Book controls it).
3. Confirmed. On payment, Let's Book confirms the booking and your dashboard updates instantly. If they booked on WhatsApp, we tell them there too.

In "Confirmed, payment pending":

1. Booking. It lands confirmed and unpaid, blocks the boat and never expires. The assistant tells the customer the booking is made and that your team will email them the payment link — never that it is paid, and never a time limit.
2. Alert. Your team gets ChatME's email with every detail and an "Action needed" block. (You get an email in the expiring-hold mode too, but it is informational — there is nothing to do unless the booking arrived unpriced.)
3. Price. In Let's Book: Edit booking → switch "Override mode" off → pick the duration → Save changes. Let's Book then calculates the rental, extras and deposit itself, and creates the payment request. Nobody types an amount.
4. Collect. Finance tab → "Payment link": send it by email or SMS with whatever deadline you choose.
5. If they don't pay, cancel the booking by hand when your deadline passes: in this mode nothing expires on its own.

In your dashboard's activity log these bookings show as "Booking confirmed (unpaid)". The payment you collect from Let's Book does not come back to ChatME's log and triggers no WhatsApp message: who has paid is checked in Let's Book.

Two things that mislead in this mode:

• Until step 3, the Finance tab shows "€0.00 · Paid in full" in green. It means the booking has no price yet, not that the customer paid.
• When you switch "Override mode" off, Let's Book applies your schedule again: the duration must be one of yours (1 h, 1:30, 2 h, 3 h…). If it doesn't fit, adjust the time on that same screen before saving. Filling in "Fixed departures" stops the chat offering slots that won't fit later.

If Let's Book ever returned the booking unconfirmed, ChatME detects it: the alert reaches you with the unpaid booking's "Action needed" block, and the connection card shows "Last error: hold_mode_ignored". Write to us if you see it.

Checking, moving and cancelling from the chat

To touch a booking, the customer has to prove it is theirs: the reference and the email they booked with (on WhatsApp, the number they are writing from works). If anything doesn't match, the assistant simply says it can't find it, without saying which part failed.

Only a confirmed booking can be moved or cancelled from the chat. An unpaid hold cannot: the assistant says it can be left to expire, or paid first. With moving and cancelling enabled, it then acts within your policy: it respects the minimum notice, keeps the duration if you ticked that, and re-applies your fixed departures to the new time. Outside those limits, and whenever they are off, it leaves the request noted on the booking and tells the customer your team will handle it. That request reaches you three ways: as a note on the Let's Book booking, in your dashboard's activity log and, since September 2026, as an email to your notification address with the customer's words and the booking details.

What the assistant never does

• It never charges in the chat: payment is always Let's Book's official link. It never asks for card details.
• It never invents prices: it quotes your knowledge base.
• It never says a booking is paid when no payment is recorded.
• It never emails your customers: every email in this integration goes to your notification address. The customer hears from Let's Book or from your team.
• It never promises refunds: cancellations follow your policy.
• It never breaks your rules: not the fixed departures, not the group limit, and it won't book a boat at a dock where it isn't (if the model has no units there, it explains that it is at another port).

Maintenance and limits

Changed your fleet in Let's Book (boats, docks, add-ons)? The assistant updates every night, whenever you open the Let's Book page in your dashboard and the fleet is more than 12 hours old, or instantly with the Refresh fleet button. If you revoke the key or it stops working, the page shows a reconnection notice and the assistant stops checking and booking until you paste a new one.

To prevent abuse there are caps: 2 bookings per conversation, 2 per email address in 24 hours and 30 per hour across the chatbot.

Try it

From your widget: ask for availability for 2 hours and ask for the booking link; open it and check that the Let's Book form arrives with the boat, date, time, length and party already set (no need to finish the booking). Ask a price too and check it quotes your list. If you work in an API mode: make a test booking and look it up with the reference and the email. In the expiring-hold mode the test draft expires on its own, though the customer stays in Let's Book and the attempt stays in your ChatME activity log. In the confirmed mode no payment email goes out and the booking never expires: cancel it by hand in Let's Book. And if you're running several tests in a row, use different email addresses or you'll hit the cap of 2 per address. If something doesn't add up, write to us at info@chatme.es.