- Market
- Saudi Arabia
- Written for
- Commercial Director, Head of Digital
- Decision
- Raise the share of bookings that come through the hotel's own channel
- Languages
- EN · AR
The funnel
Five steps, and the two that lose most of the money
Measure before changing anything. Most hotels can name the step they think is the problem, and in our experience it is usually not the one the numbers point at.
1 · Arrival
The guest lands, usually on a room type or an offer rather than the home page. What matters here is whether the page they land on states the rate and the availability for their dates, or asks them to start a search they already did elsewhere. A landing page that continues the journey rather than restarting it.
2 · Rate comparison
The guest checks your rate against the one they arrived from. This is the step where a hotel either gives them a reason to stay or does not, and where what you are permitted to offer is set by your own distribution contracts rather than by us. A stated reason to book here, within whatever your contracts allow.
3 · The booking engine handoff
The largest single drop in most funnels we measure. The guest moves from the hotel's site to a booking engine that looks different, loads slower, and sometimes loses the dates and the room type they had already selected. A continuous journey: same design, same language, selection carried across.
4 · Guest details
Fields asked for that the booking does not need, an account creation step that is not optional, and validation that rejects a correctly formatted local phone number. Each one loses a proportion of the people who reached it. The shortest form the booking actually requires.
5 · Payment
The second largest drop. Local payment methods absent, currency presented in something the guest does not hold, and a failed payment that returns them to an empty basket rather than to the step they were on. The methods guests here actually use, and a recoverable failure.
Two funnels
The Arabic journey is not the English one translated
A hotel site with an Arabic toggle usually has two funnels with two different conversion rates, and only one of them has been measured. The Arabic side is where the layout breaks under right-to-left, where the booking engine reverts to English at the handoff, and where a date picker presents a calendar the guest has to translate mentally before they can use it.
This matters commercially more than it usually gets credited for. In this market a significant share of domestic and regional demand arrives in Arabic, and it is demand with a high direct-booking propensity — a guest booking a weekend in their own country is not price-comparing across six intermediaries. Losing them at a broken date picker is losing the cheapest bookings the hotel can get.
Before a redesign
Four things that move the number without one
- 01
Carry the selection through the handoff
Dates, room type, occupancy and language passed to the booking engine rather than re-entered. Usually a configuration and integration change rather than a project, and usually the largest single improvement available.
- 02
Add the payment methods guests here use
A checkout offering only international card schemes is asking a proportion of domestic guests to use something they may not have. The gateway usually supports more than the hotel has enabled.
- 03
Make the failed payment recoverable
A declined card that returns the guest to an empty search has lost a booking that was one retry away. Returning them to the payment step with the reservation held is a small change with a measurable return.
- 04
Measure the two funnels separately
One blended conversion rate hides the language that is underperforming. Splitting the measurement costs nothing and frequently reveals that the problem everyone was discussing exists on one side only.
Scope boundary
What this work is
What we do
- Measure both language funnels step by step before recommending a change to any of them.
- Work on the booking engine handoff first, because it is usually the largest loss and rarely a redesign.
- Report the change in bookings rather than the change in a design opinion.
A booking flow collects guest personal data and payment details, so retention, residency and consent obligations follow from the data protection regime rather than from the booking engine vendor's defaults. Establish that position before changing what the form collects.
Primary sourceCommon questions
What buyers ask
How much direct share is realistic?+
It depends on the property type and where demand comes from, and any supplier quoting a target percentage before seeing your mix is quoting a template. What is worth setting instead is a target for the funnel rather than the channel: if the booking engine handoff currently loses a large proportion of the guests who reach it, halving that loss is a measurable objective and the channel share follows from it.
Do we need to replace our booking engine?+
Usually not, and it is an expensive first move. Most of the loss at the handoff is in how the engine is configured and presented rather than in the engine itself — the language not carrying across, the design reverting, the selection being dropped. Measure the handoff, fix what configuration can fix, and only then judge whether what remains is a product limitation.
How long before we see a change?+
Measurement takes two to three weeks to gather enough bookings to be readable, and less for a busy property. The configuration fixes land inside a few weeks after that and show up in the next full booking cycle. What takes longer is anything that touches the payment provider or the property management system, because those changes queue behind a third party's release schedule rather than yours.
In this cluster
Measure both language funnels
A measured read of where the funnel loses people, in both languages, before anything is redesigned.
What happens next
- 1We reply within one business day.
- 2A 30-minute scoping call with a senior consultant.
- 3A written proposal with scope, team, and timeline.
Or reach us directly

