Mastering your aviation booking flow 2.

How to master your online booking flow in aviation – part 1.

Last time, we started our journey into flight booking flows by discovering when, where (to and from), and who (at least how many people) will board that plane. However, there are still some additional necessary details to ask your passengers, such as who exactly they are, what kind of bags they have, or the method of preferred payment. And well, some not so necessary details too, regarding extras from the base fare. The revenue generated from selling ancillary products and services are particularly crucial for ultra-low-cost (ULCCs) and low-cost carriers (LCCs), based on their business model. And how you ask your users for information or to buy extra stuff during a booking flow is what, we believe, makes the difference.

With over a decade of digital design experience in the aviation industry, at Mito we know booking flows inside and out, with all their peculiarities. And believe us, there are a lot. Selling a flight ticket looks simple, but in harsh reality, it’s an edge case nightmare. Having one of the largest ultra-low-cost airlines, Wizz Air as our major client, and having designed the booking engine of the new Icelandic airline, PLAY, we’ve gained a lot of hands-on experience over the years. And luckily, we also like to talk about it – so here is part two. 

Passengers

Let’s take up just where we left off. We know how many passengers will travel from where, to where, and when. But who exactly are these people? As an industry trend, answering this is usually the third main step of the flow. Although, that might be a bit of a rush. Why ask personal details when you don’t even know if they will add any ancillary items, such as bags or a rental car? Again, maybe your user simply wants to calculate the costs of traveling to Costa Rica with two tireless teenagers, a mildly friendly cat and a certainly fragile violin. Yet again, meeting endless input fields early on will only make him/her exit the flow. Yes, backend limitations often stand in the way of good UX – still, we suggest this is the latest step that technology allows.

Ideally, saved companions could also be added to the passenger list. If you often travel with your wife, your 14-year-old teenager and her best friend’s cousin’s daughter, once saved, you should be able to select them as companions in, say, a drop-down list. Cool, right? A bit of advice, however: pay extra attention to make the saving process all transparent, together with making those passenger details editable.

Speaking of text fields, error handling is of high importance. As a rule of thumb, buttons should never be disabled. Have it enabled, and use error messages both there and at the location of error, indicating it by highlighting. Also, where possible, use on the fly error checking: if, for instance, the “@” is missing from the e-mail address, notify your users without them having to click on the CTA button. In the case of phone number formats, imagine how less the chance of error would be if passengers could simply select their country in a drop-down list, thus automatically revealing their calling code in the right way.

Everyone has some kind of bags with them when boarding a plane: be it either a tiny handbag, a middle-sized backpack that is just small enough to be a carry-on luggage, or three XXXL suitcases with their life packed inside.

Buying the luggage is a step where you can actually distinguish yourself from the industry standard, and design it in a different way. (Frequent flyers have probably noticed that booking flows are quite similar to one another).  But is it worth changing it? Let’s just suppose that bags are not tied to the passengers, as they usually are. Instead, you can take X bags in total for all the passengers. As far as we know, no one was brave enough to give this a try – and we admit, we haven’t done it either. However, it could be a great opportunity for A/B testing.

Fancy designs? No, thanks. Been there, done that, and our most important learning by far is that the easier a seat map is, the better it works for everyone. It’s fair to say that any kind of grandioseness just made things more complicated for both the passengers and us.

When designing a seat map within the booking flow, it’s important that you foreplan, including aspects you might not think of first. How many types of planes are operated by the airline? And how many different ones are planned for the future? While many use a 3-3 seating layout, transatlantic flights mostly have a 3-5-3 one. Which obviously means more functions and possibilities to prepare for.

Seat price differentiation also varies among airlines. One either defines different sections (such as front, middle and back, with the possibility of  normal or larger legrooms), offer window, middle and aisle seats, or use a dynamic pricing based on different criterias. Such as Wizz Air, whose prices vary on the actual selling volumes.

Of course, flight transfers make it all a bit more complex, or rather complicated. For each flight, you need to display a different seating chart, so each passenger can select a seat for each flight leg. Yep, that means that in the case of two people and a simple round trip, you’ll have eight seat maps. Users also need to be able to move across those, while understanding where in the process they are. The main question is, do you start by showing the seat map of the first leg for all passengers, or the map of all legs for the first passenger? In our experience, the most user-friendly and transparent solution is the former one. This also gives you the chance to iterate the preferences of the passenger(s) over the following flight leg(s). Again, a good kind of preselection.

It’s nice to have the feature of saving seats (alongside companions), so that preferred seats (such as those with extra legroom) will either be the only one listed on the map, or one of them will be randomly shown. Another idea that would be worth coming to existence.

Once again, don’t forget about parents. Seats usually can’t be selected for infants, as they are technically tied to one particular passenger. But in reality, they can travel with anyone – no first or emergency rows, though.

Seat selection, however, should never be forced. There are some definitely dark patterns here which you should try to avoid. In the case of LCCs aiming for ancillary revenue, sometimes it’s quite hard for users to manage to skip this step. But it shouldn’t take much more than clicking one button.

Of course, there are many edge cases, what ifs and infinite variations of possibilities to be prepared for. Or to not be prepared for. Because some of them, such as taking a cello onboard, are so edge case-y that they are simply not worth the needed development resources. Have you ever seen a cello aboard? Exactly. There are only around a few hundred cases such this a year. They are better off being handled manually.

Again, never forget to constantly communicate with the user, giving them either reassurance or direction during the process. Buying flight tickets can be stressful – help them. They will be grateful. You will be successful.

It’s been a long journey, and we are not quite there yet – soon, we will be back with the finishing touches of a booking flow as well as with some overall tips and tricks you should pay attention to.

Don't worry, the story continues!

Read our part 3 here!