Reserved on BookingHQ

This address is yours. There's nothing on it yet.

zz-provision-probe.bookinghq.net

We've set aside a website, a booking engine and a full property console for your property. Pick a theme and it goes live here — on this address today, on your own domain the day you want it. Every direct booking taken through it is yours, at no commission.

0%
commission on a direct booking
1 day
from demo login to a live storefront
Yours
the domain, the data, the guest list
What would you like?

No card, no contract, no automated sales sequence. One reply from a person, and you change the password on first sign-in.

Looking for a room?This property's booking pages aren't published yet — please contact them directly. Everything below is for the owner.

Before the pitch

The money leaves in four places, and three of them are silent.

None of this is a software problem in the abstract. It is what happens at your property on an ordinary week, and the reason it persists is that three of the four leave no trace you could look at on Monday.

15–25% of every OTA booking

A guest who found you on an OTA and booked there costs you a quarter of the room. The same guest, booking on your own site, costs you nothing — but only if you have a site that can take the booking.

The calls nobody picks up

Enquiries arrive at 11pm, during check-in, on a Sunday. An unanswered call is not a delayed booking — it is a booking that goes to whoever answers next.

Carts abandoned at the last screen

Most people who start a booking do not finish it. Without anything watching, that is invisible: no record, no follow-up, and no idea which rate or rule made them stop.

Rooms that go out empty

A room unsold on Tuesday is not inventory carried to Wednesday. It is revenue that no longer exists, and nothing in a spreadsheet notices it in time to act.

The website

Pick a theme. It goes live on this address.

See every theme

Yours to edit, not to code

Every heading, photograph and button label on the theme is a field in your console. Change the wording at 7am and the site says it at 7:01 — with no developer, no ticket, and no deploy.

Priced live, never stale

Rooms, rates, availability, offers and your cancellation policy are read from your account on every request. A price you change in the console is the price the next guest is quoted. Nothing is baked into the page.

Download it and it's yours

A theme is a real package you can download and run on your own server, under your own domain, paired back to this backend with a key. If you ever leave, the website leaves with you — it belongs to the business, not to us.

Switching themes later loses nothing: your wording is kept per theme, so you can try one, go back, and find your copy exactly where you left it.

Behind the booking engine

A website takes bookings. This one goes and gets them.

The difference between a brochure and a booking engine is what happens in the ninety seconds after a guest arrives and the ninety hours after they leave. At your property that work currently has to be somebody's job, or it does not happen.

An AI call centre that actually closes

It picks up from the moment a guest lands on the site — voice or chat, day or night. It answers what a front desk answers (is the room free, what does it cost, is breakfast included, can I bring a dog), quotes a real price from your live rates, and takes the booking in the same conversation. It does not take a message. It closes, or it hands a warm, qualified guest to a human with the whole thread attached.

Abandoned bookings, recovered

Every unfinished checkout is captured the moment it stalls — which room, which dates, which screen they stopped on. The follow-up goes out on its own over WhatsApp or email, in your words, and the guest returns to the cart they left rather than to your homepage.

Follow-up that doesn't need remembering

Pre-arrival details, directions, upsells, check-out, the thank-you. Sequenced against the reservation and paused automatically when a human replies, so nobody is ever mid-conversation with a person and a robot at once.

A review moderator on duty

New reviews are read, sorted and drafted for a reply before you have seen them. Anything abusive or fraudulent is held back for a human; the rest gets a considered response while it still matters — which is the week it was written, not the month.

A support officer behind the booking engine

The guest-facing desk answers from your own policies, rates and FAQs — not from a generic model's guesswork. It drafts, and where you allow it, it replies. Every thread stays attached to the reservation it belongs to, so a colleague picking it up has the whole story.

Sells the rooms that would go empty

It watches tonight and this week against your normal pace, finds the gaps, and moves them — a targeted offer to past guests, a last-minute rate, a length-of-stay nudge to bridge a one-night hole between two bookings.

Qualifies the lead before you spend time on it

Group enquiries, long stays, corporate rates and events arrive already sorted: dates, headcount, budget signal and whether you can even accommodate it. You spend your morning on the three that are real.

Automates the work nobody wants

Housekeeping lists, no-show detection, deposit chasing, invoice issue, rate-plan housekeeping, the daily arrivals sheet. Rules you set once, running whether or not anyone opened the console today.

You decide how far any of it goes on its own. Every one of these can run in draft — it writes, you press send — and be promoted to autonomous once you have watched it for a week and agreed with it.

Channels

Keep the OTAs. Stop paying them for guests who were already yours.

Nobody is asking you to leave Booking.com or Expedia. They are a shop window and they work. The goal is narrower and more valuable: one calendar behind all of them, and a direct site good enough that the guest who looks you up by name books with you instead.

One availability, everywhere

Rooms, rates and restrictions sync out to your channels and bookings sync back in. Sell a room on your own site and it comes off the OTA within moments — the double-booking and the apologetic upgrade stop being a monthly event.

Rates you set once

Rate plans, seasons, minimum stays, closed-to-arrival and per-channel adjustments live in one place. No more editing the same price in four extranets and getting one of them wrong.

You can finally see the split

What each channel actually cost you, per booking and per month, against what direct brought in. The point of the direct site is a number, and this is where you check whether it is moving.

