PlatixFor travel advisors

Agency guide

How do client-facing disclaimers work?

Create, activate, review, and use proposal and final-itinerary disclaimers for client-safe delivery.

In Proposals, Use this text adds and activates Platix's standard proposal and final-itinerary disclaimers in one step; Write your own opens Settings. The standard text is a starting point, not legal advice. Disclaimers can be replaced in Settings, and final-itinerary disclaimers apply to traveler links and exports.

Last verified 2026-10-20

Client-facing disclaimers are reusable, agency-approved text blocks that attach to proposals and final-itinerary delivery. Agencies create and activate separate language for the proposal and final stages, and Platix can include it in live traveler links and export artifacts.

Why disclaimers matter

Disclaimers make the boundary clear: Platix is software, while the agency remains responsible for the client relationship, bookings, supplier verification, payments, travel advice, and emergency support.

They also help the agency communicate limits around prices, availability, passport and visa requirements, accessibility, insurance, weather, schedule changes, and supplier terms.

Start with the standard text

The first time you build a proposal without an active disclaimer, Proposals shows the standard wording with two choices:

  • Use this text adds and activates Platix's standard proposal disclaimer and a matching final-itinerary disclaimer in one step.
  • Write your own opens Settings at the disclaimer form.

The standard proposal text reads: "This is a proposal, not a booking. Prices, availability and timings are estimates until your advisor confirms each booking with you. Nothing is reserved or charged through this page."

The standard final-itinerary text reads: "Check names, dates and times against your confirmations, and carry your own travel documents. If anything changes, contact your advisor straight away."

The standard text is a starting point, not legal advice. Agencies with their own terms should use them, and you can replace either text in Settings at any time. Only owners and admins can add disclaimers.

Create a proposal disclaimer

Use a Proposal disclaimer for proposals the client is reviewing. This is the stage where the itinerary may still be quoted, revised, accepted, or declined.

Proposal language usually covers draft status, price and availability changes, selected content scope, quote expirations, supplier confirmation, and the fact that the proposal is not yet the final travel packet.

  1. Open Settings.
  2. Open Client-facing disclaimers.
  3. Create a Proposal disclaimer.
  4. Use text approved by the agency.
  5. Activate it.

Only active proposal disclaimers can be selected when building a client-safe proposal.

Create a final-itinerary disclaimer

Create and activate a Final itinerary disclaimer when the agency is ready to deliver final traveler materials. This can differ from the proposal disclaimer because the client may already have accepted part of the trip.

Final itinerary disclaimers can appear on the live traveler itinerary and on generated artifacts such as PDF or calendar delivery when those exports are enabled.

Final-itinerary language usually covers supplier terms, traveler responsibility, passports and visas, insurance, local rules, weather, operational changes, emergency support, and what to do if something changes while traveling.

Example shape

Use unmistakably fabricated or placeholder text only in non-production test workspaces.

Proposal example shape: "This proposal is a draft for review. Prices, availability, inclusions, timing, and supplier details are subject to confirmation before booking."

Final-itinerary example shape: "This itinerary reflects confirmed or agency-approved travel details at publication time. Travelers remain responsible for documents, insurance, local rules, supplier terms, and contacting the agency if travel conditions change."

Review before use

Use unmistakably test text only in non-production test workspaces. In production, use agency-approved language and review it before sharing with clients.

If a disclaimer changes, publish a new proposal or final artifact when the client-facing language needs to change for an existing itinerary.

Next