Why Does It Still Take 14 Emails to Book a Safari?

DRAFT — NOT FOR PUBLICATION. The "14 emails" figure needs to be verified with a real booking audit or reframed as an illustrative estimate before publication.

The question

I want to be precise about what I'm examining here. Not "why does booking a safari take a long time?" — some complexity and lead time is appropriate for a high-value, highly personalised experience. The question is: why does so much of the friction in the booking process come from communication overhead rather than from the substance of what is being arranged?

Why, in an era of digital commerce and integrated systems, does a guest who wants to spend a significant amount of money on a safari experience have to answer the same questions multiple times, wait for email confirmations that require manual checks, and often not know exactly what is confirmed until days after they expected to?

What the journey actually looks like

Let me map a typical multi-property safari booking journey. [TODO: replace with a real journey audit — this is illustrative based on observation and requires verification with actual operators before publication.]

Step 1: Initial enquiry. Guest contacts a tour operator via their website form or email. They describe what they are looking for.

Step 2: Availability check begins. The tour operator contacts the properties and activity providers. Each of these usually requires a separate email or phone call. Some respond within hours; others within days.

Step 3: Proposal. The tour operator assembles a proposal based on availability responses. This often involves going back to the guest for budget clarification or to choose between options.

Step 4: Guest questions. The proposal raises questions. Further emails clarify meals inclusions, child policies, transfer options and other details.

Step 5: Revised proposal. Changes are incorporated. More property or activity confirmations may be needed.

Step 6: Booking confirmed. Guest accepts. The tour operator then needs to formally confirm each element with each supplier.

Step 7: Payment. Deposit invoice sent. Payment received. Receipt issued. This step alone can involve three to five emails.

Step 8: Pre-departure information. At some point — often a separate email campaign or a PDF — the guest receives packing lists, visa information, health requirements and property guides.

Step 9: Preference gathering. Someone asks (again) about dietary requirements, allergies, special occasions and room preferences. Often the same guest has already given some of this information in step 1.

Step 10: Final confirmation. A few days before departure: final itinerary, emergency contacts, transfer details.

By this point, a guest who booked a 10-day safari may have exchanged 20+ emails with their tour operator and received separate communications from individual properties. The same data — their dietary requirements, their anniversary, the fact that one person in the party has a knee problem — exists in multiple places and may or may not have reached the right people.

Why does this happen?

The causes are structural, not individual failures:

Fragmented supply chain. A multi-property safari involves multiple businesses with separate systems. The tour operator is coordinating, not controlling, so every change ripples out as separate communications.

Data doesn't travel. Guest information collected in the booking process doesn't flow automatically to the property's operations system or the guide's briefing notes. It has to be transferred manually, if it gets transferred at all.

No single source of truth. The itinerary, the guest preferences, the payment status and the operational notes often live in different systems or different people's email inboxes. When something changes, someone has to manually update each location.

Confirmation culture. The industry has evolved to rely on explicit email confirmations at every stage. This is partly a trust and legal issue, and partly habit.

What a better version might look like

The key shifts are not primarily technological — they are operational:

1. Shared guest profiles. Guest preferences collected once, stored centrally, and shared (with consent) with relevant properties and service providers before arrival.

2. Standardised handoff protocols. A clear format for what information passes from the tour operator to each property at the time of confirmation, so properties don't have to ask again.

3. Status visibility without email. Guests should be able to see the current status of their booking without having to email to check.

4. One pre-departure touchpoint. A single structured exchange to gather all remaining operational information, replacing the scatter of separate questions.

None of these require a new platform from scratch. They require agreement between tour operators and properties on what information flows when, and the discipline to implement that agreement.

The technology layer becomes much more useful once the operational model is clear.