cepheid
Jul 2, 05, 11:59 am
Well, this is a great example of when horrible customer service meets irate and irrational consumers.
This past Thursday I was on flight 54 from SFO-IAD. The plane was coming from IAD and was late in arriving due to weather delays at IAD (it left over an hour late, and arrived nearly 2 hours late). Of course, after 1-2 hours, people started getting very worried about their connections, and got in line at the gate to talk to the GA about rescheduling. (I was getting out at IAD so I was merely an observer for all of this.) Unfortunately, there was no GA at the gate until about 30 minutes prior to our originally-estimated delayed departure. Until only about 30 minutes before we left, there was only one CS agent to handle 50-80 pax with connection issues... this was where the trouble began. It turns out that the CS agent wasn't even an Indy employee, but a contractor of some sort. When 2 more CS agents arrived, they too were contractors. All 3 appeared completely untrained on Indy's booking/rescheduling system... they spent the first 45 minutes trying to work on a single pax's rescheduling, to absolutely no avail. Despite 90 minutes' worth of attempts and being constantly on the phone with their management, they could not figure out how to reschedule any of the customers. They only managed to speak with literally 3 pax during this entire time... everyone else was just waiting in line for 90 minutes.
Eventually, about 5 minutes before we finally boarded, the head contracted CSA gets on the horn and announces that they could not rebook anyone and that rebookings would be handled automatically during the flight - pax would get their connection info upon arrival at IAD. He said that due to the holiday weekend, most of the flights were totally full. They would try to guarantee "same day arrival" for pax traveling to certain destinations, and others would probably have to wait until Saturday. Since the delay was due to weather, Indy would not cover hotel costs (reasonable and customary, but didn't go over too well with the pax). They said pax who chose not to fly would get a full refund, but didn't offer any other alternatives to everyone else. Pax who didn't board who had checked luggage would have to wait until the *next day* to pick up their bags. Eventually, most people boarded, but the flight was probably only at ~80% capacity (instead of the original full flight).
So... clearly pax will get irate and irrational, and there's not much anyone can do about it. I don't expect Indy to offer concessions due to weather delays, and that's understandable. My main gripe with this (and it didn't even affect me!) is just the poor, poor customer service rendered at the gate. The contracted GAs were totally untrained and couldn't assist any customers. They did make an effort to help, but concentrated so hard on trying to learn the system that they only managed to speak to literally 3 pax during the whole ordeal - everyone else was completely ignored until the general announcement. For the pax they did speak to (after the general announcement, when everyone gave up on lines and mobbed the desk), they didn't seem to worry too much about courtesy and calmness... I witnessed rather heated exchanges. The GAs weren't tied to the airline and therefore didn't seem to really care about customer retention.
While this whole delay was nothing but a delay for me (I didn't have a connection to miss), I'm just amazed at the lack of customer communication and the low level of apparent service. During the whole delay, none of the GAs actually made any general announcements about WHY there was a delay... the monitors said "due to weather" but nobody knew that the plane hadn't arrived, etc. When the delay extended an hour beyond the original estimate, there was again no general announcement letting pax know that they would be waiting some more. When the plane finally did arrive, there was again no announcement that they would be preparing the plane and boarding soon, etc. Essentially, customers received absolutely no communication from the gate until 5 minutes prior to boarding, and people had to decide within 5 minutes whether to go to IAD and *hope* to get another flight within the next 2 days, or not bother getting on at all.
Now, I don't fault the GAs personally for not being good at their jobs, because clearly they did not receive the proper training in how to handle this situation - they were not Indy employees and Indy never bothered to train them. They could certainly have been a bit more on the ball with regards to communication and customer courtesy, although that often goes down the tubes when GAs are mobbed and flustered. But something should clearly be done here. Indy shouldn't be using contracted employees, and if they ARE doing so, they should specifically make sure that those contractors are trained in the same way as the Indy GAs, so that they can handle these kinds of situations (and in a personable and courteous manner). Training them in customer retention and courtesy wouldn't hurt, either.
The only good service came from the *flight crew*, who were trying to help customers while waiting for the plane to arrive. Two of the flight attendants were behind the counter, on the phone with Indy reservations to try and help pax get rebooked, and answering pax questions as much as they could. The pilots were looking up flight information to find out why the plane was late, when it would arrive, etc. They were all quite helpful and really did an excellent job as much as they could - it was obviously not something they were trained for or expected/required to do, but they helped to the best of their ability and I definitely appreciated them for it (if you're reading this, flight crew of 54: thanks!). The only information we got about the flight delays came from the crew, since the GAs were busy trying to learn how to use the computer system. Unfortunately, the crew did bear some of the brunt of the irate and irrational pax, who didn't realize (or care) that the crew was doing them a favor and it wasn't even their job... quite unfortunate.
The flight itself was wonderful... the crew did a great job. But Indy really needs to look at its customer service at SFO, and to make some major changes. I simply had to live with a delay, which I didn't mind since I wasn't in a particular hurry... if I'm this disappointed with the service purely on principle, imagine how disappointed the other pax were who missed their connections and received absolutely no communication from the gate. I would highly recommend that Indy put forth some effort to enact changes at SFO.
Thanks again to the flight crew. :)
This past Thursday I was on flight 54 from SFO-IAD. The plane was coming from IAD and was late in arriving due to weather delays at IAD (it left over an hour late, and arrived nearly 2 hours late). Of course, after 1-2 hours, people started getting very worried about their connections, and got in line at the gate to talk to the GA about rescheduling. (I was getting out at IAD so I was merely an observer for all of this.) Unfortunately, there was no GA at the gate until about 30 minutes prior to our originally-estimated delayed departure. Until only about 30 minutes before we left, there was only one CS agent to handle 50-80 pax with connection issues... this was where the trouble began. It turns out that the CS agent wasn't even an Indy employee, but a contractor of some sort. When 2 more CS agents arrived, they too were contractors. All 3 appeared completely untrained on Indy's booking/rescheduling system... they spent the first 45 minutes trying to work on a single pax's rescheduling, to absolutely no avail. Despite 90 minutes' worth of attempts and being constantly on the phone with their management, they could not figure out how to reschedule any of the customers. They only managed to speak with literally 3 pax during this entire time... everyone else was just waiting in line for 90 minutes.
Eventually, about 5 minutes before we finally boarded, the head contracted CSA gets on the horn and announces that they could not rebook anyone and that rebookings would be handled automatically during the flight - pax would get their connection info upon arrival at IAD. He said that due to the holiday weekend, most of the flights were totally full. They would try to guarantee "same day arrival" for pax traveling to certain destinations, and others would probably have to wait until Saturday. Since the delay was due to weather, Indy would not cover hotel costs (reasonable and customary, but didn't go over too well with the pax). They said pax who chose not to fly would get a full refund, but didn't offer any other alternatives to everyone else. Pax who didn't board who had checked luggage would have to wait until the *next day* to pick up their bags. Eventually, most people boarded, but the flight was probably only at ~80% capacity (instead of the original full flight).
So... clearly pax will get irate and irrational, and there's not much anyone can do about it. I don't expect Indy to offer concessions due to weather delays, and that's understandable. My main gripe with this (and it didn't even affect me!) is just the poor, poor customer service rendered at the gate. The contracted GAs were totally untrained and couldn't assist any customers. They did make an effort to help, but concentrated so hard on trying to learn the system that they only managed to speak to literally 3 pax during the whole ordeal - everyone else was completely ignored until the general announcement. For the pax they did speak to (after the general announcement, when everyone gave up on lines and mobbed the desk), they didn't seem to worry too much about courtesy and calmness... I witnessed rather heated exchanges. The GAs weren't tied to the airline and therefore didn't seem to really care about customer retention.
While this whole delay was nothing but a delay for me (I didn't have a connection to miss), I'm just amazed at the lack of customer communication and the low level of apparent service. During the whole delay, none of the GAs actually made any general announcements about WHY there was a delay... the monitors said "due to weather" but nobody knew that the plane hadn't arrived, etc. When the delay extended an hour beyond the original estimate, there was again no general announcement letting pax know that they would be waiting some more. When the plane finally did arrive, there was again no announcement that they would be preparing the plane and boarding soon, etc. Essentially, customers received absolutely no communication from the gate until 5 minutes prior to boarding, and people had to decide within 5 minutes whether to go to IAD and *hope* to get another flight within the next 2 days, or not bother getting on at all.
Now, I don't fault the GAs personally for not being good at their jobs, because clearly they did not receive the proper training in how to handle this situation - they were not Indy employees and Indy never bothered to train them. They could certainly have been a bit more on the ball with regards to communication and customer courtesy, although that often goes down the tubes when GAs are mobbed and flustered. But something should clearly be done here. Indy shouldn't be using contracted employees, and if they ARE doing so, they should specifically make sure that those contractors are trained in the same way as the Indy GAs, so that they can handle these kinds of situations (and in a personable and courteous manner). Training them in customer retention and courtesy wouldn't hurt, either.
The only good service came from the *flight crew*, who were trying to help customers while waiting for the plane to arrive. Two of the flight attendants were behind the counter, on the phone with Indy reservations to try and help pax get rebooked, and answering pax questions as much as they could. The pilots were looking up flight information to find out why the plane was late, when it would arrive, etc. They were all quite helpful and really did an excellent job as much as they could - it was obviously not something they were trained for or expected/required to do, but they helped to the best of their ability and I definitely appreciated them for it (if you're reading this, flight crew of 54: thanks!). The only information we got about the flight delays came from the crew, since the GAs were busy trying to learn how to use the computer system. Unfortunately, the crew did bear some of the brunt of the irate and irrational pax, who didn't realize (or care) that the crew was doing them a favor and it wasn't even their job... quite unfortunate.
The flight itself was wonderful... the crew did a great job. But Indy really needs to look at its customer service at SFO, and to make some major changes. I simply had to live with a delay, which I didn't mind since I wasn't in a particular hurry... if I'm this disappointed with the service purely on principle, imagine how disappointed the other pax were who missed their connections and received absolutely no communication from the gate. I would highly recommend that Indy put forth some effort to enact changes at SFO.
Thanks again to the flight crew. :)