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.

A request that does not result in a booking can easily be attributed to price, customer indecisiveness, or a bad season. But a separate refusal does not prove anything. Growth begins when the travel agent regularly distinguishes a confirmed cause from a guess and looks for recurring points where the client has become difficult to move on.

Analyzing failed sales is not a search for those to blame and is not a reason to put pressure on the client again. This is a short learning cycle: select completed requests, reconstruct the facts, group the reasons, change one element of the process and test the result on the next series of requests.

Illustrative scenario: Mikhail: “expensive” turned out to be too simple an answer

Consider this illustrative training scenario: Mikhail, a travel advisor from Nikolaev, has been in tourism for eight years and likes to respond quickly. At the end of the month, he saw twelve selections without reservations. In CRM, nine had the reason “expensive” because it seemed like the most obvious explanation.

Mikhail re-read the correspondence and discovered a different picture. Two clients directly named the budget, three disappeared before receiving comparable options, two did not understand the difference between the tariffs, one was waiting for a relative’s decision, and for four there was no confirmed reason at all.

He added neutral statuses, began to record the last clear step and analyzed ten cases once a week. The first change was small: each selection began to begin with a brief comparison of three scenarios and the next action. After a month, the proportion of dialogues that ended immediately after submitting options decreased.

When I stopped calling any refusal “expensive,” it became clear that some clients were lost not in price, but in the number of solutions without a clear next step.

Mikhail — character in the illustrative training scenario

First, determine which request is considered completed without a sale.

  • The client directly refused or chose another option.
  • The client asked to close the request or reschedule it without a date.
  • The agreed sequence of contacts ended without a response.
  • The travel dates have passed or the product has objectively lost its relevance.
  • The request does not duplicate the active card of the same client.
  • The agent completed the promised next step and recorded the result.

Don't send an active request to waste just because the client hasn't responded in a few hours. The completion criterion should take into account the type of trip, the proximity of the departure, the agreed upon rhythm of contact and the agent's promises. Otherwise, the analysis will measure your impatience rather than actual conversion.

Minimum card for analysis

  • Source of request and date of first response.
  • Trip composition, dates and stated budget range.
  • The main priority and deal-breakers from the brief.
  • What product and how many options are offered.
  • Time to first offer and number of useful contacts.
  • The last step that the client responded to.
  • Final status and confirmed reason, if any.
  • What would the agent do differently if he knew the outcome?

Separate fact, observation and hypothesis

  • Fact: the client wrote that he rescheduled his vacation.
  • Observation: after clarifying the full cost, there was no response.
  • Hypothesis: the final budget turned out to be higher than comfortable.
  • Unknown: The cause has not been confirmed and there is insufficient data.

A hypothesis is useful if it is labeled as a hypothesis. It is dangerous to turn it into a CRM fact: in a month the report will show hundreds of “expensive” requests, although the agents simply did not ask the final question. The “unknown” category is more honest and helps to see where the process is not collecting feedback.

Use a short guide of reasons

  • The dates, composition or the need itself have changed.
  • The budget did not match after a comparable calculation.
  • The product, destination or prerequisite did not fit.
  • The client has chosen another supplier or self-booking.
  • The decision depends on the participant who was not included in the dialogue.
  • The answer or offer came too late.
  • The value and differences of the options remained unclear.
  • Failed to restore contact after agreed upon contacts.
  • The cause is confirmed to be different.
  • The reason is unknown.

Leave one basic code and a short note. If there are twenty-five codes, agents will start choosing a random one. If there is only one code - “did not buy” - you will not learn anything. The reference book should answer the question of which part of the process is worth checking, and not describe the client.

Compare cases of the same type

  1. Group requests by source, product, and time to departure.
  2. Separate new requests from repeat customers.
  3. Do not mix a quick package tour and a complex individual itinerary.
  4. Compare the same stage: before the brief, after the proposal, after approval.
  5. Look for repetition on at least a few occasions, not just one glaring failure.

For example, low conversion from advertising and from recommendations may have different reasons. In the first channel, people are still testing the trust and format of the service; in the second, they often come with a specific task. The overall percentage will hide at what stage another material or question is needed.

Conduct a weekly review in 30 minutes

  1. Five minutes: Select 8-12 recently closed queries.
  2. Ten minutes: check the facts, the last step and the quality of the reason.
  3. Five minutes: Group repeating stops.
  4. Five minutes: Select one point in the process to change.
  5. Five minutes: Assign an owner, due date, and review metric.

The purpose of the meeting is not to explain every loss. The goal is to select one improvement that the team can apply in the next call.

Weekly review rule

How to Ask for Feedback Without New Pressure

If the relationship allows, ask one neutral question after closing: “To improve my work, tell me what most influenced the decision: plans changed, options didn’t work, budget, speed, or something else? It is not necessary to answer." Don't argue with the answer or use it as a reason to continue selling.

  • The request is sent once at the appropriate time.
  • It’s easy for a client not to respond.
  • The options do not push towards the desired cause.
  • There is no request to disclose another agent's decision.
  • The answer is kept brief and without unnecessary personal data.
  • The agent thanks and closes the dialogue.

Change the process, not the label you attach to the client

  • If the value is unclear, simplify the comparison and show the trade-offs.
  • If a decision is waiting for another participant, involve that person earlier with the client’s consent.
  • If the pace is lost, reconsider the promise of the first answer and priorities.
  • If the budget becomes clear late, improve the brief and full calculation.
  • If the proposal is overloaded, reduce the number of scenarios and name the next step.
  • If the reason is unknown, improve the correct closing of the request.

Don’t create a new script, a new selection, five reminders and a discount at the same time. You won't know what worked, and the client will feel more pressure. Select one change, apply it to a matched group, and predetermine the follow-up period.

What indicators to watch

  • The share of closed requests with a confirmed reason.
  • Conversion by source and comparable trip type.
  • Transitions between stages: brief, proposal, discussion, decision.
  • Median time of first response and first useful suggestion.
  • The share of requests that stopped immediately after selection.
  • The number of repeated causes in one section of the process.
  • The result of the selected change on the next series of calls.

Protect your team from a blame culture

The analysis should not turn into a rating of “bad clients” or public criticism of the agent. Consider the system: information, timing, tools, handover, scope of work, and clarity of decision. Discuss a particular error with facts and a clear way to prevent it.

Four week implementation plan

  1. Week 1: Agree on closing criteria and ten reasons.
  2. Week 2: Complete the cards without trying to fix everything right away.
  3. Week 3: Do your first review and choose one change.
  4. Week 4: Compare the next group and decide whether to pin, adjust or cancel.

Check the evidence before drawing a conclusion

  • The conclusion is based on several comparable cases.
  • Confirmed causes are separated from hypotheses.
  • There is no assessment of the client's personality or solvency.
  • Change is within the control of the team.
  • The metric and verification period are set in advance.
  • The result does not promise that every request must become a sale.

Not every failed sale is a problem: sometimes the product really doesn’t suit the client or plans change. The value of debriefing is to stop guessing, see the recurring tensions, and step by step make the path to a solution clearer, faster, and more honest.