← All ten chapters

Chapter 04 of 10 · CRM, consent and communication

Guest relationships

A guest who books three different farms over five years is a relationship, not three transactions. Holding that relationship centrally is valuable, and it is also where the platform has to be most careful: a booking is a property's data, a marketing consent is the guest's, and both need to be respected.

A single guest record

One profile gathers stays, enquiries, preferences and consent, with the household and the group attached, because rural breaks are rarely booked by one person travelling alone.

  • Contact details, household and group travel
  • Booking history across every member property
  • Saved preferences, searches and favourite stays
  • Service conversations across email, phone, chat and web forms

Consent you can prove

Marketing consent is recorded with what was agreed, when and where, and it travels with the guest. Booking communication is treated separately from marketing, because a pre-arrival message is not a newsletter.

  • Separate consent for marketing and for stay communication
  • Preferences by channel and by topic
  • Consent changes applied everywhere at once
  • Guest data access rules written down, not assumed

The messages a stay needs

Confirmation, payment, pre-arrival, access and post-stay messages are largely the same every time. Templating them removes work from the member and inconsistency from the guest's experience.

  • Confirmation and receipt with the property's own detail
  • Balance reminders and payment failures
  • Pre-arrival information maintained by the member
  • Post-stay feedback and a review request

Segments that earn their keep

Segmentation exists to send fewer, better messages: repeat visitors, lapsed guests, dog owners, accessible-stay guests, regional audiences and large groups.

  • By region, accommodation type and visit history
  • Repeat, referral and win-back journeys
  • Member-level view of its own guests only

The design decision

The guest owns their consent, the property owns its stay data, and Farm Stay owns the marketplace relationship. Each party sees what its role requires, and every access is logged.