OOfff

Oh, woe is us.

When did I even mention the jumpseat?

gloopy

The JS dramatically enables us to travel more easily than they do. While you may or may not have intended to mean that directly, this is a never ending battle we're always fighting. It predates the RA 7.5 "I'll take a strike first" mentality and has always been a festering attitude across all airlines.

The industry wide flowback benefits the FA's enjoy today exist only because of, and only because of, pilot JS benefits that were fought and paid for over many decades.

OOfff

I never mentioned the jumpseat, nor am I suggesting any change to it is appropriate. Fight another strawman.

Baradium

Relevant to the original discussion of this thread, I was doing a nonrev listing today for two segments. I first checked each segment individually and then tried to list for both legs at once. Showing each individually first class was showing available, when I tried to list all together as a connection no first class cabin was showing available and there was no option to select first class when listing. I tried to start over with an individual segment but it then did the same thing. Rather than go back to the "flight availability and listings" section I had to click "cancel" under the listing and then start over. Once I did that I discovered that selecting a single flight, and then clicking "Add another flight" I was able to put both segments in the listing while still correctly showing first class availability and listing for it.

For those who had this problem, I'm interested if it only happened on itineraries with a connection. I don't list with connections very often and expect it wouldn't be as readily apparent to those who likewise do not.

badflaps

I thought there was a section in your non-rev bio that indicated choice of class.

Bait

Ive had this happen trying to book company business to go to training. If I booked two segments under one itinerary, it showed no seats available in coach so wouldn’t allow me to create a company business reservation. When I went back and selected the exact same two flights in separate itineraries, there were 20+ seats available on each flight. Go figure...

captkdobbs

Interesting. Did it keep both segments under the same PNR? (IOW when you check in for the first segment, will you be automatically checked in for your connection?)

Kjazz130

When I started this thread I was only booking my commute home, one leg from ATL. But I was able to go back a few hours later and book it in First Class. I wonder if the “IT team” is making upgrades/changes to Travelnet and it is effecting listings.

Baradium

I added it to the same PNR. To do this, go through like you are going to list for a single flight. When it takes you to the screen that shows the flight where you can select class requested there is a button to add more flights. You can make your own itinerary that way without relying on the system to find the flights. This is useful if you are going hub to hub and beyond and need to take an earlier flight to for the first leg due to loads but the system doesn't want to show such a long connection. You will automatically be checked in for the second flight only if the connection time is in a certain limit (I forget what that limit is but it applies to all itineraries).

gloopy

Its hardly a straw man when you look at the history of non rev benefits and the JS across all airlines as well as us in particular. Its not a straw man when other work groups bring it up and CEO's at all airlines constantly struggle to placate them. I mentioned one of our former CEO's saying he'd "take a strike" to keep us from getting expanded JS benefits. Think about that for a second. Something that could potentially destroy the company was not only on the table but actually advocated for by the highest ranking person at the company, not that long ago, and what do you think the reason for that was? To placate the jealousy and class envy of other work groups who didn't think it was "fair".

You may not be "suggesting any change" but its a real and constant issue and always will be.