Scaling support: why we removed our phone number from our website

Jan 5 2012

We are a company obsessed with helping our customers get the most out of their video marketing initiatives. Providing amazing customer support has been part of that mission from day 1. For many of our customers, this is their first foray into video for their business, and our help and feedback makes them feel comfortable making that leap.

Great support to us means being as approachable as possible. We put our company and even personal contact info on our website, email blasts, and in videos series. As we were ramping up, it was a great way to get to know customers and make sure they were getting the most out of Wistia.

With our growing customer base, it's became harder to balance phone support for our great customers with meeting new and potential customers. A small team like ours simply couldn't keep up with the volume of phone calls received (we only have 3 phone lines!). Without a change, the legendary support we had become known for would cease to be a reality. The system was simply not scalable.

We spent a good deal of time pondering the way forward. This was an incredibly important topic for us - customer love and support is part of who we are. So we spoke with really smart people from companies that had gone through similar situations. We looked at our support resources on a whole, and how many of our customers were utilizing support as it was currently offered. To really drill into the phone situation, we looked at data on call volume broken out between customers, potential customers on trials, and pre-trial folks. We also tracked the type of conversations we were having on the phone, to see what percentage of them could have been handled more quickly and easily (both for us and the customer) by making other support resources (i.e. documentation, website, in-app instructables) clearer and more accessible.

Our requirements for this project were twofold: to reduce the strain on the support system, and provide superior support for the growing customer base. Many of the options we contemplated included negative consequences, such as introducing friction for the customer to get support, or removing the support lines altogether. Because the goal was to maintain or improve the overall level of support, these wouldn't work.

In the end, we made a very small, yet monumental change - we removed our phone number from the support page on the website.

illustrating the phone number move

Today, when a potential customer comes in contact with Wistia, they interact with us through the website and documentation. We installed Olark (an awesome chat widget) in both locations, so that visitors can ask questions when we're online, or leave us messages in our support inbox when we aren't. Once a visitor signs up for a trial with us, they receive emails with both our phone and email contact information.

We were incredibly nervous about how our long-term customers and new trialers would interpret this change. We didn't want them to feel like we wanted to lose contact with them. To track performance, we watched our key metrics, along with email volume and documentation traffic. The results have been extremely positive. We've seen a boost in speed of conversion, as potential customers don't have to wait as long to get their questions answered. Phone volume has gone down over 25%, and while support email has gone up, that system is far more scalable. With increased bandwidth, our support folks have been able to greatly increase the information available in the documentation. We've also been able to have more in-depth conversations with customers and new trialers, so we can learn what features within Wistia remain unclear. This means our in-app instructables can get better - giving users clearer, more-helpful instructions when they need it. Because conversations on Olark and email are saved in archives, we can track what the key questions are for each step in the customer timeline, and make sure the answers for those are present at appropriate times.

We've also gotten extremely positive feedback from customers and trialers. Because we've made our static resources more available, support is faster, more informative, and accessible when the customer needs it -- not just when we are in the office. We of course still have great phone support for trialers and customers -- you'll see the number in your accounts!

Jeff (13 Posts)

Director of Customer Happiness


