If The Big Switch can be said to represent the centralization of computing resources, then Microsoft's Live Mesh may signal the path towards the big switch back to a decentralized model (albeit with some centrally hosted Microsoft infrastructure).

Some ideas for using Mesh with our CEM platform and Salesforce:

• Real-time notifications when Leads/Contacts enter your website
• Sync and offline access to CRM data and documents across several devices
• Rich development of email campaigns and web page content
• Social networking with employees, partners, and customers

• Product catalog management
• Shopping Cart
• Globalization / Multi-currency
• Localized Taxes
• Discounting
• Membership management
• Secure online payment
• PCI compliance
• Product / service fullfillment
• Financial accounting / Back office integration
• Recurring payments

Luke Wroblewski has a thoughtful article on why Sign Up Forms Must Die.

His examples of "gradual engagement" are pragmatic, applied customer experiences that reflect concepts outlined by Rogers and Peppers and many others.

We all deal with Salesforce Web-to-Lead forms on a daily basis, but it's not often that we think of breaking a Lead form down into several smaller forms and seek to gradually learn more about prospects over time.

Granted, most of the examples in Luke's article are in a B2C context, but B2B sites with more than one case study or several pieces of collateral can apply the same concept.

I just caught wind of the new Google Visualization API, so I opened up a Google Spreadsheet (we have over 10 people using Google Apps in our company now) and all I can say is "wow!"

Just as a quick experiment, I generated a bar chart of response times for one of our hosted solutions and clicked on the newly available "publish" link to generate the image below.

If the spreadsheet is ever updated, I just re-publish the chart and all external channels referring to the image are automatically updated.

I'm extremely impressed with the mashup capabilities enabled by Google Visualization and Google Charts. If the Salesforce / Google integration observations are true, then I'll be in absolute mash-up heaven

Traditional web design and development are rooted in the concept of a Multi-Page Layout, or MPL. Contemporary web design and content management systems have transitioned towards a Single Page Layout, or SPL.

MPL web sites store their content in individual web pages. Adding more content requires adding additional pages. SPL web sites use a single web page template that derive their content from a database. Salesforce.com makes a great database for managing both content and Leads/site members.

Many organizations gradually wade into developing unique landing pages for Google AdWords or publishing products and services. At first, the MPL approach provides the path to least resistance since initial development and deployment costs are fairly low. The cost of change remains fairly linear at first as each new page is cloned from an existing page and modified to suit the campaigns needs. But over time the cost of change begins to increase. It takes longer to provision new pages and development becomes much slower.

A form of "technical debt" is accrued whereby a developer must eventually externalize common UI elements to server side include (SSI) files, such as headers, logos, navigation, and footers. Even with SSI best practices in place, a developer/programmer still remains in the critical path for each new campaign and the skills required for ongoing maintenance remain high.

SPL templates may take 3-5 times longer to initially implement, but successive pages may be easily provisioned by business users, such as Marketing and Support admins. The time to provision a new page remains linear over time as each new page is defined in a database and immediately available for use in PPC campaigns.

SPL page templates are actually very simple to develop. They may look slightly cryptic when opened in a common web page designer because they contain "merge tags" to be replaced by the database when the page is displayed. The URL typically contains some kind of unique ID to give the page context as to which content to display.

i-Dialogue 8 now supports a new scripting language called Dialogue Script that removes the need for a physical page template. The SPL template can be created directly in a web browser and the merge tags can define any Salesforce object or field.

The Professional Services group at Cubic Compass Software has extensive experience with SPL design and hosting. Contact me for more information. I'd be happy to help.

Which Super Bowl ads made an honest attempt at initiating a two-way dialogue? Here's my scorecard.

The Scorecard

Compelling Call To Action: Did the ad provide a memorable URL and call to action?
Continuity: When I go the URL, is the message in the context of the TV ad?
Fulfillment: Does the website answer my questions or deliver on any promises made?

The Winners

Based on the scores, Tide and Jack in the Box come out on top. As far as most functional campaign, SalesGenie.com is the most likely to get visitors to self-identify and enable an ongoing dialogue.

Interesting that in such a consumer driven B2C Internet world that a B2B site would have such strong positioning in the Super Bowl.

Dialogue Script (or DScript for short) provides a simple scripting language for developing interactive web pages, forms, and applications integrated with Salesforce.com. In this series of articles, I'll cover some basic scripting concepts to address the most common use cases.

Dialogue Script Articles:

1. Master Views and Lists
2. Details View
3. Web Form

