Just today, I had a client ring with a problem specific to the email newsletter I’ve setup for him. A few phone calls, an email and then I was back on the phone to him, detailing what was actually happening on the server end of his problem.
I think he appreciated it. I know I do when people actually get back to me. Find out what’s really going on. No BS.
37Signals had a problem this week also (much bigger than mine). Take a look at how they dealt with it. Some good lessons here.
First, they posted information about the problem to their Basecamp-specific blog. They didn’t hide the problem, hoping most people wouldn’t notice. They continued to post updates during the grueling night while they were trying to get things back to normal.
Second, they apologized. It’s amazing how few companies will actually say those words. And it’s equally amazing how far those few words go toward keeping your customers happy. 37Signals’ acknowledged their customers’ inconvenience rather than denying it.
Third, after the insanity was over, 37Signals’ lead developer, David Heinemeier Hansson, posted a post-mortem detailing what had gone wrong.
Jonathan D. Nolen – Lessons from the 37Signals’ Basecamp outage