That would be the basic blocking and tackling of traditional CRM that is still part and parcel of any actual strategy – and any implementation. The operational”stuff.”
Even with all the incredible roaring, growling, yelling, about social and even with the party-level polite conversation going on showing thought balloons (or tag clouds) with “social media”, “Social CRM”, “cloud computing”, “Tweet (oh wait, that’s a Scarlet Tanager that flew in the window)”, “conversation”, “mobile CRM”, “Facebook CRM”, “customer engagement” and any other sexy cool term with meaning, one thing we can’t forget. That’s would be that CRM – be it our contemporary Social form a.k.a. SCRM or even the traditional CRM which is still an instrumental part of many businesses – has some basic operational requirements and planning that has to go into the development of an overall program for customers that a business can use successfully to accomplish its particular aims regardless of the changed circumstances of the modern customer controlled ecosystem. What we are dealing with when it comes to SCRM is, simply, what kind of particular program does an individual business require to reach out to their customers and provide them with what they need to get what the business values in return?
The best way to think about SCRM/CRM for simplicity’s sake is that it its a customer centered program. The program’s focus/direction needs to change from time to time because of the business exigencies of a particular era. For example, five years ago I would have said it was a program for customer management, now I say customer engagement. Which is more than a po-tay-to, po-tah-to distinction. It has serious implications for how businesses need to conduct themselves. But the basic requirements for the program’s construction remain the same. It needs these following components if CRM in any form is going to be executed successfully.
These are the basic building blocks of what comprise a CRM strategy and program. They were needed in traditional CRM and they continue to be needed in Social CRM plans. While the emphasis and approach to the components vary from era to era, and while there are some additions to the list, all of them still need to be thought through, decided on, budgeted, organized into something and then followed through and then tweaked, tweaked and maybe even rebuilt, to make the changes in how the business thinks and runs, not just thinks. If all of that is done, the customers’ requirements for continuing to do business with your company can be met. When it comes to some of the things (note I said “some”) that distinguish Social CRM from its older sibling, such as social media (as tools) and social networks (as channels/locations) they have to be factored in, but not at the expense of the other pieces. In a perfect world, all of them need to be incorporated into the planning.
In that perfect world, technology is a part of the program, but not the program.
A Clarification on Technology
Before I continue on, I need to clarify something. In my response to Bob Thompson’s superb discussion on the Altimeter Group’s Social CRM Pioneers Google Group, “Does Social CRM Need Social Media”, I said emphatically no. That doesn’t mean I’m opposing technology, nor do I think in a business, a Social CRM program can scale without it. But also remember at this point, when I say technology is needed to scale, then I’m also saying that social media is not the only technology involved in a Social CRM implementation. It just happens to be the one currently oozing sex.
However, the traditional operational and transactional technologies such as a customer record – preferably with a single view, or a business rules engine, a workflow creation tool, a set of automated processes, communications channels etc. will continue to be as or more important than ever before. You still need to record transactions, you still will be wise to know what your customer is thinking and to use analytics help you ascertain that. You will still need to be able to track what your employees are doing with their customers, not just what the customers are doing. No way should you simply assume that you can substitute a customer’s social interactions for recording a customer’s transactions. You shouldn’t underestimate the importance of having and knowing a transaction history. Knowing an interaction history simply gives a business the means for richer customer insight when used in conjunction with customer transactional behaviors. In fact, interestingly some of the more recent efforts by vendors like Oracle and SAP base their social knowledge of the customer on existing transaction records – not social interactions. The start to some pretty sophisticated customer insights and some really sexy customer-usable tools, starts with the historic transaction record.
In fact if you look at what kind of IT framework you’re going to need for Social CRM, you’ll note some comfortably familiar faces mostly grouped on the left and underneath along with the scarily unfamiliar.
What’s sitting all the way on the left is what we think of as traditional CRM. They are on this tools map a necessary part of a larger framework of foundational architectures, web services, applications, services, and ways to deliver these services.
The technology here is what’s needed to run this thing at the enterprise level. This “thing” is CRM – be it traditional or social. Again, basic blocking and tackling stuff.
Let’s Get Real
While what I’m saying may seem rudimentary to you – meaning you know this – and I apologize to you if it is. Unfortunately, the discussion on how to handle the basics has gotten somewhat lost in the social conversation.
Businesses are primarily concerned with one thing – running their business and succeeding. If customer engagement is the key strategic parameter for success, they clearly would be smart to focus that way. To do that, they need to change how they run their business and figure out the impact that this change in strategy is going to have on all the things in the slide above. Then they need to run a program. Remember, their purpose is to be successful and meet their goals. Their purpose isn’t to engage their customers. Their strategy is to engage their customers. The businesses have operational requirements that will exist even when the customer controls the conversation as they do now. That doesn’t mean the business gives up running – it means it changes how it runs. But it still runs and the traditional CRM capabilities support that running of the business as well now as it did a year or three ago. But there is now more that needs to be done. That’s where a Social CRM program comes in.
The debates all recently have centered around what CRM used to center on. Is Social CRM a strategy or a technology? In some part the locus of the debate is due to my contributions to all this discussion among many others. For this somewhat of an incomplete discussion, I apologize for my role in propagating it. Above all, Social CRM is a program for customer engagement that encompasses a strategy, technology, system, processes, etc – just as CRM was. I’ll probably tweak my definition in a post shortly to reflect that. At this point, Social CRM is a just a bit more than a construct that has some truly important but nascent practices that are associated with it that differentiate it from CRM. These are critical differentiators as you can see if you compare historic use cases against the best first take on the use cases that were done by Ray Wang and Jeremiah Owyang at Altimeter Group last month. But they are not differentiators that don’t incorporate traditional CRM somewhere in the mix. Social CRM is never purely social.
All I’m saying here is that in the hot, steamy, hyper-charged sexy world of social everything that has revitalized the discussion around CRM – we can’t forget what is basic and fundamental for businesses. They have to run, they have objectives that are not the same as the customer’s when it comes to how they interact and they need to change with the times. The times require the them to consider Social CRM rather than just traditional CRM. Whether or not they decide to go with it won’t change the basics of what they need to do to run, but it will change how they run. Maybe add some components to the basics. But the basics remain.
And that is that.