What is a Master View?
"Recent News" is an example of a Master View. It is simply a list of items that are dynamically queried from Salesforce.

Here's an example Dialogue script that displays a top 5 list of the most recent press releases:

<dlog:repeater id="LatestNewsRepeater"
SOQL="SELECT TOP 5 * FROM Content__c WHERE Type__c='Press Release' ORDER BY CreatedDate DESC" runat="server">
<ItemTemplate>
<dlog:HyperLink ID="HeadlineLink" TextFieldName="Headline__c" NavigateURL="~/News.aspx={oid}" runat="Server" /><br/>
</ItemTemplate>
</dlog:repeater>

Example Output: (example links only)
ACME Corp Announces Q1 Financials
Jane Smith Joins ACME as VP of Operations
ABC Sees Record Growth After Using ACME Solution
ACME Announces 2008 Product Roadmap
Wall Street Journal: Inside Look at ACME

This example uses a Repeater control and SOQL Plus to query Salesforce and format the repeating layout of each item in the query result. Dialogue Script supports Salesforce Object Query Language (SOQL) plus adds support for tokens like "TOP", "ORDER BY", and "IN".

You can query any object in Salesforce. Master Views and Lists are a great way to provide customers with high level information and get them started in a general direction. Adding an ORDER BY CreatedDate DESC clause ensures the web page always stays up to date and displays the latest press releases, meaning you never need to update your web site when a new press release is launched. Query results can be cached to improve performance by adding a CachedDurationMinutes attribute to the Repeater.

In the next article, I'll demonstrate how to use Dialogue Script to format the actual Press release page using Salesforce data, plus some bonus script on creating a dynamic Google AdWords landing page.

Happy scripting!!!

From Entrepreneur.com "The Hottest Marketing Trends for 2008".

1. Engage the customer. The move toward alternative advertising versus some of the more traditional methods coincides with the emergence of technologies that enable a one-on-one dialogue with customers. For example, follow the trend of social media by posting your products on sites that encourage customer or peer reviews. Social media add an element of impartiality and are increasingly looked to as reliable sources of information.

Read the entire article online.

On-Demand software has revolutionized how enterprise software is deployed. Declarative customization provides line of business managers with an unprecedented number of options from which to "declare" how a CRM record is defined or presented in a page layout. But let's face it... at some point, all enterprise software solutions require some level of programmatic customization. Enterprise software vendors simply cannot anticipate each and every business requirement.

Salesforce customers, having reached the limits of declarative customization, now have domain specific programming languages such as Visual Force and Apex to programmatically customize their CRM system.

Content Management Systems (CMS) and Enterprise Portals already have a strong legacy of supporting programmatic customization, but achieved this flexibility through integration with existing development environments and the modification of physical files and templates.

Many CMS's have attempted to offer purely browser-based declarative customization environments, such as Wiki's and Blogs, but failed to meet the demands of creative and marketing professionals, which require detailed control over the presentation and branding of web pages and emails.

It's time for a new scripting language that meets the unique demands of Customer Experience Management (CEM). It's time to offer an optimal balance between declarative and programmatic configuration options. It's time to recognize that there is a new generation of workers entering the workforce that embrace Domain Specific Languages (see Fowler: DSL) and expect programming the web to be as easy as programming their iPod, Tivo, or DVR. It's time for a language like "Dialogue".

"Dialogue" is a new scripting language designed specifically for helping organizations to interact with their customers and partners online using concepts familiar to both the web (HTML, CSS, Javascript) and CRM (Lead, Contact, Opportunity, Case records).

The key tenants of Dialogue include:

Creativity / User Interface: Dialogue is primarily a presentation language that resembles HTML and is used in the creation of dynamic web pages, landing pages, and emails. Graphic designers and web developers have control over each pixel in the presentation of Dialogue scripts.

Business User Support: Business users can easily modify Dialogue scripts to present information most relevant to customers and partners. Changes can be made to Dialogue scripts without the assistance of a web programmer.

Multiple Development Environment Support: Dialogue scripts can be managed using either a web browser or rich client. Todays content management professionals are accustomed to working with tools such as Dreamweaver and Expression. Dialogue plug-Ins for web development environments (starting with Expression) will be developed to enable the remote persistence and management of Dialogue scripts using a locally installed rich client. But the flexibility of storing and managing content entirely on the web will remain the primary focus.

CRM-Driven: Dialogue scripts provide direct access to CRM records and data for maximum personalization.