The console

The website is the front. This is the building.

Most properties run on four systems that do not speak: a booking widget, a spreadsheet, a WhatsApp thread and a shoebox of receipts. The value is not any single screen below — it is that they are the same database, so a number changed in one place is not wrong in three others.

Front desk and calendar

Arrivals, departures, in-house, walk-ins and the occupancy view. Housekeeping status per room, and no-shows detected rather than remembered.

Booking policy that is actually enforced

Deposits, cancellation windows, refund tiers, check-in and check-out times, child and pet rules, minimum stays, ID requirements. Written once and applied by the same engine that quotes the price — so what the guest agreed to at checkout is what the refund screen calculates three weeks later. It is also the text your terms page publishes, so the policy, the quote and the page can never disagree.

Accounting that closes the month

A double-entry ledger behind every booking, payment, refund and expense. Revenue by room and by channel, profit and loss for any period, tax summaries at the rates you configured, and invoices issued and chased on their own — with a public invoice link a corporate guest can pay from without an account. Export it, or hand your accountant a period that already balances.

Take money properly

Card, transfer, POS, on arrival or a payment link. Deposits and balances tracked per reservation, with tax applied by the engine rather than by hand.

WhatsApp, email, on-site

Templates, campaigns and one-to-one threads, all filed against the guest and the reservation. Guests answer WhatsApp; that is where the conversation should be.

Kitchen and inventory

Room service, table orders, recipes, stock and food costing — for properties where the restaurant is a business of its own.

Reviews and reputation

Invitations after check-out, your own on-site reviews, and your Google Business Profile managed from the same screen.

Guests, loyalty and credit

One record per guest across every stay and channel, with house credit, loyalty and repeat-guest offers built on it. Your list, exportable, never rented back to you.

Staff, roles and audit

Invite your team with the permissions they need and nothing more. Every rate change, refund and cancellation carries a name and a timestamp.

The ask

So — do you want the website, or just the engine?

Both are real answers and neither is a trap. Pick the one that is true this month; the other stays available.

Own the whole site

A theme on this address today, your own domain when you're ready, and the console behind it.

  • A designed storefront with your rooms, rates, photographs and offers
  • Direct booking and payment, at no commission
  • Every AI surface above, on from day one
  • Download the theme any time and host it yourself

This one — set up my site

No card, no contract, no automated sales sequence. One reply from a person, and you change the password on first sign-in.

Keep your site, take the engine

Leave your website exactly as it is. Put our booking engine, calendar and follow-up behind it.

  • A booking flow embedded in the site you already have
  • The same live availability, rates and policy engine
  • Channel sync, accounting, WhatsApp and reviews included
  • Move the website over later, or never

Just the booking engine

No card, no contract, no automated sales sequence. One reply from a person, and you change the password on first sign-in.

Transitioning

Four steps, and none of them are "wait for the developer".

Nothing you run today has to be switched off to start. Your OTAs keep selling, your phone keeps ringing, and the new site is not public until you say it is.

  1. 01

    You get a login

    A real console for this address, seeded so you can click around a working property rather than an empty one. You change the password on first sign-in.

  2. 02

    We set the property up with you

    Rooms, room types, rates and your booking policy — in one session, from whatever you already have: a spreadsheet, an extranet, or a page of notes.

  3. 03

    Pick a theme and preview it

    Against your own rooms and prices, not a demo hotel. Change the wording until it sounds like you. Nothing is public until you press the button.

  4. 04

    Go live, then point your domain

    It goes live on this address immediately. Your own domain is a DNS change we walk you through when you're ready — or a download, if you'd rather host it yourself.

The reasonable doubts

What you're probably thinking.

We already have a website.

Then keep it. Take the booking engine and put it behind what you have — same live rates, same policy engine, same follow-up. The theme is an option, not a condition, and plenty of properties never take it.

We're doing fine on Booking.com.

Most properties are, and nothing here asks you to leave. The question is only what happens to the guest who saw you there and then searched your name — today they either book on the OTA again at full commission, or they find nothing.

Who owns the guest data?

You do. Guests, bookings, reviews, invoices and messages are your property's records, exportable at any time. We do not resell your list, and we do not put ourselves between you and the person staying in your room.

What if we want to leave?

Download the theme and run it on your own server — it is a real package, paired to this backend with a key you control — and export your data. That is deliberately a supported path rather than a hostage negotiation.

Our team isn't technical.

Nothing in the setup requires code. The one genuinely technical step, pointing your domain, is a DNS record we do with you on a call. Staff sign in and see only the screens their role covers.

How long until it's actually live?

A property that has its rooms and rates to hand is usually live on this address the same day. Your own domain follows whenever the DNS change suits you.

Anything not answered here is a five-minute conversation rather than a form — your property is not a support ticket to us yet, and we would rather hear the real objection than guess at it.

Start here

Are you in?

Leave an email and we'll send a login to a working console — sample rooms, sample bookings, every screen above, and a password you change the moment you sign in. No card, no contract, and nothing appears on zz-provision-probe.bookinghq.net until you press the button yourself.

If you would rather talk first, choose that instead and someone will call — about your property specifically, not a script.

What would you like?

No card, no contract, no automated sales sequence. One reply from a person, and you change the password on first sign-in.