Treat every guest message as one part of a journey, not as an isolated piece of copy. The reservation record is the source for dates and guest names, the message carries the time-sensitive action, and the private guest guide stores details that may be needed again. When those three sources disagree, automation makes the error travel faster. Review the source information first, then the wording, trigger, and destination link.
Write for a guest holding a phone while travelling. Put the decision or action in the first two lines, keep one instruction per sentence, and use labels for codes, times, networks, or addresses. A friendly opening matters, but it must not bury the useful information. Read the draft aloud and test it at the property entrance or at the exact moment the guest will need it.
Personalisation should confirm that the message belongs to this stay. Use the guest name, property name, arrival or departure date, and only variables that are reliably populated. Never let an empty variable create a confusing sentence. Keep a plain fallback version for last-minute reservations, altered access arrangements, or a platform delay.
Automation is appropriate for predictable moments and verified facts. A host should take over when a guest reports a safety issue, cannot enter, disputes a charge, requests an exception, or describes something that may require judgement. The goal is not to avoid conversation. It is to remove repetitive searching so the host has attention available when a human answer matters.