Agile: Dialogue scripts support an agile methodology that allows organizations to go from concept to deployment within a matter of hours or days. Campaigns can be modified on the fly and no longer suffer from the constraints of "waterfall" project management methodologies where considerable upfront planning is required to reduce the anticipated cost of change.

The Dialogue scripting language will help organizations transition from static, brochureware web designs common in the 90's, to highly interactive and personalized online experiences. It is our goal that all Salesforce customers will unlock the capabilities of their CRM system to delivering these rich online experiences. Dialogue is the final link in enabling this level of interaction.

Yet another great customer experience (CE) faux pas from WorseThanFailure.com. Doubtful many customers would be patient enough to wait until the year 3000 (below) to receive their discount

I can empathize with the Developers of this site. We learned the hard to always check Salesforce managed date/times when using them in CE applications and campaigns after discovering that the absence of a date actually resulted in displaying a default date (something like January 1, 1900).

Steve Andersen has developed a really interesting metric in Salesforce based on actions taken by Activists/Donors in response to nonprofit campaigns. His solution exercises some new features in Winter '08, such as hierarchical campaigns and Apex scripts.

Anyone following my "tweets" on Twitter during the Salesforce.com Dreamforce '07 conference probably saw my references to lead scoring. The presentations and discussions inspired me to revisit this topic and explore how to implement lead scoring in Salesforce using an existing i-Dialogue web event data mart.

My past experiences with lead scoring were based on assigning "A", "B", "C", or "D" scores to leads derived from their online interactions. This prioritization gave sales reps some insight into which leads were supposedly more qualified than others.

A much simpler approach to lead scoring is to simply assign a score to each interaction and let the cumulative score provide a relative indicator. For example, in the illustration below, 2 leads enter a web site and initially appear to be equally qualified. But over time, and with enough data collection, we see that one lead was actually more interested in seeking employment with the organization rather than becoming a customer.

Defining lead score rules in Salesforce is possible through the use of a "Web Event Scoring Rule" custom object (see below), which is a prototypical definition of an existing Web Event object (already included with i-Dialogue).

A periodic evaluation by the i-Dialogue-to-Salesforce integration process evaluates each interaction and checks to see if it matches a lead score rule prototype. A match results in a Lead's score being increased or decreased by a defined amount. Rule prototypes may have any number of evaluation parameters, allowing for simple or complex rule definitions. If it can be captured in i-Dialogue, it can be evaluated.

A custom field on the Lead record named "Lead Score" is updated by the scoring process. Scores in Salesforce are updated in near real-time and are accurate to within 30 minutes.

This score then becomes the basis for Salesforce Reports and Dashboards. Once the technology is in place, an iterative/incremental relationship marketing process is implemented to routinely review and adjust scores and online event collectors. Lead scores will never be perfect, but the balance of online interactions and evaluation rules can achieve an 80% "good enough" state to be widely trusted by Sales Representatives and Marketing Managers.

Our company page seems perpetually outdated as we continue to grow and add new members to our team. Enough procrastinating... I've posted the updates and look forward to making many more.

The set of capabilities and services we can offer to clients have increased considerably in recent months. i-Dialogue web sites integrated with Salesforce are now sporting Flash interfaces, PDF printing, eCommerce support, localized translations, SMS alerts, finance calculators, sophisticated search engines... the list goes on, which only points to another area of procrastination... customer case studies.

Do you want a career in the Internet-based delivery of on-demand software?

Is your definition of "team building" playing WoW with Guild members? (Horde preferred. Alliance players accepted )

Do you enjoy the challenge of working with a diverse set of web development technologies, such as Flash, ASP.NET, C#, JavaScript, CSS?

Would you like to use next-generation technologies, such as Silverlight, AIR, VisualForce, and Apex?

Do you have an appreciation for test-driven design and development?

Then send your cover letter and resume to jobs@i-dialogue.com. We'd love to talk with you!

Our portal and eMarketing Developers spend a considerable amount of time translating customer requirements into working features, which requires the use of highly abstract tools, languages, and technologies. To this end, we've standardized on the use of Microsoft tools and services, commonly referred to as ".NET".

We were fortunate enough to spend the afternoon with Scott Hanselman, Development Community Liaison for Microsoft. Scott is fairly well known in the .NET development community. In fact, if you've ever Googled any search term remotely related to .NET, chances are you've most likely come across his blog or PodCasts (prompting some to wonder if he ever sleeps ).

