Public booking
Your organization has a public booking page. A customer picks a villa, a slot and leaves a name, an email and a phone number — no account, no password. The booking is created as a hold and the customer is sent to pay.
Everything about this page lives in Team settings → Public booking. Only an owner or an admin of the organization sees that tab.
The two public pages
| Type | Address | The customer books |
|---|---|---|
| Hourly | https://www.villaslot.io/en/book/<slug> | a slot of a few hours, priced by the rate grid |
| Overnight | …/en/book/<slug>/overnight | a stay of several nights, priced per night |
<slug> is your organization's slug. Replace en with fr or es for the other languages.
Both pages read the same rules as the calendar: opening hours, rate grid, booking horizon, existing bookings and the Airbnb calendar. A slot the team could not book is never offered.
Open or close each type
Booking types has one switch per type. A closed type answers as if its page did not exist — on the public page, in the widget, and when a booking is submitted directly. Closing both types closes online booking entirely.
The booking rules themselves (hold duration, buffer, horizon) stay in the Booking tab.
Suggested payment
For each type, pick the payment method highlighted on the customer's booking link — Stripe, bank transfer, or any method you enabled — or Let the customer choose. The customer still sees the other enabled methods; this only decides which one comes first.
If the suggested method is later disabled, the booking link falls back to the methods still available, and the settings tab warns you to pick another one.
Appearance
- Theme — light, dark, or automatic (follows the visitor's device). It applies to the public page and the widget, whatever theme the visitor uses elsewhere.
- Main color — the booking button and the selected slot. Any hexadecimal color, for example
#FF385C. The button text switches between white and dark ink to stay readable.
A live preview shows the result before you save.
What the customer receives
A hold
The slot is blocked as soon as the booking is submitted, for the hold duration set in your booking rules. The customer sees the deadline.
An email with their booking link
Sent automatically right after the booking, when the customer gave an email and customer emails are enabled. It links to their booking page, with the amount due and a Pay button — so closing the browser tab loses nothing.
A booking page
/b/<token> — the summary, the amount due and the payment methods. Paying by
card confirms the booking. While nothing is paid, the customer can also
cancel the hold from this page: the slot is released at once. As soon as
any payment exists, cancelling goes through your team.
Your team is notified of every public booking, and of every card payment received.
Next
- Booking widget — put this booking flow on your own website