TrailheadClients & Guest ExperienceIdentity & preparation
CX-02Client continuityAssistant eval mapped · Partial coverage

Prepare the Guest Experience

Turn known preferences and needs into clear preparation without changing the trip promise held by the CIS.

Track

Identity & preparation

Phase

Client continuity

Starts with

An upcoming trip needs client-facing preparation.

Ends with

Reusable client context is visible

You are here

CX-02
  1. CX-01Maintain the Client Profile
  2. CX-02Prepare the Guest Experience
  3. CX-03Record Feedback and History

The situation

Turn known preferences and needs into clear preparation without changing the trip promise held by the CIS.

What starts it

An upcoming trip needs client-facing preparation.

How it unfolds

OperationsSystem
  1. 1

    Review the client record and current context

    Operations

    Confirm what belongs to the reusable client history and what belongs only to a specific CIS.

  2. 2

    Save the relevant client update

    Operations

    Record only confirmed reusable details—including returning status when known—with enough context for the next person to act.

  3. 3

    Show the updated context to the team

    System

    The shared client history is available without replacing the CIS trip document.

Who's involved

Operations

Reviews the client context and owns the next safe update.

System

Keeps the reusable client record separate from the trip-specific CIS.

What each person sees

Operations

Client identity, preferences, communication, and history relevant to the task.

Why: prepare a consistent guest experience

System

A confirmed reusable update with its client context.

Why: preserve continuity across trips

The rule to remember

Client history is reusable; the CIS remains the source of truth for one trip's promise and required work.