A blank results page can leave a customer guessing whether the holiday doesn't exist, the website has failed or their requirements are too demanding. Your agency may still be able to help. The page needs to explain what happened and give the traveller a useful next step without promising availability you haven't checked.

Start by separating the situations that your website currently groups under "no results". A completed search with no matching offers is different from a search that never received a supplier response. Your customer doesn't need the technical detail, but your team needs that distinction before choosing the message. Otherwise, a service problem can look like a shortage of holidays.

Explain the search you actually completed

A supplier catalogue describes the properties or products a connection can potentially access. Availability is a more specific answer for the dates, travellers and other criteria submitted. Booking.com's accommodation search documentation shows that dates, guest numbers, rooms and optional filters form part of that request. The presence of a hotel in a catalogue doesn't establish a matching offer for every search.

Keep the wording within the evidence your system has. "We couldn't find a match for these details" is a proposed message for a completed search with no matches. "This destination is sold out" would make a much wider claim. Don't turn a limited search result into a statement about the entire market.

Display the criteria beside the message so the traveller can spot an unintended choice. Show the dates, party and room arrangement in ordinary language. If a filter is still active from an earlier search, make it visible. Our guide to planning travel search filters covers the separate task of defining those controls and deciding which resulting pages need search visibility.

Give failures their own response

Ask your website supplier to show what happens when a search times out, a supplier connection is unavailable or only part of the search completes. Agree which outcomes can be distinguished in your setup. Where the cause is unknown, use wording that acknowledges that uncertainty. "We couldn't complete this search" gives a different expectation from "No holidays available".

Expedia Group's Rapid Shopping documentation provides a useful example of more detailed availability information. Its optional unavailable-reason response can describe certain restrictions, including an adult occupancy limit. Expedia also states that an actionable reason isn't returned for every unavailable property. That is a reason to ask what evidence your own integration exposes, rather than invent an explanation for each empty result.

Keep the troubleshooting detail in the staff record. A reference, time and search criteria can help the technical team investigate without asking the customer to repeat everything. The public message should offer a retry or an enquiry route that actually works. These are proposed behaviours to agree with your provider, not features to assume every booking tool includes.

Change one requirement with permission

An alternative is useful when the customer understands what changed. Offer to widen the departure date, remove a selected facility filter or consider a different room arrangement. Keep the original brief available. Quietly dropping a requirement may produce a fuller page while making the results less relevant.

Consider a fictional family searching for one room for two adults and two children. A suggested two-room search needs the family's agreement and a clear explanation that the arrangement differs. Two available rooms don't establish that they connect or sit next to each other. If the original requirement cannot be checked online, offer an adviser conversation instead of presenting an unverified match.

Make each change reversible. Someone trying a different departure airport should be able to return to their original choice without rebuilding the whole search. Show the revised dates or airport prominently when results return. A lower price means little if the traveller doesn't notice that the trip has changed.

Carry the original brief into the enquiry

The enquiry option should preserve useful work already completed. Where your setup allows it, carry across the destination, dates, party and selected filters, then let the customer review them. Ask which requirements are fixed and where there is flexibility. That is a more useful starting point for an adviser than an unexplained "Please contact me".

Tell the customer what your team will do next using a response promise you can meet. An adviser may review the brief, clarify a constraint or check another route to a suitable offer. Avoid implying that submitting an enquiry reserves a room or guarantees a price. The first response should distinguish confirmed information from questions still being investigated.

Your follow-up process should give these enquiries an owner. Record that the customer reached the form after an unsuccessful search, together with the useful criteria. Keep technical diagnostics out of the customer's free-text message. The adviser needs the holiday brief and the support team needs enough evidence to investigate the search.

Review empty searches by their cause

A single total for unsuccessful searches can hide very different jobs. Separate completed searches without matches from technical failures wherever your reporting supports it. Then review whether the customer edited the search, submitted an enquiry or left. Treat those observations as clues for investigation, without assuming that every departure represents a lost booking.

Agree a small set of fictional test searches with your website provider. Include an unusually restrictive combination, a party configuration requiring clarification and a controlled failure in an appropriate test environment. Record the message, preserved details and next action for each case. Don't deliberately disrupt live supplier connections to create a test.

Choose one empty-results journey on your own site and follow it through to the adviser. Use our booking engine overview to frame the discussion with the Travelgenix team if that's your setup. Bring the exact search and the message it produced. Ask the person receiving the enquiry to explain the customer's original requirement without any help from you.