What a Guide Knows That the CRM Does Not — and Vice Versa

DRAFT — NOT FOR PUBLICATION.

A guide who has been working at a property for several years knows things about the guests in their vehicle that no CRM will ever capture automatically.

They know which guests are genuinely excited and which are performing excitement for their partner. They know that the woman in the back seat slept badly and will be grumpy until she's had coffee. They know that the father is trying to connect with his teenage son through this safari and that making the son feel seen during the game drive will be the most valuable thing they can do today.

This knowledge is perishable. It exists in real time, in context, and it informs a thousand small decisions the guide makes across a full day in the field.

The CRM knows different things. It knows that this guest has stayed three times before. It knows their dietary requirements. It knows that they left a five-star review last time and mentioned the sundowner stop by name. It knows that their next stay is their 25th wedding anniversary.

The gap is in the middle: the knowledge that should flow from the guide's real-time observations back into the guest's record, and the knowledge in the guest's record that should reach the guide before they get in the vehicle.

Currently, neither of these flows reliably. The guide's field observations are rarely captured in any structured way. The CRM data rarely reaches the guide in a form they can use before a drive.

This is not primarily a technology gap. It is a workflow gap. What would it take to build a simple end-of-drive debrief that captures what the guide noticed? What would it take to send the guide a two-minute briefing on each guest before each activity?

These are design questions, not engineering challenges. They require someone to decide that this information matters enough to create a process around it.