Skip to main content

Relationships as a Service


In today's world using the world Social has become the latest trend. Every company around the world has started putting social term in their advertisement. Some Indian companies have also started putting Twitter and Facebook logo in their roadside hoardings, what is to be done with it is not yet sure, do they expect people to park their vehicle on the roadside climb up 20 feet and click on them, is not yet confirm?

The Governments have woken up to the power of social media with Indian Government acting to censor the internet in name of anti-religious sentiments and American Government attempting to pass SOPA bill 2012 in name of piracy, they have clearly shown that the time is up for the government. People are self censoring themselves and they are relying on the government lesser and lesser. Obviously Government must be there but in this post social work, Governments will loose control over the information which they so dearly protect. But lets not get into politics of things, lets keep it simple.

Six to seven years ago if anyone would want to take his girlfriend out to a decent night dinner, he would have to rely on some traditional suggestions given by his friends to choose one. Today, Yelp is helping Americans find the restaurant for the evening and Zomato is doing the same job in India, and pretty cool job they are doing.

Two days ago, I bumped into a friend in a local watering hole, the place was a big one and in earlier days it would not be possible for us to meet, but that day we both had checked into Foursquare. We all are turning social, social is becoming part of who we are.

But this is not the first time humans have shared anything with each other, we did it all along. We already discussed the latest topic of discussion over a cup of coffee at the office local cooler. We used to discuss what happened during the day with our family over dinner. Those things changed as the relationships turned weak and electronic gadgets became the companions. Those were the days of texting, mobile phone and television.

The same social objects that were with us before social media now returned back. This time they were shared not with a bunch of people, but with everyone, everyone who subscribed to it. What had changed? This is a subscription based world, this time the social objects reached to anyone who was listening. Anyone who is listening.

We do not invest into a lot for social media, we invest in relationship. Facebook is leading the way in redefining relationships like never before. With the constant birthday reminders and life events reminders, now with Facebook Timeline and Friendship features. Still at this time, Facebook remains nascent with the complexity of relationships. No its not as easy as forming separate circles as designed by Google.

Understanding relationships is not as easy for a computer system as understood by our brain, yet Social Networks are reforging the relationships like never before. Tapping into them poses a great opportunity to corporation, no not up-selling opportunities to friends but understanding in detail about the customer.

In the end, the trick is not to trick the customer into buying things, it is to manufacture things, the customer actually will benefit from.

Can any corporation offer relationship as a service?

Happy Holidays.

Picture courtesy: Wikipedia.
Depiction: Pied Paper of Hamilton.

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…