Customers are tricky creatures. Treat them well and you're likely to reap benefits of a long-term relationship. Treat them poorly and you're likely to lose them. We all know this, but sometimes we have lapses of judgment that result in treating a customer poorly.
I was put in an awkward position last week. I am a customer of Podbean, the web hosting service that hosts hundreds or thousands of podcasts. Our Selling to Consumers Podcast is hosted on Podbean. I think Podbean made us "bend over" and I hope you and your company never does anything likewise to your customers. Let me explain...
Last week, I started receiving emails and messages through our main website that our podcast site was down or not working properly. I investigated and found that I was unable to access our sales podcast site. I tried ten minutes later and got the same results.
I went to the Podbean bad podcast hosting site. They had a message posted at the top of their home page that one of their servers was being serviced or upgraded.
Podbean bendover #1: If Podbean was going to upgrade or service their servers, and this activity would cause customers' sites to be down, they should have notified customers in advance. If the server issue was something that was an emergency, they should have sent an email to all accounts affected by the emergency to notify them their sites were down, and inform them what was being done to handle it.
When I tried to access our site a few hours later, it was still down. I went to Podbean's home page again and noticed the server maintenance message was gone. So I decided it was time to contact Podbean.
Podbean bendover #2: No phone number on their site. I had to fill out an online contact form.
I inquired about the problem with our site. I hadn't heard anything a few hours later (the site was still down), so I went into my email archives and found an email I had received from Podbean when we first set up our account. I sent them an email asking (again) what was wrong with our site and when it would be up.
24 hours later, I still hadn't received a response, so went to the Podbean site again to fill out the contact form a second time. Eventually, I heard back from Podbean via email: "We are sorry about this issue. One server is down. It is expected to be fixed in 24 hours."
Podbean bend over #3: Our site was down 3 days.
To Podbean's credit, they did send an email after the site was back up to let me know they had installed new servers ("to better serve" us they said). They also told me my site might not work properly and the podcast episodes might not play on the site and what I had to do to fix it. (That's Podbean bend over #4)
Podbean bend over #5: It would have been great for Podbean to have offered to credit our account for a month or a week or three days of service, but no such offer was included. Our company paid them to host a website for the entire month, not just 28 days of the month. It's not a large amount, but proactively offering a credit would have let us know Podbean is a class act.
In the site hosting business, having customers' sites up and running is everything. It's the reason they're in business. I'll never know how many potential visitors in cyberspace had trouble visiting our podcast site during the outage, but I do know that Podbean made me, the customer, feel unimportant. I had to bend over backwards to get information, and in the process, felt like Podbean had bent me over.
Lessons we can all learn from this incident:
1. When there's a problem, be proactive. Don't wait for your customer to contact you.
2. Communicate profusely. Communicate more than you think you need to. Problems increase the need for communication.
3. Make it easy for your customers to contact you. Old fashioned phone numbers are still the contact contact medium of choice for customers with problems.
4. Compensate your customer when compensation is the right thing to do.
If you like this post (or don't) please click on "comments" below and share your comment. Skip Anderson is the Founder and President of Selling to Consumers Sales Training. He works with companies and individuals who sell to consumers in B2C, retail, in-home selling, in the financial, real estate, and insurance markets, and other consumer-selling industries.
Contact Skip | Join Mailing List
Follow on Twitter | Connect on Facebook | Connect on LinkedIn
Hi Skip. I just read this article about PodBean and then noticed that you still use their service. Does that mean that you are happy with their service? Would you recommend it for daily episodes of audio podcasting?
Cheers. Martin
Posted by: Martin Koss | 02 March 2010 at 01:26 PM
Thanks for reading my rant Martin. My only complaint with Podbean was how they handled this situation; I was frustrated at the time and would have switched hosts but it hasn't been a priority for me.
Skip
Posted by: Skip | 02 March 2010 at 09:04 PM
Podbean is a terrible, terrible company. I started with them because I didn't know any better, and 2.5 years and 60+ episodes later I am absolutely trapped there. English is their second language at best, when you contact them for an issue you have about a 1 in 3 chance of receiving a response and a 9 in 10 chance of it not directly addressing what you're contacting them about. Also their stats system is broken. Around the end of 2012, I checked statistics for "all episodes" and it showed that I suddenly had 800,000 episode downloads way back in the second month I started my podcast. Randomly a large block number of downloads is added to a month's worth of downloads, for example suddenly it shows last month I had 80,000 downloads. The previous month I had 7,000 and so far this month I have about 5,000. Obviously that is just plain wrong. But trying to speak with these people is useless. But since they hold your RSS hostage and don't let you modify it, if you do decide to leave this terrible company, you are forced to start all over again in iTues with a new RSS feed, losing all your previous subscribers and previous history and positioning with iTunes. To anyone thinking of starting a podcast with podbean or transferring there: DON'T.
Posted by: R.J. | 02 February 2013 at 08:04 PM