All Hands Support

Aug 20 2010
Recently, the team at NewRelic (an app monitoring tool we use at Wistia) announced that they crossed the 5,000th customer mark, an impressive feat for a two-year-old company. But instead of espousing about how great they are and high-fiving over their growing pile of cash (which would be justified), Lew Cirne (@sweetlew), the founder and CEO, decided to spend his time describing how a 32 person company handles 24/7 support with no support staff. In Lew’s words:

Each and every support request is handled by a development engineer who has full access to our entire source base, and the full authority to do whatever is necessary to make things right. This includes agent tweaks, production patches and—on rare occasions when we mess up—free upgrades.

The NewRelic approach resonates with me. It’s an approach that guarantees that the right people are hearing about the right problems and that customers know that you take their problems seriously.

In the comments on Lew’s post, there was feedback from Ben Congleton, the CEO at Olark, (the live chat widget we use and love) who said:

Every member of our team does a rotation on support. I think the key issue is to make sure that 1) everyone in the company knows why they have a job [hint: it's the customers], and 2) An engineer with full commit access rarely needs to escalate anything (so quicker service).

Ben is highlighting another part of the same story: that employee motivation should be aligned with happy customers, and that fast and excellent customer service is important.” would work better.

Noticing a trend?

Well, it turns out that we do support in a very similar way to both NewRelic and Olark. In our case, we call it All Hands Support, but it’s basically our spin on the same story. It means that everyone in the company takes shifts on managing the chat widget, answering the phone, and calling to check in on customers.

The benefits of a shared support system are enormous. Not only can you more easily automate technical issues, but you also end up improving your company’s messaging, reducing confusion around features, modifying pricing elements that don’t jive properly, and cleaning out issues from every other customer-facing element of business.

Fixing problems is critical to growing a business, but more important is knowing what to fix next and how to prioritize a laundry list of other evovling issues. There is no better way to do this than to make sure that everyone has a pulse on customer needs.

There is a new breed of company that doesn’t rely on the traditional models for scaling businesses. These companies can move faster on the right problems, keep customers happier, and build better products. If given the choice, I’ll always pick this new breed over the establishment. It’s great to be surrounded by such great company.

Tags: ,

  • http://susops.blogspot.com/ Maintenance Man

    I wish everyone on our team would do support. Then they might learn a lot of the deails.

    Developers on our team complain that not everyone in development has access to all the code. So there are actually places where this is done right? Wow.

  • Brendan

    I imagine it’s more challenging with larger development teams, but there are still examples of big companies getting this right (e.g. Kayak).

  • http://www.playlookit.com Jeff

    Great article. It totally makes sense for Wistia since you deal with other engineers and whatnot.

    But for a B2C company, engineers could possibly do more harm long term to your brand. We’re wired differently. We’re not exactly “cuddlers” for the lost small-business owner who can’t figure out how to login.

    Instead, why not have your support team give an overview of the top 3/5/whatever issues customers were having this week at your weekly status meeting? Everyone stays in the loop and your customers feel all warm and fuzzy on the inside.

  • Chris

    Jeff,

    I wouldn’t generalize and say all engineers aren’t exactly ‘cuddlers’, I know a few I’d consider cuddly. An engineer getting frustrated with a confused user can have an instantaneous response and make a 3 minute fix that makes the login button bigger or adds more instruction to the login page. A dedicated support person wouldn’t be able to make that change and more likely would solve that problem by following a script instead of engineering a solution.

    I think it just depends on what’s important for growing your business. In our case, we’re excited to talk with all customers so that we can process their feedback and improve our product and funnel. If you have a B2C ecommerce application it may be far more viable to have a dedicated support staff helping people through the check out process.

    Ultimately, I think we’re all on the same page: keep the customer feeling warm and fuzzy how ever you can.