Direct bookings without a booking engine: what to ship this week, and when to buy one

What you are actually replacing

Split the engine into its three jobs and handle each one separately. Two of them are easy by hand. One is not.

• Pricing. Easy. A season table on the page beats a calculator, because it also tells the guest whether they are in your price range before they write.
• Payment. Easy. A bank transfer for SEPA guests plus a card payment link for everyone else covers a full season.
• Availability. Hard. This is the only job an engine really earns its money on, and it is the one owners underestimate.

Five things a small property can ship this week

None of this needs a developer for more than an afternoon. In the order I would do it:

• A request form with six fields. Arrival, departure, adults, children, name, contact. One optional free-text box. Nothing else. No account, no address, no marketing checkbox.
• A WhatsApp link with the message pre-filled. A wa.me link carrying text like Hi, I am asking about Villa Thalia, 12 to 19 July. Guests who land in the chat with a message already typed send it. Guests who land in an empty chat close it.
• A stated reply time next to the button, not in the footer. We reply within 3 hours, 09:00 to 21:00 Greek time. Then set a WhatsApp Business away message for the other hours.
• A price table with minimum stay and what is included. Cleaning, linen, the climate resilience levy, the deposit percentage. Every number the guest would otherwise have to ask for.
• Your ΑΜΑ number in the footer and on the enquiry page. It is a legal requirement for short-term rentals in Greece, and experienced guests read it as a sign that you are a real registered property rather than a scraped listing.

Two build details that cost nothing and change everything

On the villa and guesthouse sites we build at Meraki, the enquiry notification email has the guest's address in the Reply-To header. Before we standardised that, owners were tapping reply on their phone and sending the quote to their own website. Nobody notices for a week. The guest books elsewhere in an hour.

The second one: put the answer in the subject line. ENQUIRY · 12-19 Jul · 4 adults · Weber is answerable from a lock screen while you are standing in the supermarket. New contact form submission is not. An owner who can read the whole enquiry without opening it replies faster, and speed is the only advantage you have over an engine.

The two-message close

Here is the pattern I keep coming back to, and the name I use for it with owners. The two-message close: the guest writes once, you reply once, and that single reply contains everything needed to say yes. If a booking takes more than two messages before the deposit, you are competing with an OTA checkout that takes ninety seconds, and you will lose most of the time.

Your one reply must contain, in this order: the dates confirmed as free, the total price for those exact dates and that exact number of people, what the total includes and excludes, the deposit amount, two ways to pay it, the cancellation terms in one sentence, and how long you will hold the dates. I hold for 48 hours and I say so.

A reply that says yes those dates are free, how many of you are there? is not a reply. It is a delay you charged the guest for. Write three saved templates in WhatsApp Business, one per season, with the numbers already in them.

Getting paid without an engine

Offer exactly two options and no more. A bank transfer to a Greek IBAN, which is free and instant for guests inside SEPA, and a card payment link for guests who are not. British and American guests get charged for international transfers and many of them simply will not do it. That is not a rate problem, it is a payment method problem, and it is invisible in your enquiry log because those people never reply.

Card links from a Greek or European provider take an afternoon to set up. You send a link, the guest pays, you both get a receipt. Never take card numbers over WhatsApp or email, no matter how relaxed the guest is about it.

Put the climate resilience levy on its own line in the quote, with the amount per night. Guests who discover a charge at check-in remember it in the review, and it is a fee you collect on behalf of the state, not a margin you are hiding.

The availability problem, and the stale calendar trap

There are three honest options for showing availability without an engine, and one dishonest one that owners fall into by accident.

• No calendar at all, plus a fast reply. Perfectly fine for one villa. The form asks for dates, you confirm them.
• A read-only calendar fed by iCal from your Airbnb and Booking.com listings, labelled updated daily, final availability confirmed by us. iCal feeds are pulled on a schedule, not pushed instantly, so never write the word instant next to one.
• A blocked-months list in plain text, updated when you take a booking. Ugly, honest, and it works for a single unit.
• The trap: a calendar that looks live and is updated by hand every second Sunday. It generates enquiries for dates that are already sold, costs you a reply each time, and teaches the guest that nothing on your site is reliable. If you cannot keep it true, delete it.

The engine line: when buying one starts to pay

This is the falsifiable part, and you can hold me to it. The engine line is the point at which manual direct booking costs you more than the software would. I judge it on four triggers:

• You have more than one bookable unit that could be sold to two different parties for the same dates. Double booking stops being bad luck and becomes arithmetic.
• You are listed on two or more OTAs and you block dates by hand on each one.
• Quoting takes you more than an hour a day in peak weeks, or you are breaking your own stated reply time.
• A meaningful share of your enquiries arrive from time zones where 03:00 in Crete is a normal booking hour.

One trigger, keep going by hand. Two, buy.

One trigger is a nuisance you can absorb. Two means you are already paying for the engine, in cancelled double bookings and in enquiries that went cold overnight. You just are not paying it to a vendor.

When you do cross the line, buy the channel manager first and the front-end engine second. The synchronisation is the part that saves you; the pretty date picker is not. I have seen owners buy the engine, leave the channels unconnected, and end up with two calendars instead of one.

Do the arithmetic in nights, not in euros per month. If an engine costs you the equivalent of two nights a season and it prevents one double booking or wins one late-night reservation, it has paid. If you sell fifteen direct bookings a year and answer every one within three hours, it has not.

Give the guest a reason to write to you instead of clicking book

Direct is more work for the guest, so it has to be worth something concrete. Best rate guaranteed is worth nothing because everyone writes it. Free early check-in from 11:00 and a crate of oranges from our own trees is worth something because it is specific and only you can offer it.

On price parity, check your current OTA contract rather than assuming. Parity terms in the European Economic Area have changed since Booking.com was designated a gatekeeper under the Digital Markets Act, and a lot of owners are still following rules from a contract they signed years ago.

And send a proper confirmation. Address with a pin, arrival instructions, key handover, phone number of the person who will meet them, cancellation terms again. The reason guests trust an OTA is not the checkout, it is the email that arrives afterwards. That email you can write yourself, once, this week.