DOT Full-Fare Rules, Seller-of-Travel Law, and Your Booking Page: A 2026 Playbook

A travel agency makes its living in the space between a customer and a supplier, and that is exactly the space where an assistant can hurt it. Fares move by the hour. Refund rules belong to airlines and tour operators. Financial protection when a supplier fails is governed by state law the agency has to actually satisfy. None of that is the kind of thing a website should improvise, and in 2026 a regulator reading a transcript will treat what the site said as what the agency advertised. The standard for an assistant on a booking page is built around one discipline: do not state a term the agency does not control.

This guide is the companion to the threat piece. The threat side covers the fare the site quoted and could not guarantee. This one covers the standard: what a compliant travel assistant is allowed to say, what it routes to an agent, and how to keep the booking page from rewriting a supplier’s terms.

A Quoted Fare Is a Regulated Presentation

Air pricing is not a free-for-all. The Department of Transportation’s full-fare advertising rule requires the price shown to a consumer to reflect the total fare, taxes and mandatory fees included. An assistant that tosses out a bare base number is not merely imprecise; it can present a fare in a way the rule prohibits, and the agency presenting it owns that presentation. Layer on the fact that fares are perishable, and a confidently stated price becomes a complaint the moment the booking comes in higher.

So the compliant standard treats live pricing as something an agent confirms, not something a website states. The assistant can capture the trip a traveler wants, the dates, the party, the destination, and surface published, durable information. The number itself comes from a person looking at a live booking, because that is the only number the agency can stand behind.

Refunds and Cancellations Belong to the Supplier

"Fully refundable" is the phrase that creates the most regret. Whether a booking can be refunded, and on what timeline, is set by the airline or operator’s fare rules and the agency’s own terms, not by what an assistant infers from a hopeful question. When a tool promises a refund the supplier will not give, the agency is left choosing between absorbing the loss and explaining why its website misstated the terms. Because misrepresenting refund and cancellation rules is the kind of thing the FTC treats as a deceptive practice, a pattern of it stops being a service problem and becomes exposure.

The standard is to source every refund or change answer from the actual booking conditions, confirmed by an agent. A compliant assistant explains where those terms live and routes the specific question, rather than guessing at a penalty or a window.

What AI Compliance for Travel Agencies Requires Around Supplier Risk

The hardest moment in the business is a supplier default: an operator folds, a cruise is scrapped, a flight disappears. Several states regulate sellers of travel precisely because consumers need protection when the money is already spent, with registration and bonding requirements that differ by state. Those regimes vary enough that no single statute governs them, which is its own reason an assistant should not be the one describing them.

An assistant that reassures a traveler their booking is "guaranteed" or "protected" is making a representation about financial protection the agency may not be able to back. The compliant line is that any statement about protection reflects the agency’s real, documented obligations, not a reassuring word generated on the fly. Pull the threads together and the standard for a travel assistant is short: it does not quote a live fare, it does not state a refund or cancellation term, it does not promise financial protection, and it keeps a record of what it told the traveler so a later dispute has a clean trail. Everything else, destination information, trip capture, the shape of the booking process, is fair game.

Why a Prompt Cannot Meet the Standard

The reflex is to write the rules into the assistant’s instructions: never quote a fare, never promise a refund, never say "guaranteed." Treat the boundary as set.

It is not set, and the reason is mechanical. A language model follows an instruction when the request resembles the wording it was warned about, and travelers comparison-shopping at midnight do not use that wording. You tell it never to quote a fare. The traveler does not ask for a quote. They press: "ballpark, what am I looking at for two to Rome that week?" The model reads a reasonable person who wants a number and gives one, because resolving the question is its default and a prompt is only a request to suppress that default. The rule was loaded the whole time. It just never recognized the sentence that crossed the line.

That is the gap between an instruction and a standard. An instruction asks the model to behave. It does not stop the model from speaking. A real boundary is enforced in the system and decides what the assistant may say before it answers, so a live fare, a refund promise, or a protection guarantee never reaches the traveler no matter how the question is phrased. "Will not" is a suggestion. "Cannot" is an architecture.

What a Compliant Deployment Looks Like

Meeting the standard does not mean turning off the assistant that captures leads off the destination pages overnight. It means running one built to know which terms belong to the supplier and to keep those with an agent.

Fred is built that way. It answers from your own agency content, captures the trip the traveler wants, and routes price, refund, cancellation, and protection questions to a licensed agent who can confirm live terms. It runs more than 50 industry guardrail packs, and the travel pack is built around full-fare presentation, supplier-controlled refund rules, and the seller-of-travel protections an agency actually has to satisfy. Fred does not quote a live fare or promise a refund. It cannot. It handles the everyday questions, logs every exchange, and books the regulated work for an agent.

The aim is not a more eager booking page. It is one that cannot bind the agency to a fare, a refund, or a guarantee it does not control.

Frequently asked questions