Cubic Compass Software

Many businesses are in a dilemma when it comes to upgrading or migrating their web site. On one hand, several existing web pages may have a high Google Page Rank (or other search engine ranking) as a result of several in-bound links from several other sites.

On the other hand, this high ranking is useless because the web page is outdated (either the technology or the content) and does not contribute towards lead conversion or initiating a web dialogue.

There are basically 2 techniques that I use to help businesses migrate all or part of their web site to a new i-Dialogue customer portal. Note:

301 Redirects. This involves mapping existing web content to a new location and crafting some 301 status messages that instruct search engine crawlers and web browsers to visit the new site or page. These 301 redirectors may be maintained indefinitely, but usually 3-6 months is recommended.

Extension Mapping. Web pages developed in the 90's likely have file extensions that end in ".htm" or ".html". Newer web sites may use extensions like ".jsp", ".cf", ".asp", or ".aspx". While the ".aspx" is the default used for i-Dialogue portals, it is possible to map page extensions to any number of characters.

So instead of redirecting your existing productName.html page to productName.aspx, we simply map all requests for the ".html" extension to the newer ".aspx" extension and the page requester doesn't notice the difference.

Note that Google and other search engines use a wide variety of algorithms to rank pages, and a complete overhaul of a web site, regardless if the URLs are kept in tact, often leads to temporary reduction in page rank; but with (hopefully) a long term gain since the entire portal has been optimized for the search engine.

Posted: Tuesday, January 31, 2006 11:57:58 PM (GMT Standard Time, UTC+00:00)  #   
Comments [1]  | 

Seeing news articles with headlines like "Salesforce.com suffers another outage" can be disconcerting, but I think somewhat expected given the complexity of the latest Winter '06 release. The high expectation of many Salesforce customers demonstrates 2 things:

1) CRM has definitely crossed the chasm and is well into the late-majority consumers (aka Conservatives) who place increasingly more value on service levels and price.

2) Computing has truly become a "utility" much like power and gas. An outage of 4 hours or 4 minutes does not go unnoticed.

As with other utilities, it will take time to build and harden the infrastructure. It has taken over 100 years in the U.S. to develop a power infrastructure reliable enough to support computing and the Internet today. I don't expect it will take another 100 years for utility computing to be as stable, but we truly are in the infancy of this model.

The Salesforce.com outages also get me thinking about the value of having a separate customer portal that is integrated with CRM but separately hosted. When these outages occur, our i-Dialogue customer portals for Salesforce continue to provide customer self-service features and broadcasting email.

As a backup option, we've been able to keep our customer data synchronized with the portal (requires Enterprise Edition) and manage leads and contacts directly through the portal interface when its convenient. But we prefer to keep Salesforce.com as the master record.

Posted: Tuesday, January 31, 2006 6:40:00 PM (GMT Standard Time, UTC+00:00)  #   
Comments [0]  | 

When discussing customer self-service portals with other people, inevitably the subject of online case management comes up. "The knowledge base and discussion forums are fine", they say, "but we really need a web form to help customers initiate a support request".

Often, these requirements are coupled with complex work flows, auto-responders with ticket numbers, dynamic routing, and escalation rules. It's as if some people are eager to have their work day interrupted with support requests from the web portal!

But customers often do not perceive the ability to enter a support request via the web as a benefit. In fact, of all the multiple self-service resources available via the customer portal, a support request form has the longest time to resolution (see graph below).

In the customers mind, having to fill out a support request form is anticlimactic and an inconvenience. They entered the web portal session with hopes of immediate gratification and then leave feeling that it may take days or hours until someone gets back to them.

While many support cases can be attributed to "human error", customers still expect suppliers to anticipate common problems and strategically invest in publishing FAQs, KB articles, and other online resources.

Now, I wouldn't recommend removing support request forms altogether, but I would suggest that Marketing and Support Executives view this as simply a tactical option that reinforces "reactive support" over a more strategic approach that promotes preventative support with an investment in self-service materials and content.

