June was a fantastic, fascinating month for customer happiness at Buffer as we made great strides toward meeting goals, expanded our awesome team, and pushed forward in a number of new, exciting areas.
June 2014 is the first month that I know of where we hit “inbox zero” at least once per day in both email and twitter. (We use Help Scout and Sparkcentral, respectively.) It feels great to be getting closer to the point where our customers don’t have to wait for us in order to get their work done. By better managing these two communication tools, we can also continue to devote time to Live Chat.
Our email volume is slightly lower than last month, which, naturally, has made this easier. We’ll continue to hire in the next few months so that we’re ready for autumn volume.
Email: 9,047 responses
Twitter: 6,193 responses
Olark: 625 chats
We have two shiny new faces on the Buffer happiness team this month. :) Please join me in welcoming Octavio and Nicole!
Learning to track resolution times
We have traditionally focused on response time when we measure our support statistics. We intentionally do not look at “replies per conversation” as a metric we want to reduce. If anything, we feel that this number should go up, because it means the exchange is more of a conversation and the customer doesn’t have to write long, include-every-possible-detail emails each time. Additionally, by constantly improving our design and interface, we can hopefully reduce the communication that causes our customers to say “how do I accomplish this simple task” and focus more on the tricky or strategy-based questions. This would cause emails per conversation to increase as well.
So, when we started looking at resolution times for email, it was a big “first” for us! Our Happiness Hacker Colin calculated this by determining how long the conversation went on, from first email to our final reply.
This isn’t flawless logic because conversations can drift among topics. One issue could be “resolved” while the conversation continues, but those outliers are manageable.
We arrived at 77% of conversations being resolved within 6 hours. Having no prior months to compare this to, it seems like a reasonable baseline!
Taking it one step further with self-selecting urgency
We also added a field to our online help form that invites people to select how urgent the matter is. Here’s where it gets fun!
It looks like this:
Each level of urgency is “tagged” in Help Scout, and the highest urgency tickets send an alert to our HipChat room. Whenever possible, we try to address the “emergency” tickets as fast as we can.
Now, we are tracking resolution time for each category of urgency. The most casual often take the fewest emails back and forth and are the most easily solved (3.5 emails on average). The high-urgency emails take more conversation (5 emails on average). Despite this, our resolution time for the two highest urgency categories is faster than the average for all emails. This feels like a success, and we’ll work to continue to improve this.
If you’re curious, we welcome you to follow along at our (completely public) Happiness Dashboard. (Update Sept 21, 2017: We are no longer using our Happiness Dashboard anymore and are now using reports in tools like Help Scout and Buffer Reply.)
We’ve had some fun opportunities in June to get to know the fabulous people using Buffer.
A Hangout in Paris
Our Happiness Hero Dave and Biz Dev and Product Specialist Rodolphe traveled to Paris to have coffee and croissants with some Buffer users. This is the third time we’ve been able to meet our community in person, and it continues to add a level of intimacy and friendship that can be hard to achieve over digital mediums. Let us know if we can visit your city! :)
We also launched a weekly Tweet chat. So far, we’ve dived into productivity, self-improvement, and using visuals in social media.
We’d love for you to join us Wednesdays at noon EST at #bufferchat on Twitter!
Over to you now!
Resolution time, in-person hangouts, and Tweet Chats are all new to us, so we’d love to hear any questions or suggestions you have! :) Leave comments here or get in touch anytime at @buffer on Twitter. :)