The short answer

Describe how travelers request a change, who reviews it and which booking conditions determine the available options. Separate a customer-requested change from an operator or supplier change. A public summary should direct the traveler to the terms of their own booking.

Provide a working escalation route

Identify the booking reference and contact information a traveler needs without publishing personal examples. Explain how urgent in-trip questions reach the appropriate support team. Have the booking owner review the guide when supplier arrangements or support routes change.

Keep the sector facts verifiable

A trip owner should verify itinerary details, supplier roles, inclusions and booking conditions. Clearly label proposed departures and illustrative schedules. Maintain one current trip record for dates and availability; country-specific entry or travel requirements should link to the relevant official source and be checked for the traveler’s situation.

What to check

  1. Distinguish customer and supplier changes.
  2. Link to booking-specific conditions.
  3. Verify pre-trip and in-trip support routes.

A practical example

An illustrative traveler wants a different departure date. The answer explains the request process and confirms that options are checked against the existing reservation conditions.

Sources and further reading

These steps are Arrow AI's implementation guidance. The example is illustrative; it is not a measured customer result. Publication and source access do not guarantee an AI recommendation.

Apply this to your website

Identify the source gaps and decide what to improve with Arrow's free audit. Review what Arrow GEO measures before choosing a reporting scope.