The astute observer may notice that "publishing documents" appear in the "preventative but tactical" quadrant in the above matrix. The reason for this is that web pages are documents and customers consider it an inconvenience when new browser windows and applications suddenly pop-up and take several seconds to load (my Adobe Acrobat plug-in still takes about 10 seconds to load! Forcing me to install Foxit Reader instead).

When the web became fairly ubiquitous, organizations already had several Word and PDF documents on hand and the tactical approach to self-service was to simply make these documents available online. Today this is largely unacceptable, except in rare cases when an alternative to HTML must be provided for printing.

Posted: Monday, January 23, 2006 7:54:13 AM (GMT Standard Time, UTC+00:00)  #   
Comments [0]  | 

RSS feeds (Really Simple Syndication) are basically just headlines that customers subscribe to and monitor. If they see something tantalizing, they'll click on it and read the details on your customer portal.

But RSS adoption is currently struggling for adoption. Consider what a customer must go through today to subscribe to a RSS feed:

1. Customer notices RSS button on web page (or "XML" or "ATOM") and clicks on RSS button. A blob of incomprehensible XML appears in their web browser.
2. Customer copies the URL Address of the RSS feed onto their clipboard.
3. Customer changes application context and opens their RSS aggregator/new reader.
4. Customer clicks on "New feed".
5. Customer copies RSS URL Address.
6. Customer enters other relevant notes and meta data.
7. Customer clicks Save.

Despite these 7 steps, the benefits to using RSS far outweigh the pains for people who monitor the headlines of several web sites a day. But for the average person, these multiple clicks and actions are a usability barrier.

Recently, browser plug-ins have become available the detect when a RSS feed is available and will allow a customer to add a RSS feed in one-click; maybe prompting the customer to categorize the feed much like a "Favorites" bookmark gets cataloged today.

This feature is anticipated to be built into several next generation application, such as Internet Explorer browser, Outlook, and Firefox within the next 12 months; so within 4-6 years Marketers should expect a critical mass of customers to have the ability to easily aggregate a web site with a single click.

RSS readers will likely become a free commodity tool since the real money will be made in advertising and click-throughs. Expect Google and others to help businesses drive even more traffic to ad-bearing web sites with free plug-ins and utilities.

Writing an effective RSS headline is no different than writing an effective press release. The first measured "conversion" is simply a click on a headline, which must catch the customers eye with a tantalizing message.

As mentioned in a previous log entry, Marketers also have the ability to execute some i-Dialogue decision tree rules and sending targeted content headlines instead of general broadcasts (assuming a self-identified RSS subscription occurred with a parameterized URL).

Is it better to have multiple RSS channels or a single RSS channel? The benefits to multiple channels is the user is left to decide which topics are most relevant to them, but you may miss out on advancing the relationship with a customer if they only get a single view of the company.

I recommend that businesses only have one primary RSS feed that gets the bulk of your publishing focus. This will ensure high frequency of new content (which search engine spiders will love) and will condition the customer to "stay on top" of your latest news.

A single RSS feed is all that is needed for the first 4 stages of your customer life-cycle:
Awareness
Education
Evaluation
Acquisition

Once a customer matures into later life-cycle stages of Service and Growth, they will naturally explore the deeper reaches of your customer portal and subscribe to specific discussion forums and knowledge base categories.

So, assuming you're publishing only one RSS news feed, how are you to sustain the frequency of content needed to keep a prospect or customer engaged? The answer is a hybrid of good old PR copy writing and automation.

The RSS feed to your customer portal will be a combination of headlines that you publish interspersed with non-deterministic events, such as new knowledge base article headlines and discussion forum headlines.

Posted: Saturday, January 21, 2006 6:18:50 AM (GMT Standard Time, UTC+00:00)  #   
Comments [0]  | 

Marketing and Support executives have a tough challenge in the information age as the number of customer touchpoints and speed at which information flows continues to increase.

