As I mentioned here only a few short weeks prior to that my trusted iPhone 3gs went for a swim so I duly made my way to the AT&T store to leverage my upgrade discount and order my iPhone on “opening day”.
Of course, because I hadn’t called at midnight the night before or waited in line on the sidewalk I didn’t get in to order my phone until the afternoon. By that time I was told that orders being taken were expected to ship within two weeks, rather than the anticipated one week, but that I would be able to track my order status online.
The picture above is my actual order status. Notice anything? Somehow, in ten days, according to this, the is no difference in status from the moment when I was standing talking to the AT&T employee in the store to now. My order is processing.
I put this in the “failed customer self service” folder.
Order status checkers like this one are create tools to reduce call volume. The more customers who can see what is going on with their order the fewer will clog the phone lines with questions about shipping dates.
Unless of course you fail to update that status at all.
Not only does this produce more phone activity but it also sends a subtle message that either you’re hiding something or you don’t care all that much about the customer.
So why might a system like this show NO activity over ten days?
- We’re slammed and the system is overloaded
- We don’t know from the supplier when the items will be available
- We now know it will take four weeks so we’re avoiding telling you
- We didn’t create enough differentiate status levels in the system
In truth the reason doesn’t matter, the communication does. Even if “the system” posted a status that said “we’re backlogged and hope to clear the jam buy the following date” it would be more communication than “processing”. My order has been “processing” since I first said, “Hey, I’m here to order and iPhone 5.”!!
If you’re going to use a customer self service tool like a status checker you need to remember a couple key rules for success:
Rule 1: Keep the information up to date
Now to be fair the information on my status above may BE up to date. My order may not have moved at all. But you would think that it would have processed by now and just be awaiting inventory. But is does not appear to be up to date. By leaving it mostly blank the system has failed at its two primary purposes: reducing call volume and communicating status to the customer.
Rule 2: Communicate, even if it is bad news
It is far better to know that my order will be delayed than it is to keep guessing. By communicating even the bad news you communicate that you care about the customer. Trying to hide the bad news says you care more about your image than you do about your customer.
Rule 3: Think with a customer perspective
Too often these systems glitches become internal finger pointing or design arguments. If you failed to think like a customer during design think like one during the problem period. I wonder if anyone at AT&T is asking how customers feel about a dead order status?
Customer self service tools are great when they’re firing on all cylinders. When they’re not you need to react quickly, communicate effectively, and think like the customer.
What other types of “customer self service” tools have you run across and how effectively were they managed?
Bonus points if you know the movie that is referenced in the title of today’s post. 🙂