What if Booking.com charged you to know your own guest?

If you run an independent boutique lodge, game lodge, guesthouse, or emerging private reserve in South Africa, the odds are good that Booking.com or Expedia already sits between you and a large share of your guests, taking a commission of somewhere between 10% and 25% of the room rate before you've folded a single towel. This is less true for the handful of long-established, trade-locked reserves that sell almost entirely through specialist tour operators, but for most independent properties still building that kind of trade relationship, OTAs are doing a great deal of the discovery work. Many South African owners have made peace with that toll. It's priced into the rate, budgeted for, and treated as the cost of being found by an international traveller who has never heard of your property.

There is a second toll forming behind the first one, and it has nothing to do with the booking itself. It's a toll on the relationship, and it's one South African properties are particularly exposed to, given how much of South Africa's international guest base is acquired through OTAs rather than direct search.

The guest you already can't reach

Look closely at the confirmation emails your lodge receives today. On many OTA bookings, the "guest" contact address is not the guest's real email. It's a masked, platform-generated address that forwards messages through the OTA's own servers, expires after a set period, and gives you no durable way to reach that person again without going back through the platform. Phone numbers are frequently withheld or similarly obscured until arrival, which is a real operational headache when you're trying to arrange an airport transfer from OR Tambo or coordinate a self-drive route to your gate.

OTAs typically frame this as a guest-privacy and security measure, protecting travellers from spam and phishing, and that's a genuine benefit. It also has a clear secondary effect, whether intended as such or not: it keeps the guest relationship inside the platform, not with your lodge, for the next booking. Every piece of contact information you're denied is a small, structural reinforcement of that outcome.

The thought experiment

Now take that logic one step further. If withholding the guest's real contact details already protects the OTA's repeat-business advantage, what stops the next move: charging you a fee to unlock it?

Not a booking commission. A separate, explicit toll. Pay a percentage more, and we'll hand over the guest's actual email address instead of the masked one. It wouldn't require new technology; the infrastructure already exists, and is simply switched off by default. It wouldn't even be a dramatic reversal of policy, only the monetisation of a gate that's already closed.

We are not reporting that this is happening. We're pointing out that nothing about the current architecture makes it implausible, and that the direction of travel (more gating, more platform-mediated communication, more distance between you and the person staying in your rooms) has been consistent for years.

Why the scenario doesn't actually matter

Here's the uncomfortable part: whether this specific fee ever gets introduced is almost beside the point. The property most exposed to it is the same property that's already most exposed today: the one with no first-party contact list of its own, no pre-arrival communication sequence, and no channel to its own guests that doesn't run through someone else's platform.

If every one of your guest relationships lives inside OTA infrastructure, you're not one policy change away from a problem. You already have it. The toll is already being paid; it simply hasn't been itemised yet.

The South African properties that would shrug off a guest-data fee entirely are the ones that treat every OTA booking as the start of a direct relationship, not the end of a transaction. A pre-arrival email captured with consent at the point of booking confirmation. A WhatsApp channel opened before arrival for practical logistics (directions, gate times, transfer arrangements) that naturally becomes a two-way contact line, which matters enormously here since WhatsApp has around 96% penetration among South African internet users, the highest of any messaging or social platform in the country, and it's a channel most guests are already comfortable using once a booking is confirmed. A guest profile stored in your own system, not just the OTA's dashboard.

What to build regardless of what OTAs do next

1. Capture contact details at the earliest legitimate moment. Pre-arrival communication, a welcome message, transfer coordination, a request for dietary requirements, gives you a genuine, non-spammy reason to ask for a direct email or WhatsApp number, and most guests will give it freely when the request is useful to them.

2. Store it somewhere you own. A simple CRM, or even a well-kept spreadsheet that lives on your own systems, is infrastructure the OTA cannot gate, throttle, or price.

3. Use it after the stay, not just during it. The value of a first-party contact is almost entirely in the second booking, not the first. A short, genuine follow-up, thanking the guest, sharing something relevant to their trip, is what converts a one-time OTA guest into a returning direct guest, and a returning guest is typically one of the cheapest bookings your lodge will ever get.

4. Treat this as infrastructure, not a campaign. It's not a marketing push you do once. It's a habit built into every booking, every stay, every checkout, so that a year from now your property owns a guest list that has nothing to do with any platform's goodwill.

The OTAs are not going to hand over the keys to their own advantage voluntarily, and there's no reason to expect the trend to reverse. For a South African lodge competing for international attention on a global platform, the only durable answer is to stop needing permission for the part of the relationship that should have been yours from the start.