A Travel Advisor's AI Draft Said "Confirmed." The Supplier Said "Requested."

Suppliers use a lot of words for where a booking stands. Quoted. Held. Requested. Waitlisted. Deposited. Confirmed. Ticketed. Not every supplier uses all of them, and not every one means exactly the same thing from one supplier to the next.

What they are not is synonyms. Each one says something different about what has been promised, by whom, and what happens if it falls through. Your supplier picked the word they picked, and it belongs in your client email unchanged.

An AI drafting your client email doesn't treat those words as promises unless you tell it to. Hand it a pile of trip notes and ask for a warm update, and it will do what it is built to do: produce something that reads well. Smoothing is the problem. "Requested" comes out as "all set." "Held until Friday at 5" comes out as "your cabin is booked." The sentence is friendly, the grammar is clean, and nothing in it looks wrong. That's the danger.

Why the words are not interchangeable

The precise meaning of each word belongs to the supplier, not to you and not to a chat window, so your supplier's own terms always decide. In general use, three of them work roughly like this.

Held usually means something is reserved for you, often with an expiry attached. The expiry is not a footnote. It is half the fact. A hold with the date stripped off can be worse than no hold at all, because your client now believes they have time.

Requested usually means you asked and the supplier hasn't said yes yet. They may have acknowledged the request. That still isn't a booking.

Confirmed is the one to reserve for when the supplier has said yes, in writing, and you have it.

The gap between those last two is where the trouble lives. A client who reads "confirmed" has every reason to stop worrying about that piece of the trip. If the answer later comes back no, you are not delivering news. You are retracting a promise you made.

What a smoothed draft looks like

Here is the shape of the failure. This is an illustration written to show the pattern, not output from any particular tool.

The advisor's notes say the Rome hotel is confirmed, the Florence hotel is confirmed, and the train between them is requested. The draft comes back reading:

It is warm, it is organized, and it isn't true. "Everything is set" and "All booked and ready to go" both cover a train that is only requested. They arrived because "requested" sat in a list next to two confirmations and the tool wrote sentences that covered all three.

The phrases to hunt for in any draft before it goes out are the ones that sound like relief:

• confirmed
• all set
• guaranteed
• held for you
• locked in

If any of those appear where your source says requested or quoted, the draft is wrong, and it is wrong in the direction that is hardest to walk back. "Held for you" is only right when the source says held, and even then it needs the expiry next to it.

What it looks like when the setup is right

The AI Workflow System for Travel Agents carries a worked case built on exactly this situation. The case is fictional, and the guide says so: the names, suppliers and figures are invented to show the method. A family of four, ten days in Italy in June. The advisor pastes her trip facts in:

In the case, what comes back is not a polished itinerary. It is this:

Four problems, and the requested train is only one of them. There were two nights with no hotel in the file. In the fictional case, one was a genuine gap the advisor then books, and the other was a typo in her own notes, where the confirmation read June 19.

A draft that had quietly filled those gaps would have looked finished and been wrong. "Not enough information" is a correct answer. You're far more likely to get it if your setup asks for it.

The check that catches it

You do not need a system to do this. You need a habit, and it takes about as long as one more careful read.

1. Read the draft against the source, line by line. Not against your memory of the source. The supplier's email, open, next to it.
2. Find every status word in the draft and match it to the document it came from. If a status in the draft cannot be traced to something the supplier actually told you, in writing or in their portal, it is not a status. It is a guess.
3. Check that every hold still carries its expiry, with the date, the time and the time zone the supplier gave you.
4. Compare what the client approved against what the supplier confirmed. Dates, traveler count, room or cabin category, occupancy, inclusions, price and currency, payment dates, cancellation terms. Differences between those two documents are where disputes and refunds tend to start.
5. Check traveler names and birthdates by hand, in your own system, against passports. That check never goes through an AI tool at all.

Step four is a workflow in the guide. Step five comes straight from the guide too: that check "never goes through the AI."

What this does not fix

A drafting system does not book anything, does not know today's inventory, and does not replace your supplier portals or your CRM. It writes a draft from facts you supply, and it flags what you did not supply.

You still verify every price, date, status and requirement before anything reaches a client.

What a good setup changes is the default. Left to itself, a drafting tool tends to fill gaps, because a complete answer looks more helpful than an incomplete one. It has to be told in advance, in writing, that a gap is something to report rather than something to solve. That instruction is what the guide calls a Travel Advisor Context Block, and every one of its 105 workflows runs under it.

The checklist above catches the error after the draft exists. With that instruction in place, the tool is more likely to tell you what is missing instead of papering over it. You still run the checklist.