US Air — Email Response Parsing
Posted on April 26th, 2005 in Usability | 12 Comments »
I had trouble signing up for US Air’s frequent flyer program (Dividend Miles). I literally tried about eight times, but failed. So, a couple of days ago I spent about 10 minutes looking for a way to send them an email. I found a way, sent my message and shuffled along.
Today I received a response. The customer service representative informed me that I could provide her with my contact information and she would sign me up. So, I hit the Reply button, typed the message, and sent the email.
It bounced. At first I was frustrated, figuring that, yet again, a big company is using a generic email address. I know this makes sense for many reasons, but the practice drives me crazy as a user. In any event, although it was true the email address was generic, that was not the root cause.
After scanning the email, I found the following two lines:
[===> If you need to reply to us, please type below this line ===>]
[===> If you need to reply to us, please type above this line ===>]
No, I’m not kidding. I’ve never seen anything quite like this, except in code comments. Then it hit me. Bing! That is exactly what US Air is doing. They are exposing their technology to me, the end user.
I’ll bet they have code to parse responses from schlumps like me. They probably programmatically evaluate the subject line, which includes an incident number, and then they parse out the text between the two lines. Clever. Maybe.
How about the usability factor? Does cost savings trump usability here?