Tags: , ,

  • http://www.ChiroHosting.com Mike Melton

    I’m a new Wistia customer, and I couldn’t be happier. You guys are awesome. When I had some questions when signing up, I got a response back in MINUTES – on the Friday before Christmas. I contacted another company for video hosting, and it took them two weeks to respond.

    Wistia rules.

  • Jeff

    Hey Mike! Thanks for the kind words. We love having you as a customer! –jeff

  • Scott Lewis

    I am not a customer currently but wanted to say that putting the chat widget on the online documentation pages instead of just on the support page is brilliant. Now you’ve got me thinking why not put a help chat widget or link even inside PDF documentation whether online, on CD/DVD install media, etc. for most any company and most any product? Seems like an obvious and useful step in being customer centric.

  • http://www.seomoz.org Aaron Wheeler

    As you know, we’re big fans over here at SEOmoz! We’re also trying to scale our support efficiently and painlessly. Great to hear about this phone strategy. Can I ask what you used for phone tracking and reporting? You mentioned, “To really drill into the phone situation, we looked at data on call volume broken out between customers, potential customers on trials, and pre-trial folks. We also tracked the type of conversations we were having on the phone, to see what percentage of them could have been handled more quickly and easily (both for us and the customer) by making other support resources (i.e. documentation, website, in-app instructables) clearer and more accessible.” How did you guys do this? Any more information you could provide would be sweet. Thanks, and keep up the great work!

  • Jeff

    Hey Aaron – thanks for your note, we’re big fans of the ‘Moz too :) Maybe I’ll put together a follow-up post with info on the tools/processes we used to accomplish this (and feel confident about our findings). Thanks! –jeff

  • http://helpjuice.com Emil Hajric

    Great post, guys!

    I’ve been thinking a lot about how companies scale support and how to deliver awesome support (http://www.helpjuice.com/blog/5-secret-laws-behind-awesome-customer-support).

    And one of the conclusions I’ve found is that you don’t really want to scale customer support with people. It costs a lot, and from your customers perspective, it can get slightly annoying being transfered from one department to another (like how big corporations do).

    Also, one point; A lot of the customers of Helpjuice.com I’ve been talking to have been having this exact problem…but with email. Here’s how we solve it;
    They start getting so many emails, from which a GOOD chunk of those emails are questions which are pretty damn repetitive. What I advised them is that they actually put a knowledge base as their main contact form, and if the search doesn’t pull up and results, just display the regular ol’ contact form. That way, it’s a win-win, customers get an instant answer and you guys get less support emails.

    P.S.: Good job on the latest mixergy interview, Jeff!

  • Jeff

    Hey Emil,

    Thanks for your comment, very helpful. And yes, Chris killed it in that Mixergy interview!

    jeff

  • Fertile Minds

    Hi there,

    Until the past few months, we were extremely happy with both the tools and support, but it’s not going in the right direction. We’ve been paying customers for a year or two, but the incredible support has completely gone away. Much increased delays on email support and no phone support… Even worse, the video players and embed codes have changed dramatically, so much so that we have no way to match older embeds (no social codes, completely different look, half-baked new theming, etc.).

    We’re still Wistia fans, but we’re not at all happy with the direction. As you move your platform forward, please consider those of us using it over time, and try not to launch things that break the way we use the service.

    Signed,
    A grumpy client

  • http://jeffvincent.posterous.com/ Jeff Vincent

    Hi there,

    My apologies for your poor experience. As I’m fairly well-versed with your situation, I can only promise we will do better. I appreciate your long-term support, and hope we can redeem ourselves soon.

    best,
    jeff

  • Fertile Minds

    Hi Jeff,

    Thanks for the reply. We were able to just this morning resolve our biggest complaint (the look) by using API embeds with !important CSS overrides. While it feels like a step back to use the Social Bar separately, it’s not a big deal at all. The most important thing is that we can now match the hundreds of playlists we already have in use.

    I think we were so blown away by the service when we started, and I know from personal experience how hard that is to scale. We hope you can find a good balance.

    Thank you.

  • http://jeffvincent.posterous.com/ Jeff Vincent

    We will never give up on the idea of blowing our customers away with support. As a paying customer, you have a support phone (it’s on the bottom footer of every account page) and we do our best to answer it – or respond to your voicemail.

    The scaling is certainly a challenge as we grow, but we don’t consider “crappy” support a given because of it. We will continue getting better until we get it right.

    – jeff

  • Linda Lockett

    I need to contact someone asap for permission to use Wistia in a feature film

  • http://www.devonwebdesigners.com/ Elizabeth Jamieson

    Well I love Wistia. I joined recently and they have been exceedingly helpful, timely and nice. It’s tough creating software for users . . . so they do a great job in a technically difficult space.