"They went quiet" tells you what happened after a travel quote. It doesn't tell you why. If every unanswered proposal becomes a price objection in your sales report, you may end up discounting a holiday that was never rejected on price. A useful lost-quote process keeps the customer's explanation separate from the team's interpretation.

You don't need a complicated reporting project to begin. Record the outcome of one enquiry, preserve the evidence behind it and decide what the business can learn. The aim is to improve the next decision without making advisers write an essay whenever a sale falls through.

Close the enquiry, then record the reason

An enquiry can have an outcome without a known cause. "No response after agreed follow-up" is a valid outcome when that's all you know. It should remain distinct from "customer confirmed the price was outside budget". Both need attention, but they point you towards different questions.

Pipedrive's lost-reasons documentation describes both free-text reasons and predefined choices when a deal is marked lost. It also allows extra comments to be retained on the deal. That combination is useful: a consistent category makes a report readable while the note preserves what actually happened. You can apply the principle in your current CRM or a controlled review sheet without claiming every product has the same feature.

Choose a short set of categories that your team can distinguish. Price outside budget, unsuitable product, unavailable dates and plans postponed describe different situations. Keep "reason not known" available so staff aren't pushed into guessing. Add a note when the customer gives an explanation that doesn't fit the existing choices.

Keep the evidence beside the label

Record whether the reason came directly from the customer or from an internal assessment. Include the date and a reference to the relevant conversation. A short factual note is enough when the explanation is clear. Avoid turning a hurried comment into a permanent judgement about the customer.

Consider this fictional example. A customer says the proposed holiday costs more than they want to spend and mentions another offer with different departure dates. Record the budget objection and the difference in dates. You haven't established that a competitor sells the same holiday more cheaply, so a report should not present that conclusion as fact.

HubSpot's default deal properties distinguish the deal stage from the closed-lost reason. Keeping those fields separate gives your team room to record an outcome while its cause remains uncertain. For travel teams, a further distinction helps: record whether a suitable quote was actually sent. An enquiry you couldn't fulfil should not be counted as a rejected proposal when you review quote performance.

Count one buying decision rather than every version

A customer may receive several versions of the same holiday proposal. If each revision is counted as a separate lost quote, your report can make productive consultation look like failure. Choose a consistent unit for the review, such as one enquiry for one intended trip. Link the quote versions to that enquiry so the history remains available.

Separate a new trip request from a revision to an existing one. A change of hotel for the same dates may be a revision, while an unrelated holiday later in the year may need its own enquiry. Agree a practical rule and show staff a few examples. Our guide to moving a travel quote towards a confirmed booking covers the wider proposal workflow.

Keep confirmed bookings, closed enquiries and work still in progress visible in the same review. Otherwise, a month with many slow-moving complex trips may look weaker simply because those customers haven't decided yet. State which enquiries are included and the date you checked their outcomes. Comparing unlike groups can send you chasing the wrong problem.

Read the notes before changing your prices

Review a manageable group of recent closed enquiries with the consultants who handled them. Look at the explanations behind the most common categories. Several budget objections might concern the same departure period, a missing lower-cost option or enquiries attracted by an unsuitable headline offer. Those are possibilities to investigate, not conclusions the category proves on its own.

Keep unknown reasons visible in the discussion. If most closed records lack a customer explanation, the immediate task may be improving how outcomes are captured. You could agree a brief, optional feedback question when a customer tells you they won't proceed. Avoid extending contact just to complete an internal report; the existing follow-up playbook should still guide the conversation.

Read the positive outcomes too. A price objection in one enquiry might sit beside a booking at the same price where the departure airport suited the customer better. That doesn't prove why either person decided. It does give your team a more precise question to explore than whether all your prices are too high.

Give one finding an owner and a review date

Turn the review into a small operational change. If enquiries repeatedly request dates you cannot supply, check the relevant campaign and landing page before altering the quotation process. Where the brief lacks a usable budget, improve the question asked before research starts. Choose an action that addresses the evidence you have.

Write down the proposed change, its owner and when the team will review it. Keep the recording rules consistent during that period so the next set of outcomes is comparable. Don't promise a conversion uplift from a small sample or treat every change as the cause of the next booking. The first useful result may simply be a clearer explanation of what customers are declining.

Take a handful of recently closed enquiries into your next team meeting. Ask the adviser to separate the known outcome, the customer's stated reason and anything still uncertain. Agree one change to how the next enquiry will be recorded, then put a date in the diary to examine what that better record reveals.