Showing posts with label security. Show all posts
Showing posts with label security. Show all posts

Tuesday, January 27, 2009

Cloud CRM – a definition

CloudCRM Cloud Computing is replacing SOA as the buzzword in 2009. I spent some thoughts on how this will influence CRM 2.0 in technical and business terms.

SalesForce.com is currently heavily pushing their “Service Cloud” solution, which is a little misleading in its naming I believe. The Service Cloud is not exposing any services into the cloud but utilizing some public APIs from platforms like Facebook or Google.

This is adding new channels to the contact center (and such enhancing the customer experience) and feeding solutions from customers back into the knowledge base – good thing - but what really has all this to do with Cloud Computing? My opinion… nothing!
Maybe this is just a way to get something out of the buzzword and sell new contact channels as a brand new product?!

Their example of Orange and Plantronics is nice to view, but what happens if I am not a SFDC customer? The SalesForce to SalesForce interface is (like all the others) a Point-to-Point integration and not even based on any standards like Web-Services, I believe (correct me if I’m wrong).

Having said this, what is my vision of ‘real’ Cloud CRM then?
For me, Cloud Computing means that I (as a user) do not know where the processing power or storage resides physically. In contrast Software as a Service (SaaS) is a piece of software that is running for a dedicated user at a known location (I count the url “www.salesforce.com” as a known location…).
Now if we use standards to communicate with the services in the cloud, this would make them pretty much completely exchangeable. Of course this is not a good thing for the vendors of these services and hence Amazon, Microsoft and Force.com introduced their own proprietary structures and interfaces.

In an ideal world – and we are far away from that, yet – all vendors would agree on one open standard and the consumers (i.e. users) would have the choice to dynamically exchange and combine services from the cloud to create their individual CRM platform that perfectly scales and performs as required. But how would ISVs feel if their customers had a zero vendor-lock-in? If they could exchange the CRM service with a couple of mouse clicks and the new service would still integrate seamlessly to their ERP or OSS?     Maybe then even the producers of CRM software will have to think about a CRM 2.0 strategy… (I like that idea)

Ok, stop dreaming now! We are in 2009, facing global recession and I am delighted to see that SFDC is integrating to social platforms like Facebook (more to come I suppose) and help companies that are looking to implement a CRM 2.0 strategy by giving them the right tools to execute such a vision. The IdeaExchange functionality is a good (though proprietary) starting point to gather feedback from customers and get the involved – a first step to collaboration and co-creation.

There is a long way to go until Cloud CRM becomes reality. Standards have to evolve, security has to be ensured and SLAs have to be controllable. SaaS is (only) a first step into this direction.

Thursday, April 17, 2008

Day 4 - Data Security

As I am a member of social networks and a customer to various companies as well, I tried to think of any reservations that I would have about this. And the first thing that came to my mind is obviously data security?
How can I as a user or customer control who is using my data for what? We all know how many spam we get every day, but this is sent more or less blindly to a large number of recipients.
When companies have more data about me, will this lead to even more unwanted email or will this filter the advertising and reduce the amount of communications while increasing the quality?

I think this could be a tightrope walk for companies that think about implementing CRM 2.0. A strict governance needs to be put into place that ensures that the customer data is not abused in any way. Any affairs in this area could seriously harm a company or its affected brand.

Wednesday, April 16, 2008

Day 3 - Googles OpenSocial

A very interesting project is Googles OpenSocial API. This API is intended to allow the integration of existing social networks (like LinkedIn or Xing) into new applications or mashups without having to learn or re-engineer the various APIs of the social network application.
Quote from the OpenSocial website: "The ultimate goal is for any social website to be able to implement the API and host 3rd party social applications. There are many websites implementing OpenSocial, including Engage.com, Friendster, hi5, Hyves, imeem, LinkedIn, MySpace, Ning, Oracle, orkut, Plaxo, Salesforce.com, Six Apart, Tianji, Viadeo, and XING."

This could be easily used as a basis to retrieve data from various sources and not only get enhanced information about the single customer, but also about their relationship amongst each other and how groups are created or influenced.
A big topic will be data security and the aceptance level within the users of social networks. Will customers be willing to share personal information if they know that they will be used by companies they don't know?