Calendar is read-only
The system never writes to availability without the owner. Double-booking is the one failure a small let cannot recover from.
Reference build
A holiday let enquiry system that does not overbook
A Dorset holiday let gets the same questions a hundred times: is it available, is it dog-friendly, how far is the beach. This reference build answers the repeatable ones, checks availability, and leaves the confirmation to the owner.
What “reference build” means
What “reference build” means
This is a demonstration built with synthetic availability and enquiries. It is not a deployed client system and there are no client results to quote. The pattern is real; the proof is the design, not a testimonial.
The problem
Small hospitality runs on borrowed time
A single-property let is often run by one person around another job. Enquiries arrive through the listing platform, the website, email and social messages. Availability lives in a calendar that is not always current. The same six questions are answered by hand, and a slow reply loses the booking to the next property.
Large property managers buy a channel manager. A one-property owner usually cannot justify the cost or the setup, so the work stays manual.
The flow
Enquiry to confirmed booking
-
1. Capture
Dates, guests, pets, arrival time and any accessibility needs, in one form. The listing platform's messages feed the same inbox where its API allows.
-
2. Check availability
Against the owner's calendar, read-only. If the dates clash, the reply offers the nearest alternatives rather than a flat no.
-
3. Answer the known questions
Parking, dogs, cot, beach distance, check-in time and deposit. Answers come from a maintained property fact sheet, not from a model's imagination.
-
4. Draft the reply
A short, warm response with the facts, the price for the dates and a clear next step. The owner reads and sends, or edits first.
-
5. Confirm and record
On confirmation, the booking is written to the calendar and the deposit request is issued through the owner's existing provider.
-
6. Post-stay
A thank-you and a review request, sent once, with the owner's approval.
Design
Why it is built this way
Facts live in one place
A property fact sheet is the only source of truth. Change the wifi password once and every reply is correct.
No payment handling
Deposits and balances stay with the existing provider. The system does not hold card data, which keeps the compliance burden where it belongs.
Human sends
Drafts are queued. The owner can send in one click, but the decision to send stays with a person.
Trade-offs
What it costs to run
| Component | Choice | Why |
|---|---|---|
| Hosting | Small UK VPS | Low traffic, predictable cost, data stays in the UK |
| Calendar | Existing provider, read API | No migration, no second source of truth |
| Messaging | Email plus the existing inbox | Owners already live in email; a new app is friction |
| Model use | Drafting only, with the fact sheet in context | Cheap, replaceable, and not trusted with availability |
| Backups | Nightly, tested quarterly | A booking system that loses data is worse than a paper diary |
Limits
What it will not fix
It will not make a property bookable if the listing, photos and pricing are wrong. It will not manage a portfolio of thirty properties; that is a channel manager's job. And it will not remove the need for an owner to answer the unusual question — the hen party, the late arrival, the broken boiler — with judgement.
What it does is remove the repetitive third of the inbox, so the owner has time for the third that needs them.
Related
Related
- Hotel websitesThe site that feeds the enquiry.
- AutomationThe pattern, and how we scope it.
- Hosting and careWhat running it looks like.
Questions
The things people ask first
Can it connect to Booking.com or Airbnb?
Where an API exists and the platform permits it, yes for reading availability and messages. Where it does not, the inbox is still one place and the drafting still helps.
Is guest data safe?
It is stored in the UK, access is restricted, and it is deleted on a stated schedule. There are no card details in the system because payments stay with the provider.
Will guests know they are talking to a machine?
The owner sends the message. Where a draft is used, the wording is the owner's. We do not add a fake persona.
What does something like this cost?
It depends on the calendar and messaging integrations. It is a Tier 4 custom project; we would scope it in a blueprint before quoting.
Related
Let’s find out whether technology is the answer
Tell us what you are trying to achieve. We will tell you honestly whether we can help, what it would take, and roughly what it would cost — before anyone signs anything.