Posted tagged ‘Facebook’

Announcing the 2013 TSIA Social Media Survey: Now Open!!!

December 3, 2013

Earlier this year I took over TSIA’s social media research. In previous years, we did a social support survey that collected information on how technology companies were using various social approaches to interact with customers. What became obvious to me from last year’s survey data, as well as my annual spending and adoption survey, was that while most technology companies (over 80%) now have a customer community in place, less than half of B2B tech firms were doing anything support related via social media (Facebook, Twitter, LinkedIn, etc.). My goal for 2013 was to split TSIA’s social research into 2 streams: one for online communities, where we have a lot of momentum and can begin establishing pacesetter practices; and another for social media support, which is earlier in the adoption curve with many companies still trying to understand the use cases.

As 2013 nears its end, I’m happy to say I’ve accomplished this goal. At our recent Technology Services World Conference, I launched a new Community Benchmark program, allowing TSIA members to take a brief 50 question survey and receive an in-depth look at how their online community program compares to their peers. If you’d like more information on the Community Benchmark or want to know how to participate, here’s a link to an OnDemand webcast with all the details.

The 2nd part of the goal was to launch a new annual survey specific to social media. Today that goal is also complete, and I declare the TSIA 2013 Social Media in Support Survey NOW OPEN! Here’s a link to participate:

This short, 20 question survey is open to all customer support personnel in all industries, in all geographies. The survey is also open to all in regards to social media use:  whether you are currently supporting customers via social media, are considering social media support for the future, or have no current plans to introduce social media support, please take the survey.

And here’s the carrot for participating: a free copy of the resulting research report, “The State of Social Media Support: 2014,” to be published in Q1. Normally non-members do not have access to these “state of” reports, but I will personally email a copy of the report when published to everyone who participates in the survey. (Make sure you don’t have TSIA in your ‘spam’ filter!)

So whether you think Twitter is the new customer service channel, or the whole social media topic grates on your nerves, please take 5 minutes and complete my survey. We are still in the early days on this topic and I know I still have a lot to learn. I really appreciate your time and participation!

Happy Holidays, and thanks as always for reading!

Doing a poor job on social media support is worse than not supporting social at all

March 19, 2013

I’ll probably catch a lot of flack for this column title, but that’s my opinion and I’m sticking with it. I just finished reading an article in today’s San Jose Mercury News about a study done by cloud vendor LiveOps about social media support, claiming that 70% of customer complaints on Twitter and Facebook are ignored; the average response time for Facebook questions is 2 days (opposed to 2 hours, which is the customer expectation), and that more than a third of companies have deleted a customer question from their Facebook page they didn’t want to answer.

Unlike phone calls and emails, social media support is very public. I always say that opening up a new customer interaction channel is like blowing a hole in the side of your corporate office. You now have a big gaping hole for customers and information to flow in and out, and if you don’t police that hole, including audit trails for traffic in and out, and service level agreements for who can use the hole and how quickly you must respond, you will get in big trouble.

Thousands of companies put very little thought into the decision to begin supporting customers via Twitter or Facebook, and I suspect many now regret it. Once that hole in the side of the company is open, it is all but impossible to close. And it is incredibly visible when you can’t keep up with the volume and begin ignoring–or deleting–customer questions.

Based on lots of TSIA data, it is clear that online communities/discussion forums are hugely successful for technical support–or at least have the potential for being hugely successful. But on the B2B technical support side, I remain unconvinced about social media channels. The typical use case for Twitter support is, “I called Comcast and was told there was an hour wait for an agent, so I Tweeted instead.” I don’t think any TSIA members have an hour wait for a phone agent. Ever. In the B2B, i.e., enterprise support world, in which you pay a very large fee for access to technical support, you don’t have long wait times. In fact, dedicated account reps are common for premium support. And the bottom line is, if a system administrator Tweets or Facebooks that their corporate ERP or supply chain system is down, that is not reporting a tech support issue, that is airing your company’s dirty laundry and a fireable offense.

There is also something in the article I laughed at. According to the survey, “customers are likely to spend about 30 percent more money” if the company has a social media presence. Well, I review RFPs all the time, and I’ve never seen a B2B purchase decision based on which vendor has the most Twitter traffic. It galls me that news outlets refuse to differentiate between B2B and B2C when they write things like this, and some wrong-headed B2B manager is going to bring this article into his boss and say, “Let’s start social media support and we’ll raise sales 30%.”

So, before you decide to begin supporting customers with technical issues via Twitter or Facebook, please remember:

  • Only a very small slice of traffic will have anything to do with a technical support issue. Most traffic will be about your latest commercial, your stock price, your CEO’s private life, the color of your company logo, etc. Technical support engineers are not equipped to handle these questions, and it is a waste of their time. But, if you are going to support the general public via a social channel, you need a strategy for these non-technical issues. If you don’t have an outbound marketing or PR group staffed to handle these posts, which will probably be 90% of traffic, don’t open the channel to begin with.
  • If you do insist on supporting customers via social channels, please leverage one of the many knowledge platforms now offering plugins to social media. For example, you can create a tab on your Facebook page that allows searching your self-service knowledgebase and shows lists of FAQs.
  • Record every interaction in CRM..or someplace. You need an accurate history of which customer asked which question, regardless of channel, and you need to understand which questions are asked and answered by all channels to make sure knowledgebases are current and accurate.
  • Establish SLAs. If you are going to support a new channel, whether it is social or not, you have to establish response times for the channel. And you must have staff dedicated to meet those SLAs. I’m not saying you necessarily publish the SLAs (“All Facebook posts will be answered within 2 hours”), but internally, you must have some SLA guidelines and the ability to measure how well you are doing in meeting those SLAs. Customers have expectations, and if you can’t meet them, you shouldn’t launch the channel.

