Duplicate mixed offers
Booking.com's approach
Now you'll pay€ 0
No payment needed now. You'll pay at the property.
Votes V.
UX case study · A/B testing
Findhotel already sold rooms that a traveller could pay for at the hotel instead of at checkout. Nobody could choose that while booking. I designed the first version of that choice, and a five-week test measured what it was worth.
The choice ended up on the room selection page, before checkout. I wanted it in the checkout itself, and further down is why it could not go there.
Problem
Findhotel is a smaller player in hotel booking. It works the local markets that Booking, Expedia and TripAdvisor tend to leave alone. Letting travellers pay at the hotel is one way a platform like that can stand out.
Pay later could go a thousand directions. Everyone had a view on how it should look and what belonged in a first version. Several scrum teams were involved, and the feature was meant to move conversion on the company's main product, so everyone was right to have a view. Something had to settle it.
Much of what Findhotel sells is distress inventory: rooms a hotel expects not to sell, and cannot list itself without the big platforms ranking it lower.
So the business case was never in question. Pay later meant bringing in the right hotels, changing how bookings were handled, and finally giving travellers a way to choose it. That last part is the one I designed, and it was harder than it sounds.
Goals
We knew travellers would welcome the feature. Nobody knew by how much, so the first version was designed to find out.
All three are one goal: get a number. A small first version was not a way to do less work. It was the only way to measure the feature, and only a measurement would win a second round. Everything else I wanted to design had to wait for it.
Scope and constraints
Three constraints shaped this more than any design decision I made.
The first was the checkout page. A technical limit meant we could barely change it, so the switch in checkout I wanted was off the table, along with several other designs. That left one place for the choice: the room selection page. Asking someone to pick when to pay before they reach checkout is odd. But it could ship, and shipping something measurable was the point.
The second was the search page, where a traveller decides which hotel to open. Another team owned it, and it could not change in time for the test. It showed only the top three providers for each hotel, and Findhotel's own pay-later offers were not always among them. So a traveller could see pay-later offers from Booking, Agoda and Expedia, and none from Findhotel, even where Findhotel had them.
The third was language. The first weeks of the test ran in English only, because the translation system was too slow for copy that would change several times.
A Korean, Thai or Danish traveller saw the rest of the site in their own language and the pay-later words in English, in the middle of a purchase. That is odd. But American users were by far the largest group on the platform, so most of the people who saw the feature saw it whole.
Team
I was the only designer on the feature. I studied the competition, ran the ideation and scoping sessions, prototyped and tested the concept, drew the final screens, tested the build by hand and watched real sessions once it was live. A product owner, a data scientist and a scrum team of developers built it with me.
Our product owner brought the business case and the priorities. Our data scientist brought the numbers the decisions were made against, and designed the A/B test itself, which matters more than it sounds: a test designed by the people who want a particular answer is not a test.
A dedicated copywriter wrote the words. An external agency translated them. I was the only designer on the feature, and the developers were a scrum team inside an organisation that had several.
Benchmarking the competition, running the team's ideation and scoping sessions, wireframing, building a prototype low-fidelity enough to argue with, guerrilla testing it, turning the result into a development plan, and drawing the high-fidelity screens against the design system.
After that: keeping the copy pointed at what the test was measuring, testing the build by hand against every scenario we had agreed on, watching real sessions once it was live, and writing the whole thing up for colleagues who were never in the room.
Inside the box, the product owner, the data scientist and the developers worked alongside me, one of the developers mainly on the front end. There was no scrum master. The product owner and I answered to the product director. Around the box are the other teams, built the same way: a designer, a product owner and developers. I worked mostly with their designers, and with the designer of the Search listing team on keeping the customer journey aligned. Its product owner and I communicated indirectly.
Process
This was the first version of pay later at Findhotel, and it had to earn the rest.
I took apart every major booking platform, and several smaller ones, screen by screen. I wanted findings the team could act on: what the industry had settled on, where the gaps were, and which of our arguments bigger players had already answered.
It also turned up more questions than it answered, and I handed several of them to teammates to research. That is what a benchmark is for: the useful part is often the question, not a copy of someone else's answer.
Free cancellation
Reserve now, pay later
Free cancellation
Reserve now, pay later
Free cancellation
Before Tue, Nov 24
Reserve now, pay later
Your payment options
Team note Try to find a non-refundable pay later deal.
MX$0.00 due now. Payment information is only needed to hold your reservation.
Liked Because it gives you a clear expectation of what is about to happen, and why this info is needed. All in a neat little package.
Collected at the property Unless specified otherwise, rates are quoted in Euros. Rate quotes in EUR are based on current exchange rates, which may vary at time of travel. Final payment will be settled in local currency directly with the hotel.
Pricing and rewards
US$47.17 total collected by hotel
Collected by the hotel Rate quotes in EUR are based on current exchange rates, which may vary at time of travel. Final payment will be settled in local currency directly with the hotel. Unless specified otherwise, rates are quoted in USD.
NO PREPAYMENT NEEDED
pay at the property
Free cancellation546
Book without credit card4
No prepayment194
Liked Because it gives you an expectation of “how many of these are there”.
FREE Cancellation, NO PREPAYMENT NEEDED29
Breakfast included24
Liked Because it allows you to filter right in a hotel.
FREE cancellation before 20 November 2020
NO PREPAYMENT NEEDED, pay at the property
Between the room options
Now you'll pay€ 0
No payment needed now. You'll pay at the property.
Liked Because it gives you a clear expectation of what is about to happen.
NO PREPAYMENT NEEDED, pay at the property
Liked Because it gives you a clear expectation of what is about to happen.
Team note We don't know per hotel, so we will need to mention something vague.
Liked Because it gives you a reason why they need this info.
Further down the confirmation page
Price approx. € 63Payment info
You will pay in the local currency US$74.39. The displayed amount (in EUR) is indicative and based on the exchange rate at the time of booking.
You have guaranteed your booking by credit card
This property doesn't require prepayment. However, the property may temporarily hold an amount on your card, to test your card and guarantee your booking. This test payment will be returned to you.
Your payment will be handled by the property. The 'Payment' section below has more details
Price € 62.91Payment info
Book now, pay later
Free cancellation526
Pay at the hotel365
Book now, pay later97
Pay later, through Agoda
Pay nothing until 23 November 2020
RISK FREE! Pay nothing until 23 November 2020
Free cancellation before 23:59 hrs. on 24 November 2020 (property local time)
Depending on your payment currency, Agoda's currency exchange rate may be applied as per Agoda's terms of use
Liked Because it allows you to switch right in the Payment page.
Liked Because it gives you a very last reminder that you will not be paying now. Albeit VERY SHOUTY!!!!!11
Reserve now, pay at stay
Free cancellation
Reserve now, pay at stay
Properties with special offers
Free cancellation until 11/25/20
Reserve now, pay at stay
Team note On the Expedia and Hotels.com offers, not on Agoda's.
Free Cancellation until Nov 25, 2020
Book now, pay at stay!
Book now, pay at stay!
Book now. Pay later when you stay.
€0 due now. Payment information is only needed to hold your reservation.
Liked Because it gives you an expectation of your CC statement in the short term.
Your reservation is with Hotels.com, who will handle your customer service needs.There are no surprises and no hidden fees. This is your total price.You can cancel for free before Nov 25, 2020.
On the result card, desktop
Pay on the spot
Team note ZenHotels seems to have forgotten to add pay later to its mobile results.
No card required for booking
Free cancellation available
Pay now
Pay on the spot
Free cancellation before November 20*
Pay on the spot, Card is required for booking
Pay on the spot
Credit card required
Liked Because it gives a clear expectation of what you need.
Your card details will be transferred to the hotel for your booking guarantee. According to the booking conditions, the hotel can withdraw the amount from your card before checking-in.
On the result card, desktop
Pay now or at property
Team note Strangely enough, Hotels.com does not display pay at property on mobile, only on tablet or desktop.
In the window that asks when to pay
Choose when you'd like to pay
Team note Nothing in the payment tells you how much the so called “Deposit” will be.
Six platforms let a guest book now and pay at the property, and no two of them call it the same thing.
What the team liked most was a plain statement of what happens next: nothing is due now, and the card is only there to hold the booking. The two platforms that were followed past checkout kept saying who collects the payment, in the email and again under booking management.
I ran the ideation sessions, and the benchmark made them work. A room of people with strong opinions is hard to lead. A room that has just seen what five competitors shipped is easier: the material did the arguing.
Before the sessions, I wrote down why a traveller would want to pay later, from my own research into payment motivations.
I want to reserve something without tying up my money
I prefer to pay in cash
It is low risk if I need to cancel, and it feels more secure
I do not have the money at the moment
I want to lock in the price I see
Booking.com's approach
Now you'll pay€ 0
No payment needed now. You'll pay at the property.
Votes V.
Selected approach
Expedia's approach
Votes A., M.
Agoda's approach
RISK FREE! Pay nothing until 23 November 2020
Free cancellation before 23:59 hrs. on 24 November 2020 (property local time)
Depending on your payment currency, Agoda's currency exchange rate may be applied as per Agoda's terms of use
You can also choose to pay now with a credit card or other payment methods below.
Votes Gil
Where a property offers both, list only pay later
Anything that comes from Back-office FindHotel and has both the Pay now and Pay later option should be Pay later.
No votes
I wanted the choice in the checkout itself, the way Agoda does it. The checkout could barely change, so we took Expedia's approach instead: a choice made before checkout. Expedia had the most mature pay-later system in the benchmark, which made it the one to learn from.
Scoping ran alongside, with the product owner and the data scientist. We kept two questions apart: what is the ideal version, and what is the smallest version worth testing? Keeping both meant every cut was written down, ready for a second round.
Before anything else, I mapped what a traveller could do and what would happen when they did. Not just the happy path: every outcome, including the ones nobody wants.
The development plan is only as good as this map. Mapping the scenarios first turns edge cases into design decisions instead of bugs found in the last sprint. It does not catch everything, and this one did not.
Every interaction, and what follows from it. The edge cases are the point of this drawing, not the middle.
The wireframe became a clickable prototype. It opens on a choice of three proposals for showing the price, and each one carries on through search, room selection, the choice between paying now and paying at the property, and the payment page. Feedback on something people have clicked through is worth more than feedback on a diagram, and it comes sooner.
I kept the prototype rough on purpose. The audience was stakeholders and anyone with an interest in the outcome, and a polished screen invites a conversation about the polish. Then I tested it in the corridor with colleagues, to catch the obvious problems before they cost a sprint. The questions it raised went back to the team to research properly.
The Figma prototype, wired the way it was built, for a booking of one night and two rooms. The payment choice is the screen the whole feature turns on, where paying now and paying at the property become two different things.
Then I drew the final screens with Findhotel's design system, so the developers built a layout instead of guessing one. Spacing, colours and icons all came from the system, and the key desktop and mobile screens went to the developers in Zeplin.
From the final screens I drew the development plan: the happy path, the main edge cases and the screen each one lands on. The product owner and the developers wrote their tickets from it.
Two questions sort a booking into one of three versions, and a third question, about currency, adds one message along the way.
Is it a pay later deal?
Does the room offer both pay later and pay now?
What gets builtDon't show the Pay later label.
Movenpick Hotel Amsterdam City Centre
★★★★8.8Superb
What gets builtShow a Pay later label on the deal, the same in the results list and on the hotel page.
Movenpick Hotel Amsterdam City Centre
★★★★8.8Superb
What gets builtDon't show the Pay later label.
Standard double or Twin room
Breakfast included
Free cancellation before Tue, Aug 27What gets builtReserve goes straight to the payment page. Back from there returns to the room page.
Standard double or Twin room
Breakfast included
Reserve now, pay later
Free cancellation before Tue, Aug 27Go to the next screen (payment page)
What gets builtReserve opens Select payment preference, so the traveller picks pay later or pay now.
Standard double or Twin room
Breakfast included
Reserve now, pay later
Free cancellation before Tue, Aug 27Pay at property
Pay now online
What gets builtHide the pay later messages and the label. Display the tooltip that explains why part of the price is paid at the property.
Price details
What gets builtShow Pay now as zero and the whole amount under Pay at property, with the label and the card notice.
Price details
Your credit card information is needed to guarantee your booking. You’ll pay at the property.
What gets builtDisplay the tooltip that explains why part of the price is paid at the property.
Payment
What gets builtShow what is already paid and what is due at the property, on the page and in the email.
Payment
What gets builtNothing to add.
No changes
What gets builtShow the same amounts above the price details.
What gets builtA cancelled booking looks as it does today.
No changes
Is there a cross-currency conversion?
Asked at checkout, confirmation and booking management
Rates quoted in EUR are based on current exchange rates, which may vary at the time of payment. The property will charge you the full amount of €316.00 in USD.
Don't display the message.
Beyond the screens
Two pages of words had to change as well: the Terms page, to describe nominal fees in legal language, and the help page that answers “Do I need a deposit when making a reservation?”. Both followed Expedia's example. Expedia's rules, below
It also settled something design could not decide alone. This version ran on Expedia's data, so it had to follow Expedia's rules for handling a booking after checkout. I read those rules and redrew them as a decision flow anyone could follow. The developers found it as useful as everyone else: it showed which features we inherited, and which we chose not to build yet.
The traveller checks out
Was the transaction pre-authorised?
The booking does not succeed
The traveller sees a message about the unsuccessful booking, and goes back to checkout
Is it a pay later booking (property collect)?
The traveller is charged right away (the pay now path)
Is it a property collect with a deposit?
The traveller is charged the deposit
The traveller is told the schedule of payment and how much will be charged
Is there a nominal amount to be charged?
The property holds the funds on the card to verify it, without taking the money out
A nominal amount is charged to the traveller's card
The traveller is told a nominal amount will be charged, and how much
At the property, the nominal amount is deducted from the total payment, and the traveller is told
Was the booking consumed?
Was the cancellation done on time?
The cancellation policy is taken into account
The traveller is recommended to contact the property directly, to ensure refunds
A penalty is applied to the traveller, who is told
Was the booking partly refundable?
The traveller is charged or refunded, with the necessary deductions
The traveller is given the contact details of the property
The cancellation policy is shown to the traveller
Was the booking non-refundable?
The cancellation policy is shown to the traveller
The booking was free cancellation
The cancellation policy is shown to the traveller
The traveller is recommended to contact the property directly if they see a charge on their card
The traveller is given the contact details of the property
Does the traveller deserve a refund?
The traveller gets a refund email
The booking is cancelled
The traveller gets a cancellation email
Did the traveller show up on the first night?
The cancellation policy is taken into account
Does the traveller deserve a refund?
The traveller gets a refund email
The traveller is charged the deducted amount
The traveller is charged
Side A was the booking flow as it was. Side B added the choice, and side B is what shipped. I drew the two sides next to each other, so a colleague who missed every meeting could see in seconds what had changed.
An experiment that only its own team understands has told the company nothing. So the product owner and the data scientist wrote the report, and I made this drawing to go with it.
Side Athe control
Side Bthe change
Between brackets: what pay later added or changed
Does the deal support pay later?
Palms Place
★★★★8.4Very good 10,553 reviews
4381 West Flamingo Road, West of the Las Vegas Strip, Las Vegas, Nevada, United States
Studio Suite, One King Bed, No B…
Free cancellation before Dec 08, 2020Compared with 1 other site
Nightly price including taxes and fees
Palms Place
★★★★8.4Very good 10,553 reviews
4381 West Flamingo Road, West of the Las Vegas Strip, Las Vegas, Nevada, United States
Studio Suite, One King Bed, No B…
Compared with 1 other site
Nightly price including taxes and fees
Pay at property
Pay now online
Which way did the guest pay?
Palms Place
★★★★8.4Very good 10,553 reviews
4381 West Flamingo Road, West of the Las Vegas Strip, Las Vegas, Nevada, United States
Check-in instructions
Studio Suite, One King Bed, No Balcony
Free cancellation before Dec 08, 2020Price details
Pay at property amount will be collected by the property in the local currency.
About Us · Careers · Privacy Policy · Terms of Use · Hotels FAQ · Contact
Palms Place
★★★★8.4Very good 10,553 reviews
4381 West Flamingo Road, West of the Las Vegas Strip, Las Vegas, Nevada, United States
Check-in instructions
Studio Suite, One King Bed, No Balcony
Price details
Pay at property amount will be collected by the property in the local currency.
Your credit card information is needed to guarantee your booking. You’ll pay at the property.
Payment
We accept the following payment methods
VISA●●AMEXD
Card number *
Only needed to guarantee your booking
Expiration MM/YY *
CVV code *
First name of card holder *
Last name of card holder *
We use secure transmission
We protect your personal information
Important information
Free cancellation before Dec 08, 2020
Property fees
By clicking “Confirm Payment”, you agree you have read and accepted our Terms & Conditions, Privacy Policy
About Us · Careers · Privacy Policy · Terms of Use · Hotels FAQ · Contact
Congratulations!
Your booking has been confirmed
Booking ID:
653164925677003
We’ve sent a confirmation email to gilberto@findhotel.net. This might take a few minutes.
Didn’t receive the email?
Manage bookingPrice details
Pay at property amount will be collected by the property in the local currency.
About Us · Careers · Privacy Policy · Terms of Use · Hotels FAQ · Contact
FindHotel Confirmed Booking at Palms Place
FindHotel customer service <support@mail.findhotel.net>
To: gilberto@findhotel.net
Thank you for booking with us, Test!
Palms Place has confirmed your stay 🎉
Palms Place4381 West Flamingo RoadContact details+17029327777
Booking overview
StatusConfirmed
Reserved for Test Test last name
Studio Suite, One King Bed, No Balcony
28 nights, 2 adults 0 children
Check-in
Dec 9, 2020 from 16:00
Check-out
Jan 6, 2021 from 11:00
Price breakdown
1 room, 28 nightsUSD 2477.75
Taxes and feesUSD 331.47
Payment
Already paidUSD 2809.22
Due at propertyUSD 1238.16
Total price (with taxes & fees)USD 4047.38
Check-in instructions
Extra-person charges may apply and vary depending on property policy. Government-issued photo identification and a credit card may be required at check-in for incidental charges. Special requests are subject to availability upon check-in and may incur additional charges; special requests cannot be guaranteed. The name on the credit card used at check-in to pay for incidentals must be the primary name on the guestroom reservation.
Congratulations!
Your booking has been confirmed
Booking ID:
544952678778708
We’ve sent a confirmation email to gilberto@findhotel.net. This might take a few minutes.
Didn’t receive the email?
Manage bookingPrice details
Pay at property amount will be collected by the property in the local currency.
Cancellation Policy
Free cancellation until 08 December 2020 12:00 AM (GMT -08:00). Cancellations made after 08 December 2020 12:00 AM (GMT -08:00) are subject to a 1 night penalty plus taxes and fees. If you fail to check-in for this reservation, or if you cancel or change this reservation after check-in, you may incur penalty charges at the discretion of the property of up to 100% of the booking value.
Questions?
Contact us+31 20 200 8439
Email uscustomercare@ian.com
About Us · Careers · Privacy Policy · Terms of Use · Hotels FAQ · Contact
FindHotel Confirmed Booking at Palms Place
FindHotel customer service <support@mail.findhotel.net>
To: gilberto@findhotel.net
Thank you for booking with us, Test!
Palms Place has confirmed your stay 🎉
Palms Place4381 West Flamingo RoadContact details+17029327777
Booking overview
StatusConfirmed
Reserved for Test Test last name
Studio Suite, One King Bed, No Balcony
28 nights, 2 adults 0 children
Check-in
Dec 9, 2020 from 16:00
Check-out
Jan 6, 2021 from 11:00
Price breakdown
1 room, 28 nightsUSD 2477.75
Taxes and feesUSD 331.53
Payment
Already paidUSD 0.00
Due at propertyUSD 4047.44
Total price (with taxes & fees)USD 4047.44
Check-in instructions
Extra-person charges may apply and vary depending on property policy. Government-issued photo identification and a credit card may be required at check-in for incidental charges. Special requests are subject to availability upon check-in and may incur additional charges; special requests cannot be guaranteed. The name on the credit card used at check-in to pay for incidentals must be the primary name on the guestroom reservation.
Before release, I checked the build by hand. Once it was live, I watched real travellers use it.
Once the developers had something unreleased, I worked through that sprint's scenarios by hand. This is where the scenario map and the scope diagrams paid off: without them, “did we test everything?” is a question for memory.
Alongside the scenarios, the team checked the build against each of these, wherever they applied. It is a long list for a small feature. That is what adding a payment choice to an existing booking funnel takes.
Once it was live, the question changed from whether it works to what people actually do with it. I used FullStory, which records real sessions and filters them by behaviour or by country. Every problem, bug or idea I found, I wrote down. Bugs slip through, and interfaces do strange things in some browsers. This is how you find out which.
Five sessions of travellers checking out with pay later, on different devices. Two are on side A of the test and three on side B.
Taiwan, desktop, A side
India, desktop, B side
Ohio, phablet, B side
Qatar, mobile, A side
Spain, tablet, B side
Conclusion
Conversion on Expedia offers, the only offers in the test. It already counts the extra cancellations below, so it is what the feature was worth after them.
More cancellations on pay-later bookings than on pay-now ones, as a relative increase. We expected it: an unpaid booking is easier to walk away from. It is the cost of the gain above.
The search page problem from the start also shaped the result. It often hid Findhotel's own pay-later offers, so an unknown share of the travellers in this test never found the thing being tested.
So 4.2% is a floor, not the full measure. The feature was probably worth more, and we do not know how much more. The search page was fixed later, but the test never ran again. What the test gave us was a direction, and that was enough to justify the work that followed.
Our data scientist designed the test. Development ran from October to December 2020, the test went live in December, and the results came in January 2021.