Illustrative training scenario. Names, cities, experience and figures in this story illustrate the method. This is not a verified case study or a confirmed result of an XO network member.

In the work of a travel agent, important decisions rarely appear in one place. The composition of the family was clarified over the phone, the type of food was chosen in the messenger, the passport number was sent later, and the consent to the additional payment remained a voice message. While the trip is simple, memory and correspondence search seem to cope. But when the price changes, the case is transferred to a colleague, or the client asks a question, the fragments begin to contradict each other.

The travel decision log does not collect all communications, but only confirmed agreements: what was chosen, on the basis of what data, by whom and when it was confirmed, what period is valid and what should happen next. Such a log reduces the number of repeated questions, protects the quality of service and makes the agency's promises repeatable.

Illustrative scenario: Natalya: one “we discussed” changed the process

Consider this illustrative training scenario: Natalya, a travel advisor from Lvov, is attentive and calm in her communication. She was leading a family trip with two rooms, a separate transfer for grandma and different luggage options. Clients responded quickly in several chats, and agreed on some details during calls. Before paying, one of the adults was sure that a fare with a higher baggage allowance for everyone had been chosen, although in the final selection only two passengers had it.

Natalya did not rely on memory to argue. She paused payment, collected confirmed messages, showed the service configuration again and obtained the family’s explicit agreement. She then created a short log in the trip record: decision, source, date, expiry, owner and next step. A few days later the airline changed one segment, and Natalya’s colleague could continue without asking the family the same questions. The clients received one clear summary instead of a chain of forwarded messages.

The message history shows what we discussed. The decision log shows what we agreed.

Natalya — character in the illustrative training scenario

What counts as a decision?

A decision is a fact that changes the composition, price, timing, risk or next step of a trip. The client’s phrase “I like this hotel” is not a solution. The entry “hotel A selected, family room, meals HB, final price checked at 16:20, choice confirmed by the client in chat” already allows you to act.

  • Select an option: hotel, flight, room type, meals, transfer, insurance or additional service.
  • Refusal of an option or service with a clear consequence.
  • Confirmation of the composition of tourists, spelling of names, ages of children and important needs.
  • Coordination of price, payment currency, payment schedule and deadline.
  • Acceptance of the terms of modification, cancellation or other significant restriction.
  • Changing an already made decision with a new version and a new next step.

Do not turn the log into a transcript. Greetings, passing emotions, promotional language and every rejected idea do not need to be recorded. The aim is for another competent agent to understand the current position in a minute, without having to make assumptions.

When to open the decision log

Create a journal as soon as a client moves from general interest to a specific match. The first entry can be very short: travel itinerary, date range, budget frame, top priority and next contact date. Then add only decisions that affect the work.

  • There are two or more tourists or several payers.
  • The discussion is going on in more than one channel.
  • A trip has multiple services, suppliers or payment steps.
  • There is a hold, booking, ticket issuance deadline or another time limit.
  • A colleague or an agent on duty can get involved in the case.
  • The client changes the conditions after the initial selection.

Six fields in one record

  1. Decision: one short sentence without ambiguity.
  2. Context: which trip, passenger or service the entry relates to.
  3. Source: message link, call note, or supplier confirmation.
  4. Status: Proposed, Customer Confirmed, Supplier Confirmed, Completed, or Replaced.
  5. Duration: until what time the price, option or action remains relevant, always with a time zone.
  6. The next step is who is doing the specific action and when the result will be checked.

One entry should answer the question “is it possible to act now?” If the customer has chosen an option but the supplier has not yet confirmed it, the two states cannot be mixed. Write separately: “the client has chosen” and “we are waiting for the supplier’s confirmation until...”.

Ladder of Confirmation: Don't Confuse Choice with Fact

  1. Discussed: option shown, but no solution.
  2. Selected by the client: explicit consent has been obtained for a specific composition and price.
  3. Requested from the provider: action sent, result not yet received.
  4. Confirmed by the supplier: there is an official status or document.
  5. Completed: payment, ticket issuance, changes or sending documents have been completed and checked.

The ladder is especially useful in times of time pressure. It prevents the dangerous phrase “everything is confirmed”, when only the client’s choice is confirmed. For every critical service, two sides are visible: customer intent and actual execution.

After the call: the five-minute rule

Immediately after a meaningful call, write the solution on the card and send the client a short written summary. Don't try to resume the conversation in the evening. In five minutes, write down your choice, open questions, the upcoming deadline, and your next action. Ask for confirmation only of what actually requires consent.

To confirm our call: we are choosing option A for the agreed travelling party and budget. By 18:00 I will check availability and conditions, then send the final status separately after the supplier responds. Baggage for the third passenger remains an open question.

