Originally Posted by
dan1431
Channa, I think the difference, and it is tangible, is that blocking is a deliberate act to prevent something from occuring, while if you want to call ineptitude or poor infrastructure is more a problem that can be corrected.
Dan
Dan, agreed. But as I mentioned before, this has been going on pre-Star, and for years, so I'm not sure about the motivation in correcting it. I'm hoping they do, and do so quickly, but I've been a victim of similar types of issues for years.
For example, with AS flights in the past, CO was aware of the issue for two years, and the issue continued until the final day with AS. In some instances, every AS flight was not being displayed. At other times, some AS flights weren't showing. This is exactly what the posters are experiencing right now, but with other carriers.
At some point the issue goes from honest mistake to deliberate obstruction. The agents don't see the stuff, and the agents don't offer manual sells (you have to know to tell them this). Is CO taking reasonable steps to avoid the issue -- e.g., sending out daily or weekly updates to agents advising them to try manual sells since they're having display issues? Posting a customer notice that some flights or carriers are currently not bookable due to xyz issue, and to try back in a few days?
So I guess the question is where the line between honest mistake, and not taking reasonable steps to correct an issue. Normally, I'd be more likely to agree with the "they're new to *A" contingent and cut them some slack (heck, I work in IT, I know how this interconnection stuff can be). But since I struggled and had to educate agents for years in how to book DL or AS flights (and not all were receptive, mind you, my redial button is very well worn

) without improvement, I'm tending to lump these issues in with my prior experience.