Three-step guest booking
Treatment and duration → date and time → details. Guests book from the hotel site or a direct link, with no account to create.
Treatment booking for hotel spa and wellness desks — three languages for the guest, one screen for reception
Appointment booking for hotel spa and wellness departments. Guests book from the hotel's own site in Hungarian, English or German; reception manages bookings, rosters and rules from a single admin.
Illustration — not an actual screenshot.
Everything you need day to day — designed by people who know the industry.
Treatment and duration → date and time → details. Guests book from the hotel site or a direct link, with no account to create.
You choose which languages are enabled and which is the default. Guest emails always go out in the language the booking was made in.
The cancel link in the confirmation email works until your deadline. A cancelled slot is immediately bookable again, and the spa is notified.
HTML and plain-text email in the booking's language, with an .ics attachment and a 30-minute reminder; reception gets its own "new booking" notice.
Shifts per staff member. The system assigns each booking to whoever has the fewest treatment minutes that day — overridable by hand at any time.
With no roster, the daily headcount sets how many treatments can run at once; add a single shift to the week and it switches to roster-driven automatically.
A treatment can require 1–20 therapists. Companion rows get their own staff member and always change state together with the main booking.
Not just an application check: PostgreSQL exclusion constraints guarantee the same therapist or slot can never hold two overlapping bookings. In a race, the second request is refused.
Create, move, cancel and close bookings; block time for breaks and maintenance without a guest attached.
Opening hours, closure days, buffer between treatments, minimum notice, and how far ahead guests can book — all editable in the admin.
No online payment and no card data in the system: reception charges the treatment to the room at the price captured when the booking was made.
Revenue, confirmed future revenue, cancellation rate and the most-booked treatments — by month, 30 or 90 days, or all time.
Guest notes are deleted 30 days after the treatment and personal details anonymised 12 months later — with no one having to remember.
Who changed what and when, in plain language. Entries are deleted automatically after 12 months; guest notes and contact details never enter the log.
Logo, colours, sender and notification addresses, languages. Terms are versioned: every booking records which version the guest accepted, and when.
Each hotel gets its own deployment and its own database from the same codebase — no shared tables, and no way for two properties' data to meet.
Hydra SPA includes plenty more — role-based access, equipment lending, variance analysis and more. Browse the full, categorized feature list.
What's different about the Hydra approach? Built for the real problems of Hungarian hospitality.
Booking, moving, cancelling, blocking, rosters and rules in the same admin. The week view lays the day out as a timetable and flags bookings that no longer fit the roster, or gaps in opening hours nobody is covering.
Availability is decided by eight conditions together — opening hours, closure days, notice, the time grid, buffers, capacity, active treatments — and the server recalculates on save. The database has the last word, not the browser.
Hungarian, English and German, with treatment names and descriptions written per language. Confirmations and cancellations follow the booking's language, and the calendar file lands in the guest's phone.
Notes disappear after 30 days, personal details after 12 months, log entries the same. Nothing to remember to delete, and no card data to protect in the first place.
Treatment booking for hotel spa and wellness desks — three languages for the guest, one screen for reception