And as always, thanks for reading!

Your Opinions Can Get You Fired: Think First Before Posting, Texting, Tweeting and Emailing

June 19, 2012

When I published my first book, Lessons Unlearned, last month, I didn’t intend to start a conversation about free speech in the workplace. But I’ve received a number of comments about 2 sections of my book related to how sharing your thoughts can threaten your job security, and there are some items in the news this week that made me think this a worthy topic for a blog, even if it is outside customer service.

Here are the two topics in my book that people keep commenting on:

  • I talk about using a “magic slate” for stress relief when dealing with difficult customers because you can scribble a word that describes the customer, show it to your cube mates to elicit empathy and release some stress, then lift the plastic sheet to erase what you have written, eliminating any audit trail. This hit a nerve with multiple readers, who say it is politically incorrect to criticize customers at their company, regardless how irrational their behavior is. I learned early in my career that making rude, however accurate, comments about customers in case notes will definitely get you in trouble.
  • In the chapter on startups, I talk about the importance of establishing company culture, and how one company I worked for destroyed its culture by shutting down the email system one weekend, reading everyone’s email archives, and firing anyone who had made a negative comment about management in an internal email. While clearly this company had some unhappy employees, this didn’t fix the problem, it only inflamed it, making all employees paranoid and distrustful of management.

I think most of us have an internal editor that keeps us from going too far in emails, blog posts, Facebook posts, Tweets, text messages, etc. We’ve all probably typed something in anger and regretted sending it later, and I try really hard to not hit ‘send’ on ‘flame’ emails until I’ve had time to calm down and re-read my text. As a manager, I’ve certainly encountered problems when employees were rude or indiscreet in written communications, and typically I am pretty understanding and counsel them to go ahead and write down the frustration, which helps purge you of the stress, but definitely don’t send or post until later.

There are two things in the news this week that make me think this is going to be a bigger problem for future managers than I ever experienced in the past. The first is a story in today’s San Jose Mercury News that a sales executive is leaving a major Silicon Valley high tech firm for texting opinions about the company that not only weren’t outrageous, they reflect the opinion of many analysts and technology reporters. I suppose I can understand why the executive needed to leave, but this wasn’t a company email or statement to the press, this was a personal text message he never intended anyone else to see. Definitely worrisome, and I hope the company learned something about the importance of internal marketing.

The other story in the news this week is that Facebook is exploring options to allow kids under 13 to join. Now, my friends with kids tell me they are all on Facebook already, registered using 5-10 year lies on birth year to get around current restrictions. Be that as it may, if I, in my 40s, have yet to learn to self-edit 100% of the time, how can we expect kids to know what is safe to post and what isn’t, knowing that every single word and picture will follow them around on the internet for the rest of their lives? There is even pending legislation being discussed because some employers and schools have demanded that applicants hand over their Facebook passwords so they can view their profiles before hiring or admitting them. Big brother is watching.

As a child of the 70s, I grew up being told to express myself and revel in free speech. And I do. But there were also some common sense limitations to this, such as not discussing topics that are incendiary (politics and religion), and not to put anything in writing you don’t want your mother to read. Those common sense limitations don’t seem to have made it to the younger generations.

I’m sometimes shocked at the political and religious comments made by people I’ve known for years. In polite conversation, we usually avoid topics that are controversial, but that internal edit doesn’t seem to apply to Facebook. I’ve “unfriended” several people who I genuinely like, and interact with in real life, because I can’t stand to read their off-the-deep-end political views. I have one friend who spends his days at work posting comments about how much he hates his job and how stupid his boss is. When I asked him if he was concerned about being fired for those posts, his reply was, “I don’t share my posts with my boss.” Well, all it takes is someone to print out pages and pages of those posts and mail to him, and next stop is unemployment. I’m sure the software sales exec who lost his job this week had no idea that the personal text message he sent would come back to haunt him.

Bottom line, be careful what you post, email, Tweet, whatever. Here are John’s rules to not letting social networking destroy your livelihood:

  • Think before you post. Writing your frustrations down is a great way to vent, but take an hour and think about it before hitting ‘send.’
  • Don’t social network after drinking. On Mondays I look at pictures and comments posted by friends over the weekend, and there is usually something really embarrassing from 2am on Sunday morning. Once posted, it is really hard to delete.
  • Steer clear on overly controversial subjects. If you wouldn’t express that opinion in the company lunchroom for all to hear, maybe Tweeting it isn’t the best career move. You can believe what you want on your own time, but realistically, people will judge you for outrageous views, especially narrow-minded views. If you really believe “the earth is flat” keep it to yourself.
  • Your ultimate distribution list is larger than you think. Don’t think for a second that your text won’t be forwarded or that ‘non friends’ will never see your Facebook posts. In 2012, that is extremely naive.

What do you think? What are your rules about what to post and what not to post? What are your pet peeves about “over sharing?” Have you changed an opinion about a friend or co-workers based on social posts? If you have kids, what advice do you give them? And as always, thanks for reading!


Get every new post delivered to your Inbox.

Join 93 other followers