Post-call message template

The template must not create the appearance of a reservation. Separate the client's decision, the agent's action, and the provider's outcome. If the price is dynamic, indicate the time of the last check and explain that the final fixation will only occur at the appropriate stage.

The source is stronger than the retelling

For each significant entry, attach a primary source: a specific client message, a letter from a supplier, an official document, or a brief note about the call followed by written confirmation. A screenshot without date or context is weaker than the link to the original post. A verbal promise is weaker than a written consent.

  • For the price, keep the service content, inspection time and applicable terms, not just the amount.
  • For names, store the confirmed spelling from the document in a secure field, without duplicating copies across chats.
  • For a hotel room, please indicate the accommodation and actual beds, if confirmed.
  • For a flight, separate the selected route from the issued ticket and the current status of the segments.
  • For payment, record the purpose, amount, term and fact of receipt verification.

How to change a decision without losing history

Don't rewrite an old post as if the original solution never happened. Mark it as superseded, create a new version, and link the two entries. Indicate the reason for the change in simple words: customer request, change in availability, new price, supplier adjustment or discovered error.

Versioning helps restore the chain without finding someone to blame. You can see what data the team acted on at each moment, what changed and who was informed. It is especially important not to delete the old deadline: the new deadline must be a separate confirmed fact.

Transfer to a colleague in one minute

  • The currently selected scenario is at the top of the card.
  • The last confirmation of the client and the supplier differ in status.
  • The nearest irreversible deadline is highlighted along with the time zone.
  • Open questions are listed without hidden tasks in the correspondence.
  • Each next step has a responsible person and time control.
  • Solutions that are no longer relevant are marked as superseded but remain available.

Before a vacation, day off, or change of person in charge, open the card through the eyes of a colleague. If you need to re-read a hundred messages to continue, the journal is not doing the job. A good handover contains the current decision, evidence, risk, deadline and action.

Minimum data - more security

The decision log should not become a second copy of all client documents. Store only the data needed for the process, in designated secure fields and according to agency rules. A record can reference a document without duplicating the full number, address, medical information, or payment details.

Access must also match the role. For on-duty support, a colleague needs the current trip logic, but not necessarily the entire set of personal data. Do not forward the entire journal to external chats; Send only a clear summary to the client that is relevant to their decision.

How not to turn the service into bureaucracy

  • One entry - one solution; break a long protocol into several related points.
  • Use ready-made statuses and templates, but leave the wording human-readable.
  • Record only changes, risks and obligations, not every message.
  • Update the log at the point of decision, rather than in a separate large report at the end of the day.
  • Show the client the result and the next step, and leave internal service details in the CRM.

If a recording takes more than two minutes, check to see if you are trying to save the entire conversation. Most solutions fit in two or three lines. Complex cases require several short entries on services, rather than one large text without statuses.

Quality control before payment

  • The composition of tourists and the payer have been confirmed.
  • The selected service configuration is the same in the selection, calculation and journal.
  • Price, currency, schedule and payment term are current.
  • Significant restrictions and conditions of change are noted as notified.
  • There is no solution with a "discussed" status that the team mistakenly considers confirmed.
  • The next action after payment is assigned and has a verification period.

This short control is best carried out before the effect becomes irreversible. It does not replace the verification of a reservation, contract or documents, but links them to the client's last confirmed choice. If the data disagrees, stop and agree on a new version.

Three indicators of usefulness

  1. The percentage of cases that a colleague can continue without asking the client again.
  2. Number of corrections due to discrepancies between correspondence, calculation and actual order.
  3. Time from change to a clear summary to the client and assigned next step.

Don't judge agents based on the number of entries. This stimulates bureaucracy. Look at the results: fewer repeated clarifications, fewer forgotten deadlines, and fewer situations where the client and team understand the chosen option differently.

Launch in fifteen minutes

  1. Add fields to the card: decision, status, source, deadline, responsible, next step.
  2. Create five standard confirmation ladder statuses.
  3. Prepare two templates: call summary and change confirmation.
  4. Select one current trip and enter only the last five relevant decisions.
  5. Pass the card to a colleague for a minute check: can he name the condition and the nearest deadline.
  6. After a week, remove the extra fields, but maintain the separation of selection, confirmation and execution.

Main principle

The decision journal is not needed to control the client and not to accumulate evidence in case of a dispute. Its job is to maintain a shared understanding of the trip as channels, people, prices and circumstances change. Record not everything that is said, but what the team will act on.

Natalya’s experience showed a simple effect: when a solution has a source, status, deadline and owner, the service becomes calmer. The client sees consistency, the colleague doesn't have to start from scratch, and the agent can focus on the next useful action - instead of searching for a phrase in an old chat.