The customer was about to book. What made them close the page?

Imagine someone who needs a car for a few days. They enter their dates, compare the available options and choose one. Then they select a rate, start entering their details and reach the final stage. At that point, they close the page.

All the business sees is a booking that was never completed. It is easy to assume the customer found a better price. But perhaps they discovered too late how much would be charged right then. Perhaps they did not understand the difference between two rates. Or perhaps the form showed an error and asked them to start again.

They may also have been comparing options and planning to book later. An abandoned booking alone does not explain why it happened. To understand what went on, we need to follow the journey, see where it stopped and check whether other people encounter the same obstacle.

Not every departure is a lost booking

Someone may check availability before settling on dates, share an option with a travelling companion or compare several companies before choosing. No website can prevent every one of these departures, and it should not treat every visit as a failed purchase.

The more useful question is: are we making it difficult for someone who does want to finish their booking?

A drop between search and the results list may have very different causes from a drop after someone enters their details and clicks “Pay”. Looking only at how many people started and how many finished combines situations that deserve separate investigation.

That is why, before changing the design or adding a promotion, it is worth reconstructing the decisions we ask the customer to make.

First stop: choosing without all the answers

Back to our example. The customer has found a suitable vehicle, but now has to choose between a basic rate and a flexible one. One allows changes; the other does not. One includes certain cover; the other shows a lower starting price.

If the differences are spread across several screens or hidden in text that is hard to compare, moving forward means accepting uncertainty. The customer may go back, open several detail pages or leave to ask a question by phone.

The problem here may not be the number of rates. It may be how their consequences are explained: what is included, what is paid now, what might be paid later and what happens if plans change.

The final price also needs to be clear. The total cost of a booking is different from the amount charged at that moment or a deposit temporarily held. Showing those figures without distinguishing them can create doubts just as the customer is asked to confirm. In its analysis of accommodation websites, Baymard identifies problems with the clarity of total costs and charge breakdowns. That research offers useful questions to ask; it does not prove what happens on any particular booking website.

Second stop: asking for details without losing someone’s work

The customer chooses a rate and starts the form. From the business’s point of view, every field may have a purpose: managing the booking, preparing a contract or meeting an operational requirement. From the customer’s side, every field is another task to understand and complete, often on a phone.

It is worth reviewing which details are genuinely needed at each point. If a piece of information is only needed after the booking is confirmed, perhaps it should not interrupt the initial decision. If it is essential, the form should explain clearly what is required and help people correct errors.

One particularly frustrating failure happens when, after completing several steps, a generic error message sends someone back to the form and erases what they entered. At that point, the problem is no longer just the time lost: they may also lose confidence that the booking will be completed correctly.

Third stop: knowing what will happen when paying

Reaching the payment screen does not mean every question has been answered.

Before the last click, the customer should be able to check the dates, their chosen option, the relevant conditions and the amounts involved. The button should also make the action clear: does it confirm a booking, send a request or start a payment?

Afterwards, they need an unambiguous response. If the transaction is complete, they should know. If they have only sent a request awaiting confirmation, they should know that too. And if payment fails, the message should explain what to do next without forcing them to start from scratch.

There is no single solution for every business. Accommodation, activities and vehicle hire each come with different conditions. What they share is the need to make the next step clear.

How to investigate where a booking breaks down

So far, we have only described possibilities. To find out which ones affect a real website, I would start by observing the journey through four questions:

1. At which step do people stop? Search, results, rate selection, form, payment attempt and confirmation should be distinguishable. That helps identify the point worth investigating.
2. Who experiences the problem, and under what conditions? If it appears mainly on mobile, with a particular rate or after a validation error, that difference helps form a hypothesis. Conclusions drawn from only a few sessions need caution.
3. What do we see when replaying some sessions? Behaviour analysis tools such as Microsoft Clarity can help review interactions and spot repeated attempts, backtracking or elements that appear unresponsive. In a booking process, it is essential to mask sensitive data.
4. What do people say, and what do the systems record? A recording might show someone returning to a rate’s conditions three times; it cannot show whether they were looking for a detail, doubted the price or received a phone call. User testing and comments help uncover reasons a screen alone cannot reveal. Nielsen Norman Group points out this limitation of recordings without audio. We should also check form errors, payment system responses and questions received by the customer service team.

Together, these pieces can turn “people are leaving” into a testable hypothesis. For example: several people compare rates again after seeing the final summary; let’s check whether the differences and the amount due were clear earlier. Or: failed attempts cluster around one field on the mobile form; let’s reproduce that error before changing anything else.

Fix the obstacle, then observe again

Once a problem is identified, the answer does not have to be a complete rebuild of the booking engine. Sometimes it means explaining a condition more clearly, organising the rates, showing an amount earlier or fixing an error. In other cases, part of the journey may need to fit the way the business sells, which is different from changing its internal operations. We discussed that possibility in our article on MyBooking customisation in WordPress.

The key is to decide which specific problem the change should solve and then check whether it helps. Improving one screen does not, by itself, guarantee more bookings: seasons, visitor mix and offers can change. We need to keep looking at the whole journey.

The aim is not to stop everyone from leaving. It is to help someone who wants to book understand the offer, move forward without avoidable obstacles and finish knowing what they have purchased.

Conclusion

When a booking is left unfinished, the missing final click often attracts more attention than all the steps that came before it. But the doubt may have appeared much earlier: while comparing rates, interpreting a condition, filling in a field or checking the final amount.

Investigating that journey lets us stop guessing. First, we observe where it breaks down. Then we test possible causes. Finally, we change what the evidence supports.

If your business gets visitors but many bookings are left unfinished, Tornem can help you review the journey and find where the obstacles appear.