mherdeg
Aug 12, 12, 9:23 pm
A recent experience with a series of Reservations glitches and long phone calls has made me realize that some of the magic is gone; managing my own travel post 3/3 is not as much fun as it used to be.
Here is what I was trying to do that led to "R8" becoming "R0" and my wife and I being seated in separate cabins on the same flight:
I wanted to fly with my wife LHR-LAX, SFO-IAH-LHR, about a month from now.
I wanted to use two electronic travel certificates (CO-style, "12TCVA") to pay for most of each trip. This meant having two separate reservations, one for me and one for my wife, since you can't combine travel certs.
I wanted to upgrade only one direction of travel with a GPU. Since the trip booked entirely into K, this meant holding a reservation online with the "book by phone" button, then calling UA and asking them to up-fare from K to W.
In a perfect world I would have liked the trip to be fared with sales city LON (total price $1070) instead of sales city LAX (total price $1090), although I'm not picky and have no idea why the fares work out that way.
Here is what happened:
My wife's trip's return segment was changed to W, repriced at $1090 (sales city in the U.S.), and ticketed online about 20 minutes after I hit the "purchase online" button, with some amount being paid by e-certificate and the balance being paid by my credit card. Upgrade went through just fine, flight went from R8 to R7.
My trip's return segment was changed to W, priced at £688 (sales city in London, about $1070), and never ticketed online after I hit the "purchase online" button. The root-cause problem was that united.com was unable to bill my credit card, although it took many agents a long time to realize this and try to fix it and submit a new successful "ticketing request". Meanwhile I watched upgrade inventory drop down to R3, then R2, then R0. Ouch, ouch, ouch.
My wife's trip took one call and about twenty minutes. My trip took about five calls, a little bit over two hours on the phone, and about twelve real-time hours before it ticketed. Worst of all, none of this surprised me even a little! I was totally okay waiting tens of minutes for reservations and ticketing to have back-and-forth discussions; this doesn't surprise me at all. Expectations are really, really low.
During those calls, I got to hear cool systems-internals things like
"This isn't auto-pricing, I need to call our rate desk";
"OK, your billing address is in the UK, so we've re-priced this ticket in pounds, but my ticketing desk says you pretty much have to book it with us right now or it will never work." ["Can I use my e-certificate?" ] "No." ["Can I just try online and call you guys back if anything goes wrong?"] "Ha, good luck." [He actually snickered. I should have known something was wrong.];
"Yes, I see that you haven't ticketed…This says you don't owe us any money at all! … [20 minutes on hold] … OK, you were right, you owe us money";
"Everything you've given me is fine, but our credit card processing system must be down right now, so please give me your full credit card number and I'll write it down and try to run it later";
"Yes, I see that there's currently R availability and there may not be any inventory left by the time this tickets. I'll try to upgrade you with your GPU after I ticket this for you [she didn't ticket it for me]. And I'll make a note in your record and you can follow up with a supervisor in the morning. [This did not happen]";
"No, that ticketing last night never happened. Okay, can you give us your full credit card number from scratch again?";
"Yes, you're all ticketed." ["Great, I see that I have an e-ticket number … but, umm, can you explain why the return segment is in K? The whole reason I called you guys in the first place was to make that a W fare.."] "We have fixed it." [they manually changed the fare to W and reissued the ticket?!];
"I see you're on the priority upgrade waitlist. There's nothing else we can do. Don't worry, this cabin is just over half full [28/50], you should be fine."
"Ha ha, a supervisor? What? That's ridiculous. No, we don't oversell R. No, no one has put any notes about anything like that in your record."
The upgrade inventory that was shown online when I hit the "buy" button was gone, gone, gone by the time I could try for it. A layman would surely call this "bait and switch".
Obviously what really happened was more complicated — I made two identical bookings, one "just worked" and one broke disastrously — but one should not need an expert-level understanding of an archaic distributed system to understand why things are not going their way!
Meanwhile, I have irrationally lost faith in the upgrade waitlist system and am manually polling united.com for R inventory and mobile.united.com for new "booked" numbers in the front cabin, just to see what's happening. Who can say whether this upgrade will clear eventually? In the meantime, this uncertainty is not contributing to a magical travel experience.
It's wearying. I have invested a fair amount of time in understanding this carrier's GDS and have spent a while communicating with other people who are experts in the system, but lately I seem to be, uh, wasting my talents by spending so much time waiting for people to do simple tasks. Chatting with reservations agents always used to be fun, but when I'm spending 20–30 minutes at a time on hold while they confer with a supervisor and a ticketing expert, things are not great.
Getting travel sorted and booked smoothly has become a chore. Nothing has changed about the people; the people are awesome. But the infrastructure has changed and it is not fun.
Here is what I was trying to do that led to "R8" becoming "R0" and my wife and I being seated in separate cabins on the same flight:
I wanted to fly with my wife LHR-LAX, SFO-IAH-LHR, about a month from now.
I wanted to use two electronic travel certificates (CO-style, "12TCVA") to pay for most of each trip. This meant having two separate reservations, one for me and one for my wife, since you can't combine travel certs.
I wanted to upgrade only one direction of travel with a GPU. Since the trip booked entirely into K, this meant holding a reservation online with the "book by phone" button, then calling UA and asking them to up-fare from K to W.
In a perfect world I would have liked the trip to be fared with sales city LON (total price $1070) instead of sales city LAX (total price $1090), although I'm not picky and have no idea why the fares work out that way.
Here is what happened:
My wife's trip's return segment was changed to W, repriced at $1090 (sales city in the U.S.), and ticketed online about 20 minutes after I hit the "purchase online" button, with some amount being paid by e-certificate and the balance being paid by my credit card. Upgrade went through just fine, flight went from R8 to R7.
My trip's return segment was changed to W, priced at £688 (sales city in London, about $1070), and never ticketed online after I hit the "purchase online" button. The root-cause problem was that united.com was unable to bill my credit card, although it took many agents a long time to realize this and try to fix it and submit a new successful "ticketing request". Meanwhile I watched upgrade inventory drop down to R3, then R2, then R0. Ouch, ouch, ouch.
My wife's trip took one call and about twenty minutes. My trip took about five calls, a little bit over two hours on the phone, and about twelve real-time hours before it ticketed. Worst of all, none of this surprised me even a little! I was totally okay waiting tens of minutes for reservations and ticketing to have back-and-forth discussions; this doesn't surprise me at all. Expectations are really, really low.
During those calls, I got to hear cool systems-internals things like
"This isn't auto-pricing, I need to call our rate desk";
"OK, your billing address is in the UK, so we've re-priced this ticket in pounds, but my ticketing desk says you pretty much have to book it with us right now or it will never work." ["Can I use my e-certificate?" ] "No." ["Can I just try online and call you guys back if anything goes wrong?"] "Ha, good luck." [He actually snickered. I should have known something was wrong.];
"Yes, I see that you haven't ticketed…This says you don't owe us any money at all! … [20 minutes on hold] … OK, you were right, you owe us money";
"Everything you've given me is fine, but our credit card processing system must be down right now, so please give me your full credit card number and I'll write it down and try to run it later";
"Yes, I see that there's currently R availability and there may not be any inventory left by the time this tickets. I'll try to upgrade you with your GPU after I ticket this for you [she didn't ticket it for me]. And I'll make a note in your record and you can follow up with a supervisor in the morning. [This did not happen]";
"No, that ticketing last night never happened. Okay, can you give us your full credit card number from scratch again?";
"Yes, you're all ticketed." ["Great, I see that I have an e-ticket number … but, umm, can you explain why the return segment is in K? The whole reason I called you guys in the first place was to make that a W fare.."] "We have fixed it." [they manually changed the fare to W and reissued the ticket?!];
"I see you're on the priority upgrade waitlist. There's nothing else we can do. Don't worry, this cabin is just over half full [28/50], you should be fine."
"Ha ha, a supervisor? What? That's ridiculous. No, we don't oversell R. No, no one has put any notes about anything like that in your record."
The upgrade inventory that was shown online when I hit the "buy" button was gone, gone, gone by the time I could try for it. A layman would surely call this "bait and switch".
Obviously what really happened was more complicated — I made two identical bookings, one "just worked" and one broke disastrously — but one should not need an expert-level understanding of an archaic distributed system to understand why things are not going their way!
Meanwhile, I have irrationally lost faith in the upgrade waitlist system and am manually polling united.com for R inventory and mobile.united.com for new "booked" numbers in the front cabin, just to see what's happening. Who can say whether this upgrade will clear eventually? In the meantime, this uncertainty is not contributing to a magical travel experience.
It's wearying. I have invested a fair amount of time in understanding this carrier's GDS and have spent a while communicating with other people who are experts in the system, but lately I seem to be, uh, wasting my talents by spending so much time waiting for people to do simple tasks. Chatting with reservations agents always used to be fun, but when I'm spending 20–30 minutes at a time on hold while they confer with a supervisor and a ticketing expert, things are not great.
Getting travel sorted and booked smoothly has become a chore. Nothing has changed about the people; the people are awesome. But the infrastructure has changed and it is not fun.