Skip to main content

Do you know your customers?

CRM is probably one of the most risky business strategies evolved in the modern times. True, many customers would want to buy things from you, if they feel comfortable with your brand, but also true that most of the value the customer gets to you is when he purchases the product and not exactly the customer relation. Will you care about a customer if he really has no chance of buying a product from you?

An 80 year old man walks into the clothes store looking for a good tie for his (probably) last high-school reunion. Helping it out will lose your brownie points for any up-selling opportunity, but might as well score well in the humanitarian department. What would you prefer?

The most important malfunction of a CRM system is removal of the human touch from the whole system. We all detest system, we are born into one and have no choice but to choose and all humans avoid the system since then. You have a billion dollars and you set up a great call center, with a SLA of less than 5 hours, quite impressive, but what happens to your customer has another issue with your service? True your customer service agent will get all the case history along with it, but will he also get the sentiment out of the system?

CRM was one of the early strategies of free world, the local shop keeper knew my name, my school name, the class in which I studied as well as which pencil I use in school (he used to give it to me), now knowing all this was really cute, but if the pizza place knows that I was recently divorced because I know only order plain non-veg pizza without extra cheese in a different address, it is totally and exceptionally creepy.

So if you are implementing a CRM, do you know your customers?

Popular posts from this blog

The curious case of the custom redirection on Salesforce Console

Every developer worth their salt knows that the easiest way of redirection from a page to another is by using everyone's favorite function

public PageReference redirect() { PageReference pageRef = page.peskyProblemRedirection; pageRef.setRedirect(true); return pageRef; }
And the method is called by adding it to the Action attribute of the CommandButton or link, which works like charm and the user is redirected to the page after completion of the action.
So why am I going back to the basics? Because this way of redirection causes a pesky little problem in using the Service Cloud or Sales Cloud console.

Let's illustrate the problem, let's say you have a visualforce page as follows:

<apex:page sidebar="false" showHeader="false" controller="myExampleController"> <apex:form > <apex:pageBlock > <apex:pageBlockButtons > <apex:commandButton action="{!Redirect}&qu…

Some PDF tricks on Visualforce: Landscape, A4, page number and more

The beauty of Visualforce is simplicity. Remember the shock you received when you were told the entire page renders as PDF if you just add renderAs=PDF to the Page tag.

For those who thought I spoke alien language right now, here is the trick, to render a page as PDF, we add a simple attribute to the <apex: page> tag

<apex: page renderAs='pdf'> This will render the entire page as PDF.

Now, say we need to add some extra features to the PDF. Like a page number in the footer or we need to render the page in landscape mode. Faced with this problem, I put on my Indiana Jones hat and went hunting for it in the vast hay-sack of the internet (read: googled extensively). Imagine my happiness when i found a big big page with many big big examples to solve the problem. The document I am referring to is from W3C, paged Box media.

Long story short, I now possess the ultimate secret of rendering the page in any format I want. So here are few tricks I learned from the page. To p…

Cache me if you can: What you should know before daring to set URL parameter on visualforce

If someone gave me a pence for every time there was an SOQL query in an APEX Class without using Limit or a condition during a code review, I could afford a Lamborgini this month. Sigh. If only. We make it a habit of going digging for data, at the very moment we need it. The crux of this problem happens when you have chain classes which are independent of each other. Each class needs the reference from a single record and we have to query for that record every single time.

While we don't see it, every SOQL query has a cost to it, and it does not go in my Lamborghini fund, however, it should. In a recent project, we had to construct an Account 360 page that could fetch information from different integration points. The page was also called using a live telephony integration, which could pass the phone number for the account. This required an ability to keep in context the Account that was on call.

Passing the Account id in URL parameter was a valid option, however, any manipulatio…