The Guest Preference Hidden in an Old Email

DRAFT — NOT FOR PUBLICATION.

The best source of personalisation data for a returning safari guest is almost always their previous booking. The dietary requirements, the specific preferences, the things they mentioned in passing that made the experience remarkable — it is all there, in the email thread from their last visit.

The problem is that "all there" means trapped in a chain of email correspondence that may be in an archive, may have left with a previous staff member, may require knowing what you are looking for to find it.

This is not primarily a technology problem. It is a process problem that technology has failed to solve for most operators.

The gap is between what was said (guest data, rich and specific) and what was retained (fragmentary, inaccessible, dependent on individual memory). A good CRM should bridge this gap. In practice, CRM adoption in safari lodges is patchy, and even where a CRM exists, the discipline to enter contextual notes — and the time to do it — is inconsistent.

What would actually help:

• A simple, mandatory post-departure note for every guest, covering anything that should inform a future stay.
• That note linked to a guest record that travels with the booking next time.
• A pre-arrival briefing process that actually consults that record.

This is not difficult. It requires a process decision, not a technology purchase. The technology becomes useful once the process is clear.