Playbook · Guest messages

The pre-arrival email that stops the 10 pm WhatsApp

Guests do not message the night before because they are difficult, they message because a booking confirmation read once three weeks ago has vanished from memory. What a good pre-arrival message has to get right, why copy and paste keeps failing, and how a personalised guide link sends it on time for every stay.

The message arrives at ten, sometimes closer to eleven: "Hi, sorry to bother you, just checking, is the gate code still 4521? And is there parking?" You sent the booking confirmation three weeks ago. It had all of this in it. What it did not have was a pre-arrival email that landed when the guest was actually paying attention. The guest read the confirmation once, on the day they booked, and has not thought about your flat since, until tonight, when the bags are half packed and tomorrow suddenly has a shape. This is not a lazy guest. It is a guest whose only source of information is a document they last opened a month ago, who has just realised they do not know how to get there.

Why the message always lands the night before

Nobody rereads a booking confirmation for fun. It gets opened once, skimmed for dates and price, and archived. Whatever you wrote in it, however clearly, is gone from working memory within a week. The night before arrival is the first time most guests actually think through the mechanics of the next day: what time to leave, where to park, whether the code they half remember is still valid. A first-time visitor to Cape Town carries an extra layer of doubt, because nothing about the route or the neighbourhood is familiar yet. The 10 pm WhatsApp is not a failure of your guest's attention. It is the predictable result of sending detail once and expecting it to survive three weeks of not being looked at.

What a pre-arrival email has to get right

The fix is not a longer message. A good pre-arrival email is short, and it is hard to write well, because it has three jobs at once. It has to answer the questions a tired traveller asks, in the order they ask them, for that specific unit: the way in, the parking, the keys, the one or two things people forget. It has to arrive at the moment the guest's attention has moved to the trip, not the day they booked and not the night before. And it has to carry information, a gate code or an alarm code, that should be readable during the stay and not a day longer.

A street address means nothing to someone who has never driven the route. A landmark does.

Each of those is a decision a host makes, unit by unit, and gets slightly wrong under pressure. Directions written by someone who drives the route every day skip the turn a stranger misses. Parking described as "easy" becomes twenty minutes of circling. A message sent too early is buried; a message sent too late is the 10 pm WhatsApp all over again. The difference between a pre-arrival email that ends the late messages and one that does not is rarely the wording. It is the order, the specifics and the timing, done the same way for every stay.

The copy and paste problem

Most hosts already write something close to this. The trouble is writing it every single time, from a template in Notes or scrolled back out of last month's chat, adjusted for whichever unit is checking in that week. It is easy to send the wrong gate code to the right guest, or the right code with last season's parking instructions, because the message gets assembled under time pressure between two other things. And because it lives in a chat thread, the guest's copy of the code sits in their messages long after check-out, which is not where a lockbox code should stay readable.

The obvious objection is that a WhatsApp message already does most of this, and it does, right up until the week you are travelling yourself, or the busy weekend when the third guest's parking instructions go to the fourth. A scheduled message does not get tired on a Friday night. Stay forty gets the same plan as stay four.

What the Guest hub sends, and when

This is the job the Guest hub add-on does for members. Each stay gets its own personalised guide link, and the notes go out by email on a schedule rather than being retyped from memory.

One plan, every stay, without you
Guide link
sent when the stay is created
Directions & keys note
two days out
Wi-Fi details
on the guest's phone from the day before
Lockbox or alarm code
appears 24 hours before check-in
Same code after check-out
closed

If you would rather say it on WhatsApp, the two-day-out note comes with a prefilled WhatsApp link you tap from the stay page, the wording already in it. If a guest loses the message, they still have the link. If you change the code between guests, last month's guest can no longer see it. You are not more careful than you were before; the timing is simply no longer something you have to remember to enforce by hand.

Let us send it

Members set the property up once: the way in, the parking, the keys, the house rules. From then on every booking gets the guide, the arrival note and the check-in-day message on time, with codes that switch on and off on their own, so the night before arrival is quiet again. The Guest hub is an add-on per rental, in rand, priced on request. Ask about the Guest hub for your rental, and tell us how many units you run.

Worth reading next: Load shedding, tides and the south-easter, on the Cape-specific things a first-time guest gets wrong before they even unpack.

The message plan described here, guide link when the stay is created, directions two days out, codes unlocked on check-in day, is the default schedule in RateVeld's Guest hub add-on. Those scheduled notes are email; the WhatsApp version is a prefilled link the host taps from the stay page. The gate code in the opening is illustrative, not a real property or booking.
Know your numbers before you argue them

RateVeld prices your own listing six months ahead from live market data, with every rate explained. Plans start at R333 a month, in Rands, with no debit orders.

See plans

← All posts on The Ledger