Disappointed by Alaska Airlines IT, satisfied by their customer service

I wrote a few weeks back about the maze of rules relating to the elimination of change fees by most US carriers. My basic conclusion was that eliminating fees is better than keeping them, but that if you’re trying to claim a credit for a fall in price you should anticipate having to put some work in.

That turned out to be prophetic in my own case, rebooking a 3-week trip out West in July. But while I didn’t run into any problems with Alaska’s change fees, I am now 3 weeks into an IT saga.

My reservation was complicated, but uneventful

For my summer trip, I booked a fairly straightforward multi-city itinerary, with stops in California, Oregon, and Montana. I was able to book the itinerary entirely online, and I didn’t violate any of Alaska’s rudimentary routing rules. However, I did pay for it in a modestly complicated way:

  • I made the reservation logged into another person’s account, using their companion fare;

  • I paid for part of the fare using their Wallet funds;

  • and I paid for the rest using their Alaska Airlines credit card.

Obviously there are a lot of moving pieces here, but the reservation itself was made online with no hiccups.

Changing the reservation was straightforward

In my original post, I wrote that Alaska “offers two methods of changing an existing itinerary.” It turns out that’s not right. You can also “Deposit a ticket” through the “Wallet” tab in your account, which offers three additional options:

In hindsight, I wish I’d chosen one of those options! Instead, I called in, had my ticket re-priced, and was told I’d receive a certificate by e-mail I could deposit to my Wallet.

But, the certificate never came.

A “known issue,” but nobody knows what it is

When I called back last week to follow up, the rep made me walk through the entire story from scratch, researched the history of the ticket, put me on hold while she called accounting, and then confirmed that I was due the $720 certificate, which I would receive by e-mail.

Yet again, the certificate never came.

When I called in again today, I decided to be a bit more straightforward: they had screwed up, I was sick of being given the runaround, and I needed to know what they were doing to fix it. This elicited a slightly more effective reaction, and the phone rep contacted the most knowledgable person in accounting she knew (“I’ve been working here for 29 years and Carrie’s been here even longer than me”).

This time, I got what seems like a sensible answer: “there’s a known IT issue, accounting is making great strides to fix it, and it will hopefully be resolved soon.” She even threw in that “Carrie” had recognized my name and knew I was one of the “handful” of people affected by the issue.

She also offered me a $100 discount code, bringing the total gross value of the rebooking to $783. I don’t believe I’ll be able to use the discount code since (unlike Wallet funds) I don’t think discount codes can be combined with companion tickets. Still, someone will surely use it.

Conclusion

I don’t know exactly which piece of my booking broke Alaska’s IT, so there’s nothing I can recommend to avoid running into the same problem until it’s finally resolved. I suspect it has something to do with how their change fee waiver populated across various systems, since I was using a companion fare, Wallet funds, and a non-traveler’s credit card.

But despite the incomplete and inadequate information they’ve given me since the beginning, I came away impressed with their overall customer service. Even as an entry-level MVP elite, I never had to wait more than a few minutes on hold. Every rep I spoke to confirmed that I was owed the fare difference, so there was no need to recite terms and conditions to them at any point. And when the problem continued far too long I was even offered a fare discount as a goodwill gesture.

It’s not like people have much of a choice in carrier these days, but I’m frankly thrilled Alaska's doing their best to keep up their customer service standards.