How about a red flag marker on "My Itineraries" when schedule changes occur, such that one does not need to manually check every future itinerary? ... Or maybe even an immediate email notification then a schedule change affects one of your itins.
|
Originally Posted by palmetto86
(Post 21750960)
- Stop companion PNR splitting!
|
Originally Posted by bmr12
(Post 21752394)
That's fine, but there's nothing to stop them from automatically kicking off a batch immediately after opening up R space.
|
This isn't exactly important to me, but since we're making a laundry list, perhaps someone should add "fix infant ticketing process" to the list.
|
Originally Posted by Zappity
(Post 21752194)
This is simply not possible with SHARES. Shares is a batch-based system. Everything has to be done in batches.
Down the road, some day, the airline will move to Amadeus. However, as this is a $30M project, it has been shelved for a long time. By the time it happens, United will likely be known as Lufthansa USA ;) |
Originally Posted by ual744777sta
(Post 21753217)
That means better lounges, snacks on Domestic Y, and consistency in service.
|
Originally Posted by escapefromphl
(Post 21753251)
But rigid enforcement of rules, HUCA will be dead.
|
Originally Posted by escapefromphl
(Post 21753251)
But rigid enforcement of rules, HUCA will be dead.
|
This thread is a great idea. Can I propose it be a wiki, two parts- First, the open issues, then a separate listing of the issues which were, but have since been fixed (or is actually hoping for fixes overly optimistic?).
It would be nice to see if things change over time, or if the list keeps growing. I would also add to the list some method for 3rd parties to see the data and present it in a more useful fashion (the EF issue), as well as reiterate the R=RN lies. |
Make SWU means something I have not had one clear since January. I typically book Y and B fares too.
|
UAL.COM still does not display Shenzhen Airlines' award seat availability, one year after its join of Star Alliance.
|
Originally Posted by paulyras
(Post 21754092)
This thread is a great idea. Can I propose it be a wiki, two parts- First, the open issues, then a separate listing of the issues which were, but have since been fixed (or is actually hoping for fixes overly optimistic?).
It would be nice to see if things change over time, or if the list keeps growing. I would also add to the list some method for 3rd parties to see the data and present it in a more useful fashion (the EF issue), as well as reiterate the R=RN lies. Question about the R/RN issue: Where in marketing materials does UA promise "enhanced upgrade chances for elites"? They very clearly make the promise about better premium cabin Saver awards for Plats and 1Ks -- hence why I included the I/IN issue. Point me to what the promise broken is on R/RN and I'll happily include. I had left the EF issue off my original post as I felt it was a policy thing and not a systems thing... If we put that on, we may as well put on "Make GPUs valid on all published fares" and stuff like that. But maybe it's worth making policy changes their own section.... |
Y/B/M fare Instant Upgrade (M for 1K or higher) for Elite seemed to be fixed two weeks ago, but it did not work this week. Had to call UA to get the upgrade. The agent upgraded three segments into PN bucket, instead of JN. The first segment was upgraded into JN bucket, which was done via web.
|
Originally Posted by Tracer_SEA
(Post 21754851)
Question about the R/RN issue: Where in marketing materials does UA promise "enhanced upgrade chances for elites"? They very clearly make the promise about better premium cabin Saver awards for Plats and 1Ks -- hence why I included the I/IN issue. Point me to what the promise broken is on R/RN and I'll happily include.
I had left the EF issue off my original post as I felt it was a policy thing and not a systems thing... If we put that on, we may as well put on "Make GPUs valid on all published fares" and stuff like that. But maybe it's worth making policy changes their own section.... Regarding the EF issue, I see your point, and however you feel best to approach it in this thread / wiki, I am fine with it. It is a policy thing rather than a systems issue, but many of these are a grey area. The I / IN and R / RN issues were systems issues allegedly with the shares switchover, but I wonder if it's not a policy at this point, as they've had quite some time to fix it... |
Originally Posted by paulyras
(Post 21755176)
RN was specifically the bucket for the enhanced domestic first and int'l business RPU and GPU availability for Platinum and above (prior to platinum becoming a thing, it was 1k specific). There was a post a long time ago from Shannon (previous UAinsider) stating that they were 'working on it', as post 3/3, R always equalled RN (Just like I and IN do now also). I will try to dig it up later, but it's late here and I need to get some sleep. Whether they just decided it wasn't a priority or not, I don't know. If not, why not just get rid of RN and IN and make life easier for everyone trying to understand their benefits or lack thereof.
|
All times are GMT -6. The time now is 4:57 am. |
This site is owned, operated, and maintained by MH Sub I, LLC dba Internet Brands. Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Designated trademarks are the property of their respective owners.