November 8, 2004
When things go right
For the most part, customer service stories are the most engaging when they're about something going wrong. However, in the interest of giving credit where credit is due, here's a story about something going right.
Last week I sent an e-mail to Macworld's webmaster with feedback about their reviews RSS feed - it was sending out headlines, but no summary text.
I wasn't really expecting a reply so it was a little bit of a surprise when, the next day, I got a note from their Editorial Director, Jason Snell, saying that it would be put on their development list right away. Three days later, a new batch of reviews went out with summaries in place, making the RSS feed just that much more useful.
Pretty boring, huh?
But even though it's not as dramatic as when things go wrong, you can still find lessons in good customer service. I asked some questions about how their process worked, and a few things stood out for me:
- Quick sharing of information
My e-mail was circulated to several staff members who had a stake in the quality of the RSS feed. Their internal discussion and reply to me took place within one business day. - Having a process
Even though deliberately loose, their decision-making process is still a process - if deemed necessary, changes are either made immediately (if small enough or important enough) or added to a development list for future site updates. - Breaking the process
Evidently, their technical staff decided to go ahead with the fix immediately, even though they were given leave to put it off to a later date as one of many development requests on their list.
None of this is earth-shattering, which is exactly my point: good service is really easy when you're doing the little things right.
Posted by kenking at November 8, 2004 6:08 PM
