Originally Posted by
Connected1
Ticketing automation takes care of the SSRs.
A prerequisite, of course, is that ticketing must occur before the SSRs can be generated. I suspect that in this case the culprit may be the inexperience of a ticketing agent in an airport location with 1 flight/day and very little upline/downline connecting activity. Ticketing is not simple, particularly if the tickets and both international and interline. .
Say what you want, but if there's only one carrier out there that understands inter-system messaging, my bet goes to the inventor of the first GDS, the holder of the 001 airline code, that must send some sort of inter-system message for just about any interline itinerary it tickets.
I am actually not really techical at this but from what the agents tell me in Oneworld, it is actually a MANUAL task to enter any changes/new ticket nos are sent across to the airlines that are not using the same system.
Basically to cut it short my experience was that AA incorrectly issued a new e-ticket on my CX segments and did NOT "tell" them my new ticket nos. When CX tries to retrieve the booking in their system they can't see any tix nos.
From a PAX point of view IMO this is all BS! because we shouldn't worry ourselves with tix nos, pnrs etc.. We paid for a tix and all we have to do should only be showing the airline our receipts/actual tix coupons and not trying to do their work for them and note down all the every single minute detail.