The holy grail of CRM is to integrate all channels in real-time and ensure your customer dialogues are always relevant.

Achieving integration of the whole requires businesses to first begin with integration of each individual channel.

 



In the Internet channel alone, there are several services that customers are increasingly demanding from their suppliers and vendors.

Many solutions have emerged to offer these services individually and businesses may often defer integrating any particular self-service solution until there is significant demand or ROI to justify the integration costs.

Over time, the accumulation of disparate Internet marketing solutions leads to a fragmented solution that de-personalizes the relationship with the customer and leaves the businesses incapable of effectively integrating the Internet channel with the broader CRM strategy.




A unified Internet Marketing solution integrates the commonly used Internet services into a single, cohesive solution that keeps all interactions relevant and provides a single integration point back into the larger CRM solution.





These integrated customer portals may be outsourced to a service provider or hosted in-house, depending on the architectural system constraints.

By taking these steps, it becomes for each customer interaction to be highly relevant and personalized, regardless of channel source.

The grand goal of achieving a 360 degree view of the customer may be challenging, but it can only be achieved by taking several smaller steps towards an integrated solution.
 | 
Posted: Friday, January 20, 2006 8:08:01 PM (GMT Standard Time, UTC+00:00)  #   
Comments [0]  | 

Some Canadian researchers have determined that it takes people 1/20th of a second to make an aesthetic judgement about a web site (news.com article here).

The researchers didn't identify the reasons for liking or disliking a web site, nor why they conditioned the subjects for such a test in the first place, but it does reinforce the fact that first impressions do matter on the web.

I would recommend the following to get past the first blink with customers:

  • 5 W's: Make sure to focus on the Who, What, Where, When, and Why on the home page.
    The W's can have multiple meanings and contexts.
    "Who" you are and "What" you do are important. But who your customers are and what you can do for them is even more important.
  • No animation or blinking. These are often perceived as advertisements and distract the eyes search for content.
  • Familiar "L" navigation. Do not get creative with navigation, such as employing hover-overs to reveal the navigation item.
  • High density information links on home page. The customer should feel like "this is the place" to start looking if there are several well categorized links. A high density home page also acts as a true "home" so that is customers ever get lost, they know they can also get back to where they started in just one click.
  • Reduced or no images. This is to improve download speed and allow for higher density of links.

 

Posted: Wednesday, January 18, 2006 2:26:16 AM (GMT Standard Time, UTC+00:00)  #   
Comments [0]  | 

Well, it's official. Salesforce.com's AppExchange was formally announced and released today. CEO Marc Benioff's comments on the "Business Web" are right on the money. In 10 years, people will wonder how we lived without on-demand, hosted business applications.

I hope to have our i-Dialogue AppExchange plug-in uploaded within the next 60 days. While i-Dialogue is very focused on the customer experience and web usability, the internal CRM experience is critical to advancing customers through the customer lifecyle.

That's why I continue to emphasize that a whole relationship marketing solution requires tight integration between customer facing web portals and CRM software.

Because Salesforce makes it convenient for other vendors to integrate with their platform, you'll find that Salesforce and AppExchange will get the bulk of my attention in the coming years as we pursue richer dialogues between businesses and customers.

Posted: Wednesday, January 18, 2006 1:40:33 AM (GMT Standard Time, UTC+00:00)  #   
Comments [0]  | 

Definition of acronyms and terms used on this blog:

B2B = Business to Business
B2C = Business to Consumer
CRM = Customer Relationship Management
iCRM = Internet CRM
RSS = Really Simple Syndication
SEO = Search Engine Optimization
PPC = Pay Per Click
SERP = Search Engine Results Page
CPM = Cost Per Thousand (from Roman numeral "M")
WSS = Web Self-Service

 |  |  |  |  | 
Posted: Sunday, January 15, 2006 11:14:14 PM (GMT Standard Time, UTC+00:00)  #   
Comments [0]  | 

Search