Stop Waiting for Permission to Get Permission

permission slipMany business leaders are still concerned about interacting with customers or prospects in Twitter (and other social utilities) because they are unsure whether the social utilities will survive long enough to justify the investment required, and they don’t want to build a bunch of interaction data that could evaporate when Twitter (or other social utilities) go away (potentially). That concern is a mistake, and here’s why.

Whether Twitter survives or not, it is a rich source of permission-based customer data that you should be gathering and incorporating into your CRM system and customer records today. If Twitter dies, and something else evolves, it won’t matter as long as you have your own permission-based data.

If you fail to store the interaction data in your own CRM system, then, yes, that would be a big mistake. But if you get all of the interaction data into your CRM system, then you will build a valuable asset that you can leverage beyond Twitter or any other social utility — whether they survive or not.

If your social media team is cutting and pasting between social media tools, then you’re leaving all that data for someone else to own, and your ability to flex as this highly dynamic environment changes will be severely handicapped.

The trick, of course, is finding a way to automate integration between the social utilities and your CRM system. For tips on making that happen, please see my earlier posts here and here where I list technologies and vendors that can help you.

One Response to Stop Waiting for Permission to Get Permission

  1. lisavalentine April 19, 2010 at 12:40 am #

    Yes, and another growing problem: more companies/workplaces are simply blocking employee access to social media apps across the board. There's a helpful whitepaper on the subject, it's called “To Block or Not. Is that the question?”

    It has lots of insightful and useful information about identifying and controlling Enterprise 2.0 apps (Facebook, Twitter, Skype, SharePoint, etc.)

    Blocking shouldn't have to be an “all or nothing” proposition, and it certainly shouldn't be done out of fear or misunderstanding of the risks.