This is a good discussion.
So far so good. I did get a feeling that you think they didn't have considered it and if they did, they would have offered it. But of course, I can be wrong.
Originally Posted by
San Gottardo
Well good, if you are so familiar with it, why are we having the debate about booking guarantee creating more IDBs.
Because it is necessary that a booking guarantee mechanism increases potential IDBs, as I shall follow on:
Originally Posted by
San Gottardo
Precisely, that is how inventory management works! That is already how they manage their fare buckets today between J, C, D, Z, I and so on: they close lower booking classes so that they can keep higher ones open. At one point they close them all to avoid creating too much overbooking and having to bump people. Nothing to do with booking guarantee. For instance, if the algo gets it wrong and closes I, Z, D, and C too early and only leaves seats in J because the airline expects people to turn up and buy J but then they don't - unsold seats are the result. And vice versa, if you leave availability open for too long (=create too much overbooking) then you create IDBs. We agree on that, don't we? Now just apply exactly that principle to booking guarantee: make the booking guarantee class the highest booking class (with the highest protection level), then close lower booking classes earlier depending on what you expect for the highest booking class. Exactly the same thing as today. Booking guarantee is just a different bucket, the one that you close last.
The key difference is, that even if you leave availability open for too long, you might easily end up with lower income due to lower fares getting sold, but you can still zero out all classes at capacity (or capacity +1 or capacity +2, as you desire, whether that is specific flight capacity, capacity for the rest of the day, group capacity etc.). General guarantee mechanism (i.e. open to all eligible customers at all times) removes this option as it forces theoretically up to unrestricted (but always non-zero) availability.
Eventually, someone will use this non-zero availability to force an (undesirable) overbooking (which is not much of a problem in Y, but is a much bigger issue in J).
Originally Posted by
San Gottardo
?? This is the part I don't get. You accept that inventory management is good enough to manage inventory between the different fare buckets, that it manages to close fare buckets earlier or later based on predictions, differentiating between different protection levels - but it wouldn't be good enough to manage one additional bucket using precisely the same methods? Why not?
Originally Posted by
San Gottardo
I agree. In today's world, this is why they leave lower booking classes open long enough toavoid unsold seats. In the booking guarantee world, they would leave "non-Elite" availability open long enough to avoid unsold seats.
Because I believe that booking guarantee demand is much more volatile than general demand and as such less predictable.
Originally Posted by
San Gottardo
You are right. You would need 100% reliable inventory management to avoid unsold seats or to avoid overbooking. But that is the case already today. See above: if you close lower booking classes too early you may find yourself with unsold seats if you mis-predict the number of people buying at high fares; or if you leave booking classes open for too long , you create too much overbooking. But that is already a problem with inventory management today, predictions can be wrong. Not different if you introduce booking guarantee. You can get it wrong as well in the future, but there is no reason why you'd get it wronger than before.
I would say the reason is necessarily increased volatility of guaranteed flight demand + inability to zero out a flight in advance.
Originally Posted by
San Gottardo
In theory, yes. But, the way this was explained to me by a revenue manager is that you hardly have any more fluctuation in the last 24 hours before departure. The ratio of booked seats/available seats (the "overbooking factor") stays pretty stable, and waitlists hardly move.
I would also not expect this to actually exist in the wild, but it would be an option, if it existed.
Originally Posted by
San Gottardo
This is where I fundamentally disagree with you. I believe that over time repeat high fare customers have higher economic value for the company than one-time customers. I would look at LTCV (long term customer value or life time customer value, depending on whose term you use) rather than the economic value a customer generates with one flight. Especially since the booking guarantee customer would in any case have to pay the highest fare. Result: the booking guarantee customer has higher lifetime value and equal transaction-value-on-this-flight.
Whether Plats are always higher LTCV customers is a different debate and may well be questioned.
That is an entirely fair belief. Probably less likely to be shared by AFKL, judging by signals such as the state of Ultimate program...
Originally Posted by
San Gottardo
No. What I have certainty about is that inventory management systems can run a booking guarantee scheme without problems. That is one statement.
What I have no certainty about at all and said so repeatedly and therefore asked the question was if they had considered and dismissed it or never considered it. I don't know. That is another statement.
I would still say it's riskier than not having such a scheme; that however does not mean it can not be worth it to an airline. I just think AFKL has decided, opposite to LHg (and in line with most other airlines around the world, it seems) that it isn't.
Originally Posted by
San Gottardo
Yes. Because I can think of some customers who find this valuable.
Some? Certainly. Enough? That'd debatable.
Originally Posted by
San Gottardo
Because you mention another airline's inventory.
As a point of comparison of what can drive the difference in risk assesment. Certainly general revenue management takes the structure in account in both cases.
Originally Posted by
San Gottardo
Is it? Since when? Not in my original quesiton at least. Because it's also in the short haul network that I would find booking guarantee super helpful and where it is sometimes needed.
OK, maybe I shouldn't have used the term "whole discussion", although to be fair, only one other poster also mentioned short haul, in reaction to your reaction to them, and to point out that they don't disagree with you.
Originally Posted by
San Gottardo
Yes, you are right. This is exactly the situation where bumping pax will be unavoidable and it will cost the airline. The very same moment where those that can benefit from the booking guarantee will say "Those guys really got me out of a critical situation". In marketing there is something called the gratitude moment which translates into higher loyalty, which is worth money (FYI: there are firms who actively play with that. Make small issues appear big and then let the customer agent who solves the problem appear as the saviour, and create the moment of gratitude, which has been proven to translate into higher lifetime value of those customers)
That is actually an extremely good point I haven't considered...
Originally Posted by
San Gottardo
But there are ways around it: AFKL could suspend booking guarantee in the case of network meltdowns (strikes in France...) and simply revert to the promise that already exists today: "you'll be top of the wait list."
Yes, potentially, or limit the number of "guarantee" seats on any given flight to, say, 2... however, that sort of defeats the purpose of the guarantee I'm afraid, making it sort of a "we'll take you if we have place" stand-in with only slightly better conditions for qualifying elites than general public.
Originally Posted by
San Gottardo
Why? Hypothetical example: ff Lufthansa has to bump a passenger from Dublin to Athens; it can put him on one of four LHG A320 planes that leave in the next couple of hours. Each of those next planes has 160 seats, a total of 640 seats. One connections is via Frankfurt, one via Munich, one via Zurich, one via Vienna. To re-accommodate the bumped pax it has to find just one seat among the 640 seats that leave in the next hours.
Now if KLM has to bump a passenger from Dublin to Athens; it can put him on one of four A320/B738 AFKL planes that leave in the next couple of hours. Each of those next planes has 160 seats, a total of 640 seats. Three connections are via Amsterdam, one via Paris. To re-accommodate the bumped pax it has to find just one seat among the 640 seats that leave in the next hours.
The point that I am trying to make: it doesn't matter if you have four hubs or two or three. What matters is how much capacity you have to re-accommodate bumped passengers. It doesn't matter if all those re-accommodation solutions fly through one or different hubs.
The difference is, if there is flight disruption in Amsterdam, you are down to 1/4 capacity. If there is a disruption in Frankfurt, LH still has 3/4 capacity. Or maybe 1/2 of F seats, if we take a hypothetical destination served from FRA and ZRH with F and MUC and VIE with no F.
Originally Posted by
San Gottardo
The debate would then be if LHG has a much denser network than AFKL which would allow it to have access to more inventory. Probably the answer depends on what connections one is looking at, and to what extent airline alliances are being taken into account. Being bumped of a Lufthansa flight from ATL or Rio de Janeiro will leave you in a worse place than bumped off an AF flight. LHG has one daily to each ATL and GIG, whilst AFKL have three dailies to ATL (plus the DL JV) and 18 weekly flights to GIG. Bangkok would be the other way around: one AF and one KL, but three (or even four?) daily LHG flights and alliance partner TG.
Not particularly more inventory, but more distributed, and therefore more disruption resistant.
Originally Posted by
San Gottardo
They do. Already today. Also in Business Class. Nothing news. Algos are imperfect.
Yes, but a guarantee concept would make the imperfection even more pronounced, IMO.
Originally Posted by
San Gottardo
You would be right if booking guarantee worked until the last minute, because as you say it would remove the concept of sold out. But that's not what I suggested. The flight *is* sold out even for everybody, including the top customer 24/36 hours (pick your number) before departure. I just apply the same principle that inventory already apply today: close lower booking classes earlier to only leave the higher ones open. I just make the booking guarantee class the highest one.
It removes the concept of "sold out" at any time sooner than 24h before departure. And as you earlier yourself noted, there is not much sales in this period anyway...