I was really impressed with what Scott presented. Not only with the wealth of new features and services in .NET 3.0 and 3.5, but the myriad 3rd party and open source tools available that can be uniquely combined to create an extremely powerful, test-driven development environment.

The development tools space has become very stable and commoditized. Much like the component-based Eclipse development environment used by Salesforce.com, Visual Studio.NET is so extensible and customizable that the only limits are the Developers imagination. Scott maintains a great list of indispensable tools and utilities.

The highlight of the session? Probably LOL CODE. An actual programming language based on the LOL CATS concept. Who knows... maybe next generation CRM applications will be programmed in languages that look like this?

News is out that Microsoft is investing $240 Million in Facebook for 1.6% in equity, putting a $15B valuation on Facebook. What?! You read correctly. A 1.6% stake for $240M.

Hard to justify by any means, but it reminds me of when the Yankees signed Alex Rodriguez to a 10 year $252M contract. I was among the many Seattle Mariners fans who paid top dollar to see this new Yankee's star play, which in itself probably justified the valuation because the Yankees were selling out just about every game in every town.

A self-fulfilling prophecy perhaps? I would expect Facebook's 50M user community to easily double within the next year as people tune in to see what the commotion is all about.

Hey... if a survey has only 3-5 questions and can be taken quickly, I'm more than happy to provide feedback. These surveys, however, may make customers think twice.

I started reading Edward Tufte's 'Beautiful Evidence' (BE) over the weekend. This is the 4th book in a series (he says a quintet is to be expected) dedicated to the craft of information design.

Tufte's books have withstood the test of time with a high level of integrity. His work quite simply reveals "The Truth" of information design as he identifies great works from centuries past (and modern era) that have fought to change mankinds beliefs through the power of the pen and paper on thinking such as "the world is flat" and "the earth is the center of the galaxy".

I personally borrow heavily from Tufte's "let no pixel go to waste" philosophy. There's is most definitely an art to depicting thousands of data points within a single image.

My only complaints with this book are:
a) material from previous books is recycled, such as Joseph Minyard's March of 1812 (to Tufte's credit, he does spend considerably more time on this piece than in previous books)
and
b) the chapter dedicated to PowerPoint bashing takes away from the overall integrity of his work. It would have sufficed to say that PowerPoint templates and charts are the cause for much misinformation, and many people would tend to agree. But just about everyone uses PowerPoint occasionally, so this chapter does little more than to alienate everyone to a degree and denies PowerPoint it's key utility of being a framework for discussion rather than an actual informational artifact.

Those who work with massive datasets in Salesforce.com understand the "If we only knew what know" feeling. But it is the work of Tufte that helps us focus on mining these databases and unearthing hidden information through heat maps, graphs, and other types of multi-variate charts.

A few years ago, when this book was in pre-publication, I wrote a simple sparkline program based on Tufte's latest research, but alas it was abandoned as a solution looking for a problem. I'm inspired to start using VisualForce to implement some of these concepts again.

I recommend catching Edward on one of his many book tours. All of his books are typically included in the registration fee and he explains the concepts in a very entertaining manner. This is a must attend event for anyone in Graphic Design or BI Visualization.

I sometimes wonder if we've forgotten the original purpose for CAPTCHA images, which is to prevent the repeated, automated submission of web forms by non-humans.

This CAPTCHA engine (original here) has apparently become a little lazy. It simply displays the challenge code un-obfuscated and calls the end user a "twit". Wussup with that?!

On the heels of my previous post, I forgot to mention the English/Spanish localization by i-Dialogue customer www.ArcoProperties.com. Perusing their site really makes me want to spend a couple weeks down in Panama

i-Dialogue customer iGrafx recently localized their interactive online resource center with German content.

Salesforce.com CRM is easily configured to capture customers language preference. Just add a custom field to Lead and Contact named something like "Preferred Language" and map the field to i-Dialogue's "Language" field.

Whenever a customer clicks on the language bar at the top of an i-Dialogue page, or submits a localized web form, the customer's language selection is automatically updated in Salesforce.

iGrafx has also localized their email auto-responders to German for a truly relevant and localized dialogue. Future plans are in the works for Italian and Spanish sites too.

Want to do your part and contribute to a greener Internet? Use www.BlackGoogle.com instead of regular www.Google.com to reduce the watts used by your display.

Who knew?

Actually, this topic brings up an interesting point. When designing landing/web pages or emails, do you prefer white backgrounds? Blue? Black? Other colors?

Some research shows that a variety of background colors may be used, as long as there is high contrast.